Skip to main content

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

Updating the application

Updated on September 3, 2021

To update your application, complete the procedures in this section.

Pega Customer Relationship Management for Insurance Update Guide Pega Customer Relationship Management for Insurance Update Guide
Before you begin: Complete the prerequisites for this update.

Importing the application file

The system data and rulesets for Pega Customer Relationship Management for Insurance are loaded during this task.

Note: Updating your application does not affect client-defined operators.
  1. Log in to Pega Platform (https://<hostname>:<port>/prweb) by entering the administrator ID, for example, [email protected] and the password that you used during Pega Platform installation.
  2. In the header of Dev Studio, click ConfigureApplicationDistributionImport.
  3. Select the Rules\PegaCRMI.jar file from your distribution media, and then follow the wizard instructions.
  4. Select the Enable advanced mode to provide granular control over the import process check box. When that check box is selected, the wizard displays all instances in the current environment that have a newer version of the RAP being imported. For each instance, you decide whether to override the instance or skip the import.
  5. For environments that use the Db2 database, on the Inserts tab, clear the check boxes for the persona categories shown in the following image to avoid receiving an exception error later in the process:
    Persona rules to deselect
    Clear these persona rules on the Inserts tab
  6. For schema changes, depending on your site's requirements, select either Automatic or Manual, and then continue following the wizard instructions.

    If you select Manual, see Viewing and applying schema changes.

    • During the manual process, the wizard displays a Pre-existing rule conflict warning for rules that already exist in the system in a different ruleset. In the Pre-existing rule conflicts section, select the Replace check box for all of the rules that are listed to ensure that the rules are moved to the correct rulesets.
    • To ensure that the following classes will work correctly in Pega Customer Service for Insurance, always choose to replace them when the Pre-existing rule conflicts page opens. These conflicts occur because Pega Foundation for Insurance and Pega Customer Service use the CRM data model, while Pega Customer Service for Insurance uses the foundation data model.
      • PegaApp- (RULE-OBJ-CLASS PEGAPP-)
      • PegaApp-Interface- (RULE-OBJ-CLASS PEGAPP-INTERFACE)
      • PegaApp-Work- (RULE-OBJ-CLASS PEGAPP-WORK)
  7. For environments that use the Db2 database, a known issue in Pega Platform release 8.5 causes an error message to appear during the schema import.

    Complete the following steps to import the schema data.

    1. Click the Total Errors link.
    2. Click Next.
    3. Click View/Download SQL DDL.
    4. Open the text document, and change the column size from 38 to 31 for the PXEFFORTACTUALDELTA and PXRESOLUTIONCOSTDELTA entries.
    5. Save the changes.
    6. Run the updated queries manually.
  8. When the import is complete, click Done.
  9. Apply the required hotfixes by using Hotfix Manager. For more information about applying hotfixes, see Applying the latest on-premises patch.
  10. Optional: Verify the application rules.
    1. In the navigation pane of Dev Studio, click RecordsApplication DefinitionApplication.
    2. Confirm that the following application rule or rules are displayed in the list:
      • For Pega Customer Service for Insurance: CustomerServiceForInsurance 8.
      • For Pega Sales Automation for Insurance: SalesAutomationForInsurance.8.

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