Skip to main content

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

Configuring correspondence rules

Updated on June 15, 2021
Correspondence rules
Pega Warranty Implementation Guide

You can use correspondence rules in your implementation layer to automatically generate or customize outbound emails, faxes, printed letters, telephone messages, and other notifications. Outgoing email can contain Pega UI sections, plain text or HTML, and may also include attachments such as PDF files and images.

In Pega Warranty, you can resave or customize the following types of correspondence rules based on the customers' needs.

Claim file - PegaMfg-AMS-Work-WR-CL-ClaimFile

ProgramNotification Email

Repair order - PegaMfg-AMS-Work-Service-RepairOrder

CampaignEmail Email RepairTechnicianEmail Email SampleRepairOrder Email

Use the implementation layer to define new templates.

Note: Resave the correspondence template to the implementation layer to ensure that it appears during the creation of a program.

You can update the logo, text, layout, and incorporate values from the application, for example, claims and repairs as a part of the correspondence content. Use the following example to configure the correspondence rules.

  1. In Dev Studio, search for ProgramNotificationEmail and select the PegaMfg-AMS-Work-WR-CL- ClaimFile correspondence rule from the results.
  2. Save the rule into your implementation layer. For additional information about locked and unlocked rulesets, see Copying a rule or data instance.
  3. Edit the available correspondence template according to your business requirements.
  4. ClickSave.
  5. Repeat the following steps for the repair order related rules if necessary.

For more information about how to create or modify the correspondence rule template, see Correspondence.

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

Close Deprecation Notice
Contact us