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.

Upgrading your system of record (8.3 and earlier)

Updated on September 10, 2021

The system of record defines the logical and physical database tables that your application requires. If you are using the system of record database tables that were included with Pega Customer Relationship Manager 7.31, after upgrading the application, your database schema consists of two set of tables: one that exists from Pega Customer Relationship Manager 7.31 and the other set of tables from the Pega Platform upgrade. You can point your application to use the new set of tables from Pega Platform so that your application uses the new data tables.

However, you can continue using your existing set of tables from Pega Customer Relationship Manager 7.31 without mapping your tables to the latest tables from Pega Platform 7.4 or migrating your data.

The following table lists the updated database tables that the Pega Platform provides:

Old tables (Pega CRM 7.31)New tables (Pega CRM 7.4)


Before upgrading your data, ensure that you complete the following steps.

  • Back up your database tables.
  • Validate the tables with respect to the use cases and approve its performance and scalability.
  • If new or extra columns are added to the old system of record tables, migrate those columns to the new system of record tables. You must also change the upgrade scripts accordingly.

To upgrade your system of record, complete the following steps:

  1. Log in to Designer Studio.
  2. In the Explorer panel, click Records > SysAdmin > Database Table.
  3. Map your existing tables to the new tables.
    1. Search for and open your implementation data class, for example, PegaCA-Interface-Contact.
    2. Enter the new table name in the Table name column, for example, p_contact.
    3. Click Save.
    4. Repeat steps 3a through 3c and map each table separately.
  4. Update the Address and Contact implementation class to map new columns to the existing properties.
    1. In the Explorer panel, click App and search for the Contact data class, for example, PegaCA-Interface-Contact.
    2. Right-click the class name and click Definition.
    3. On the class definition page, click the External Mapping tab, then add the new external mappings to point to the new columns. For example, the Column name PYTIMEZONE maps to the Property name .TimeZone.
    4. Update the rules references for customized rules with respect to the new properties that are listed in the following table:
      Old propertiesNew properties
      1. In the Explorer panel, click App > Data Model > Property> <property name>.
      2. On the property page, click Actions > View references.
      3. In the Referencing Rules column, expand the When rule.
      4. Click the edit icon for .LaunchWhen.
      5. On the When rule form, on the Advanced tab, update the rule name with the updated or new property name. The following list details the new properties in your system of record:
        • pxCreateOpName
        • pxUpdateSystemid
        • pxCreateSystemid
        • pxUpdateOpName
    5. Repeat steps 4a through 4d to update the Address data class.
  5. Migrate the data records from your existing table to the new system of record tables. You can run an SQL script to migrate the data. For more information on how to migrate data, see Modifying the data import process.

For more information on data types, see CRM data types in Pega Platform.

  • Previous topic Pega Customer Relationship Management integration with Pega Marketing


Pega Customer Service 7.4 - 8.3 Pega Sales Automation 7.4 - 8.3 Pega Customer Service Pega Sales Automation

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