OP-TED / eForms-SDK

eForms is the notification standard for public procurement procedures in the EU. The eForms SDK is a collection of resources providing the foundation for building eForms applications.
Creative Commons Attribution 4.0 International
59 stars 30 forks source link

BT-01(c)-Procedure should be mandatory if BT-01(d)-Procedure was filled #996

Closed magdalenasPwC closed 2 months ago

magdalenasPwC commented 3 months ago

We encountered an issue while sending notice type 16. Field BT-01(d)-Procedure was filled, BT-01(c)-Procedure left empty. Field validation did not show any mistakes. Error occurred in publication response that xml is not correct. The Xml lacked ID which comes from BT-01(c)-Procedure field. Therefore BT-01(c)-Procedure field should be mandatory if BT-01(d)-Procedure was filled

YvesJo commented 3 months ago

Hi, There are various cases that use the same aggregate element "cac:ProcurementLegislationDocumentReference" and the basic element "cbc:ID" is carrying the semantic that allows to differentiate the case. In absence of cbc:ID information, it is impossible to know whether the description is about "Cross Border Law", "Other Legislation with ID", or "Other Legislation without ID". Therefore having only "cbc:DocumentDescription" is not sufficient to identify what is actually missing (BT-09(a)-Procedure, BT-01(e)-Procedure or BT-01(c)-Procedure). This has to be addressed on the UI side to ensure the correct cbc:ID will be specified and prevent the XSD non-conformance.