Skip to main content


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

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Configuring a decision in a process

Updated on February 6, 2019

Objective

In App Studio, learn how to configure a decision in a process to define the different paths that a case can follow at run time.

Note: This task takes approximately 5 minutes to complete.

Procedure

  1. In the navigation panel, click Case types, and then click the case type that you want to open.
  2. On the Workflow tab, click Life cycle if Optional actions is selected.
  3. Hover over a process in a stage, and then click the Configure process icon.
  4. Click the Flow shapes icon, and then click Decision.
  5. Drag the Decision shape to a position on the canvas, based on when the decision occurs in the process.
  6. Connect a shape in the canvas to the Decision shape, by dragging the end point of a connector to a connection point on the Decision shape.
  7. Define at least one conditional path:
    1. Click the Decision shape to configure it.
    2. In the When section, click Click to add condition.
    3. In the Field list, select a field to evaluate in a case.
    4. In the Comparator list, select a comparator.
    5. In the Value list, enter a value to compare with the field that you select.
    6. Click OK.
    7. In the Go to list, select the shape to which the case advances when the conditions that you define return a true value.
  8. In the Otherwise go to list, select the shape to which the case advances when no conditions return a true value.
  9. Click Save.
  10. Click Stages & steps to return to the life cycle of your case type.

Previous versions

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.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us