Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

Shape icons in a process

Updated on March 29, 2022

Shape icons in a process are a visual indicator of a shape's configuration and current processing. You can use shape icons to quickly review the functionality and progress of a process without having to open the individual shapes.

For example, you can view which assignments have corresponding tickets, or if an assignment generates any notifications.

You can view shape icons on assignments when you edit your process in a flow diagram. Shapes in a process support the following icons:

IconDescription
The assignment has one or more corresponding tickets. By creating a ticket, you can jump to a specific assignment in a process and skip a part of the processing. For example, a user can skip assignments to provide the personal details of their spouse if they select an option that they are single in one of the previous assignments.

For more information, see Creating a ticket.

The assignment includes a service-level agreement (SLA). For example, you can define a deadline of three business days to resolve an assignment.

For more information, see Setting service-level agreements (SLAs) for stages, processes, and steps.

The assignment generates one or more notifications. For example, you can notify interested stakeholders about the progress of a case.
Note: You can add notifications directly to assignments only in Dev Studio. For more information, see Sending custom notifications about new assignments.
The assignment includes routing configurations. For example, an application can route an assignment to a current user or a work queue that a group of users can access.

For more information, see Assigning tasks to users.

A spin-off subprocess runs simultaneously with the current process. The current process can end without completing the spin-off subprocess first. For example, an office worker can work on a spin-off subprocess of granting a new hire a parking spot in parallel to a main onboarding process.

For more information, see Adding additional configuration to a subprocess.

When a case reaches an assignment, the case status changes to a value that includes the New prefix. For example, when a customer submits a new case and the case status changes to New-Ready.

For more information, see Changing case statuses.

When a case reaches an assignment, the case status changes to a value that includes the Open prefix. For example, when an application routes a case to a user for processing and the case status changes to Open-InProgress.

For more information, see Changing case statuses.

When a case reaches an assignment, the case status changes to a value that includes the Pending prefix. For example, when an application routes a case to a manager for approval and the case status changes to Pending-Approval.

For more information, see Changing case statuses.

When a case reaches an assignment, the case status changes to a value that includes the Resolved prefix. For example, when processing of a loan request ends and results in granting of the requested money, the case status changes to Resolved-LoanGranted.

For more information, see Changing case statuses.

For example: The following figure shows a sample process of running a background check that includes Start and End shapes, three assignments, and one subprocess. The processing occurs in the following order:
  1. The application routes the Verify education assignment and the case changes status to Open-InProgress.
  2. A specific user processes the Verify work experience assignment, which includes an SLA.
  3. Simultaneously, a spin-off subprocess named Check social security starts. Currently, the subprocess does not include defined routing.
  4. After the user completes the Verify work experience assignment, the case moves to the Prepare for approval assignment and routes the assignment according to a defined configuration. Additionally, the application sends a notification.
  5. The End shape in the process includes a ticket. If a use case does not require a background check process, an application can skip the process and move straight to the End shape with the ticket.
Icons in a Running a background check process
A sample process that includes assignments with icons.

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