Before starting your update, contact your database administrator and drop the following
tables from the PegaData and CustomerData
schemas:
Note: When you import the latest JAR files, these tables are re-created with the required
data.
PegaData schema:
- IIF_AGENCY
- IIF_AGENT
- PA_CONTACT
- IIF_QUESTIONS
- PR_PEGAINSPROD_INDEX_PRODFORMS
CustomerData schema:
- IIF_POLICY
- IIF_POLICY_LINK
- ORGANIZATIONS_INS
- IIF_POLICY_LOBDATA
- P_ADDRESS
- P_CONTACT
- P_CONTACTCONTACTREL
- P_CONTACTORGREL
- P_ORGANIZATION
- P_ORGORGREL
- P_ROLE
These tables are considered sample tables, and it is assumed that none of these tables are
being used in the site-specific implementation. If any of these tables are being used to
store implementation data, then create a backup of the data and restore it after the
update.
Note: If you are updating from a version prior to Pega Foundation for Insurance 7.31,
before you start your update, contact your database administrator and drop the
IIF_CAUSESOFLOSS table, which you can find in the
PegaData schema.
- If this table was being used for storing implementation-specific data, create a backup
of the data and restore it after the update.
- If this table was not being used to store any implementation-specific data, then a
backup is not necessary because the product import installs the required sample
data.
Note: If you are updating from a version prior to Pega Foundation for Insurance 8.2, before
you start your update, contact your database administrator and take backup of below tables,
which you can find in the PegaData schema. And post update do import of the backup taken.
- IIF_POLICY
- IIF_POLICY_LINK
- ORGANIZATIONS_INS
- IIF_POLICY_LOBDATA
- If this table was being used for storing implementation-specific data, create a backup
of the data and restore it after the update.
- If this table was not being used to store any implementation-specific data, then a
backup is not necessary because the product import installs the required sample
data.
