Overview
A policy field's Conditional Value does not trigger even though the configured conditions appear to be met. This typically occurs when the parent Requirement Set or Policy is out of scope at the time the condition is evaluated.
Why This Happens
In Fenergo SaaS, scoping is applied before Trigger Conditions and Conditional Values are evaluated. When a Requirement Set is out of scope, all fields within it are removed from evaluation. As a result:
Trigger Conditions defined on those fields will not fire.
Conditional Values configured for those fields will not apply.
This applies whether the set is out of scope due to entity type, product, or journey configuration.
Resolution
Identify the Requirement Set that contains the field with the non-triggering Conditional Value.
Check whether that Requirement Set is in scope for the current entity and journey context.
If the set is de-scoped, review the scoping rules and adjust them so the set is in scope when the Conditional Value is expected to fire.
If the field must remain out of scope, consider relocating the Conditional Value logic to a field in a set that is always in scope.
Key Rule
Scoping is always evaluated first. Conditional Values and Trigger Conditions on out-of-scope fields are ignored, regardless of whether the data conditions are met.