> For the complete documentation index, see [llms.txt](https://docs.avonnicomponents.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avonnicomponents.com/videos/all-videos/page-1/set-up-a-clickable-progress-indicator-with-router-salesforce-screen-flow-tutorial.md).

# Set Up a Clickable Progress Indicator with Router   Salesforce Screen Flow Tutorial

Screen Flows · 17:29

A multi-screen flow with a clickable progress indicator that lets users jump between steps.

{% embed url="<https://www.youtube.com/watch?v=7kQqx7lw-8c>" %}

## Chapters

* [0:00 INTRODUCTION](https://www.youtube.com/watch?v=7kQqx7lw-8c\&t=0)
* [1:17 CREATING THE VARIABLE TO DEFINE THE CURRENT STEP](https://www.youtube.com/watch?v=7kQqx7lw-8c\&t=77)
* [1:45 CREATING THE VARIABLE TO DEFINE THE PROGRESS INDICATOR TYPE](https://www.youtube.com/watch?v=7kQqx7lw-8c\&t=105)
* [2:45 CREATING THE PROGRESS INDICATOR STEP COLLECTION](https://www.youtube.com/watch?v=7kQqx7lw-8c\&t=165)
* [4:50 ADDING THE ROUTER DECISION](https://www.youtube.com/watch?v=7kQqx7lw-8c\&t=290)
* [6:25 ADDING THE SCREEN 1](https://www.youtube.com/watch?v=7kQqx7lw-8c\&t=385)
* [10:42 ADDING THE SCREEN 2](https://www.youtube.com/watch?v=7kQqx7lw-8c\&t=642)
* [12:23 ADDING THE SCREEN 3](https://www.youtube.com/watch?v=7kQqx7lw-8c\&t=743)
* [14:10 CONNECT THE SCREENS TO THE ROUTER](https://www.youtube.com/watch?v=7kQqx7lw-8c\&t=850)
* [14:40 SETTING UP THE NEXT SCREEN FLOW INTERACTION](https://www.youtube.com/watch?v=7kQqx7lw-8c\&t=880)
* [15:35 FINAL RESULT](https://www.youtube.com/watch?v=7kQqx7lw-8c\&t=935)
* [15:56 CHANGING THE PROGRESS TYPE VALUE ON THE VARIABLE](https://www.youtube.com/watch?v=7kQqx7lw-8c\&t=956)

## Related documentation

[Follow the documentation](https://docs.avonnicomponents.com/flow/flow-components/progress-indicator)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.avonnicomponents.com/videos/all-videos/page-1/set-up-a-clickable-progress-indicator-with-router-salesforce-screen-flow-tutorial.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.