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
76:releasenotes [2021/02/25 03:53] – emr76:releasenotes [2024/02/15 00:00] (current) – external edit 127.0.0.1
Line 23: Line 23:
 Any user can participate in a review or approval step. Any user can participate in a review or approval step.
  
-If your system has been upgraded from a previous Stages version and does not contain any pre-defined automations yet, you can download //**a sample automation here**//  . To import, log in with administrative access, go to ''Administration > Process Release''  and click or tap ''…''  in the top right corner. Then select ''Import''  and upload the sample automation.+A sample automation for a process review followed by an approval could look like this:
  
 [[https://doc.stagesasaservice.com/lib/exe/fetch.php?tok=ce69ae&media=https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/76/releaseautomation.png|{{  https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/76/releaseautomation.png?direct&800x482  }}]] [[https://doc.stagesasaservice.com/lib/exe/fetch.php?tok=ce69ae&media=https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/76/releaseautomation.png|{{  https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/76/releaseautomation.png?direct&800x482  }}]]
Line 41: Line 41:
 ===== Process Execution* ===== ===== Process Execution* =====
  
-To assure that processes are actually applied in practice, the defined process activities need to be planned, executed and monitored. The latter typically happens in task management tools (also known as Application Livecycle Management or ALM) like Atlassian Jira or IBM Engineering Workflow Management (formerly known as Rational Team Concert or RTC).+To assure that processes are actually applied in practice, the defined process activities need to be planned, executed and monitored. The latter typically happens in task management tools (also known as Application Lifecycle Management or ALM) like Atlassian Jira or IBM Engineering Workflow Management (formerly known as Rational Team Concert or RTC).
  
 With Stages version 7.6, modelers can extend the processes that should be executed with the new “activator” elements and deploy the resulting executable models directly into those task management tools. With Stages version 7.6, modelers can extend the processes that should be executed with the new “activator” elements and deploy the resulting executable models directly into those task management tools.
  
-{{  https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/76/stages-alm-integration.png?direct&600x406  }}+[[https://doc.stagesasaservice.com/lib/exe/fetch.php?tok=9a2b21&media=https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/76/stages-alm-integration.png|{{  https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/76/stages-alm-integration.png?direct&600x406  }}]]
  
 In contrast to BPMN and similar modeling techniques, the business process logic can be separated from the technical task execution and platform details. With the Stages approach, the same process can be executed in Jira in one project and IBM Engineering Workflow Management in a different project, each with its individual tailoring. Both processes can be derived from the same organizational standard process, which assures compliance with all required standards and reference models. In contrast to BPMN and similar modeling techniques, the business process logic can be separated from the technical task execution and platform details. With the Stages approach, the same process can be executed in Jira in one project and IBM Engineering Workflow Management in a different project, each with its individual tailoring. Both processes can be derived from the same organizational standard process, which assures compliance with all required standards and reference models.
  
-Stages comes with different predefined activator types. The "Step-by-step" activator executes all activities in a workflow sequentially as defined by the predecessor/successor relationships. The "All-at-once" activator creates all tasks of a workflow in one step. Users with the respective permissions can start those process executions directly from Stages. Alternatively, they can also be triggered by an action in the task management system. The technical execution can also be scripted for maximum flexibility. All process execution elements can be found under ''Management > Execution''. If you need help to exploit the full power of the new process execution capabilities, please contact your Stages product consultant.+Stages comes with different predefined activator types. The "Step-by-step" activator executes all activities in a workflow sequentially as defined by the predecessor/successor relationships. The "All-at-once" activator creates all tasks of a workflow in one step. Users with the respective permissions can start those process executions directly from Stages. Alternatively, they can also be triggered by an action in the task management system. The technical execution can also be scripted for maximum flexibility. 
 + 
 +See [[:76:process_execution|here for more info]]. If you need help to exploit the full power of the new process execution capabilities, please contact your Stages product consultant.
  
 ===== Workspace Collections ===== ===== Workspace Collections =====