OPT-170-Tenderer is mandatory even if there is no tenderer

[GarrusMD]

The fields.json states that the OPT-170-Tenderer field is mandatory if there is not equal to 1 tenderer. This means that the field is even mandatory if there is no tenderer at all. Please change the rule so that the field only becomes mandatory if there are at least 2 tenderers.

[YvesJo]

The context for the rule is the parent node ND-Tenderer which only contains OPT-170-Tenderer and OPT-300-Tenderer.
Empty nodes aren't also allowed, therefore in absence of OPT-170-Tenderer and OPT-300-Tenderer, ND-Tenderer shouldn't be present in the XML and the CM rule won't get triggered (i.e. OPT-170-Tenderer is not mandatory).
May be what is meant is that the UI is not able to deal with the rules context properly and a solution would be to update the current condition so that the field won't appear as mandatory?

[GarrusMD]

Correct. The current rules lead to strange side effects when entering the data.

Because the OPT-300-Tenderer field only appears after several preconditions have been met, only the ‘OPT-170-Tenderer’ field is initially displayed (as a mandatory field). Even after the preconditions have been fulfilled and OPT-300-Tenderer is displayed, it is irritating for the person entering the data that OPT-170-Tenderer is displayed as a mandatory field until OPT-300-Tenderer has been filled in.

Is there any reason why OPT-170-Tenderer should not be displayed until there are at least two tenderers?

[YvesJo]

Indeed, business wise, the indicator used to specify that a tenderer is a group leader is useless until at least 2 organizations have been identified.
Develop a UI able to deal with the various rules and their context may be quite challenging and not have a great ROI and the proposed rule update is certainly the best option, therefore I will update this with the next SDK.
KR

[GarrusMD]

Thanks a lot!