Helps a single user complete complex tasks by presenting multiple screens in a logical sequence

Helps you organize separate tasks into steps, so you can control how, when, and by whom work is performed for each step

Provides an easy way to add a step that is preconfigured with functionality, such as sending an email, to a process

Provides a way to add an assignment that is preconfigured with one or more actions a user can take to a process

At the stage level

At the process level

At the case level

At the assignment level

A course selection case requires university students to choose courses they are interested in taking. Their proposed schedule must be approved by their academic advisor.

An onboarding case requires an IT member to set up the new hire’s hardware and a facilities member to set up the new hire’s desk.

A job application case requires the applicant to fill out personal information, enter job history, and provide a cover letter.

An expense report must be reviewed by an employee’s manager, senior manager, and director.

A process where new employees enroll in benefits

A Collect Information step where new employees enter their full name, start date, manager, and department

A stage where a member of human resources reviews and verifies the validity of the documents provided by the new employee

An Approve/Reject step where the new employee's manager either approves or rejects the software and hardware requests for the new employee

describes the business value of the step

defines the step

describes to users the action to take in a step

instructs an application developer how to build the step

Case status updates at the beginning of the step.

Case status updates at the end of the process containing the step.

Case status cannot update automatically.

Case status updates at the end of the step.

assign cases to the appropriate case worker

automatically change assignment status

generate service-level reports

help ensure timely completion of work

in which the case or step should be completed

allowed before an assignment is considered overdue

in which the case or step must be completed

allowed for users to advance to the next stage

Picklist

Boolean

User reference

Text (paragraph)

Text (single line)

Location

Text (paragraph)

Attachment

Data reference

Embedded data

Case reference

Lookup

A single record data relationship establishes a single entity grouping together related fields. A multiple record data relationship establishes a list of entities grouping related fields.

A single record data relationship stores data. A multiple record data relationship does not store data.

A single record data reference can include multiple record data references, but a multiple record data reference cannot include single record data references.

A data object can be used to establish either a single record data relationship or a multiple record data relationship, but not both.

Query

Data reference

Embedded data

User reference

Create a Products picklist that contains the list of products and attributes.

Connect your application to an external database that contains product information.

Configure a Products data object with a local system of record and add your data records to the Products data object.

Create a case view with fields for the product and product attributes

Data pages are not configurable with a new data source

Data pages are only available when Pega is the system of record.

In App Studio, data pages identify how to obtain data from a system of record.

Data pages identify how to render a user form.

Data records must be stored using a database table for local data storage.

Data records direct how an assignment moves forward.

Data records provide access to data that is used to process cases but is not part of an application.

Data records and data objects share the same role, which is to provide structure for data pages.

By assigning work to the party in the appropriate time zone

By assigning work to the most senior person in a work group

By assigning work to the currently available party

By assigning work to the most appropriate parties

Route the assignment to the user.

Route the assignment to the user’s work group.

Route the assignment to the user’s work queue.

Route the assignment to the user’s manager.

Configure an Approval step to route to a specific user.

Configure an Approval step to route using business logic. Enable mobile approval.

Configure an Approval step to route to a specific user. Enable mobile approval.

Configure an Approval step to route to a work queue that all division vice presidents can access. Enable mobile approval.

After the assignment, add a Send Email step.

Compose email notifications in the assignments.

Before the assignment, add a Send Email step.

Enable assignment notifications for the case type.

Copy values into the email for the applicant name, loan office, and loan amount.

Include a link to the organization's website page so the user can log in and view their loan information.

Add placeholder text for the applicant's name, loan office, and amount.

Add the applicant's name, loan office, and loan amount properties.

Pega Platform low-code development increases both productivity and IT involvement.

Pega Platform makes low-code development easy for very simple applications only.

The Pega Platform low-code development tools create the code for you.

The Pega Platform user interface allows only low-code users to build applications.

Picklist

User Reference

Text (single line)

Boolean

Collect Information

Change stage

Send email

Create case

Route the assignment based on an appraiser role.

Route the assignment to the correct work queue based on business logic.

Route the assignment based on appraiser skills.

It is not possible to support this requirement. The router must define a specific work queue.