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.

Adding a conditional path to a flow

Updated on November 22, 2021

You can use a connector to add a conditional path to a flow. By defining the events that cause your flow to follow different paths, you can create cases that support more than one outcome.

  1. Open a flow by searching for it or by using the Application Explorer. For more information, see Finding rules by class.
  2. Define a new path by connecting a sequence of shapes to an existing shape the flow. For more information about the different shapes that you can use, see Flow shapes.
  3. Configure the conditions that cause the flow to follow the new path.
    1. Double-click the connector that goes from the existing shape in the flow to the first shape in the new path.
    2. In the Condition type list, select When .
    3. In the When field, enter a when condition that your application evaluates at run time.
    4. In the Likelihood field, enter a number between 1 and 100 to control the order in which your application evaluates the connector at run time.
    5. Click Submit.
  4. Review the configuration of all other paths, or connectors, from the shape to ensure that it supports the following best practices:
    • There is only one Else connector, so that the flow can continue when no conditions return a true value.
    • There are no Always connectors, which are applicable only when there is a single path from one shape to another.
    • Each connector provides a unique Likelihood value.
  5. Click Save.

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