updating to Pega Platform 7.4 and Pega Foundation for Insurance 7.4 brings in Pega Platform class and sample tables and their respective class-table mappings. If your implementation uses Pega Foundation for Insurance 7.4 classes and sample tables, you must map the classes back to the tables in Pega Foundation for Insurance 7.31 for the existing customer operations to work, or migrate data from the tables in Pega Foundation for Insurance 7.31 to the tables in Pega Platform 7.4.

To update the database table mapping, in Dev Studio, use the Records Explorer.

1. In the navigation panel of Dev Studio, click RecordsSysAdminDatabase Table.
2. On the Instances of Database Table page, open a record in the list that corresponds to the class whose table mapping needs to be modified.
3. In the Database field, select the appropriate schema name and click Save.
4. Repeat steps 2 and 3 for each of the classes that require modification.If your implementation makes use of any of the Pega Foundation for Insurance 7.31 tables, store the data by using Pega Foundation for Insurance classes. For more information, see the following table.

   Table name in Pega Foundation for Insurance 7.31	Class name in Pega Foundation for Insurance 7.31	Table name in Pega Platform 7.4	Class name in Pega Platform 7.4
   PA_ADDRESS	PegaApp-Interface-Address	P_ADDRESS	PegaData-Address
   PA_ADDRESSTYPE	PegaApp-Interface-AddressType	Columns merged in P_ADDRESS table
   PA_BUSINESSUNIT	PegaApp-Interface-BusinessUnit	P_ORGANIZATION	PegaData-Organization
   PA_CONTACT	PegaIns-Interface-Contact	P_CONTACT	PegaData-Contact
   PA_CONTACT_BUSINESSUNIT_LINK	PegaIns-Interface-BusinessUnitLink	P_CONTORGREL	PegaData-ContactOrgRel
   PA_COMMUNICATION_OPTIONS	PegaIns-Interface-Contact-CommunicationOptions	Columns merged in P_CONTACT table
   PA_ROLES	PegaApp-Interface-Roles	P_ROLE	PegaData-Role

Starting with Pega Foundation for Insurance 8.2, sample data is found in CustomerData schema (it was previously located in PegaData schema in version 8.1.

If your implementation makes use of any Pega Foundation for Insurance sample table that is part of a schema other than CustomerData and you need to continue using the other schema, then you must update the corresponding database table mapping rules.

To update the database table mapping, in Dev Studio, use the Records Explorer.

1. In the navigation panel of Dev Studio, click Records > SysAdmin > Database Table.
2. On the Instances of Database Table page, open a record in the list that corresponds to the class whose table mapping needs to be modified.
3. In the Database field, select the appropriate schema name and click Save.
4. Repeat steps 2 and 3 for each of the classes that require modification.

   If your implementation makes use of any of the Pega Foundation for Insurance 8.1 tables, store the data by using Pega Foundation for Insurance classes. For more information, see the following table.