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.

Calling an activity or an automation from a flow

Updated on November 22, 2021

You can use the Utility shape to call an activity or an automation from a flow. By using an activity or automation, you can use fewer shapes in your flow and perform processing that does not require human input.

  1. Open a flow by searching for it or by using the Application Explorer. For more information, see Finding rules by class.
  2. On the Diagram tab, click the Flow shapes icon, and then click Utility.
  3. Drag the Utility shape to a position on the flow diagram, based on the order of events in the flow.
  4. Connect the Utility shape, by dragging connector end points to connection points on different shapes in the flow.
  5. Double-click the Utility shape to open the property panel.
  6. In the Select type of rule field, select the type of rule.
  7. Complete the following fields based on the type of rule you are using:
    • Activity – In the Rule field, select the name of an activity that is set to type Utility. If the activity supports input parameters, additional fields are displayed for you to define name-value pairs.
    • Automation – In the Resource field, select type of automation you are using, then in the Name field, select the automation to use. If the activity supports input parameters, additional fields are displayed for you to define name-value pairs.
  8. Click Submit to close the property panel.
  9. 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