| Both sides previous revisionPrevious revisionNext revision | Previous revision |
| 74:versions [2020/11/16 05:05] – aakr | 74:versions [2024/02/15 00:00] (current) – external edit 127.0.0.1 |
|---|
| ====== Create a new version ====== | ====== Manage Process Versions ====== |
| |
| Stages processes can be baselined by using the versioning feature. Navigate to Management > Process version and click or tap on the ''Add Version'' button to create a new version. This baselines the entire workspace. Stages takes you through four steps to accomplish versioning. | Stages processes can be baselined by using the process version feature. A modeler will always be making changes in the [[:general:workingversion|working version]] of the process, while the end users will typically only be shown the baselined [[:general:validversion|valid process version]]. |
| | |
| | ===== Create a new version ===== |
| | |
| | To create a new process verisons, navigate to Management > Process version and click or tap on the ''Add Version'' button to create a new version. This baselines the entire workspace. Stages takes you through four steps to accomplish versioning. |
| |
| **1. Check readiness** | **1. Check readiness** |
| ===== Recommended practices for managing process versions ===== | ===== Recommended practices for managing process versions ===== |
| |
| It is highly recommended to **not set working version as valid**. When a process is newly created, the working version by default is also the valid version. The process should be baselined and marked as valid so that the working version no longer continues to be the valid version. | It is highly recommended to **not set working version as valid**. When a process is newly created, the working version being the only version is set as valid by default. The process should be baselined and marked as valid so that the working version no longer continues to be the valid. |
| | |
| [[https://doc.stagesasaservice.com/lib/exe/fetch.php?tok=3a0ec1&media=https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/74/workingversionasvalid_1.png|{{ https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/74/workingversionasvalid_1.png?direct&800x254 }}]]End users should always view the released baselined process which is the valid version of a process in Stages. If the working version is set as valid, users view the process which is still been updated by modelers and is not ready to be viewed or used. | |
| |
| Another reason to refrain from setting working version as valid is the impact it has on remote associations. During the life of the process (e.g. Change Management), if the working version is set as valid; and the processes it has remote association with have a separate valid and working version, then the remote associations will be linked to working and valid versions separately and appear twice. | {{ https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/74/workingversionasvalid_1.png?direct&800x254 }} |
| |
| {{ https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/74/workingversionasvalidcm.png?direct&900x425 }} | End users should always view the released baseline of the process which is the valid version in Stages. If the working version is set as valid, users view the process which is still been updated by modelers and is not ready to be viewed or used. |
| |
| ===== Import versions or translations ===== | ===== Import versions or translations ===== |