Skip to main content


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

Updating from Pega Sales Automation for Insurance 7.22 or 7.31

Updated on September 20, 2021

After an update to the current version of Pega Sales Automation for Insurance, perform the following post-update tasks if you are upgrading from Pega Sales Automation for Insurance 7.22 or 7.31.

Pega Customer Relationship Management for Insurance 8.6 Post-update Tasks for Pega Cloud services Environments
  1. Update access groups and application instances to reference the SalesAutomationForInsurance 08.40 application.
  2. User defined functions (UDFs) are no longer supported for Cloud deployments. Existing objects and instances referencing UDFs in the 8.4 application will generate missing value errors for unexposed columns. If your customized application rules used properties that relied on UDFs, you must optimize the affected properties after the update by running the column population job to repopulate these properties. To obtain the list of the properties you must optimize after the update, review the DDL SQL file to find the altered database tables.
  3. Unique ID prefixes might be altered during the update. Review the Unique ID prefixes to ensure that they are still appropriate for the environment.

    Unique ID prefixClass reference
    BTPegaCRM-Data-BusinessTerritory
    DF-Pega-DM-DDF-Work
    HH-

    PegaCRM-Entity-RelationshipGroup-Household

    PegaInsCRM-Work-RelationshipGroup-Household

    PRPegaCRM-Data-Product
    RT-PegaCRM-Data-RelationShipTypes
    TP-PegaCRM-Data-TimePeriod
  • Previous topic Configuring Federated Case Management case types for web mashup
  • Next topic Migrating data from Pega Sales Automation for Insurance 7.22 or 7.31

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