Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

Configuring Common Request Programs

Updated on June 15, 2021

A Pega Warranty system administrator can use a common request program to initiate prior approval and parts return cases by selecting the part return and pre-authorization program types. Additionally the administrator can create and configure campaign programs.

To create a common request program, complete the following steps:

  1. Log in as a Pega Warranty system administrator using the WarSysAdmin operator ID.
  2. In the header of Dev Studio, click Configure > Common Request Program > Add Program.
  3. Select a program type and supporting type from the available list, and then click Create.
  4. Configure filters, criteria, and responses based on your business needs.
  5. When creating a Common request program, define business rules in a cause and effect form. The defined cause is the business rule. The action using the Common request program is the effect.
    • The effective date is an automatic program activation date. The end date is an automatic program deactivation date.
    • To configure the applicable regions that are connected to the program, click Add filter, and then select a Region name and Country. To confirm your selections, click Add.
    • Define the particular criteria for the program to start. Configure a qualifier and a value for the selected property type. Note that you can add multiple criteria.
    • The Equals qualifier applies only to numeric or text values.
    • The EndsWith and StartsWith qualifiers apply only to text values.
    • You can configure the response to either notify the subscribers or to create a case for the selected program type.
  6. Review the provided information. To complete the assignment, click Finish.
Pega Warranty Implementation Guide

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

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.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us