> 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/flow/actions/ui-and-navigation/new-progress-indicator-step-collection.md).

# New Progress Indicator Step Collection

## Overview

The Progress Indicator Step Collection simplifies the management of steps within your Salesforce screen flows, particularly when using the Avonni Progress Indicator component. By defining a centralized collection of progress steps, you can streamline the configuration of multiple progress indicators, ensure consistency, and improve the maintainability of your flows.

## How it Helps

* **Centralized Step Management:** Define and manage a single source of truth for progress steps, eliminating redundant configuration across multiple components.
* **Enhanced Reusability:** Apply the same progress step structure to various screens or flows, saving development time and effort.
* **Consistent User Experience:** Maintain a uniform visual representation of progress across your application.
* **Simplified Maintenance:** Update steps in one location, and changes automatically propagate to all linked Avonni Progress Indicator components.

## How It Works

1. **Drag and Drop:** In Flow Builder, locate the Progress Indicator Step Collection in the Avonni Actions section and drag it onto your canvas (outside any specific screen element).
2. **Define Progress Steps:** Within the Action Collection's properties, configure the details for each step:
   * **Label:** The text displayed to represent the step in the progress indicator.
   * **Value:** A unique identifier for the step (used internally for logic and tracking).
   * **Content:** (Optional) Additional text or information to display below the step label.
   * **Icon Name:** (Optional) Select an icon from the available library to enhance the step visually.
   * **Sub Steps:** (Optional) Create nested steps representing sub-processes or finer granularity within a main step.
   * **Actions:** (Optional) Define actions to trigger when a step is completed or clicked (e.g., navigate to a specific screen).
3. **Link to Avonni Progress Indicator Components:** In your Avonni Progress Indicator components, reference the ID of the Progress Indicator Step Collection you've created. The component will automatically populate the progress steps based on your collection.

## Settings and Options

* **Label:** Descriptive text for the step.
* **Value:** Unique identifier.
* **Content:** Additional step information (optional).
* **Icon Name:** Visual representation (optional).
* **Sub Steps:** Hierarchical step organization.
* **Actions:** Triggerable actions associated with steps.

## Integration with Avonni Progress Indicator

This Action Collection is designed to work seamlessly with the Avonni Progress Indicator component. Once you've defined your step collection, reference it in multiple Progress Indicator components to maintain a unified representation of progress throughout your application.

## When to Use It

* **Onboarding Flows:** Guide users through steps during onboarding or setup processes.
* **Multi-Stage Forms:** Break down complex forms into smaller, more manageable steps.
* **Application Wizards:** Provide a clear visual representation of progress in multi-step wizards.
* **Status Tracking:** Display the progress of long-running processes or approvals.

## Key Considerations

* **Clear Step Descriptions:** Use concise and informative labels for each step.
* **Logical Ordering:** Ensure the order of steps in the collection aligns with the flow's progression.
* **Visual Clarity:** Leverage icons to enhance the visual appeal and intuitiveness of the 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.avonnicomponents.com/flow/actions/ui-and-navigation/new-progress-indicator-step-collection.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.