Skip to main content


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

Setting up a Common Request Program

Updated on March 18, 2021

Automatically create subcases while creating a claim unit or a repair order as a manufacturer or supplier manager, by using the Common Request Program. If the criteria of the claim unit or the repair order match the criteria defined in the program, the configured subcase is automatically added to the claim unit or repair order.

You can set up common request programs that automatically create the following subcases for claim units or repair orders:

  • Campaign Program
  • Parts return
  • Pre-authorization
  1. Log in to the Pega Warranty application as a supplier manager. For more information on login credentials, see Operators list and description.

  2. In the header of Dev Studio, click ConfigureCommon Request ProgramAdd Program.

    Note: Alternatively, in the header of Dev Studio, click CreateCaseProgram.
  3. In the Program type box, select a program type.

  4. In Case/Supporting Type box, select a value.

  5. In the Program Description field, enter a description for the request program, and then click Create.

  6. In the Configure filters section, select the Effective date and the End date within which the request program is valid.

  7. In the Configure location section, click Add filter to select a region and country, and then click Continue.

  8. In the Configure criteria section, select the required criteria to apply to this request program, and then click Continue.

    Note: When an operator with the appropriate permissions creates a repair order or a claim unit with this criteria, the application automatically creates the configured subcase (Campaign Program, Parts return, or Pre-authorization) and applies the request program to the repair order or claim unit.
  9. In the Parts return setup section, in the Request type list, select a request type.

    When you select a request type, you choose the priority for the parts return so that the right teams review the part return requests, in accordance with the OEM's priorities.

    • Field action
    • Safety / quality
    • Recall
    • Prior approval
    • OEM Claim
    • Supplier Claim
  10. If you want the dealer to be able to select the parts to return, click the Choose parts to return button.

  11. If you want the dealer to return all the parts, click the Return all parts in claim button.

  12. In the Add parts box, click select the parts that you want the dealer to return using this program, and then click Add.

  13. In the Number to return field, enter a value.

  14. In the Interval to return field, enter a value.

    For more information on Number to return and Interval to return, see Creating and configuring a parts return request.

  15. In the Return Percentage field, enter a percentage.

    Based on the return percentage that you specify, the system randomly creates parts return requests for the repair orders.

  16. Select the Use supplier registration default center (if configured) check box to automatically add the default return center address that you specified during supplier registration, to the case.

  17. In the Shipping code box, enter or select the shipping code.

  18. In the Carrier list, select a carrier.

  19. In the Create multiple RAs area, click True or False.

  20. In the Return mode area, click Part and image, Image only, or Part only.

  21. In the Does this part require inspection? area, click True or False.

  22. Click Continue.

  23. If you want to notify subscribers, select the Requires Notify Subscribers? check box, and then click Continue.

  24. Review your configuration changes and then click Submit.

  25. Click Approve to approve the program.

  26. To update the program, go to ActionsAdd workUpdate program.

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