With local packs, it is possible to you can collect all the necessary configuration changes in the same one place and transfer them to another instance. Export the 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 settings imported from the first instance settings. This approach minimizes the risks of mistakes, errors, and conflicts that may affect the production instance during the application development.
| Note |
|---|
All Perform all system configuration activities should be performed within a separate local pack. Do not Never use the default local pack for these needs of the application for this purpose. |
A local pack is a record in the VCS Local Pack (sys_vcs_local_pack) table, and it compiles relevant to the configuration changes done records from the the VCS Record (sys_vcs_record) table related to the configuration changes. Use local packs to associate VCS records with a particular specific 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 a versioned tables table (those having that has 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 that can be exported 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, for example, within a specific task can only be saved only in the local pack that is selected pack selected in the Admin Preferences menu at the right. That is, if the selected Default 3 local pack is Default 3selected, all changes made by the current user will be stored in the Default 3 pack.
|
On the form of the local pack, all the record versions are displayed in the VCS RecordRecords related list.
| Info |
|---|
In theAdmin Preferencesmenu, select the local pack that you are going need to work on. This local pack will be saved as the preferred one: if you switch between the applications, this pack will be automatically selected automatically for this the application. Only a local pack in the In progress state In Progress can be selected as the preferred one. Once the state changes, the prefered preferred pack in the Admin Preferences menu switches to the default one for this appthe application. |
VCS Local Pack form fields
| Field | Mandatory | Description |
|---|---|---|
| Name | Y | The name of the local pack. |
| Is default | N | Select this checkbox to set the local pack as default. When you work on the selected application, all changes will ba saved to this local pack unless another local pack is selected in the Admin Preferences → Local Pack. |
| State | Y | The local pack states. Available options:
|
| Application | N | Select the application that this local pack belongs to. A local pack contains only those records that belong to the same application. |
| Description | N | Add a description for the local pack. |
| Tip |
|---|
If there is no need to assemble a separate local pack to export, all record versions can be stored in the default local pack. The default pack can also contain the VCS records moved from other local packs that are in the In Progressprogress 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 specific records.
After any action (create, update, or delete) on a an object of any versioned table object, a record is created for that object in the VCS Records (sys_vcs_record) table for this object. The records displayes display the state of the object after the action 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 Removed records are not deleted, they are stored in the default local packpacks. If a local pack includes unwanted VCS records, move them to the default pack by completing the following steps:
As a result:
|
Restore VCS Records
All the record versions, both previous and current, are stored in the VCS Record table. Current The current versions have the Is Current checkbox selected.
To restore one of the record from previous versions of a record, complete the steps below:
- Open a the record that you need to restore to a particular version.
- Scroll down to the Related Lists area and open the VCS Records In the Related Lists area, select the VCS Records tab.
- Open the record version you need to restore.
- Click Restore Versionversion.
| Info |
|---|
Another way to restore a record version is the following:
|
After that, a new VCS record is associated with the current local pack and displayed in its VCS Records related list.
| Info |
|---|
Some forms may not display the VCS Records related list by default. But you can add it to the versioned table form on your own. After that, all versions (previous and current) of the current record will be displayed on the record form. To add a VCS RecordRecords related list, do the following:
|
| Table of Contents | ||||||
|---|---|---|---|---|---|---|
|