The Version Control System by SimpleOne is a built-in engine that enables the users to track and fix changes to the business logic implemented by the platform tools. The business logic of the platform is implemented with the configuration records including business rules, client scripts, ACLs, form views, etc.
Each configuration record has at least one snapshot, a VCS record that contains all the up-to-date information about the configuration record at the time the version snapshot was created. Any change to a configuration record generates a new, actual version of this record, while all the old versions are preserved.
The changes to configuration records that have been saved and packed in packages can be transferred between different instances of the platform. During the pre-check before importing a retrieved package, you may receive notifications about possible errors and collisions, which also contain recommendations for solving the problems occurred. Thanks to this, the application of the received packages to the current instance or their migration is safe for the system.
All the aspects above guarantee the portability of applications and the absence of errors when updating them and the entire platform.
The articles below provide all the information you need to get started with version control system and configuration package management.
This article provides general guidelines for getting started with creating new applications and use of configuration packages. In particular, it also describes the VCS record naming policy and the security policy.
In this article, read the basic information about the VCS record storage and interaction with the VCS records in terms of protection policy and client activity. The article also describes the differentiation of the changes made by the client and the system.
This set of articles gives a quick guide on creating an application, completing a local pack, and migration recommendations.
This set of articles describes the whole and precise process of working on a local pack—from assembling to implementing it on different instances. It also describes the ways to avoid or manage all possible collisions, and the rollback option.
