Published at: 2026-09-17
04-manage-stage-progressors.md
Manage Pipeline enablement, reuse, Priority, and display rules.
Overview
After a Pipeline is published, you need to maintain its enablement Status, Priority, Stage view visibility scope, approval method for Stage changes, and task Display Order. Clear management rules prevent multiple pipelines from matching at the same time and reduce ambiguity during Stage Advancement.
Key capabilities
Pipeline management supports centralized maintenance, enablement control, and global rule configuration for created pipelines. You can use the list page and Global configuration to manage matching Priority, visible scope, Approval method, permission checks, and display rules.
- Support centralized Pipeline search: Filter pipelines by Object and Status, or search by Name to quickly Location the Pipeline that needs maintenance.
- Support list-based key information: The list displays Pipeline Name, API Name, Description, Trigger Object, Object Field, Applicable Scope, Created By, Created On, and other information. This helps identify the Business Scenario and users.
- Support Enable, Disable, and Delete: After Enable, qualified business data can use the Pipeline. After Disable, new data cannot Trigger or initiate it. A Disabled Pipeline that is no longer used can be Deleted.
- Support Copy and New: Copy an existing Pipeline into a New configuration, and then adjust the Object Field, Applicable Scope, stages, tasks, or conditions. This helps reuse similar Stage management rules.
- Support configuration Export: Export Pipeline configuration for archiving, review, or offline confirmation.
- Support Priority by Object: In Priority, select an Object to view pipelines under that Object, and drag them to adjust matching order. The list also displays Trigger Object, Object Field, Applicable Scope, Created By, Created On, Last Modified By, Last Modified On, Status, and other information.
- Support Stage view settings: Control whether the Stage view shows Deleted pipelines, whether users can View All or only definitions in their Applicable Scope, and whether a Pipeline shows all stages.
- Support Approval Type for Stage changes: Select Stage change Approval or Edit Approval. This setting takes Effect for all Pipeline definitions and instances, and controls which Approval Type is triggered by Stage changes.
- Support External process settings: Control whether downstream-initiated processes can match only enabled External pipelines under the current External Apps, or all pipelines related to the Object.
- Support entry Notice settings: Configure whether to ignore the prompt that asks whether to enter the next Stage directly, so pop-ups do not interrupt users after task completion.
- Support Stage task display settings: Configure task Display Order, whether to show Task Handler and Processing Time, and whether In Progress but optional tasks show the Complete button.
- Support Edit permission validation on Stage changes: Configure whether the System checks data Edit permission during Stage changes. When enabled, users need Edit permission on the data to advance the Stage.
- Support unlink control for Stage task related data: Configure whether only CRM administrators can unlink related data in Stage tasks, which prevents ordinary users from incorrectly removing task and business data associations.
- Support Custom Plugin configuration: Configure Web and Mobile PWC plugins for the Pipeline plugin and Stage view plugin, or create a New plugin to extend page display and interactions.
- Support quota usage View: The page footer displays total quota and Used quota, so administrators can evaluate Available capacity before creating or copying a Pipeline.
Before you begin
- The Pipeline has been created.
- You have Pipeline management permission.
- You have Confirmed the matching Priority among multiple pipelines.
Manage basic operations
| Operation | Description |
|---|---|
| Edit | Edit the Pipeline configuration again |
| Enable | Only processes with Enable Status set to enabled can initiate Pipeline records |
| Disable | A Disabled Pipeline cannot be reinitiated |
| Reuse and New | Copy the current Pipeline configuration and create a New Pipeline |
| Delete | A Disabled Pipeline can be Deleted. Historical instances still Support query and View Details |
Configure Priority
When multiple pipelines meet Trigger conditions at the same time, the System matches them by Priority.
- Open advanced Pipeline management.
- Go to Priority settings.
- Adjust the order of pipelines under the same Object.
- Save the configuration.
If Object-level Priority has been set in global configuration, the System matches from top to bottom. If no Priority is specified, the System sorts by Last Modified On from earliest to latest, and triggers only one Pipeline.
Configure the Stage view scope
Stage view supports two visibility scopes:
| Scope | Description |
|---|---|
| View all definitions | Users can View all Pipeline definitions under the Object |
| View only definitions in Applicable Scope | Users View only Pipeline definitions in their Applicable Scope |
View all definitions helps administrators and supervisors understand all processes. Viewing only definitions in Applicable Scope is better for ordinary Handlers because it lowers selection cost.
Configure the Approval Type triggered by Stage changes
The Approval Type triggered by Stage changes determines which Approval trigger method is used when a Stage changes.
| Type | Description |
|---|---|
| Stage change Approval | The definition shows the option for binding Stage change Approval. Stage changes Trigger Approval only after a process is bound |
| Edit Approval | The definition does not show the process binding option. Any Stage change triggers Edit Approval |
Configure External process settings
External process settings control which pipelines are Available when a Downstream process is initiated.
| Option | Description |
|---|---|
| Yes | When the Downstream process is initiated, it can use only pipelines created by the current External Apps |
| No | When the Downstream process is initiated, it can use all pipelines related to the Object |
Configure entry Notice settings
The entry Notice controls whether the System prompts users to enter the next Stage after all tasks in the Current Stage are Completed.
| Option | Description |
|---|---|
| Yes | Ignore the prompt: All current tasks are Completed. Do you want to enter the next Stage? |
| No | Do not ignore the prompt. The System displays a pop-up Reminder |
This setting Supports only standard stages and does Not Support terminal stages.
Configure Stage task Display Order
Stage tasks Support two display orders:
| Order | Description |
|---|---|
| Default order | Display tasks in the backend definition order, regardless of whether they are Completed |
| Show Not Completed tasks first | Move Not Completed tasks up and Completed tasks down |
Showing Not Completed tasks first suits stages with many tasks. The Handler can identify remaining work faster.
Configure Custom Plugin
A Custom Plugin can extend Process task Operation buttons, Stage view display, and other capabilities. If the Enterprise needs a special Pipeline experience, extend it with a plugin.
Expected result and validation
- Use data that matches multiple Pipeline conditions to Trigger a Pipeline.
- Check whether the System matches the target Pipeline by Priority.
- Use an ordinary user Role to View the Stage view.
- Validate task Display Order and entry Notice.
- If External process is enabled, use a Downstream Role to validate the Visible Pipeline scope.