Open skyazid opened 3 weeks ago
Hi, The group association shouldn't have changed and it should remain associated to ND-ProcedurePlacePerformanceAdditionalInformation,. We will fix this in a next release KR
Hi @YvesJo,
Thank you for the clarification regarding the BT-728-Procedure.
However, I would also like some clarification on the BT-127-notice. As mentioned above, adding the nodeId "ND-ProcedureProcurementScope" to "GR-Procedure-Description" prevents the XML from being generated correctly. If I remove this nodeId (as was the case in SDK version 1.11), the XML generation works correctly. Could you clarify whether this is a bug as well?
Additionally, could you provide an estimated release date for the fix? Will it be addressed in a 1.12.1 update?
Thanks again for your help.
Hello, BT-127-Notice will be assigned to a separate display group within the procedure section for the affected subtypes in a future release.
Hello,
Since the update to version 1.12, I have been experiencing difficulties with the XML transformation of the BT-127-notice and BT-728-Procedure fields.
Context
After analyzing this commit: https://github.com/OP-TED/eForms-SDK/commit/315a03acaeecc5eb3b064f997cfbeed6bee410db, I noticed two changes that seem to prevent the correct generation of XML files.
Identified Issues
BT-127-notice:
A nodeId "ND-ProcedureProcurementScope" was added to the "GR-Procedure-Description" level. If I remove this nodeId (as in SDK version 1.11), the XML generation works correctly.
BT-728-Procedure:
"GR-Procedure-PlaceOfPerformance" underwent a nodeId change. Previously, it was "ND-ProcedurePlacePerformanceAdditionalInformation," but now it has been replaced by "ND-ProcedurePlacePerformance." This change seems inconsistent to me because, according to the fields.json file, BT-728-Procedure has a parentNodeID = "ND-ProcedurePlacePerformanceAdditionalInformation."
I have noticed these inconsistencies across all subTypes:
Code Used
I am using the XML generation code from the following branch: https://github.com/OP-TED/eforms-notice-editor/tree/feature/TEDEFO-2456-use-of-fields-attribute-information
Could you please clarify these changes and explain how to ensure the correct XML generation for these fields?
Thank you in advance for your help.
@rouschr @bertrand-lorentz