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:manage_process_release [2021/02/25 05:37] – emr76:manage_process_release [2024/02/15 00:00] (current) – external edit 127.0.0.1
Line 21: Line 21:
 Automations can be defined for multiple purposes, e.g. for a simple process release, for a more complex review and approval, or for approval of a process tailoring. Automations can be defined for multiple purposes, e.g. for a simple process release, for a more complex review and approval, or for approval of a process tailoring.
  
-To create and modify automations, go to ''Administration > Process Release > Automations''.+To create and modify automations, go to ''Administration > Process Release > Automations''. If you are not able to see those menus, ask your Stages administrator to [[:76:users_groups_permissions|add the respective permissions]].
  
-Every automation consists of a series of steps with transitions between them. +A sample process release automation consist of the following steps:
- +
-For example, a simple process release could consist of the following steps:+
  
   * Create a new process version   * Create a new process version
-  * Set its state to "Under Review" 
   * Send email notifications to the reviewers   * Send email notifications to the reviewers
   * Wait for their review to finish   * Wait for their review to finish
   * If all reviewers finished their review with "OK"   * If all reviewers finished their review with "OK"
-      * Release the process version +      * Release the process version and mark it as valid 
-      * Set the previous process version into "Obsolete" state+      * Mark the previous valid version as obsolete
       * Send email notification to all process users       * Send email notification to all process users
   * If any of the reviewers finished their review with "NOT OK"   * If any of the reviewers finished their review with "NOT OK"
-      * Set the process version to "Invalid" +      * Mark the process version as invalid
-      * Send email notification to process owner +
- +
-The following video shows how to create an automation that implements this process release.+
  
-TODO: video+The following video shows how to create this automation in Stages:
  
-HINT: if you are unable to watch the video directly, you can [[https://www.methodpark.com|download it from the Method Park website]].+{{ youtube>gGhm3ZIAgKM?large&rel=0 }}
  
-You can also use the predefined "Review and Approval" automation to build your own automation.+//HINT://  if you are unable to watch the video via YouTube, you can [[https://public.methodpark.de/videos/HowToCreateSimpleProcessReleaseAutomation.mp4|download it from the Method Park website]].
  
-If your system has been upgraded from a previous Stages version and does not contain any pre-defined automations yet, you can download the [[:76:reviewandapproval.xml?media=76:reviewandapproval.xml|sample "Review and Approval" 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.+You can also use the predefined {{:76:reviewandapproval.xml|sample "Review and Approval" automation}}  (click right and select "Save Link As" or similar) to build your own automation. To import, log in with administrative access, go to ''Administration > Process Release > Automations''  and click or tap ''…''  in the top right corner. Then select ''Import''  and upload the sample automation.
  
 Of course, the Stages consultants are also happy to help with process automations. Of course, the Stages consultants are also happy to help with process automations.