Fields that appears optional in TED preview and looks like to be mandatory in SDK 1.13

[douret]

Dear,

I have identified several fields that are optional in ted preview and looks to be mandatory in SDK definition. As sample, let's take notice subtype 16.

BT-01(f)-Procedure:
In TED this field is optional:

If I have a look in SDK definition (fields.json):

{
"id" : "BT-01(f)-Procedure",
"parentNodeId" : "ND-LocalLegalBasisNoID",
"name" : "Procedure Legal Basis (NoID Description)",
"btId" : "BT-01",
"xpathAbsolute" : "/*/cac:TenderingTerms/cac:ProcurementLegislationDocumentReference[cbc:ID/text()='LocalLegalBasis']/cbc:DocumentDescription",
"xpathRelative" : "cbc:DocumentDescription",
"xsdSequenceOrder" : [ { "cbc:DocumentDescription" : 15 } ],
"type" : "text-multilingual",
"attributes" : [ "BT-01(f)-Procedure-Language" ],
"businessEntityId" : "procedure",
"legalType" : "CODE",
"maxLength" : 400,
"repeatable" : {
"value" : false,
"severity" : "ERROR"
},
"forbidden" : {
"value" : false,
"severity" : "ERROR",
"constraints" : [ {
"noticeTypes" : [ "X01", "X02" ],
"value" : true,
"severity" : "ERROR"
}, {
"noticeTypes" : [ "1", "2", "3", "4", "5", "6", "7", "8", "9", "10", "11", "12", "13", "14", "15", "16", "17", "18", "19", "20", "21", "22", "23", "24", "25", "26", "27", "28", "29", "30", "31", "32", "33", "34", "35", "36", "37", "38", "39", "40", "CEI", "E1", "E2", "E3", "E4", "E5", "E6", "T01", "T02" ],
"condition" : "{ND-LocalLegalBasisNoID} ${BT-01(e)-Procedure is not present}",
"value" : true,
"severity" : "ERROR"
} ]
},
"mandatory" : {
"value" : false,
"severity" : "ERROR",
"constraints" : [ {
"noticeTypes" : [ "1", "2", "3", "4", "5", "6", "7", "8", "9", "10", "11", "12", "13", "14", "15", "16", "17", "18", "19", "20", "21", "22", "23", "24", "25", "26", "27", "28", "29", "30", "31", "32", "33", "34", "35", "36", "37", "38", "39", "40", "CEI", "E1", "E2", "E3", "E4", "E5", "E6", "T01", "T02" ],
"value" : true,
"severity" : "ERROR"
} ]
}
}

So, if my understanding is correct this fields should be mandatory

BT-09(b)-Procedure:
In TED this field is optional:

If I have a look in SDK definition (fields.json):

{
"id" : "BT-09(b)-Procedure",
"parentNodeId" : "ND-CrossBorderLaw",
"name" : "Cross Border Law Description",
"btId" : "BT-09",
"xpathAbsolute" : "/*/cac:TenderingTerms/cac:ProcurementLegislationDocumentReference[cbc:ID/text()='CrossBorderLaw']/cbc:DocumentDescription",
"xpathRelative" : "cbc:DocumentDescription",
"xsdSequenceOrder" : [ { "cbc:DocumentDescription" : 15 } ],
"type" : "text-multilingual",
"attributes" : [ "BT-09(b)-Procedure-Language" ],
"businessEntityId" : "procedure",
"legalType" : "TEXT",
"maxLength" : 1000,
"privacy" : {
"code" : "cro-bor-law",
"unpublishedFieldId" : "BT-195(BT-09)-Procedure",
"reasonCodeFieldId" : "BT-197(BT-09)-Procedure",
"reasonDescriptionFieldId" : "BT-196(BT-09)-Procedure",
"publicationDateFieldId" : "BT-198(BT-09)-Procedure"
},
"repeatable" : {
"value" : false,
"severity" : "ERROR"
},
"forbidden" : {
"value" : false,
"severity" : "ERROR",
"constraints" : [ {
"noticeTypes" : [ "1", "2", "3", "4", "5", "6", "15", "38", "39", "40", "E1", "E2", "E6", "T01", "T02", "X01", "X02" ],
"value" : true,
"severity" : "ERROR"
}, {
"noticeTypes" : [ "7", "8", "9", "10", "11", "12", "13", "14", "16", "17", "18", "19", "20", "21", "22", "23", "24", "25", "26", "27", "28", "29", "30", "31", "32", "33", "34", "35", "36", "37", "CEI", "E3", "E4", "E5" ],
"condition" : "{ND-CrossBorderLaw} ${BT-09(a)-Procedure is not present}",
"value" : true,
"severity" : "ERROR"
} ]
},
"mandatory" : {
"value" : false,
"severity" : "ERROR",
"constraints" : [ {
"noticeTypes" : [ "7", "8", "9", "10", "11", "12", "13", "14", "16", "17", "18", "19", "20", "21", "22", "23", "24", "25", "26", "27", "28", "29", "30", "31", "32", "33", "34", "35", "36", "37", "CEI", "E3", "E4", "E5" ],
"value" : true,
"severity" : "ERROR"
} ]
}
}

So, if my understanding is correct this fields should be mandatory

Following your documentation this 2 fields appears to be mandatory:

Could you please advise?

Regards

[rouschr]

@pdonohoe maybe for you?

[pdonohoe]

Dear @douret ,

The "forbidden" rules are always applied before the "mandatory" rules. Both these fields also have forbidden rules. For BT-01(f)-Procedure, it is forbidden if BT-01(e)-Procedure (within the same parent node) is missing. For BT-09(b)-Procedure, it is forbidden if BT-09(a)-Procedure (within the same parent node) is missing. Taken in combination, the forbidden and mandatory rules mean that:

Within the same parent node, BT-01(f)-Procedure is mandatory if BT-01(f)-Procedure exists, otherwise it is forbidden.
Within the same parent node, BT-09(b)-Procedure is mandatory if BT-09(a)-Procedure exists, otherwise it is forbidden.

These forbidden rules are shown in the documentation page https://docs.ted.europa.eu/eforms/latest/reference/business-rules/notice-subtype-16.html , but in the table above the mandatory rules. We realise that separating the rules in this way may be confusing, and we are considering how to improve this page.

[douret]

@pdonohoe , thank you for your answer.

As you said:

The "forbidden" rules are always applied before the "mandatory" rules. Both these fields also have forbidden rules. For BT-01(f)-Procedure, it is forbidden if BT-01(e)-Procedure (within the same parent node) is missing. For BT-09(b)-Procedure, it is forbidden if BT-09(a)-Procedure (within the same parent node) is missing.

This is exactly what we do.

My question was about fields that are in ted preview and looks to be mandatory in SDK definition. Could you please advise about that?

Within the same parent node, BT-01(f)-Procedure is mandatory if BT-01(f)-Procedure exists, otherwise it is forbidden.
I don't understand your saying. Could you please explain? What do you mean by "if BT-01(f)-Procedure exists"?

Is there a way to organize a phone call with you and @xavierdila on that subject?

Regards.

[xavierdila]

Subject linked to #943
@pdonohoe

Clarifications would be appreciated.
Thanks

[pdonohoe]

Many apologies, I made a typo, that made my last message confusing. I should have written:

Within the same parent node, BT-01(f)-Procedure is mandatory if BT-01(e)-Procedure exists, otherwise it is forbidden.

So within a single instance of <cac:ProcurementLegislationDocumentReference>, BT-01(e)-Procedure is exactly:
<cbc:ID>LocalLegalBasis</cbc:ID>

If this exists, then BT-01(f)-Procedure is mandatory - <cbc:DocumentDescription> containing the description of the local laws.

The element <cbc:DocumentDescription> within the container <cac:ProcurementLegislationDocumentReference> is used for three different expressions of legal basis, depending on the content of the <cbc:ID> element:

• <cbc:ID>CrossBorderLaw</cbc:ID> - This is BT-09(a)-Procedure. If it is present then <cbc:DocumentDescription> is BT-09(b)-Procedure and is mandatory
• <cbc:ID>LocalLegalBasis</cbc:ID> - This is BT-01(e)-Procedure. If it is present then <cbc:DocumentDescription> is BT-01(f)-Procedure and is mandatory
• <cbc:ID> contains anything else - This is BT-01(c)-Procedure. If it is present then <cbc:DocumentDescription> is BT-01(d)-Procedure and is mandatory

I hope this clarifies the issue. Please ask if anything is still unclear.