| Tip |
|---|
Role required: admin. |
Concept
...
In short, the VCS configuration pack provides version control in SimpleOne. Version control system allows:
...
For example, your team has created a new application on the development instance. Instead of copying scripts and recreating all elements one by one manually, they assemble a configuration pack and import it to the production instance. While importing this pack into the target instance, the system checks changes for possible collisions. This way, you can make sure that these changes work fine.
Configuration pack flow
...
Good practice is to develop new applications and implement changes into existing ones on a separate instance. This will lessen mistakes and risks for everyday processes on the production instance. Therefore, VCS records should be collected into one local pack within the relevant application.
The configuration management involves two main processes:
- Export – collecting Configuration PacksVCS records into a local pack on Instance #1, the result of which is a Local Pack in the Completed state and a .SOP file.
- Import – uploading and deployment of the previously prepared configuration pack on Instance #2.
...
Local packs Anchor local pack local pack
| local pack | |
| local pack |
...
Local packs allow the development of application configurations on a separate instance, exporting it as a .SOP file, and implementing changes to the production instance. This approach minimizes the risks of mistakes, errors, and conflicts, which may affect the production instance during application development.
| Note |
|---|
All system configuration activities should be performed within a separate local pack. Do not use the Configuration Packs default local pack for these needs. |
Local pack is a record in the VCS Local Pack (sys_vcs_local_pack) table compiling relevant records from the VCS Record (sys_vcs_record) table. This allows associating VCS records with a particular pack and exporting them as a complete set.
...
Every single version is an atomic state of versioned tables (those ones which have 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} |
...
| Tip |
|---|
If there is no need in assembling a separate local pack for export, all record versions will be compiled into the Configuration Packsdefault local pack. The default pack can also contain VCS records moved from developing local pack (for example, created by mistake). |
Local packages
...
Retrieved packages
...