Handling factory data

With every major update of Sterling™ Order Management System, complete factory data (default configuration) is deployed in an upgrade mode to your existing cloud environment. In this process, new entries are added to the database and existing entries in the database are overridden, except for the tables or columns that are protected from change.

Here are some guidelines that you can use to handle the factory data during an update.

You must not make changes to the factory data except for the tables or columns that are protected from change. If you make any change to the tables or columns that are not protected, your changes are overridden during the major update. If you want to create your own custom data, you can use the Save as option for the factory record in the Applications Manager. The custom data that you create is not affected by the major update. If you make any changes to the tables or columns that are protected from change, your changes are retained when a major update is deployed in your environment.

For example, you must not modify the default factory data for agent criteria because the corresponding tables are not protected from change, and hence are overridden during the major update. You must create a new agent criteria, or save the factory criteria as a new agent criteria.

When a specific column is protected from change, any changes that are made in that column are retained though the other columns might be overwritten.

To view the protected tables and columns, open the runtime/properties/fcmigrator.properties file in your developer toolkit. The fcmigrator.properties file is a system-defined file and you must not change it. The yfs.migrator.protect.entities.fromchange property lists the protected tables and the yfs.migrator.protect.attributes.<entity name of table> property lists the protected columns.