Differences

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

--- 76:process_execution [2021/03/15 15:05] – prnr
+++ 76:process_execution [2024/02/15 00:00] (current) – external edit 127.0.0.1
@@ Line 7: / Line 7: @@
 [[:76:process_execution_rtc|]]
-[[:76:process_execution_jira|]]
+[[:76:process_execution_jira|]] (server version)
 === Model Execution in Stages ===
-In Stages the existing process information is used regularly. The execution information is  attach as an addition to it. Ideally this leads to the situation that whenever the process is changed or tailored, the execution changes behavior without changing the execution information.
+In Stages the existing process information is used regularly. The execution information is attach as an addition to it. Ideally this leads to the situation that whenever the process is changed or tailored, the execution changes behavior without changing the execution information.
 Hence it is possible to attach execution information only to parts of a process, it can be taken into execution selectively.
@@ Line 19: / Line 20: @@
 === Run Execution in ALM Systems ===
-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.
+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 =====
@@ Line 88: / Line 91: @@
 === 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: 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).
+**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
-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 ====