Stages Documentation

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
77:releasenotes [2021/07/14 22:53] – emr77:releasenotes [2024/02/15 00:00] (current) – external edit 127.0.0.1
Line 45: Line 45:
 Before version 7.7, interfaces were shown between process versions with the same name. This capability has been removed. Before version 7.7, interfaces were shown between process versions with the same name. This capability has been removed.
  
-===== Scheduled process releases =====+===== Scheduled Process Releases =====
  
 Some process changes should be made effective at a specific date, e.g. at the first day of a month. With Stages 7.7, the release automations can be configured so reviewers and/or approvers can set a specific date and time when the process will be released and marked as valid. Some process changes should be made effective at a specific date, e.g. at the first day of a month. With Stages 7.7, the release automations can be configured so reviewers and/or approvers can set a specific date and time when the process will be released and marked as valid.
Line 55: Line 55:
 [[https://doc.stagesasaservice.com/lib/exe/fetch.php?tok=53cdc6&media=https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/77/77-schedulereleasedate2.png|{{  https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/77/77-schedulereleasedate2.png?direct&800x694  }}]]When the automation is being executed, the respective participants can then either select the date and time when the release should take place or select "After automation has finished" to immediately release the process. [[https://doc.stagesasaservice.com/lib/exe/fetch.php?tok=53cdc6&media=https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/77/77-schedulereleasedate2.png|{{  https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/77/77-schedulereleasedate2.png?direct&800x694  }}]]When the automation is being executed, the respective participants can then either select the date and time when the release should take place or select "After automation has finished" to immediately release the process.
  
-===== Value streams are available by default =====+===== Value Streams are available by Default =====
  
-The value stream mapping capabilities that have been introduced in previous releases are now available in each new Stages installation. To enable value streams, select the "Unified Configuration (with Value Streams)" metamodel under ''Management > Settings''.+Value streams are a method to manage cross-functional and cross-organizational activities and provide macro views of a process landscape. 
 + 
 +The value stream mapping capabilities that have been introduced in previous Stages releases are now available in each installation. To enable modeling value streams, select the "Unified Configuration (Value Streams)" metamodel under ''Management > Settings''.
  
 [[https://doc.stagesasaservice.com/lib/exe/fetch.php?tok=cee097&media=https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/77/77-valuestreams.png|{{  https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/77/77-valuestreams.png?direct&800x219  }}]] [[https://doc.stagesasaservice.com/lib/exe/fetch.php?tok=cee097&media=https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/77/77-valuestreams.png|{{  https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/77/77-valuestreams.png?direct&800x219  }}]]
Line 63: Line 65:
 If you have a customized metamodel version, please contact your respective product consultants for more info. If you have a customized metamodel version, please contact your respective product consultants for more info.
  
-===== Compliance overview report =====+===== Compliance Overview Report =====
  
 A new report has been added that can be run from a reference model workspace to provide an overview of all mappings and coverage across all workspaces where that reference model has been mapped. A new report has been added that can be run from a reference model workspace to provide an overview of all mappings and coverage across all workspaces where that reference model has been mapped.
Line 71: Line 73:
 As the report shows both the coverage and the number of mappings for a particular standard requirement, it is also useful to detect mappings that have been created, but not rated for a specific coverage yet. As the report shows both the coverage and the number of mappings for a particular standard requirement, it is also useful to detect mappings that have been created, but not rated for a specific coverage yet.
  
-If you are upgrading from a previous version, you can {{:77:complianceoverview.rptdesign|download the report here}}  //(download via left-click and "Save as")//.+If you are upgrading from a previous version, you can [[:reports:start#compliance-overview|download the report here]]. 
 ===== Process Feedback in Codebeamer ===== ===== Process Feedback in Codebeamer =====
  
Line 110: Line 113:
 </code> </code>
  
-===== Support for feedback issue collectors =====+===== Support for Feedback Issue Collectors =====
  
 We added the new [[:77:process_feedback_link|feedback system link]]. A stages user who wants to give feedback will be directed to a issue collector page of the specific feedback system. The user will see a form with some fields filled out beforehand by Stages. We added the new [[:77:process_feedback_link|feedback system link]]. A stages user who wants to give feedback will be directed to a issue collector page of the specific feedback system. The user will see a form with some fields filled out beforehand by Stages.
Line 126: Line 129:
   * The access to PDF exports can now be controlled via its own security domain. While upgrading to version 7.7, all users with process read permissions are automatically given this new permission.   * The access to PDF exports can now be controlled via its own security domain. While upgrading to version 7.7, all users with process read permissions are automatically given this new permission.
   * The Y scales in the user activity statistics under ''Administration''  have been switched for better readability.   * The Y scales in the user activity statistics under ''Administration''  have been switched for better readability.
 +  * The "Phases" switch in the Flow visualization has been disabled by default. As most clients are using multiple lifecycles (= phase models), it has lost its usefulness and showed incorrect information. If you would like the switch to be re-enabled, please contact your consultant.
  
 ===== End of Life for CMMI in Stages ===== ===== End of Life for CMMI in Stages =====