Skip to main content


Defining conditions for skipping a stage

Suggest edit Updated on October 29, 2021

Ensure that cases move to the next stage in the sequence when the current stage is not relevant, by defining the conditions that cause a case to skip a stage. When a customer service representative (CSR) can skip irrelevant stages, a case reaches its resolution faster.

At run time, your application evaluates the condition before the case enters the stage. If the value is true, the case skips the processes in the stage and moves to the next stage in the sequence.

  1. In the navigation pane of App Studio, click Case types, and then click the case type that you want to open.
  2. On the Workflow tab, click Life cycle.
  3. In the Case life cycle section, click a stage name.
  4. In the Stage property panel, on the General tab, define the condition for skipping the stage:
    Never skip a stage
    1. In the Skip stage list, select Never.
    Use a custom condition
    1. In the Skip stage list, select Custom condition.
    2. Click the Configure conditions icon.
    3. In the Configure condition window, define a condition that starts the process.For example: Case status is equal to Pending-Blocked
    4. Optional: To add more conditions, click Add a row, and then repeat substep 4.c.
    5. Optional: To group the conditions, select operators in the list.
    6. Click Submit.
    Use an existing condition
    1. In the Skip stage list, select Existing condition.
    2. In the list of conditions, select a condition, and then define whether the process skips when the condition is true or false.
    Note: You cannot skip the Create stage and last stage in the sequence.
  5. Click Save.
Result: At run time, the system evaluates the condition and skips the stage if the value meets the condition.
Did you find this content helpful? YesNo

100% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us