You are viewing an old version of this page. View the current version.
Compare with Current View Page History
Version 1 Next »
Local packs
Technically, a local pack is a record in the VCS Local Pack (sys_vcs_local_pack) table related to versions of the related records in a VCS Record (sys_vcs_record) table. Every single version is an atomic state of versioned tables (those ones which have the is_VCS_enabled attribute turned ON). All record versions in the local pack are displayed on a related list on a local pack form.
To create a local pack, please complete the steps below:
- Navigate to Configuration → Local Packs.
- Click New and fill in the fields.
- Attach the file you need by clicking the attachments button
.
- Click Save or Save and Exit to apply changes.
VCS Local Pack form fields
Field | Mandatory | Description |
---|---|---|
Origin ID | N | This ID is assigned to the local pack after creating it on a source instance. |
ID | N | This ID is assigned to the local pack after importing. |
Is Default | N | This attribute defines that this local pack will be set as default for any user changing the application to the one specified in the Application field. |
Application | N | Specify an application of which record changes are stored in this local pack. |
State | Y | Local pack state. Available options:
|
Description | N | Local pack description. |
Completed at | N | The date and time when the local pack state changed to Completed. |
Completed by | N | Reference to the user who has set the state to Completed. |
Version restoring
A non-actual version (the is_current attribute value is equal to FALSE) can be restored if needed. To perform this, please complete the steps below:
- Navigate to Configuration → VCS Records.
- Find the record to be recovered. You can use list search for search criteria narrowing, or a Condition Builder.
- Click on a desirable record to open it.
- Click Restore Version.
After that, a new VCS record is created in the current local pack.
You can add a versions list to the versioned table form as a related list. After that, all previous versions of the current record are displayed on the record form.
Default local pack
Default local pack is a local pack named "Default 1" created automatically after creating a new application.
It is not recommended to use the Default 1 local pack to store versions for the purpose of further import to other instances. Create separate packs for these tasks.
If a version has been created in a default local pack erroneously, then you can move it to the required local pack. For this, please complete the steps below:
- Navigate to Configuration → Records.
- Find the record to recover. You can use list search for search criteria narrowing, or a Condition Builder.
- Click on a desirable record to navigate into it.
- Click the magnifier icon on the left of the Local Pack field and choose the required local pack.
- Click Save or Save and Exit to apply changes.
Local Pack Exporting
After you are done with record versions collection within the task implementing, you need to export the changes for further import to other instances. For this, please complete the steps below:
- Navigate to Configuration → Local Packs.
- Find the local pack to export. You can use list search for search criteria narrowing, or a Condition Builder.
- Click on a desirable local pack to navigate into it.
- Change the state value to Completed.
- Open the hamburger menu and navigate to Export → As a New Application.
Recommendations:
- It is a good practice to give a relevant name to the local pack after exporting, for example:
- Good – "New Incident States.sop"
- Bad – "some task.sop", or leaving the name generated by system, like this: 2020-08-06_08-47-19_159654161718816631.sop
- Also, it is recommended to download your local pack straight away after the job is done; otherwise, the versions stored in it may go out of date.
Local Pack Merging
Two local packs can be merged in one if necessary. For this, please complete the steps below:
- Navigate to Configuration → Local Packs.
- Choose local packs you need to merge by selecting the appropriate checkboxes, then click the Merge button.
- Fill in the name and description of the consequent local pack.
- Wait until local packs are merged.
- As a result, a new local pack is created, referenced with the last versions of the VCS Record (sys_vcs_record) for every record.
- Resulting local pack transits into the In Progress state.
- The original local packs are removed.
- If any versions were referenced to original local packs and didn't get into the resulting one, then this reference is reset.
Team Development
In SimpleOne, you can perform your parallel development on multiple instances. For now, team development is represented an an operation approach and is handled by two engines:
- Configuration packs
- Merging.
In brief, in order to facilitate the team development process, you need to perform the steps below:
- Every team member does his work part. It is written down on the instance in the configuration pack.
- When the development is over, these configuration packs must be exported onto the main one and merged.
- After merging, work on collisions if there are some, and after that, the final configuration pack will be the result of the team development.
- No labels