Skip to main content
close Search
Close search

Challenge

Configuring flow action pre- and post-processing

3 Tasks

20 mins

Visible to all users
Beginner Pega Platform 8.2 English

Scenario

Currently, the Candidate case type creates a candidate participant to represent a job applicant and adds the candidate participant to the case at the beginning of the Screening stage. Candidates are not participants in the case throughout the Submission stage. As a result, users cannot contact candidates by email while the case is in the Submission stage.

In a future release of the HRApps application, users are allowed to save cases after a candidate has provided personal information at the start of the Submission stage. This allows users to contact by email candidates who have not completed the Submission stage.

To support this change, the vice president of Human Resources has asked you to configure the application to support emailing candidates whose cases have not completed the Submission stage. For more information on sending case updates to case participants, see the Pega Community article Send important case updates to case participants.

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

Role Operator ID Password
Senior System Architect SSA@TGB rules

Your assignment

Reconfigure the Collect Candidate Details process so that a candidate is added as a participant to the case when the user submits the Collect Personal Details form. After you complete this change, the Create Candidate Party process in the Screening stage is no longer needed.

  • Update the Collect Personal Details flow action so that it runs the addWorkObjectParty activity as a post-processing action. Use the following activity parameter values.

    Parameter Value
    PartyRole Candidate
    PartyClass TGB-HRApps-Data-Candidate
    PartyModel NewParty
  • Remove the Create Candidate Party process from the Screening stage.

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

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

Detailed Tasks

1 Update the Collect Personal Details flow action

  1. In Dev Studio, from the Candidate case, open the Collect Candidate Details process.
  2. Right-click the Collect Personal Details connector and select Open Flow Action to open the CollectPersonalDetails_0 flow action.
  3. On the rule form, open the Action tab.
  4. In the Post-Processing section, in the Run activity field, select addWorkObjectParty.
  5. Update the parameter values with the following values.

     

    Parameter Value
    PartyRole Candidate
    PartyClass TGB-HRApps-Data-Candidate
    PartyModel NewParty

    When you are done, the section will look like the following image.

    addWorkObjectParty
  6. Save the changes. When a user submits the Collect Personal Details form, the system adds the candidate to the case.

2 Remove the Create candidate process from the Screening stage of the Candidate case life cycle

  1. On the case life cycle, in the Screening stage, select the Create Candidate Party process.
  2. Click the Trash icon to delete the process.
  3. On the case life cycle header, click Save. The Create Candidate Party process is removed from the life cycle of the Candidate case type.
When you remove a rule from use in a case type, remember to determine whether the rule is used elsewhere in your application. If the rule is unused, consider removing it from the application. If the rule exists in a previous ruleset version, you must withdraw the rule to remove it from your application.

3 Confirm your work

Create a Candidate case and advance it to the Collect Professional Details form. The form displays the candidate in the Participants area on the harness.


If you are having problems with your training, contact Pega Academy technical support.

Did you find this content helpful?

Want to help us improve this content?

Suggest an edit

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