Support Article
Validation for screen flow tabs when user jumps using tab click
SA-2726
Summary
The Developers are trying to identify the preferred mechanism to perform validation on a Screen Flow.
Resolution
You cannot easily combine the validation so that it performs validation across all tabs at the end of a screenflow, plus add validation as you change tabs.
The reason for this is if you don't have “Allow Errors” set then this will prompt you to fill each tab with the required values before it lets you change to a different tab. This is normally fine for all tabs. However, if the last tab uses validation that will check the data behind all tabs then if something fails the validation, and the associated property isn't on the last tab, then you won't be able change tabs to correct it.
So, in short you can either choose: -
1. Don't “Allow errors”, perform validation per assignment, and allow users to select tabs at will.
However, please not that if a user doesn't select a tab then it will not perform validation on that tab.
2. Don't “Allow errors”, perform validation per assignment, force users to systematically go through the screens.
This will enforce validation, but you will lose the flexibility of the user being able to move through the screens (tabs) at will.
3. Select “Allow errors” and perform full validation at the end of the screenflow.
Again, this will enforce validation, but it will only do so at the end of the screenflow.
One other option, which may or may not be applicable to your design, would be to remove the screenflow.
That is, instead of displaying the sections on each assignment in the screenflow, build a master section and add your existing sections directly to it as Tabs.
Published January 31, 2016 - 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.