Skip to main content

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.

Creating a repair order based on XML processing

Suggest edit Updated on September 10, 2021

In addition to the standard Pega Warranty repair order creation procedure, a repair order can also be created based on a sample XML data file that comes from an external system in the Pega Warranty application. The repair technician enters the repair data in an external system, and the data is then sent to the Pega Warranty application.

To create a repair order based on uploaded XML data, complete the following steps:

  1. Log in as a Pega Warranty administrator using the WarSysAdmin operator ID.
  2. In the the navigation panel ofDev Studio, click Records.

  3. Click Integration-Services > Service SOAP.

  4. Click the filter for Customer Method Name and search for CreateRepairOrder.

  5. Click the desire instance, and then click Actions > Run.
  6. On the Simulate SOAP Service Execution screen, select Supply SOAP request envelope and paste the XML format repair order details data that is required to create the repair order. You can find the sample XML file in the \Sample Data folder in the .zip file that customers receive.
    You can upload multiple repair orders at once.
  7. Click Execute and review the success message with the generated repair order ID that is visible in Response Parameter Values.
    The repair order is not created if any input XML file validation errors or any exceptions occur.
  8. In the Explorer panel, click App.
  9. Under Classes, expand Service, and then click Repair Order.
  10. Click the repair order ID number that was created in step 5.
  11. Verify that the data was uploaded based on the repair order details that were provided in step 5.
  12. Click Review and submit (Review submission) and then click Submit.

For more information about XML processing, see the Pega Warranty Implementation Guide.

Related articles

Repair order case typeRepair order cost calculationRepair order data elementsCreating an in-shop or in-field repair orderRepair order data validation based on XML processing

Tags

Pega Warranty System Architect Lead System Architect Business Architect UX Developer Project Manager System/Cloud Ops Administrator Case Management Manufacturing
Did you find this content helpful? YesNo

Have a question? Get answers now.

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

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