Differences

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

--- 78:manageprocessversions [2022/01/14 20:29] – aakr
+++ 78:manageprocessversions [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 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]].
+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 9: / Line 9: @@
 **1. Check readiness**
-Several process readiness checks are executed in parallel. See [[:72/consistency|]] for more info.
+Several process readiness checks are executed in parallel. See [[:72:consistency|]] for more info.
 If you are not interested to see the results, for example for a backup version, you can skip the readiness checks.
@@ Line 27: / Line 27: @@
 A short summary of the version creation is shown here.
-===== Recommended practices for managing process versions =====
+===== Managing Working and Valid process versions =====
-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.
+It is highly recommended to **not set working version as valid **//(Exception: reference models, see next chapter below).//
-[[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}}]]
+When a new process is created in an empty workspace, only working version would exist which would have become valid version by default. However, to avoid working version from been marked as valid for a new process, Stages automatically creates an additional empty valid version “V0”. Moreover, end users will now see the empty valid version instead of the unreleased working version, until a new valid version is officially released. This prevents modelers from accidentially revealing information that should not be shown to end users yet.
-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/plugins/ckgedit/fckeditor/userfiles/image/78/v0_1.png?nolink&800x467  }}
+In a scenario, where the working version is explicitely made the the valid version, two versions show up in the version selection as follows:
+{{  https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/78/workingasvalid_5.png?nolink&800x464  }}
+If the valid working version is selected, it will be treated like all other versions, e.g. modeling is not possible. When process interfaces are followed to other workspaces, the interface will point to the valid version of the other workspace. If the non-valid working version is being selected, the interfaces will point to the working versions of the other workspaces.
+===== Versioning of reference models =====
+Reference models like Automotive SPICE should **__not be versioned__**  . If you need to create a version of a reference model, make sure to **set Working Version as the Valid Version**. If the working version is not the valid version, it will not be possible to create or modify compliance mappings.
 ===== Import versions or translations =====
@@ Line 41: / Line 50: @@
 [[https://doc.stagesasaservice.com/lib/exe/fetch.php?tok=fa07f8&media=https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/74/importversion.png|{{https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/74/importversion.png?direct&800x368}}]]
-Process content that was translated via an automated translation system can also be imported here by using the ''Import translation'' operation. See [[:74/import_translation|]] for more details.
+Process content that was translated via an automated translation system can also be imported here by using the ''Import translation'' operation. See [[:74:import_translation|]] for more details.
 ===== How to roll back the Working Version to a previous version =====