Published at: 2026-09-17

02-configure-stages.md

Define Stage details, entry conditions, and completion conditions.

Overview

Stages control how an Object moves from one Business Status to the next. You need to Configure the Stage Name, duration, timeout Reminder, Stage completion conditions, and Stage entry conditions.

Key capabilities

Stage configuration defines stay rules, task requirements, entry conditions, and terminal-state handling for each Stage. Based on the Stage Type, stages are divided into standard stages and terminal stages.

Standard stages

A standard Stage carries an intermediate Status in business advancement, such as Verify Account, Requirement Confirmation, Proposal / Quote, and Negotiation Approval for an Opportunity. It can also represent a Regular Account stage for another Object. It includes these capabilities:
  • Configure Stage Basic Info: Maintain the Stage Name and Description to explain the processing goal and business requirements.
  • Configure Stage duration: Select no time limit or set a specific duration. After you set a duration, the System can Trigger timeout reminders based on the stay Time.
  • Configure timeout reminders: After a Stage exceeds its configured duration, remind related Personnel to process it. This is suitable for Timely follow-up on long-stalled data.
  • Configure Stage tasks: Add multiple tasks under each Stage, and specify the Task Handler, execution method, and operation Object.
  • Configure completion conditions: In Completion conditions, select tasks that must be Completed before users enter the next Stage. If required tasks are Not Completed, users cannot advance to the next Stage.
  • Configure entry conditions: In Entry conditions, set Field conditions to control which records can enter the Stage.
  • Support Skip control: Configure whether users can Skip the Stage, which prevents users from bypassing key processing nodes.
  • Support Parallel or serial task generation: Select whether Stage tasks are generated in Parallel or in sequence after a record enters the Stage.

Terminal stages

A terminal Stage represents the Process result. In an Opportunity Pipeline, terminal Opportunity Stage states usually Include Closed Won, Closed Lost, and Invalid. In pipelines for other objects, terminal states usually Include Terminal stage - Success and Terminal stage - Failed. It includes these capabilities:
  • Distinguish terminal results: Opportunities can use Closed Won, Closed Lost, and Invalid to distinguish results. Other objects can use Success and Failed to distinguish completion directions.
  • Configure terminal Stage details: Maintain the Stage Name, Description, and entry Notice so users understand why they enter the terminal state and what is required.
  • Control whether to ignore standard Stage configuration: When a record enters a terminal state, you can Configure whether to ignore standard Stage settings. This suits scenarios that need to end the Process directly.
  • Configure actions required before entering a terminal state: Require users to fill in information or create a Related Object when entering a terminal state.
  • Configure information to fill in on entry: Select no Content, Custom Form, or process layout to collect Closed Won, Closed Lost, Invalid, Success, or Failed reasons.
  • Support reactivation: Configure whether a record can be reactivated after it enters this Stage, so Completed data can return to an active advancement Status.
  • Configure activation conditions and Content: Set conditions that allow activation, and Configure the Content users must provide during activation.
  • Configure terminal Stage entry conditions: Use Field conditions or Custom Function APL code to control whether users can enter a terminal state. This prevents data from ending before key conditions are met.

Before you begin

  • The Pipeline has been created.
  • The Stage Field and Stage values are Confirmed.
  • You have identified the required tasks under each Stage.
  • You have confirmed which stages are standard stages or terminal stages.

Configure Stage details

Configuration item Description
Stage Name Customize the Stage Name based on your business
Stage Description Describe the Stage purpose and processing goal
Stage duration Supports no time limit or a specific duration
Timeout Reminder Supports reminders before and after timeout
When no time limit is configured, you cannot Configure a timeout Reminder. After you set the Stage duration, you can Add reminders before and after timeout.
Reminder recipients Support colleagues, Department, Department Owner, process-related variables, Role, user groups, data-related variables, and personnel Object variables. Reminder Content can reference data variables.
Stage detail configuration

Configure Stage completion conditions

Stage completion conditions control which tasks must be Completed before the record enters the next Stage.
  1. Open the target Stage.
  2. Find Stage completion conditions.
  3. Under Tasks required before entering the next Stage, select required tasks.
  4. Click Save.
The System lists all tasks under the Stage. Users can enter the next Stage only after the selected tasks are Completed.
Stage completion condition configuration

Configure standard Stage entry conditions

Standard Stage entry conditions Support these fields:
  • Current Object fields.
  • Lookup Object fields.
  • Owner primary Department.
  • Personnel.
  • Personnel attributes.
Configure only necessary conditions. Too many conditions increase troubleshooting costs when users perform Stage Advancement.

Configure terminal Stage entry conditions

A terminal Stage can use Field conditions or a Custom Function to control whether users can enter it.
Method Description
By Field Use current Object fields, Lookup Object fields, Owner primary Department, Personnel, and Personnel attributes for validation
By Custom Function Use a Custom Function to validate entry permission. The return value Type must be ValidateResult
You can also Configure these items for a terminal Stage:
  • Stages that must be Completed before entering this Stage.
  • Notice for entering the terminal state.
  • Stages that must be Completed before entering the next Stage.
The terminal-state Notice can contain up to 100 characters. Use business language to explain why entry is blocked, such as: Complete the quote confirmation task before entering the Closed Won Stage.
Stage entry condition configuration

Expected result and validation

  1. Use a test record to enter the target Stage.
  2. Check whether the Stage duration and Reminder take Effect.
  3. Try to enter the next Stage before required tasks are Completed.
  4. Complete required tasks, and then enter the next Stage again.
  5. Use data that does not meet terminal Stage conditions to test the blocking Notice.

Related topics

Submit Feedback
Previous
01-create-a-stage-process.md
Next
03-configure-stage-tasks.md