Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Adding decisions to processes

Updated on May 11, 2022

Make your business processes flexible and responsive by providing conditional paths that a case can follow to reach a resolution. By adding a decision point to your case, you support more than one outcome for your business process, and adjust the case to changing business needs and circumstances.

For relevant training materials, see the Automating workflow decisions module on Pega Academy.

Before you begin: Configure a process:
  1. Add a process to a stage in your case life cycle. For more information, see Processes in a case life cycle.
  2. Define the steps for your process. For more information, see Adding single steps to processes.
  1. In the navigation pane of App Studio, click Case types, and then click the case type that you want to open.
  2. In the case working area, on the Workflow tab, click Life cycle.
  3. In the Case life cycle section, hover over a process in a stage, and then click the Configure process icon.
  4. Above the canvas, click the Add a flow shape icon, and then click Decision.
  5. In the Decision shape, click [Decision], and then replace the default label with a descriptive name.
    For example: In the Decision shape that represents a decision about an approval or rejection, enter Approved?.
  6. Drag the Decision shape onto the canvas, to a position where the decision occurs in the process.
  7. Connect the Decision shape to the process:
    1. Drag a connector from a shape that precedes the decision in the process to the Decision shape.
    2. Drag the end point of the connector from the Decision shape to the connection point of the shape that follows the decision on the canvas.
    Tip: The Decision shape works correctly when the connector is green.
  8. Click the Decision shape.
  9. In the Decision shape property panel, define at least one conditional path:
    Create a custom condition
    1. In the When list, select Custom condition.
    2. Click the Configure conditions icon.
    3. In the Configure condition window, select a condition, a comparator, and a value to compare with the condition.
      For example: Case status is equal to New
    4. Optional: To define more conditions, click the Add row icon, and then repeat substep 9.c.
    5. Optional: To group the conditions, select comparators from the list.
      For example: To make only one condition compulsory, from the list, select OR.
    6. Optional: To reuse the condition in the future, click ActionsAdd to when conditions library.
    7. Click Submit.
    Use an existing condition
    1. In the When list, select Existing condition.
    2. In the list of conditions, select a condition.
  10. In the Go to list, select the shape to which the process advances when the case meets the conditions that you define.
  11. In the Otherwise go to list, select the alternative shape to which the process advances when the case does not meet the conditions.
  12. Click Save.
Result: At run time, when the case reaches a decision point, the system evaluates the conditions. If the case meets the conditions, the process moves to the step that you defined. If the case does not meet the conditions, the system moves the case to the alternative step.
  • Types of decision logic

    You can use different types of logic when you add the Decision shape to a flow. By understanding what makes each type unique, you can create flows that make decisions more effectively.

  • Changing the decision logic in a process

    You can change the way that you implement a decision in a process. By using a rule instead of a series of when conditions to define your decision logic, you can create cases that support complex decisions and are easier to maintain.

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

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