Update System Engine

Change Storage

All the changes are stored as VCS records in the VCS Records (sys_vcs_record) table. They are created automatically and cannot be deleted or edited.

VCS Records 

Each action (create, delete, update) on a versioned table object leads to creation of a record in the VCS Records (sys_vcs_record) table. This table contains information about the changes done in any application on the platform.

All the changes are stored in the local pack selected in the Local pack field of the Admin preferences menu. To know more, see Managing VCS records in the Assembling Local Packs article.

It is also possible to import and preview the imported VSC records, find more information in the Importing Configuration Packages article.

Protection Policy 

The Protection Policy attribute is responsible for data protection. After creating a record in the versioned table, the Protection Policy of this record changes to Open. Once the record is updated, the Protection Policy field value becomes Changed. These values are transferred to the Record Policy field in the related VCS record, that is, the record version has the same Policy as the record itself.

Admin can update only the Local Pack and Is Strong Overwrite fields of the records with any protection policy.

During the importing process, the records that can be overwritten, can also be updated. Both record policy values set in the system and in the configuration pack are taken into account. All possible policy combinations are described in the table below.

See the Development Recommendations article, to know more about the Record Policy.

Client Company Identification

To enable a client company identification when the update is implemented, a vendor sets a client prefix on the instance. This prefix is added to the names of tables created by the client. This measure eliminates the confusion in case when a client creates a table with a name similar to one created by one of the applications. So the application prefix follows the client prefix. For example, there is a table Work Schedule, that exists in the Simple application (its prefix is sys), and a client (whose prefix is client) creates a table with the same name Work Schedule in the same application. As a result, the client's table name appears as sys_client_work_schedule.

The general table name pattern is:

applicationPrefix_clientPrefix_tableName

To get a client prefix from a table name, use the ss.getTablePrefix() method in your scripts.