Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
76:process_execution [2021/02/25 09:08] – mir | 76:process_execution [2024/02/15 00:00] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== Model and Manage Process Execution ====== | ====== Model and Manage Process Execution ====== | ||
- | Find technical details for the Process execution systems | + | The principal idea of the Stages Process Execution concept is to use process information in Application Lifecycle Management (ALM) Systems to work process compliant and to automate workflows. |
+ | |||
+ | Find technical details for the ALM Systems | ||
[[: | [[: | ||
- | [[: | + | [[: |
- | ===== General concept ===== | + | === Model Execution in Stages |
- | The principal idea of the Stages | + | In Stages |
Hence it is possible to attach execution information only to parts of a process, it can be taken into execution selectively. | Hence it is possible to attach execution information only to parts of a process, it can be taken into execution selectively. | ||
Line 17: | Line 19: | ||
The Process space contains the process elements like activities, roles, work products etc. The Execution space contains elements like Activators, Execution Properties and Execution Scripts. Both spaces are part of a process version, so that also the execution information is subject of versioning. | The Process space contains the process elements like activities, roles, work products etc. The Execution space contains elements like Activators, Execution Properties and Execution Scripts. Both spaces are part of a process version, so that also the execution information is subject of versioning. | ||
- | ===== How to use ===== | + | === Run Execution in ALM Systems |
- | Top level steps to use the Stages Process Execution are: | + | After exporting the Stages Process into the ALM System, the System has access to process and execution elements. This leads to the advantage that events (like saving or changing the state) from within the System can run automation and follow the process. |
+ | |||
+ | Also Stages is capable of triggering such events in the Workflow Management System with the Executable-Activator. | ||
+ | |||
+ | |||
+ | ===== How to start with Execution ===== | ||
+ | |||
+ | Top level steps to use the Stages Process Execution | ||
* activate execution configuration in config.xml | * activate execution configuration in config.xml | ||
- | * equip your process with execution information | + | * equip your process with Execution Activators |
* create a process version and set this as valid version | * create a process version and set this as valid version | ||
- | * export the process to the Excution | + | * export the process to the ALM system |
- | After export your Process execution will work in the Execution | + | After export your Process execution will work in the ALM system and you can use Stages to run the Executable |
===== Concept Example ===== | ===== Concept Example ===== | ||
Line 40: | Line 49: | ||
===== Activate Execution configuration in config.xml ===== | ===== Activate Execution configuration in config.xml ===== | ||
- | You have to activate process execution by adding the execution | + | You have to activate process execution by adding the ALM system type to the config.xml. You can choose to activate |
<code xml> | <code xml> | ||
Line 49: | Line 58: | ||
</ | </ | ||
</ | </ | ||
+ | |||
</ | </ | ||
+ | It’s recommended to add server configuration information: | ||
+ | |||
+ | <code xml> | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | </ | ||
+ | </ | ||
+ | </ | ||
+ | |||
+ | </ | ||
===== Process execution Elementtypes ===== | ===== Process execution Elementtypes ===== | ||
Line 58: | Line 81: | ||
==== Step-by-step Activator ==== | ==== Step-by-step Activator ==== | ||
- | The purpose of the step-by-step-Activator is to execute a workflow | + | The purpose of the step-by-step-Activator is to execute a workflow |
The Activator is reactive, meaning that it gets into action when an execution object of type “issue Type” changes state from “Start State” to “End State”. This triggers the creation of the execution object for the first activity. This is created with type “Children Issue Type” | The Activator is reactive, meaning that it gets into action when an execution object of type “issue Type” changes state from “Start State” to “End State”. This triggers the creation of the execution object for the first activity. This is created with type “Children Issue Type” | ||
Line 68: | Line 91: | ||
=== Attributes === | === Attributes === | ||
- | Issue Type: defines the type of execution object which represents the workflow | + | **Issue Type**: defines the type of execution object which represents the workflow |
- | Start State & End State: defines the state transition from start to end state for which the activator is triggered (the first child Execution Object is created) | + | **Start State & End State**: defines the state transition from start to end state for which the activator is triggered (the first child Execution Object is created) |
- | Parent Next State: defines the state of the execution object which represents the workflow when all children are in end state (e.g. the workflow is finished) | + | **Parent Next State**: defines the state of the execution object which represents the workflow when all children are in end state (e.g. the workflow is finished) |
- | Bound-to-process: | + | **Bound-to-process**: indicates whether this activator triggers for every Execution Object of type “Issue Type” (bound to process = false) or only when the Process Element is associated to the Execution Object (bound to process = true). |
- | Children Issue Type: defines the type of execution object a child-element is created with | + | **Children Issue Type**: defines the type of execution object a child-element is created with |
- | Children Issue Initial State: defines the state of execution object a child-element is created with (RTC only) | + | **Children Issue Initial State**: defines the state of execution object a child-element is created with (RTC only) |
- | Children Start State & Children End State: defines the state transition from start to end state for which a child is to be considered as done and the next child is created | + | **Children Start State & Children End State**: defines the state transition from start to end state for which a child is to be considered as done and the next child is created |
- | XXX State is a group: defines whether the given state is the name of a single state or a state group (RTC only) | + | **State is a group**: defines whether the given state is the name of a single state or a state group (RTC only) |
==== All-at-once Activator ==== | ==== All-at-once Activator ==== | ||
Line 96: | Line 119: | ||
=== Attributes === | === Attributes === | ||
- | Issue Type: defines the type of execution object which represents the workflow | + | **Issue Type**: defines the type of execution object which represents the workflow |
- | Start State & End State: defines the state transition from start to end state for which the activator is triggered (the children Execution Objects are created) | + | **Start State & End State**: defines the state transition from start to end state for which the activator is triggered (the children Execution Objects are created) |
- | Bound-to-process: | + | **Bound-to-process**: indicates whether this activator triggers for every Execution Object of type “Issue Type” (bound to process = false) or only when the Process Element is associated to the Execution Object (bound to process = true). |
- | Children Issue Type: defines the type of execution object a child-element is created with | + | **Children Issue Type**: defines the type of execution object a child-element is created with |
- | Children Issue Initial State: defines the state of execution object a child-element is created with (RTC only) | + | **Children Issue Initial State**: defines the state of execution object a child-element is created with (RTC only) |
- | XXX State is a group: defines whether the given state is the name of a single state or a state group (RTC only) | + | **State is a group**: defines whether the given state is the name of a single state or a state group (RTC only) |
==== Transition Workflow Activator ==== | ==== Transition Workflow Activator ==== | ||
Line 120: | Line 143: | ||
=== Attributes === | === Attributes === | ||
- | Issue Type: defines the type of execution object which triggers the activator | + | **Issue Type**: defines the type of execution object which triggers the activator |
- | Start State & End State: defines the state transition from start to end state for which the activator is triggered and the Execution Script is executed | + | **Start State & End State**: defines the state transition from start to end state for which the activator is triggered and the Execution Script is executed |
- | Bound-to-process: | + | **Bound-to-process**: indicates whether this activator triggers for every Execution Object of type “Issue Type” (bound to process = false) or only when the Process Element is associated to the Execution Object (bound to process = true). |
- | XXX State is a group: defines whether the given state is the name of a single state or a state group (RTC only) | + | **State is a group**: defines whether the given state is the name of a single state or a state group (RTC only) |
==== Executable-Activator ==== | ==== Executable-Activator ==== | ||
Line 133: | Line 156: | ||
When an Executable-Activator is associated to a Process Element, in the Process Execution widget a “play-button” is visible to run the Executable-Activator (user triggered) | When an Executable-Activator is associated to a Process Element, in the Process Execution widget a “play-button” is visible to run the Executable-Activator (user triggered) | ||
+ | |||
+ | ==== Legacy Activators ==== | ||
+ | |||
+ | The Activator-types with " | ||
==== Issue Property ==== | ==== Issue Property ==== | ||
Line 140: | Line 167: | ||
=== Attributes === | === Attributes === | ||
- | Issue Type: defines the type of execution object for the Process Element | + | **Issue Type**: defines the type of execution object for the Process Element |
- | Issue Initial State: defines the state of execution object when it gets created (RTC only) | + | **Issue Initial State**: defines the state of execution object when it gets created (RTC only) |
- | Event Start State & Event End State: defines the state transition from start to end state for which the desired event is triggered | + | **Event Start State & Event End State**: defines the state transition from start to end state for which the desired event is triggered |
- | Bound-to-process: | + | **Bound-to-process**: indicates whether this activator triggers for every Execution Object of type “Issue Type” (bound to process = false) or only when the Process Element is associated to the Execution Object (bound to process = true). |
- | XXX State is a group: defines whether the given state is the name of a single state or a state group (RTC only) | + | **State is a group**: defines whether the given state is the name of a single state or a state group (RTC only) |
==== Execution Scripts ==== | ==== Execution Scripts ==== |