Skip to main content

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

Setting up the initial configuration

Updated on June 15, 2021

Resave Pega Warranty models marked for extension, sample operators and recommended rules into your new application, and expose application fields for reporting. The initial configuration enables you to easily extend the application later.

Pega Warranty Implementation Guide
  1. In the header of Dev Studio, click Configure > Implementation Wizard.
  2. In the Configure system environment tab, review the predefined system environment attributes.
    The system uses these values as a basis for the Dynamic Class Referencing (DCR) in the Warranty application.
  3. Click Next.
  4. In the Configure rules tab, select all the predefined rules and click Export to implementation layer.

    A success or failure icon will be displayed regarding each rule. Hover over the failure icons, if any, to see the failure details. You should manually resave the failed rules into the implementation layer. In Microsoft SQL Server, timeout exceptions have been observed. Resave the rules manually. For more information, see There are a large number of SQL timeout errors MS/SQL.

  5. Click Next.
  6. In the Property optimization tab, click Initiate optimization to optimize the selected property list.
  7. Click Done to complete the initial setup.
  8. Update the following rules marked as extensible, based on your business requirements, with the newly created workbaskets, work groups, and operator IDs.
    • DetermineClaimAssignment
    • DetermineHLA
    • DeterminePAWorkBasket
    • DeterminePAApproverWB
    • DetermineRAWorkbasket
    • CustomerProfile

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