Differences

This shows you the differences between two versions of the page.

--- 74:versions [2020/11/18 20:50] – aakr
+++ 74:versions [2024/02/15 00:00] (current) – external edit 127.0.0.1
@@ Line 1: / Line 1: @@
 ====== Manage Process Versions ======
-Stages processes can be baselined by using the versioning feature.
+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 =====
@@ Line 29: / Line 29: @@
 ===== 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.
+{{  https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/74/workingversionasvalid_1.png?direct&800x254  }}
-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 (e.g. Requirements Management) it has remote associations with have a separate valid and working version, then the remote associations will be linked to working and valid versions separately and appear twice.
+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.
-[[https://doc.stagesasaservice.com/lib/exe/fetch.php?tok=982af9&media=https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/74/workingversionasvalidcm_1.png|{{  https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/74/workingversionasvalidcm_1.png?direct&900x425  }}]]'Analyze Change Request' ''activity'' uses 'Functional Specification' ''work product'' as an input through remote association as this ''work product'' belongs to Requirements Management. Requirements Management has a separate working version and valid version. Thereby making the remote association link to each version separately and showing twice.
-[[https://doc.stagesasaservice.com/lib/exe/fetch.php?tok=9c89e3&media=https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/74/workingasvalidissue_1.png|{{  https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/74/workingasvalidissue_1.png?direct&800x365  }}]]
-If Change Management continues to have working as valid version, it can lead to some unintended consequences. One, end users will find this confusing and not know which input to refer back to. Secondly, a modeler might manually choose to delete on the duplicates. In this case, if the input without the V (i.e. the one linking back to working version) is deleted and later Change Management process is released and marked valid, then the working version will no longer have the remote association as it was previously deleted. This might potentially introduce an error in working and future baselined version of missing remote associations.
 ===== Import versions or translations =====