summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorVrishali Doke2013-09-12 02:23:46 (EDT)
committerStephan Born2013-10-23 06:36:14 (EDT)
commitea856fc03a1238212072a576d0638a0300181afc (patch)
tree6b04cf94146ef771d21c58d7d0fa45148d29ba27
parent5be393267b4c12c8b6eeddc9fdf30c24e8e2a12d (diff)
downloadorg.eclipse.stardust.documentation-ea856fc03a1238212072a576d0638a0300181afc.zip
org.eclipse.stardust.documentation-ea856fc03a1238212072a576d0638a0300181afc.tar.gz
org.eclipse.stardust.documentation-ea856fc03a1238212072a576d0638a0300181afc.tar.bz2
Jira-ID: CRNT-29911
Added events in process history details git-svn-id: https://svn.csa.sungard.com/repos/ipp2/product/trunk/stardust/documentation@67228 8100b5e0-4d52-466c-ae9c-bdeccbdeaf6b Signed-off-by: Vrishali Doke <vrishali.doke@sungard.com>
-rw-r--r--org.eclipse.stardust.docs.dev/html/concepts/workflow-basics/mg-basics-11.htm37
-rw-r--r--org.eclipse.stardust.docs.enduser/html/handbooks/execution-clients/detail-views/process-details/proc-history-act.html3
2 files changed, 15 insertions, 25 deletions
diff --git a/org.eclipse.stardust.docs.dev/html/concepts/workflow-basics/mg-basics-11.htm b/org.eclipse.stardust.docs.dev/html/concepts/workflow-basics/mg-basics-11.htm
index 4d653bc..fd7d8f5 100644
--- a/org.eclipse.stardust.docs.dev/html/concepts/workflow-basics/mg-basics-11.htm
+++ b/org.eclipse.stardust.docs.dev/html/concepts/workflow-basics/mg-basics-11.htm
@@ -180,11 +180,6 @@ remove the activity instance from resubmission because the reason for being
hibernated no longer exists. When unbinding this activity instance there has to
be a mechanism to put it back to the worklist. This could be done by an
appropriate scheduled unbind action.</p>
-
-
-
-
-
<h2 id="bpmn">Intermediate Events in the Business Process Modeler</h2>
<p>The Business Process Modeler uses intermediate events, following the BPMN 2.0 standards.
As the name implies, the Intermediate Event indicates where an event happens somewhere between the
@@ -194,21 +189,16 @@ Intermediate Events can be used to:</p>
<li>Show delays are expected within the Process</li>
<li>Disrupt the normal flow through exception handling</li>
</ul>
-
<p>Following diagram depicts the classification of intermediate events
supported in the Business Process Modeler.</p>
-
<p class="image"><img src="images/intermediateve.png" alt=""> <br>
<strong>Figure:</strong> Intermediate Event</p>
-
-<!-- TODO: description/what to use for -->
<ul>
<li><a href="#boundary">Boundary Events</a></li>
<li><a href="#nonbound">Non-Boundary Events</a></li>
<li><a href="#interrupt">Interrupting and Non-interrupting Events</a></li>
<li><a href="#exflow">Exception Flow</a></li>
</ul>
-
<h3 id="boundary">Boundary Events</h3>
<p>Boundary events are Intermediate events attached to the boundary of an Activity.
Boundary events can be:
@@ -221,8 +211,6 @@ Boundary events can be:
if an activity is not processed within specified time interval, explanation email should be sent.</p>
<p>You should use Error Boundary event in case an error occurs when executing an activity and
the activity should get aborted.</p>
-
-<!-- done: description/what to use for -->
<h4 id="flow">Sequence Flow of Boundary Events</h4>
<p>Boundary Events can have only one outbound exception flow, but multiple paths
can be supported using a gateway. All Boundary Events
@@ -234,7 +222,6 @@ it in a future release.</p>
<h3 id="nonbound">Non-Boundary Events</h3>
<p>Non-boundary events are Intermediate events specified always between two activities,
or gateway and activity. Only timer event can be added as a non-boundary event.</p>
-
<p>You can use the non-boundary timer event if you want a delay between the two activities.</p>
<p class="note"><strong>Note</strong><br>
Non-Boundary Events are not directly supported by the @productnameshort@ engine,
@@ -243,17 +230,6 @@ but it works as a Route Activity at runtime.</p>
<h4>Sequence Flow of Non-Boundary Events</h4>
<p>Non-boundary Intermediate Events can have both an inbound and outbound sequence flow.
All Intermediate Events in a model must have both an incoming and outgoing sequence flow.</p>
-<h3 id="exflow">Exception Flow</h3>
-<p>The following elements can be the exception flow target:</p>
-<ul>
- <li>Activity (all types)</li>
- <li>Gateway</li>
- <li>End Event</li>
- <li>Non-Boundary Intermediate Event (e.g. Timer Event)</li>
-</ul>
-<p>Note that Data may not be connected directly to Events in the Business Process Modeler.</p>
-<p>An existing exception flow (i.e., connection) is maintained when dropped
-onto another activity or onto the drawing canvas.</p>
<h3 id="interrupt">Interrupting and Non-interrupting Events</h3>
<h4>Interrupting Events</h4>
<p>Interrupting events do:</p>
@@ -269,6 +245,19 @@ onto another activity or onto the drawing canvas.</p>
<li>not interrupt the activity to which they are attached</li>
</ul>
<p>Non-interrupting events can be timer boundary or non-boundary events.</p>
+
+<h3 id="exflow">Exception Flow</h3>
+<p>The following elements can be the exception flow target:</p>
+<ul>
+ <li>Activity (all types)</li>
+ <li>Gateway</li>
+ <li>End Event</li>
+ <li>Non-Boundary Intermediate Event (e.g. Timer Event)</li>
+</ul>
+<p>Note that Data may not be connected directly to Events in the Business Process Modeler.</p>
+<p>An existing exception flow (i.e., connection) is maintained when dropped
+onto another activity or onto the drawing canvas.</p>
+
<h3 id="bindun">Binding and Unbinding Boundary Events to and from Activities</h3>
<h4>Binding Boundary Events</h4>
<p>To bind boundary events to an activity, they can be dropped onto another activity
diff --git a/org.eclipse.stardust.docs.enduser/html/handbooks/execution-clients/detail-views/process-details/proc-history-act.html b/org.eclipse.stardust.docs.enduser/html/handbooks/execution-clients/detail-views/process-details/proc-history-act.html
index c07142a..b3e1dd1 100644
--- a/org.eclipse.stardust.docs.enduser/html/handbooks/execution-clients/detail-views/process-details/proc-history-act.html
+++ b/org.eclipse.stardust.docs.enduser/html/handbooks/execution-clients/detail-views/process-details/proc-history-act.html
@@ -64,6 +64,7 @@ activities that spawned them.</p>
<li><a href="#qacode">Displaying Quality Assurance Code</a></li>
</ul>
</li>
+ <li><a href="#eve">Events in Process History</a></li>
</ul>
<h2 id="typeIcons">Activity Types</h2>
<p>The specific type of an activity is indicated via the following icons:</p>
@@ -345,7 +346,7 @@ assurance code(s) is displayed.</p>
<strong>Figure:</strong> Display Quality Assurance Code(s) for the activity</p>
-<h2>Events in Process History</h2>
+<h2 id="eve">Events in Process History</h2>
<p>To view the event in Process History, the <strong>Log Handler</strong> option in the <strong>Implementation</strong> properties of
event should be selected.</p>
<h3>Non-boundary Timer Event</h3>