LinkedIn
Copied!

Table of Contents

Types of processes (flows)

Version:

Only available versions of this content are shown in the dropdown

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.

The following types of flows are supported:

  • Simple — Contains a linear sequence of assignments, smart shapes, or subprocesses only

  • Complex — Contains at least one alternate path

    Decision shapes create alternate paths in a flow because they can have more than one outgoing connector.

  • Straight-through — Contains no assignments, and therefore runs from start to finish without user input

  • Screen — Contains a start shape that is configured with routing options, and therefore sends all assignments to a single user

  • Parent — Calls another flow by using the Subprocess, Split Join, or Split For Each shape

  • Subprocess — Called by another flow

    By default, control is returned to the parent flow when the End shape in the sequence is reached.

  • Parallel — Runs without causing the parent flow or another subprocess in the parent flow to wait for it to finish

    A spin-off subprocess is one example of a parallel flow.

  • Shape icons in a flow

    Shape icons in a flow give a visual indicator of how a shape is configured. You can use shape icons to quickly review the functionality of a flow without having to open the individual shapes.

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

  • Screen flows

Have a question? Get answers now.

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