Progress indictors show your flow stages to the running user. Before you start adding
stages to your flow, plan for all the possible stages that you want your running users to see in
a progress indicator.
Figure out all the stages that the running user can go through while running the flow,
accounting for all flow paths. Consider what stages you want to appear in the progress
indicator and when.
For example, if you have a Decision element in your flow and you want the user to go
through different stages depending on the decision outcomes, include all stages for every
decision outcome.
Determine the Order to Show the Stages
Standard progress indicators show the active flow stages in the order that you set them in on
each stage resource. If you have different stages depending on what path the user takes in
your flow, order the stages in the correct order, no matter what path the flow takes. The
order numbering can be nonsequential as long as it’s in ascending order as you go through
the flow. For example, one flow path can have this stage order: 1, 2, 3, 7. And the other
flow path can have this order: 1, 4, 5, 6, 7.
Identify Which Stages Are Active by Default
Standard progress
indicators and most custom progress indicators show all active flow stages.
If your
screen flow is simple with one path, set all your stages to Active by default and order the
stages in sequential order. For example, 1, 2, 3, 4, 5.
If your screen flow has
multiple paths, plan for when you want specific stages to be active and show up in the
progress indicator. Also, plan for when you want specific stages to be removed from the
progress indicator. If you don’t want a stage to show up in the progress indicator when the
flow starts, don’t set it to active by default.
For the next step in the stage and progress indicator set up process, see Create Flow Stages.
We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required Cookies
Always Active
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional Cookies
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising Cookies
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.
