Handling Visual model to generate Conceptual Model - why is lot group missing ? about eforms-sdk HOT 7 CLOSED

Hello,

your question looks a lot like this one from another person: #693
Please see the answer there as answering this here would almost end up in a duplicate answer.

from eforms-sdk.

Thanks for the answer.
My question is a bit more straight if I may.
Can you pls confirm the notice type 16.json and fields.json are 100% correct in SDK 1.8.0 and it's right the parent node for "BT-137-Lot" is the "ND-Lot" for a well formed concept model the SDK is looking for?

from eforms-sdk.

The fields.json of the SDK is the reference for the XML generation:

"id" : "BT-137-Lot",
"parentNodeId" : "ND-Lot",

If the notice type contradicts this in terms of ancestry then there is a problem somewhere in the notice type.
Some of these notice type problems may also depend on how the algorithm going from visual, conceptual and physical works (how tolerant the algorithm etc.).
In is not impossible that there could be a problem in the fields.json but this would be rare compared to problems in the notice types. The notice types have been improving gradually, often catching up with the updates done in the fields.json (new fields and nodes, REG NEXT, ...). The editor demo is that last thing to catch up as it needs most things provided by the SDK.

from eforms-sdk.

Is there any possible open-source code we could check in order to have a concrete ready-to-production example where understand the correct application of SDK principle? Would it be possible to inspect for instance enotices2 portal source code at https://enotices2.ted.europa.eu/home ?

from eforms-sdk.

The code of enotices2 will not be open sourced any time soon (as far as I understood).
I am looking into the editor demo between other tasks, I think it is not far from generating the desired XML. I managed to fix a problem in the mentioned branch, but it broke a unit test. More work is required there.
By the way SDK 1.9.0 was released.

from eforms-sdk.

Using SDK 1.9 and this branch of the editor demo: https://github.com/OP-TED/eforms-notice-editor/tree/feature/TEDEFO-2456-use-of-fields-attribute-information
With an empty form having 2 lots (LOT-0001 and LOT-0002) using notice sub type 16.
I obtain this XML:
16-physical.xml.txt
Now that SDK 1.9 was released, let me know what kind of XML you can generate using notice 16.

from eforms-sdk.

I worked on an old idea on how to improve the unit tests using xpath and found a problem which was not covered previously.
I fixed the problem in the branch and the new improved unit tests are passing now.
It is recommended you do a git pull to get the latest version of the branch and try again.

from eforms-sdk.