Users often assume that non-mandatory fields should never cause validation issues. However, in Fenergo Journeys, the validation engine evaluates all scoped fields, not just the mandatory ones, whenever Conditional Validation Rules or Dependent Rules are active. This means a field marked as “optional” can still participate in validation logic and generate warnings or blocking errors if it forms part of a conditional expression or dependency chain.
Solved
Why do non-mandatory fields sometimes trigger validation warnings or errors in my Journey, even though they’re not required fields?
Best answer by jawadkhan
Fenergo’s validation engine runs on all scoped fields, not just mandatory ones, when Conditional Validation or Dependent Rules are active. A field marked “non-mandatory” can still generate warnings or errors if it’s included in a validation condition.
To fix or tune validation behaviour:
- Review the Field Validation Rule Set in Policy Configuration.
- Ensure conditional logic (e.g., “Run only if Field X is populated”) is correctly set.
- If a rule should produce a non-blocking warning, mark it as Non-Blocking in the task or workflow configuration.
- Confirm your environment’s workflow configuration does not treat warnings as errors.
Tip
You can inspect warnings in the Validation Summary for the Journey task. If progression is blocked, check whether the workflow step definition interprets “warnings” as “blocking” errors.
Fenergo’s validation engine runs on all scoped fields, not just mandatory ones, when Conditional Validation or Dependent Rules are active. A field marked “non-mandatory” can still generate warnings or errors if it’s included in a validation condition.
To fix or tune validation behaviour:
- Review the Field Validation Rule Set in Policy Configuration.
- Ensure conditional logic (e.g., “Run only if Field X is populated”) is correctly set.
- If a rule should produce a non-blocking warning, mark it as Non-Blocking in the task or workflow configuration.
- Confirm your environment’s workflow configuration does not treat warnings as errors.
Tip
You can inspect warnings in the Validation Summary for the Journey task. If progression is blocked, check whether the workflow step definition interprets “warnings” as “blocking” errors.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.