Support Article
Validation condition fails with screen flow
SA-33928
Summary
Flow continues after validation fails in Screen-flow.
In a screen-flow having multiple assignments, validation error for date field fails in screenflow while navigating to next screen without satisfying validation condition.
A validation is configured to disable selection of future dates (OOTB Edit validate rule - NoFutureDate) in an assignment.
It was observed that when the "Next" button is clicked on the screen, validation gets triggered and error message displayed as expected.
Though, when the "Next" button is clicked again, validation gets ignored and user is able to navigate to second screen/assignment in the screen-flow.
Error Messages
Not Applicable
Steps to Reproduce
1. Create a screen-flow with multiple assignments.
2. In first assignment, add a date field.
3. Add "NoFutureDate" Edit validate rule in the flow action of the first assignment. It will be validate the date, such that no future date could be selected.
4. Run the use-case, observe that validation gets triggered on click of "Next" button in screen-flow first time.
But later it allows user to navigate to next screen without validating user inputs.
Root Cause
A defect in Pegasystems’ code or rules.
For drop-down lists of date, after finish assignment form unable to reset the hidden form value.
That's why if Pega do not update the value as the hidden value is empty and there is no validation for empty datetime, it is proceeding to the next screen.
Resolution
Apply HFix-32203.
Published March 15, 2017 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.