Skip to main content

Queuing a task for background processing

Archived

1 Task

30 mins

Visible to: All users
Intermediate Pega Platform 8.6 Dev/Designer Studio English
This content is now archived and is no longer updated. Progress is not calculated. Pega Cloud instances are disabled, and badges are no longer awarded. Click here to continue your progress in the latest version.

Scenario

To reduce errors and complaints with payroll processing, the Human Resources department allows employees of TGB to enroll in direct deposit. When employees enroll, their paycheck is automatically deposited into their checking account when the accounting department processes the company payroll.

To automate payroll processing and avoid both case processing delays and performance impacts during peak business hours, add a step to the case life cycle to queue the creation and sending of an email once the user completes a Payroll Setup case.

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

Role User name Password
Senior System Architect SSA@TGB rules
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.

Challenge Walkthrough

Detailed Tasks

1 Create Run in background and confirmation steps

  1. In Dev Studio, configure the Payroll Setup case as shown in the following image.
    standard-queue-processor-complete-enrollment-stage
  2. Change the name of the Run in background step to Upload payment information.
  3. In the contextual properties panel for the Run in Background step, use the information in the following table to configure a standard queue type to run the UploadToPaymentProcessor activity.

    Field Value
    Type of queue Standard
    Activity name UploadToPaymentProcessor
    Lock using Primary page
    Alternate access group  
    Audit note upload to payment processor and send confirmation email
    Tip: The activity must already exist prior to the configuration of a standard queue processor. The UploadToPaymentProcessor activity sends an email using the call method.
    Standard queue
    Note: By default the queue processor uses the access group of the user who queued the item.
  4. After the Upload payment information step, add a Payroll information received send email step, to confirm that the payroll information is received.
  5. In the contextual properties panel for the Payroll information received step, use the following image to configure the correspondence.
    standard-queue-processor-send-email
  6. Save your changes.

Confirm your work

  1. Create a new Payroll Setup case.
  2. Complete the Collect employee information form by using a valid email address.
    standard-queue-processor-collect-employee-information
  3. Click Submit
  4. Advance the case to the Complete enrollment stage.
  5. In the Review selections view, click Submit to complete the case with a Resolved-Completed status.
  6. Verify the confirmation emails are present on the case. 
    standard-queue-processor-attached-emails
  7. Click Actions > History and locate the audit note you entered for the Run in Background step to verify the standard queue processor ran.
    Note: You may need to refresh the case after 1-2 minutes to see the audit note and the email sent by the activity.
    2.7 image border

     

  8. From Admin Studio, click the Queue processors tile to view the list of queue processors.
    Admin studio
  9. Verify that there are no broken processes and that the Ready to process column is zero to confirm the case step processed.
    2.9imagewithborder
    Note: The Processed in the last hour column may reflect the standard queue item you just ran; however, the field may also reflect other background processes occurring in the system at the same time.


Available in the following mission:

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