Skip to main content

Designing a Case Life Cycle

8 Tasks

30 mins

Visible to: All users
Beginner
Pega Platform '24.2
Case Management
User Experience
Constellation
English

Scenario

The mayor of MyTown wants to increase resident engagement and improve the town’s responsiveness to issues raised by residents.

To achieve this goal, the services coordinator wants residents to submit service requests that available city services can resolve. To begin the process, the mayor and the services coordinator have outlined a workflow for submitting, reviewing, and resolving service requests and have created the Service Request Case Type to manage such requests.

In MLP1, residents create service requests from the User Portal, service coordinators review the requests from the Web Portal, and department managers and service coordinators resolve the requests from the Web Portal. In MLP2, residents, services coordinators, and department managers have the option to interact with service request Cases from the mobile Channel.

The following table provides the credentials you need to complete the challenge.

Role User name Password
Application Developer author@mytown pega123!
Note: Your practice environment may support the completion of multiple challenges. As a result, the configuration shown in the challenge walkthrough may not match your environment exactly.

You must initiate your own Pega instance to complete this Challenge.

Initialization may take up to 5 minutes so please be patient.

Challenge Walkthrough

Detailed Tasks

1 Hide items from the Case Life Cycle View

  1. In the Pega instance for the challenge, enter the following credentials:
    1. In the User name field, enter author@mytown.
    2. In the Password field, enter pega123!.
  2. In the App Studio navigation pane, click Case Types > Service Request to display the Service Request Case Life Cycle.
  3. Under Case Life Cycle, click the View: Steps, Personas, Data, Releases (All) menu to display a list of check box items.
    Steps, Personas, Data, Releases list on the case life cycle
    Note: As a best practice, first define the Case Life Cycle at a high level to help you determine the Personas, Channels, and Data objects. Hide Personas and Data for now.
  4. Clear the Personas check box to hide the Personas & Channels section in the Case Life Cycle.
  5. Clear the Data check box to hide the Data & Interfaces section in the Case Life Cycle and automatically clear the Releases check box.
  6. Click outside the menu to hide the View: Steps, Personas, Data, Releases menu.

2 Add the Review and Resolution Stages

  1. To the right of the Create Stage, click Stage to add a second Stage.
    Add a stage to the case life cycle
  2. In the text box that is displayed, enter Review to add the second Stage name and display the contextual property pane on the right.
  3. In the General tab of the contextual property pane, select Automatically move to next stage to enable the case to advance automatically when the Review Stage is complete.
    stage transitions
  4. To the right of the Review stage, click Stage to add a third Stage.
  5. In the text box that is displayed, enter Resolution to add the third Stage name and display the contextual property pane on the right.
  6. In the General tab of the contextual property pane, select Resolve the Case to resolve the Case automatically when the Resolution Stage is complete.

3 Build the Create Stage

  1. On the Workflow tab, in the Create Stage, in the Create Process, hover over the Create Step, and then click Delete to delete the Create Step. 
    Delete the Create step
  2. Click Form Step to add a Step to the Multi-step Form.
  3. In the field that is displayed, enter Report problem.
  4. Click Form Step to add a Step to the Multi-step Form.
  5. In the field that is displayed, enter Identify location.
  6. Click Form Step to add a Step to the Multi-step Form.
  7. In the field that is displayed, enter Identify submitter.
  8. Click Form Step to add a Step to the Multi-step Form.
  9. In the field that is displayed, enter Request updates.

4 Build the Review Stage

  1. Under the Review Stage, hover over Process, and then click Step to choose a Step type.
  2. Click Collect information to add a Step that collects user input.
  3. In the Collect information field, enter Schedule repair to name the Step.
  4. Click the Review Process and enter Review submission to replace the Process label.
    Note: When a new Process is created, Pega Platform™ automatically assigns the Process name based on the Stage name. You can change the default Process name after creating the first Step in that Process.
    Rename the review submission process

5 Build the Resolution Stage

  1. In the Resolution Stage, hover over Process, and then click Step to choose a Step type.
  2. Click Collect information to add a Step that collects user input.
  3. In the Collect information field, enter Perform repair to name the Step.
  4. Click the Resolution Process and enter Resolve issue to replace the Process label.
  5. Click Step > Approve/Reject to add a decisioning Task to display an Approve/Reject Step under Perform repair and add an Alternate Stage to the Case Life Cycle.
    Add an Approve/Reject step
  6. In the Approve/Reject field, enter Review repair to name the Step.
  7. Click Step to add the third Step to the Resolution stage.
  8. Click More to display three Step type categories: Processes, User actions, and Automations.
  9. Click Automations to display steps that are automatically performed or processed by the system.
    Add an automation step
  10. Click Send email > Select to add a Step that automatically sends preconfigured emails.
    Select send email automation step
  11. In the Send email field, enter Send repair confirmation to name the Step.
  12. In the upper right, click Save. The Service Request Case Life Cycle is displayed with the Stages and Steps created.
    Case life cycle
  13. On the Case Type navigation bar, in the upper-right, click the configuration issues icon to display the Draft process warnings dialog box.
    7 errors alert
    Note: The dialog displays a warning for each Step with an incomplete configuration in the Process. The number of warnings varies as you configure the Case Life Cycle. Disregard the warnings, as these issues are addressed in subsequent challenges.
  14. Click Close modal to return to the Case Life Cycle.
    Draft process warnings modal with Close modal icon highlighted in the top-right corner

6 Identify the Personas and Channels for MLP 1

  1. In the upper-left corner of the Case Life Cycle, click the View: Steps menu to display a list of check box items.
  2. Select the Personas and Releases check boxes to display the Personas & Channels Section in the Case Life Cycle.
  3. In the Personas & Channels section, in the Create Stage, click Persona > New Persona to display the New Persona dialog box.
    The New persona dialogue box.
  4. In the Persona name field, enter Resident.
  5. On the next line, click an icon to represent the image of the new Resident Persona.
  6. Click Submit to dismiss the New Persona dialog box and display the Resident Persona and Web Portal Channel, which is added by default.
    Note: To update the Persona name or icon, in the App Studio navigation pane select Users > User Management > Personas. Click on the name of the Persona you would like to update and select the Configuration tab. Once the updates have been made, click Save.
  7. Click the Web Portal Channel to display the configuration pane on the right.
  8. In the configuration pane, in the Additional details section, click the Release list, and then click MLP 1. The MLP 1 tag is displayed on the Web Portal Channel in the Case Designer.
    Contextual panel
  9. Repeat steps 3-8 to add a new Persona named Services coordinator to the Review Stage and tag the Web Portal with MLP 1.
  10. In the Resolution Stage , click Persona > Managers to add the Managers Persona.
  11. Repeat steps 7-8 to tag the Managers Web Portal channel with MLP 1.
  12. In the Resolution Stage, click Persona > Services coordinator to add the Services coordinator Persona.
  13. Repeat steps 7-8 to tag the Services coordinator Web Portal Channel with MLP 1.
    Personas and channels
  14. In the upper right, click Save. The Personas and Channels for MLP1 have now been created.

7 Identify the Personas and Channels for MLP 2

  1. In the Create Stage, in the Resident Persona, click Channel > Mobile to add the mobile Channel to the Resident Persona.
  2. With the User Mobile App Channel selected, in the configuration pane, in the Additional details section, click the Release list, and then click MLP 2.
  3. Repeat steps 1-2 to add and tag the mobile Channel for each Persona with MLP 2.
    Personas and channels
  4. In the upper right, click Save. The Channels for MLP 2 have now been created.

8 Identify the data objects for MLP 1

  1. In the upper-left corner of the Case Life Cycle, click the View: Steps, Personas, Releases (All) menu to display a list of check box items.
  2. In the list, select the Data check box to display the Data & Interfaces section in the Case Life Cycle.
  3. In the Data & Interfaces section, in the Create Stage, click Data > Data object > New data object to display the New data object dialog box.
    Add a new data object to the case life cycle
  4. In the Name field, enter Request type.
  5. Click Submit to dismiss the New data object dialog box and display the Request type data object and Pega system of record, which is added by default.
  6. Click Pega to display the configuration pane on the right.
  7. In the configuration pane, in the Additional details section, click the Release list, and then click MLP 1.
    Configuration pane for the Pega SOR with Configure release icon highlighted
  8. Repeat steps 3-7 to add the Person data object to the Create Stage with the MLP 1 tag.
    Data & Interfaces
  9. In the upper right, click Save. The data objects and interfaces for MLP1 have now been created.

Confirm your work

  1. On the Workflow tab, in the upper right, click Save and run to save changes and create a new Service Request Case.
  2. In the Report problem View, click Next to proceed to the next View. 
    Create
  3. On the Identify location View, click Next.
  4. On the Identify submitter View, click Next.
  5. On the Request updates View, click Advance this Case.
  6. On the Schedule repair View, click Advance this Case.
  7. On the Perform repair View, click Advance this Case.
  8. On the Approval Step, click Approve to complete the Case.
    Approve

This Challenge is to practice what you learned in the following Module:


Available in the following mission:

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

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