Skip to main content

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

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Automatically created online repair order claims

Updated on September 10, 2021

Pega Warranty automatically creates a Warranty claim after a repair order is processed. If you add more than one repair line, then Pega Warranty creates a Claim unit case for each repair line separately under one claim file.

After a dealer creates a repair order in the Warranty system, a claim unit is created for each entered repair line.

For more information about how to create a repair order, see Creating an in-shop or in-field repair order.

Pega Warranty automatically adjudicates the claim, based on dynamic parameters. These parameters might be different for each manufacturer. The business users can configure rules, however, if one or more required parameters do not match the total cost entered, a claim unit is automatically sent to an assessor for a manual assessment. The assessor then takes appropriate action on the claim unit.

The assessor verifies that no further action is required or anticipated on a claim unit. This includes ensuring that all financial aspects of the claim unit are complete and that all correspondence is closed. An assessor resolves the claim unit and the system updates the claim status to Resolved-Completed.

For more information about additional actions performed on the claim unit, see Managing a Warranty claim.

Related articles

Warranty claim case type


System Architect Lead System Architect Business Architect Experience Designer Pega Delivery Leader System/Cloud Ops Administrator Case Management Manufacturing

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