Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
76:manage_process_release [2021/02/25 04:18] – emr | 76: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, | + | To create and modify automations, |
- | If your system has been upgraded from a previous Stages | + | A sample process release automation consist of the following steps: |
+ | |||
+ | * Create | ||
+ | * Send email notifications to the reviewers | ||
+ | * Wait for their review to finish | ||
+ | * If all reviewers finished their review with " | ||
+ | * Release the process | ||
+ | * 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> | ||
+ | |||
+ | // | ||
+ | |||
+ | You can also use the predefined {{:76: | ||
+ | |||
+ | Of course, the Stages consultants are also happy to help with process automations. | ||
+ | |||
+ | // | ||