> For the complete documentation index, see [llms.txt](https://docs.work-relay.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.work-relay.com/processes/process-settings/progress-component-settings.md).
# Progress component settings
In the process builder, click "Open Process Settings" in the "Actions" menu to open the "Edit Process Settings" window.
Open the "Progress Component Settings" tab.
### Component type
The Progress Bar component can be set to the following types:
* **Standard** - Displays branches separately with an option to switch between them:
* **Summarized** (Default) - Displays steps from all branches in the process in one line, allowing the user to switch between the steps. Completed steps are shown first, then active, and then future:
{% hint style="info" %}
For Processes that can have more than one Step in progress at any given time, the Step currently selected to view or interact with is outlined.
{% endhint %}
* **Sequential** - Displays steps from all branches in the Process in one line, in the order [defined in the steps grid](/processes/building-a-process/steps-order.md) in the Process Designer.
### Enable actual dates
Allows the user to define the Start Date and End Date when proceeding the Step.
### Enable comments
Allows the user to add a Comment when proceeding the Step. The Comment will be visible in the Process Instance History.
### Keep history on restart
When turned on, the History of step status changes will be retained and available after a Process Instance is restarted.
### Keep timelogs on restart
Turn this on to make process instance have already added [timelogs](/functional/dashboards/time-logs-dashboard/time-logs-dashboard-overview.md) stored for time calculation needs. Uncheck it if you have no need in timelogs [reported](/functional/dashboards/time-logs-dashboard/reporting-time.md) for previous iterations.
This option works when "Change step" and "Restart branch" features are used too.
### Show Issues
If turned on, tasks and issues added for a step are displayed in the workflow line like other steps—active or completed. This can be useful for process managers or assignees and behaves like additional steps.
When this toggler is turned on, a picklist with options to filter displayed issues is available:
{% hint style="info" %}
These issues do not affect steps and process durations.
These issues shift [dates](/processes/working-with-processes/forecasted-dates-and-durations.md) of subsequent steps properly depending on their End dates.
This is correctly shown in Gantt if it has "Show Issues" turned on too. See the [proper article](/processes/process-settings/gantt-settings.md).
{% endhint %}
### Load connected instances
Defines whether progress bars of [sub-processes](/processes/working-with-processes/start-and-plan-the-process.md#triggered-by-another-flow) and [connected instances](/processes/process-steps/process-step-settings/connection-points.md) should be manually or automatically opened under the parent process progress bar.
### Default chatter feed
Defines a feed that will be shown by default in the "Feed" subtab on Instance details:
### Step filters
"Past Step Filters" and "Future Step Filters" define which Steps will be hidden in the progress bar. Move necessary filters to "Selected" sections to have them applied.
### Layout for completed process
This feature allows you to select a separate layout for the process to display when the whole instance is completed. This layout can only be a Form, and it is specified like a step layout of the proper type.
{% stepper %}
{% step %}
#### Open layout settings
Click the "Settings" button (gear icon) to display the Layout Settings popup.
{% endstep %}
{% step %}
#### Configure the form
Select a form, set form mode, and specify parameters if necessary. The ID of the record which instance has been started at will be passed to the form automatically.
{% endstep %}
{% step %}
#### Apply the settings
Click "Apply" to apply layout settings.
{% endstep %}
{% endstepper %}
### Standard Buttons Settings
The color of the Proceed, Approve, and Reject standard buttons may be overridden here by selecting the proper value in the picklist in the "Color" column.
Button behavior may be overridden by selecting a Before Handler in the proper column. The following Handler types are available:
* Form
* Action
* Action Group
{% hint style="info" %}
By default, the following parameters are passed to button handlers: Cursor ID, Flow Instance ID, Process ID.
{% endhint %}
Custom Parameters may also be defined and passed to the button handler:
### Custom Buttons
Custom buttons may be added to the Workflow Progress Component menu (arrow button at the right side, Process Instance Menu in [this article](/functional/process-progress-component/progress-component-overview.md#menus-and-buttons)). These buttons must have click handlers. Handlers can have the following **types**:
* **Form** - Opens a Work-Relay form, which can be for any Data Source Object. If selected, the Form Layout Mode must also be defined.
* **Action** - Executes a Global Action.
* **Action Group** - Executes a Global Action Group.
* **Visualforce Page** - Redirects to a Visualforce page.
* **Lightning Component** - Opens a Lightning Component.
* **URL** - Redirects to the specified URL.
By default, the following parameters are passed to custom button handlers: Process Instance Cursor ID, Process Instance ID, Object ID.
For "Form" handler types, both default and custom parameters can be accessed via the Form's $FormParameters context object, for example `{$FormParameters.myParameter1}`.
For "Action" and "Action Group" handlers, parameters can be accessed via the $Variables context object, for example `{$Variables.cursor}`.
Custom parameters are set in the proper popup. Click the "Settings" button (gear icon) to open it:
The "Access" picklist defines which users will be able to view the custom button.
The following options are available:
* "Managers" are Work-Relay Process Managers.
* "Admins" are Work-Relay Process Admins.
* "Assignee" is the cursor assignee.
The "Visibility" picklist contains different options for custom button visibility:
### Additional Access
In this table, access to perform additional actions can be provided to users, roles, or profiles, whether they are step assignees or not, by selecting them in the proper field. Access can be granted to Process Manager(s) and Instance Manager(s) separately with the appropriate checkboxes:
Entities for additional access can be selected together:
These settings are active by default for Process and Instance Managers:
* Create Issue/Task
* Create Work Logs
Click "Save" to apply changes or "Cancel" to discard them.
Releases prior to 8.7
Open the "Progress Component Settings" tab.
### Component Type
The Progress Bar component can be set to the following types:
* **Summarized** (Default) - Displays steps from all branches in the process in one line, allowing the user to switch between the steps. Completed steps are shown first, then active, and then future:
{% hint style="info" %}
For Processes that can have more than one Step in progress at any given time, the Step currently selected to view or interact with is outlined (2).
{% endhint %}
* **Standard** - Displays branches separately with an option to switch between them.
* **Sequential** - Displays steps from all branches in the Process in one line, in the order [defined in the steps grid](/processes/building-a-process/steps-order.md) in the Process Designer.
### Keep history on restart
When checked, the History of step status changes will be retained and available after a Process Instance is restarted.
### Keep timelogs on restart
Starting release 8.4, the "Keep Timelogs on Restart" feature is available. Select this checkbox to retain existing [timelogs](/functional/dashboards/time-logs-dashboard/time-logs-dashboard-overview.md) for time calculations. Clear it when previous-iteration [timelogs](/functional/dashboards/time-logs-dashboard/reporting-time.md) are not needed.
This option works when "Change step" and "Restart branch" features are used too.
### Show Issues
Starting release 8.4, the "Show Issues" checkbox is available. If checked, tasks and issues added for a step are displayed in the workflow line like other steps—in progress or completed. This can be useful for process managers or assignees and behaves like additional steps.
When this checkbox is shown, a picklist with options to filter displayed issues is available:
{% hint style="info" %}
These issues do not affect steps and process durations.
These issues shift [dates](/processes/working-with-processes/forecasted-dates-and-durations.md) of subsequent steps properly depending on their End dates.
This is correctly shown in Gantt if it has "Show Issues" turned on too. See the [proper article](/processes/process-settings/gantt-settings.md).
{% endhint %}
### Load connected instances
Defines whether progress bars of [sub-processes](/processes/working-with-processes/start-and-plan-the-process.md#triggered-by-another-flow) and [connected instances](/processes/process-steps/process-step-settings/connection-points.md) should be manually or automatically opened under the parent process progress bar.
### Step filters
"Past Step Filters" and "Future Step Filters" define which Steps will be hidden in the progress bar.
### Enable actual dates
Allows the user to define the Start Date and End Date when proceeding the Step.
### Enable comments
Allows the user to add a Comment when proceeding the Step. The Comment will be visible in the Process Instance History.
### Standard buttons settings
The color of the Proceed, Approve, and Reject standard buttons may be overridden here by selecting the proper value in the picklist in the "Color" column.
Button behavior may be overridden by selecting a Before Handler in the proper column. The following Handler types are available:
* Form
* Action
* Action Group
Also, you can pass custom parameters too. Click the ">>" button to see the parameters list.
{% hint style="info" %}
By default, the following parameters are passed to custom button handlers: Cursor ID, Flow Instance ID, Process ID.
{% endhint %}
Custom Parameters may be defined and passed to the button handler.
Click the ">>" button to open the formula builder:
### Custom Buttons
Custom buttons may be added to the Workflow Progress Component menu (arrow button at the right side, Process Instance Menu in [this article](/functional/process-progress-component/progress-component-overview.md#menus-and-buttons)). These buttons must have click handlers. Handlers can have the following types:
* **Form** - Opens a Work-Relay form (the form can be for any Data Source Object). If selected, the Form Layout Mode must also be defined.
* **Action** - Executes a Global Action.
* **Action Group** - Executes a Global Action Group.
* **Visualfoce Page** - Redirects to a Visualforce page.
* **Lightning Component** - Opens a Lightning Component.
* **URL** - Redirects to the specified URL.
By default, the following Parameters are passed to custom button handlers: Process Instance Cursor ID, Process Instance ID, Object ID.
For "Form" handler types, both default and custom parameters can be accessed via the Form's $FormParameters context object, for example `{$FormParameters.myParameter1}`.
For "Action" and "Action Group" handlers, the parameters can be accessed via the $Variables context object, for example `{$Variables.cursor}`.
The "Access" picklist defines which users will be able to view the custom button. The following options are available. "Managers" are Work-Relay Process Managers. "Admins" are Work-Relay Process Admins. "Assignee" is the cursor assignee.
The "Visibility" picklist contains different options for custom button visibility:
### Additional access
In this table, access to perform additional actions can be provided to users, roles, or profiles, whether they are step assignees or not, by entering the Salesforce Record IDs for the desired entity. Access can be granted to Process Manager(s) and Instance Manager(s) separately with the appropriate checkboxes:
{% hint style="warning" %}
Multiple IDs should be separated with a comma.
{% endhint %}
Starting release 8.2, the following Additional Access settings are available:
* Create Issue/Task
* Create Work Logs
These settings are active by default for Process and Instance Managers.
Click "Save" to apply changes or "Cancel" to discard them.