Skip to main content

Designing background processing

4 Tasks

1 hr 30 mins

Visible to: All users
Advanced Pega Platform '23 English

Scenario

In the MDC product delivery scenario, the business partner membership must be renewed every six months, and the partner will have the flexibility to upgrade or downgrade their membership during renewal. Renewal can be initiated at any time before the membership expires. A notification is triggered 15 days (about 2 weeks) prior to the membership expiry date, and a message is displayed on the portal until the membership is renewed.

The delivery service wants the emails to be processed efficiently.

Use the following credentials to complete the exercise:

Role User name Password
Admin admin@deliveryservice rules

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 Identify design options

As you develop your implementation, rely on the rules in Pega Platform™. Consider the following approaches to addressing the requirements:

  • Option 1: Create a single-node job scheduler that queries business partners whose expiration date is less than 15 days and sends an email to each business partner to renew their membership.
  • Option 2: Create a single-node job scheduler with spun-off queue processors to send emails.
  • Option 3: Open the business partner registration case and configure a service level agreement (SLA) that sends an email notification with a deadline of 15 days.

2 Evaluate design options

Design Pros Cons
Create a single-node job scheduler
  • Minimal maintenance
  • Avoids redundant emails
  • Not immune to node disablement.
Create a single-node job scheduler with spun-off queue processors
  • Minimal maintenance
  • Distributed processing
  • Avoids redundant emails
  • Immune to node disablement
  • Additional complexity from having to spin off queue processors.
Create an SLA in an open case
  • Reaps the benefits of case management features
  • Distributed processing
  • Avoids redundant emails
  • Immune to node disablement
  • Keeping the case unresolved just for the sake of email notifications will create a process hindrance with too many assignments and an unresolved case.

3 Recommend the best design option

The single-node job scheduler with spun-off queue processors is the recommended approach because of its better performance.

4 Tasks to perform

  1. Query the business partners whose expiry dates are less than or equal to 15 days (about 2 weeks).
  2. Use the report definition and its pagination settings to query 50 records at a time in an incremental way.
  3. Queue every record to the standard queue processor to send an email.
Membership-Expiry-Notification

Confirm your work

      



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