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.

Repair order data validation based on XML processing

Updated on September 10, 2021

Pega Warranty receives data from an external system that is provided by a repair technician multiple times during a repair procedure. When the data is updated, the Dealer Management System (DMS) only sends the data that changed with the IsRepairComplete processing flag set to False. Every time Pega Warranty receives the data, it checks whether the pre-validated rules should be applied. When the pre-authorization rule is applied to a repair line, a Prior approval case is automatically created and the dealer receives a notification email from the application.

When the system receives data, it performs the following validations:

  • Whether a repair order already exists
    • If the repair order exists, the system opens it and compares the data in the repair line with the received data.
    • If the repair order does not exist, the system creates a new repair order and populates it with the received data.
  • Whether the data has changed
    • If the data has changed, the existing repair line is replaced with the new repair line that is received. If the data matches the pre-authorization rules criteria, the system automatically sends an email to the dealer and creates a prior approval.
    • If the data is unchanged, no additional actions are performed.
  • Whether the data contains a new repair line
    • If the data contains a new repair line, the repair line is analyzed for pre-authorization.
    • If the data is unchanged, no additional actions are performed.
      Apply pre-authorization rules to each repair line separately. If one repair line is waiting for authorization, the system should be able to receive and process a second repair line simultaneously.

The response information from Pega Warranty is also sent as an XML file. If the repair order passes the pre-validation rules for each repair line, the case advances to the review and submit stage.

Related articles

Repair order case typeCreating a repair order based on XML processingRepair order data elements

Tags

System Architect Lead System Architect Business Architect Experience Designer Pega Delivery Leader System/Cloud Ops Administrator 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.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us