BT-136-procedure - mandatory rules are not invited during validation

[tompeeszter]

We have noticed that some mandatory rules according to field BT-136-Procedure aren't invited during schematron validation of specific notices.
The following notices are concerned: eForm 25, 26, 27, 28, 29, 30, 31.
(validation-stage-4-25.sch)
For example:
<assert id="BR-BT-00136-0032" role="ERROR" diagnostics="BT-136-Procedure" test="count(cbc:ProcessReasonCode) &gt; 0 or not(../cbc:ProcedureCode/normalize-space(text()) = 'neg-wo-call')">rule|text|BR-BT-00136-0032</assert>

On the other hand the mandatory rules for filed BT-135-Notice are invited, for example:
(validation-stage-4-25.sch)
<assert id="BR-BT-00135-0032" role="ERROR" diagnostics="ND-ProcedureTenderingProcess_BT-135-Procedure" test="count(cac:ProcessJustification[cbc:ProcessReasonCode/@listName='direct-award-justification']/cbc:ProcessReason) &gt; 0 or not(cbc:ProcedureCode/normalize-space(text()) = 'neg-wo-call')">rule|text|BR-BT-00135-0032</assert>
The rule will still return an error if the field BT-135-Notice is filled in (BT-136-Notice still does not exist).

Maybe there is a problem with the contexts for rules on BT-136-Procedure?
We use SDK 1.13.0.

Could you please investigate the issue?
Thanks in advance!

[YvesJo]

Hi,
There was indeed a context issue for the rules on BT-136-Procedure and the context has been updated (i.e. changed from "ND-DirectAward" to "ND-ProcedureTenderingProcess") for SDK 1.14.
KR

[tompeeszter]

Thanks a lot!