We have implemented guardrails by saving the OOTB place holder CheckForCustomWarnings as mentioned here. Now we also use Customer service which also implements CheckForCustomWarnings so our guardrail is not called.
How can we achieve that the correct rule is called?
Application structure:
Custom application build on the following:
CS containing CS guardrail CheckForCustomWarnings, available
Enterprise layer Containing custom guardrail CheckForCustomWarnings, final
Seems like in CS , final rule czCheckForCSRuleOverride being called from CheckForCustomWarnings from several classes (rule-html-section, rule-obj-model) so there is no single rule which gets called at the end.
cyEnableCustomGuardrailCheck , this is a DSS which is present on every when condition in the CheckForCustomWarnings rule .
But now it is not taken the CheckForCustomWarnings which contains the custom warnings for our organization. Is this a bug in CS or should we implement the custom guardrails in a different way for CS?