Differences

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

--- 76:manage_process_release [2021/02/19 16:35] – created emr
+++ 76:manage_process_release [2024/02/15 00:00] (current) – external edit 127.0.0.1
@@ Line 1: / Line 1: @@
 ====== Manage Process Release Automations ======
-Todo
+Automations can be used for a varienty of purposes, for example to organize a controlled and documented review and approval of processes or process tailorings.
+Automations consist of states, participants, and the actual automation workflows. As participants can also be used for other purposes, they are [[:76:manage_process_participants|described here]].
+===== Managing States =====
+Every process version has a certain state, e.g. Draft or Released. All possible states can be managed via ''Administration > Process Release > States''.
+[[https://doc.stagesasaservice.com/lib/exe/fetch.php?tok=fe3c63&media=https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/76/states.png|{{  https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/76/states.png?direct&800x414  }}]]
+To add or modify states and their color, click or tap on the state name or use the respective menus.
+[[https://doc.stagesasaservice.com/lib/exe/fetch.php?tok=997a6c&media=https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/76/stateedit.png|{{  https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/76/stateedit.png?direct&600x407  }}]]The different languages can be modified via the selection on the top right.
+In previous Stages versions, those states and their colors were statically defined in configuration files. When upgrading to version 7.6, the configured values are automatically migrated to the new mechanism.
+===== Managing Automations =====
+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''. If you are not able to see those menus, ask your Stages administrator to [[:76:users_groups_permissions|add the respective permissions]].
+A sample process release automation consist of the following steps:
+  * Create a new process version
+  * Send email notifications to the reviewers
+  * Wait for their review to finish
+  * If all reviewers finished their review with "OK"
+      * Release the process version and mark it as valid
+      * Mark the previous valid version as obsolete
+      * Send email notification to all process users
+  * If any of the reviewers finished their review with "NOT OK"
+      * Mark the process version as invalid
+The following video shows how to create this automation in Stages:
+{{ youtube>gGhm3ZIAgKM?large&rel=0 }}
+//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]].
+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.
+//HINT://  to successfully use the "Send E-Mail" automation step, an email server needs to be configured on your server. If you do not receive any emails testing while testing an automation, ask your Stages administrator if this information is correctly configured in the ''<notification>''  section of the ''config.xml''  file.