Table of Contents

Calling an activity or an automation from a flow


Only available versions of this content are shown in the dropdown

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.

  • Flow shapes

    A shape in a flow represents a task that a user or application completes as part of a business process. By connecting different types of shapes in a flow, you can define the path that a case follows from creation to resolution.

  • Integrating a case with an external resource

    You can call an external resource, such as a robotic automation or another application, from a flow. By reusing the services that other resources provide, you can enhance your cases without having to maintain extra functionality in your application.

  • Keystores

    A keystore is a file that contains keys and certificates that you use for encryption, authentication, and serving content over HTTPS. In Pega Platform, you create a keystore data instance that points to a keystore file.

0% found this useful

Have a question? Get answers now.

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