|author||Vrishali Doke||2013-09-02 06:51:49 -0400|
|committer||Stephan Born||2013-09-06 06:22:27 -0400|
Events description git-svn-id: https://svn.csa.sungard.com/repos/ipp2/product/trunk/stardust/documentation@67045 8100b5e0-4d52-466c-ae9c-bdeccbdeaf6b Signed-off-by: Vrishali Doke <firstname.lastname@example.org>
6 files changed, 127 insertions, 25 deletions
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/intermediateve.png b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/intermediateve.pngBinary files differ
deleted file mode 100644
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-activities.htm b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-activities.htm
index 901154f..d26234c 100644
@@ -34,7 +34,7 @@ by default, it creates a User task. You can create following types of activities
<li>Service Task- This <img src="images/service-task.png"> icon represents the service task. The service task has
non-interactive application associated with it. </li>
<li>Script Task - This <img src="images/script-task.png"> icon represents the script task. The script task
- has Message Transformation application associated with it.</li>
+ has Script Invocation application associated with it.</li>
<li>Send Task - This <img src="images/send-task.png"> icon represents the send task. The send task has a
JMS application associated with it. </li>
<li>Receive Task - This <img src="images/receive-task.png"> icon represents the receive task. The receive
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-events.htm b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-events.htm
index 696dde0..bf4cd3e 100644
@@ -35,6 +35,7 @@ The Business Process Modeling perspective supports two types of events:</p>
<li><a href="#fly">Using Events Flyout Menu</a></li>
<li><a href="#prop">Viewing and Editing Properties of Start Event</a></li>
<li><a href="#end">Viewing and Editing Properties of End Event</a></li>
+ <li><a href="#weve">Working with Intermediate Events</a></li>
@@ -573,22 +574,17 @@ If the other user selects the comment or no comment is selected, the Delete icon
-<h2>Working with Intermediate Events</h2>
+<h2 id="weve">Working with Intermediate Events</h2>
<p>The Web-based modeler supports Intermediate events which follows BPMN 2.0 semantics.
Intermediate Events are events that occurs after a process has been started.
An Intermediate Event affects the flow of the process by showing where messages
and delays are expected, distributing the normal flow through exception handling.
However, an Intermediate Event does not start or directly terminate a process.
-You can use Intermediate events to:</p>
- <li>Show where Messages are expected or sent within the Process</li>
- <li>Show delays expected within the Process</li>
- <li>Disrupt the normal flow through exception handling</li>
<p>Following sub-types are supported: </p>
- <li>Boundary Events - When an event is associated with any manual activity
- it is called Boundary event.
+ <li>Boundary Events -
Note that Boundary events must have an exception flow.
@@ -601,12 +597,13 @@ You can use Intermediate events to:</p>
<li>Non-boundary Events - Non-boundary event is always between two activities, or gateway and activity.
+ Non-Boundary Intermediate Events should have one inbound and one
+ outbound sequence flow, otherwise a warning is issued during model deployment.
<li>Timer - For non-boundary timer event, the activity goes into Hibernate state
till the time period is defined. Once the time period criteria meets, the
next activity gets activated by completing a timer for the underline activity.
- Non-Boundary Intermediate Events should have one inbound and one
- outbound sequence flow, otherwise a warning is issued during model deployment.
<li>Non-interrupting Timer Events</li>
@@ -616,10 +613,6 @@ You can use Intermediate events to:</p>
-<p class="image"><img src="images/intermediateve.png" alt=""> <br>
-<strong>Figure:</strong> Intermediate Event</p>
<h3>Adding Intermediate Event</h3>
<p>In the toolbar, click Create Intermediate Event icon and drop it to swim lanes.
@@ -673,11 +666,6 @@ events in the Web-based modeler:</p>
-<p>The delay needs to be present before the activity instance is activated.</p>
-<p>the value must be set before the activity is started
-(for bound events) or the intermediate event is reached.</p>
<h3>Using Intermediate Event Flyout Menu</h3>
<p>The intermediate event flyout menu is displayed when you hover the mouse in the proximity of the data.
@@ -784,7 +772,8 @@ If the other user selects the comment or no comment is selected, the Delete icon
<h4>Timer Event - Implementation</h4>
<p>This option is available only when you switch to <a href="model-views/pep-panels.html">Integrator</a> profile.</p>
-<p>Note that you need to start Event Daemon when working with Timer Event. For more information about event daemon,
+<p>Note that you need to start Event Daemon when working with Timer Event.
+For more information about event daemon,
please refer to the
<!-- link from inside Portal Documentation jar -->
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-modeler-compatibility.html b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-modeler-compatibility.html
index bcfd3ab..5eac54d 100644
@@ -181,10 +181,16 @@ Web-based modeler.</p>
-<p>Modeling of Intermediate events is supported only in Web-based modeler. If you import a model
-created in Web-based modeler which contains intermediate event to Eclipse-based modeler, it does not
-disturb the intermediate event XML and should work as expected. </p>
+<p>Modeling of Intermediate events is not supported in Eclipse-based modeler.
+However, if you import a model which contains non-boundary event to Eclipse-based modeler,
+you need to adjust the model accordingly as the non-boundary event icon will not be visible but
+event mapping will exist. Similarly, if you import a model which contains boundary event to
+Eclipse-based modeler, the boundary event icon and also the mapping will be visible. </p>
+ <li>Timer events in Eclipse-based modeler are mapped to Timer events</li>
+ <li>Exception events in Eclipse-based modeler are mapped to Error events</li>
<h4>Event Action Types</h4>
diff --git a/org.eclipse.stardust.docs.dev/html/concepts/workflow-basics/images/intermediateve.png b/org.eclipse.stardust.docs.dev/html/concepts/workflow-basics/images/intermediateve.pngBinary files differ
new file mode 100644
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 d9177f4..df61e12 100644
@@ -180,6 +180,113 @@ 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
+start and end of a Process. It affects the flow of the Process, but does not start or (directly) terminate the Process.
+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>
+<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 -->
+ <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>
+<h3 id="boundary">Boundary Events</h3>
+<p>Boundary events are Intermediate events attached to the boundary of an Activity.
+Boundary events can be:
+ <li>Interrupting - branch the process flow</li>
+ <li>Non-interrupting - fork the process flow </li>
+<p>You should use Timer Boundary event
+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
+in a model must have an outgoing sequence flow.</p>
+BPMN 2.0 allows multiple outbound exception flows from a boundary event.
+The @productnameshort@ engine currently does not support this, but may provide
+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>
+Non-Boundary Events are not directly supported by the @productnameshort@ engine,
+but it works as a Route Activity at runtime.</p>
+<!-- DOne: description/what to use for -->
+<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>
+ <li>Activity (all types)</li>
+ <li>End Event</li>
+ <li>Non-Boundary Intermediate Event (e.g. Timer Event)</li>
+<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>
+<p>Interrupting events do:</p>
+ <li>terminate other execution paths (within the container)</li>
+ <li>interrupt the activity</li>
+<p>Interrupting events can be timer or error boundary events.</p>
+<p>Non-interrupting events do:</p>
+ <li>execute in parallel</li>
+ <li>not interrupt the activity to which they are attached</li>
+<p>Non-interrupting events can be timer boundary or non-boundary events.</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
+or the drawing canvas. The existing exception flow, e.g. a connection, is maintained
+in that case.</p>
+<p>When binding an unbound event that has incoming and outgoing connections,
+the incoming is deleted, whereas the outgoing will be maintained.
+An exception is when the event is bound to the activity that is attached
+to the event's outgoing connection. In this case both, the incoming and
+outgoing connections, are deleted.</p>
+<h4>Unbinding Boundary Events</h4>
+<p>Boundary Events can be unbound from activities via drag-and-drop.</p>