Change
Storagestorage and VCS records
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.
| Note |
|---|
Remember: |
|---|
- VCS records cannot be created, updated, or deleted manually. These records are created automatically by the system. Only users with the admin role can read them.
- Admin can also edit the Local Packpack and Is Strong Overwritestrong overwrite fields.
|
VCS Record form fields
NameSystem The system name of the target record table. |
Record IDUnique| The unique ID of the source record processed by the transaction. |
| Document |
RecordThe target table ID and | record | A reference to the target record |
ID for which the current VCS record is created. |
| JSON |
Copy| copy | This field stores target record attributes in JSON format as an associative |
massivearray. | Code Block |
|---|
| language | js |
|---|
| theme | Eclipse |
|---|
| title | Example |
|---|
| {"value": "Report Item", "policy": "Open", "sys_id": 159653803414986194, "column_id": 156941403909472422, "record_id": 159653803414985080, "language_id": 156628684306541141, "application_id": 155931135900000002, "sys_created_at": "2020-08-04 10:47:14", "sys_created_by": 155931135900000001, "sys_updated_at": "2020-08-04 10:47:14", "sys_updated_by": 155931135900000001} |
|
| Is |
CurrentSelect this checkbox to make this version | This checkbox is selected if the version is current. |
| Created by | The user who did the change. |
| Created at |
Date | The date and time of the record creation. |
| Local |
Pack| pack | The local pack that contains this record. |
| Retrieved |
Pack| pack | The Retrieved pack to which this record is related to. |
| Restored by | A unique ID of the version record from which the current record was restored. |
| Action | Action type. Available options: |
| Record |
Policy| policy | Current record protection policy after the transaction is over. Available options: |
| Is |
Strong Overwrite| strong overwrite | When the checkbox is selected, the current record will be written over the existing version with the Protected policy. |
All the changes are stored in the local pack selected in the Local pack field of the Admin preferences menu. You can also set the local pack as current on the form of that pack. To know learn more, see Managing VCS recordsin theAssembling Local Packsarticle.
It is also possible The VCS records can also be imported from another instance. See the Importing Configuration Packages article to learn how to import and preview the imported VSC records, find more information in theImporting Configuration Packagesarticle.
Protection
Policy policy
The Protection Policy policy attribute is responsible for data protection. After creating a new record is created in the a versioned table, the Protection Policy of this record changes its Protection policy is set to Open. Once the record is updated, the Protection Policy field value becomes Changed. These values are transferred to the Record Policypolicy field in the related VCS record, that is, the record version has the same Policy as the record itself.
Admin can only update only the the Local Packpack and Is Strong Overwritestrong 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.
Protection Policy| protection policy | Target record |
|---|
Protection Policy| protection policy | Result |
|---|
Protected
| Protected | Success |
| Open | Success |
| Changed | Success |
Changed
| Protected | Failed. Use Strong |
Overwrite| overwrite to proceed. |
| Open | Success |
| Changed | Success |
Open
| Protected | Failed. Use Strong |
Overwrite Overwrite See the Development Recommendationsarticle, to know more about the Record Policy.
Client
Company Identificationcompany 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 the one created by one of the applicationsexisting in the application by default. 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:
| Code Block |
|---|
applicationPrefix_clientPrefix_tableName |
To get a client prefix from a table name, use the ss.getTablePrefix()method in your scripts.