Skip to main content
Verify the version tags to ensure you are consuming the intended content or, complete the latest version.

Adding Stages and Steps

In a Pega Platform™ application, the steps in a business process are grouped into stages. Ren, the graphic designer developing a Pega Platform application for his team, defined four stages for his ideal process flow: Submission, Processing, Verification, and Delivery.

The four stages of the Content Request case type: Submission, Processing, Verification, and Delivery.

Ren adds the four stages to his Content Request case type.

Adding stages

When a new case type is created, the system automatically adds a Create stage to the case type. The Create stage collects the information that is necessary to initiate a new case.

In the application that Ren builds, the stage name Create is updated to Submission to better reflect the ideal process flow. 

Ren adds a second stage, Processing, by performing the following steps:

  1. In the navigation pane of App Studio, click Case types > Content Request.
  2. In the case working area, on the Workflow tab, click +Stage.
  3. In the text box for the stage, enter Processing.
  4. In the contextual property pane on the right, in the Set case status on stage entry field, enter Processing.
  5. Click Save.

Ren repeats steps 1-3 to add the Verification and Delivery stages. 

Adding steps

Steps are defined as user actions or automated actions. Steps are grouped into stages. A stage may have one or more steps.  

For example, the Create stage comes with a preconfigured Create step.  

As seen in the following figure, the green clipboard icon on the left of the Create step identifies it as a Collect information step:

A Collect information step is denoted by a green clipboard icon.

Ren's application requires three types of steps:

  • Collect information
  • Send email
  • Approve/Reject

Collect information

A Collect information step creates a form in the user interface in which users can enter information.  

In Ren's application, there are two Collect information steps.   
 
First, in the Create stage, the requester completes a form that is designed to initiate the creative content request. This form includes information such as the requester's name, email address, the type of content needed (video, brochure, or slide deck), and the details of the request.  
 
In the Processing stage, the Creative Content team member responsible for completing the requested work completes a form with any relevant notes about the project and includes the completed project, added as an attachment. 

For more information on creating the forms associated with each Collect information step, see the topic Collecting data.

Send email 

The Send email step is a type of Automation step in Pega Platform.

Note: An Automation step is a step that adds a preconfigured, automatic process to your case type. Example of automation steps include Send email, Change to a stage, Create PDF, and Search duplicate cases.

Adding a Send email step sends an automated email to a specific user at a pre-determined point in the business process.  Send email steps are used to update relevant parties on the status of a case. 

In Ren's application, he'll add a single Send email step which will send an email notification to the requestor to confirm receipt of the request.   

For more information on the process of defining the parameters of the Send email step, see the topic Sending automated emails.

Approve/Reject 

An Approve/Reject step creates a place in the user interface where a specific user or group of users can approve or reject a project or request. 
 
Ren's application has two Approve/Reject steps: one for supervisor Gab's approval, and one for the requester's approval.  
 
Additionally, Approve/Reject steps can send an automated email or text notification to the approver. The approver can then approve or reject the request directly from the email or mobile device without logging into the system. 

For more information on the process of defining the behavior of each Approve/Reject step, see the topic Designing an approval process.

Additional steps 

Pega Platform offers many additional steps beyond the three Ren uses. For more information on the different steps that are available in Pega Platform, see Step types.

Adding steps to the application

Next, Ren manually adds the steps that are associated with the remaining stages of his application: ProcessingVerification, and Delivery.  

Referencing his ideal process flow, Ren adds steps for Send confirmation and Submit content to the Processing stage. 

The Send confirmation step involves sending a confirmation email to the requester. Sending an email is an example of an Automation step that uses Pega Platform tools. 

Ren adds the Send confirmation step to the Processing stage by performing the following steps:

  1. In the Processing stage, hover over the area labeled Process.
  2. Click Step > MoreAutomations > Send email.
  3. Click Select
  4. In the Send email field, enter Send confirmation
  5. Click Save

Ren follows similar steps to add a Collect information step to the Processing stage, and Approve/Reject steps to both the Verification and Delivery stages. 

Once the steps have been added to each of the four stages, Ren's Content Request case type appears as reflected in the following figure: 

The Content Request stages and steps built in Pega Platform.

The following video shows Ren's process for adding stages and steps to his application: 

Note: The example application in this mission is built on Pega's new view-based architecture Constellation (previously referred to as Cosmos React). For more information about Constellation, see Constellation architecture. For an example application built using Pega's Traditional UI architecture (previously referred to as Theme Cosmos), see the Low-Code Maker version 8.7 mission.
Note: The user interface depicted in the videos associated with this mission might differ slightly from your own due to alternate versions of the Pega Platform. This video has no audio and no closed captions.

Check your knowledge with the following interaction:

In your environment

In your own Pega environment, create a case type and add the corresponding stages and steps. You can duplicate the Create Request case type that Ren creates or create a case type that details the stages and steps of one of your own business processes.

 


This Topic is available in the following Module:

If you are having problems with your training, please review the Pega Academy Support FAQs.

Did you find this content helpful?

100% found this content useful

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Academy has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice