Differences

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

--- 76:process_execution [2021/03/15 15:06] – [Step-by-step Activator] 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 =====