Table of Contents

Flow shapes


Only available versions of this content are shown in the dropdown

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.

The following table describes all supported flow shapes. Some shapes are not available for screen flows or flows that you update in the case life cycle instead of the Flow form.

Name Description Icon
Annotating a flow Adds notes or comments to the flow without affecting how the flow runs.

Requesting approval from users Routes a case to one or more reviewers, based on a user name, reporting structure, or authority matrix.

Collecting information from a user Creates a task in a work queue or worklist so that a user can provide input to the flow.

Moving a case to a different stage Moves the case to a different stage in the life cycle.

Creating a contextual case Creates a top-level case or one or more child cases.

Adding decisions to processes Evaluates an expression or calls a rule, such as a decision tree, to determine which step is next in the flow progression.

End Designates the end of flow processing.

Preloading a data page Asynchronously starts loading a data page to reduce the time that a screen takes to load the data page.
Posting messages to a case Creates a message that is sent to the Pulse social stream.

Sending push notifications from cases Sends a notification to an iOS or Android mobile device to indicate that an action is required by the user.
Saving data in a data page as part of a flow Saves the data in a savable data page to a system of record.

Sending automatic emails from cases Sends an email to one or more work parties.

Start Designates the start of flow processing.

Calling one process from another process Calls another flow from the current flow.

Pausing and resuming processes in cases Pauses an assignment for a specified length of time or until one or more cases reach a specific status.

  • Types of processes (flows)

    You can create different types of processes, or flows, based on the shapes or steps that you choose or way that you integrate your process with the case life cycle. By understanding what distinguishes one flow type from another, you can select the configuration options that meet your business needs.

  • Annotating a flow

    You can use the Annotation shape to add notes and comments to your flow. By documenting the functionality of a flow, you can share information with other developers.

  • Keyboard shortcuts for flows

    You can use keyboard shortcuts in the Flow form. Using keyboard shortcuts makes creating flows easier and more efficient.

  • Defining the case life cycle

    Track and resolve your cases in a convenient and facilitated way by defining the case life cycle that represents a business model. You can define the life cycle as smaller modules that match the elements of your business process.

  • Creating a stand-alone process

    Create a stand-alone process, or flow, to support or supplement the steps in a case life cycle. By creating a process outside the context of a case life cycle, you can reuse the process in other cases.

  • 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.

100% found this useful

Have a question? Get answers now.

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