-
Hello there, according to the Best Regards |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 4 replies
-
Hi, |
Beta Was this translation helpful? Give feedback.
-
Hello there, according to the Best Regards |
Beta Was this translation helpful? Give feedback.
-
Hi, |
Beta Was this translation helpful? Give feedback.
Hi,
The context for the rules is the node ND-LotProcurementDocument which may contain BT-14-Lot, BT-15-Lot, BT-615-Lot, BT-707-Lot,
OPT-140-Lot.
BT-14-Lot is the "entry point" for the Procurement Documents, in its absence neither the listed fields, nor the parent node shall exist.
In absence of the parent, the rules wouldn't get fired.
Additionally, the existence of the parent node with the the absence of OPT-140-Lot would lead to a non XSD compliant XML instance, while OPT-140-Lot is only allowed when BT-14-Lot is defined.
The 42 condition on the conditionally mandatory rule for BT-615-Lot in Notice Subtype 7 is in fact useless.
Given these details, BT-14-Lot is Mandatory where Procureme…