Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
With local packs, it is possible to continue the development of application configurations on a separate collect all the necessary configuration changes in the same place and transfer them to another instance. Export it as a .SOP file, and implement changes to the production instancethe local pack and add it to the Retrieved Packs (sys_vcs_retrieved_pack) table of the target instance. When the pack is loaded, a new local pack is created on that instance. This local pack contains the imported from the first instance settings. This approach minimizes the risks of mistakes, errors, and conflicts , which that may affect the production instance during the application development.
Note |
---|
All system configuration activities should be performed within a separate local pack. Do not use the default local pack for these needs. |
A local pack is a record in the VCS Local Pack (sys_vcs_local_pack) table compiling relevant and it compiles relevant to the configuration changes done records from the VCS Record (sys_vcs_record) table. Use it local packs to associate VCS records with a particular pack and export them as a complete set.
Note |
---|
Only users with the admin role can:
|
Every single version is an atomic state of the versioned tables (those having the Is VCS Enabled checkbox selected). All records in this table contain JSON formatted changes and other attributes described below.
Code Block | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
{"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} |
Application configurations are stored in configuration packs represented as a .SOP file. Administrators can create their own applications if needed.
Tip |
---|
There can be more than one local pack in the system, but the changes made by a single source , for example, within a specific task can be written saved only in one the local pack that is selected in the Admin Preferences menu at the right. That is, if the selected local pack is Default 3, all changes will be stored in the Default 3 pack. |
All On the form of the local pack, all the record versions in a local pack are displayed in the VCS Record related list.
Info |
---|
In the Admin Preferences menu, select the local pack that you are working going to work on. This local pack will be saved as preferred: if you switch between the applications, this pack will be selected automatically . for this application. Only If the preferred local pack has a in state other than In Progress can be selected as preferred. Once the state changes, the local pack will switch prefered pack in the Admin Preferences menu switches to the default one for this app. |
Tip |
---|
If there is no need to assemble a separate local pack to export, all record versions will can be compiled into stored in the default local pack. The default pack can also contain the VCS records moved from the developing local pack (other local packs that are in the In Progress state, for example, when some records were created or moved to the local pack by mistake). |
VCS Records Anchor VCS records VCS records
VCS records | |
VCS records |
Use configuration packs to monitor changes in particular records.
After any transaction action (create/, update/, or delete) for the on a versioned table object, a record is created in the VCS Records (sys_vcs_record) table corresponding to for this object. The records displayes the state of the object state after the transactionaction was done. The record version contains the information described below.
Note |
---|
|
Tip | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
Note that removing of a record does not mean its 'deletion': the removed records are stored in the default local pack. If a local pack includes unwanted VCS records, move them to the default pack by completing the following steps:
As a result:
|
Restoring VCS Records
All the record versions – , both previous and current – , are stored in the VCS Record table. Current versions have the Is Current checkbox selected.
To restore one of the record from previous versions, complete the steps below:
- Open a record that you need to restore to a particular version.
- Scroll down to the Related Lists area and open the VCS Records tab.
- Open the record version you need to restore.
- Click Restore Version.
Info |
---|
Another way to restore a record version is the following:
|
After that, a new VCS record is associated with the current local pack . It is and displayed in the its VCS Records related list.
Info |
---|
Some forms may not display the VCS Records related list by default. You But you can add it to the versioned table form as a related liston your own. After that, all versions (previous and current) of the current record are will be displayed on the record form. To add a VCS Record related list, do the following:
|
Table of Contents |
---|
...