Stages Documentation

Differences

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

Link to this comparison view

712:manageprocessversions [2025/09/15 14:55] – created - external edit 127.0.0.1712:manageprocessversions [2026/01/23 18:01] (current) – Meier, Erich
Line 9: Line 9:
 **1. Check readiness** **1. Check readiness**
  
-Several process readiness checks are executed in parallel. See [[:712:consistency|]] for more info.+Several process readiness checks are executed in parallel. See [[:712: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. If you are not interested to see the results, for example for a backup version, you can skip the readiness checks.
Line 17: Line 17:
 Enter the name and state of the new version here. To mark the new version as valid, set the respective switch. Enter the name and state of the new version here. To mark the new version as valid, set the respective switch.
  
-[[https://doc.stagesasaservice.com/lib/exe/fetch.php?tok=a649fb&media=https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/72/addversion.png|{{https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/72/addversion.png?direct&800x409}}]]+[[https://doc.stagesasaservice.com/lib/exe/fetch.php?tok=a649fb&media=https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/72/addversion.png|{{https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/72/addversion.png?800x409}}]]
  
 **3. Create version** **3. Create version**
Line 33: Line 33:
 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. 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.
  
-{{  https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/78/v0_1.png?nolink&800x467  }}+{{ https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/78/v0_1.png?800x467&nolink }}
  
 In a scenario, where the working version is explicitely made the the valid version, two versions show up in the version selection as follows: 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  }}+{{ https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/78/workingasvalid_5.png?800x464&nolink }}
  
 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. 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.
Line 44: Line 44:
  
 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. 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 ===== ===== Import versions or translations =====
  
 ZIP files created via the ''Export'' operation can be imported into Stages. The imported content replaces the current working version. If the current working version is not empty, a ''Backup working version'' is being created before the import. ZIP files created via the ''Export'' operation can be imported into Stages. The imported content replaces the current working version. If the current working version is not empty, a ''Backup working version'' is being created before the import.
  
-[[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}}]]+[[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?800x368}}]]
  
-Process content that was translated via an automated translation system can also be imported here by using the ''Import translation'' operation. See [[:712: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 [[:712:import_translation]] for more details.
  
 ===== How to roll back the Working Version to a previous version ===== ===== How to roll back the Working Version to a previous version =====
Line 56: Line 57:
 Open the menu of the process version you would like to roll back to. Then select ''Replace Working Version.'' Open the menu of the process version you would like to roll back to. Then select ''Replace Working Version.''
  
-[[https://doc.stagesasaservice.com/lib/exe/fetch.php?tok=a995ef&media=https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/74/replaceworkingversion_1.png|{{https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/74/replaceworkingversion_1.png?direct&800x391}}]]+**WARNING: this operation rolls back ALL changes in a workspace!** 
 + 
 +[[https://doc.stagesasaservice.com/lib/exe/fetch.php?tok=a995ef&media=https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/74/replaceworkingversion_1.png|{{https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/74/replaceworkingversion_1.png?800x391}}]]