summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorVrishali Doke2013-08-12 05:41:33 (EDT)
committerStephan Born2013-09-02 04:06:38 (EDT)
commit9878a3c134af3ad185417dd7f4ad9581fa98d09d (patch)
tree1329e732df439655d066ac118cca7bd732b6f89c
parent3bef0fae8baef1777f0c2a6e22e2cb3b7c7f128d (diff)
downloadorg.eclipse.stardust.documentation-9878a3c134af3ad185417dd7f4ad9581fa98d09d.zip
org.eclipse.stardust.documentation-9878a3c134af3ad185417dd7f4ad9581fa98d09d.tar.gz
org.eclipse.stardust.documentation-9878a3c134af3ad185417dd7f4ad9581fa98d09d.tar.bz2
Jira-ID: CRNT-28678
Added Intermediate events details git-svn-id: https://svn.csa.sungard.com/repos/ipp2/product/trunk/stardust/documentation@66628 8100b5e0-4d52-466c-ae9c-bdeccbdeaf6b Signed-off-by: Vrishali Doke <vrishali.doke@sungard.com>
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/event-fly.pngbin0 -> 4488 bytes
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-events.htm110
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-modeler-compatibility.html92
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-modeler-preface.html2
4 files changed, 188 insertions, 16 deletions
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/event-fly.png b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/event-fly.png
new file mode 100644
index 0000000..7d5c2b2
--- /dev/null
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/event-fly.png
Binary files differ
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 ee3df18..4283a7b 100644
--- 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
@@ -582,12 +582,12 @@ However, an Intermediate Event does not start or directly terminate a process.
You can use Intermediate events to:</p>
<ul>
<li>Show where Messages are expected or sent within the Process</li>
- <li>Show delays are expected within the Process</li>
+ <li>Show delays expected within the Process</li>
<li>Disrupt the normal flow through exception handling</li>
</ul>
<p>Following sub-types are supported: </p>
<ul>
- <li>Boundary Events
+ <li>Boundary Events - Note that Boundary events must have an exception flow.
<ul><li>Timer
<ul>
<li>Interrupting Timer Events</li>
@@ -598,9 +598,14 @@ You can use Intermediate events to:</p>
</li></ul></li>
</ul>
</li>
- <li>Non-boundary Events
+ <li>Non-boundary Events
<ul>
- <li>Timer
+ <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.
+
<ul>
<li>Non-interrupting Timer Events</li>
</ul>
@@ -636,13 +641,75 @@ the diagram canvas between two activities or activity and gateway. </p>
<p>Note that only Timer event can be added as a non-boundary event.</p>
+<h2>Dos and Don'ts wrt. boundary event modeling (29694)</h2>
+<p>Following topology rules should be followed when modeling events in Web-based modeler:</p>
+<ul>
+ <li></li>
+ <li></li>
+ <li></li>
+ <li></li>
+ <li></li>
+
+
+</ul>
+
+
+
+<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>
+
-<h2>Dos and Don'ts wrt. boundary event modeling (29664)</h2>
-<h3>Intermediate Event Flyout Menu</h3>
+<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.
+</p>
+
+<p class="image"><img src="images/event-fly.png" alt=""> <br>
+<strong>Figure:</strong> Intermediate Event - Flyout Menu</p>
+
+<table>
+ <tr>
+ <th>Menu Icon</th>
+ <th>Menu Option</th>
+ <th>Description</th>
+
+ </tr>
+ <tr>
+ <td><img src="images/data-connect.png"></td>
+ <td>Connect</td>
+ <td>Adds a Sequence Flow or Exception Flow with the event as the first endpoint
+ </td>
+ </tr>
+ <tr>
+ <td><img src="images/activity-g.png"></td>
+ <td>New Activity</td>
+ <td>Adds a new manual activity with sequence flow or exception flow
+ connecting the event to the new activity.
+ </td>
+ </tr>
+ <tr>
+ <td><img src="images/gateway-icon.png"></td>
+ <td>New Gateway</td>
+ <td>Adds a new Gateway(XOR) with sequence flow or exception flow
+ connecting the event to the new gateway.
+ </td>
+ </tr>
+ <tr>
+ <td><img src="images/gfly-del.png"></td>
+ <td>Delete</td>
+ <td>Deletes the event.</td>
+ </tr>
+
+</table>
+
+
+
+
<h3>Viewing and Editing Properties</h3>
<h4>General Properties</h4>
@@ -747,7 +814,8 @@ of the <a href="PLUGINS_ROOT/org.eclipse.stardust.docs.enduser/html/handbooks/ex
<h4>Error Boundary Event - Implementation</h4>
<p>The Error Boundary Events may only be Interrupting,
-meaning when the event is triggered the Activity that it is bound to is aborted and the exception path followed.
+meaning when the event is triggered the Activity that it is bound to is aborted
+and the exception path follows.
The following properties are displayed:
</p>
@@ -759,20 +827,22 @@ The following properties are displayed:
Boundary Events are always interrupting. For more information, refer to the General Properties section.</li>
<li>Event Trigger - You can select from the following options:
<ul>
- <li>General(java.lang.Exception)</li>
- <li>Network IO Issue(java.io.IOException)</li>
+ <li>General (java.lang.Exception)</li>
+ <li>Network IO Issue (java.io.IOException)</li>
<li>Runtime Issue (java.lang.RuntimeException)</li>
- <li>Web Service SOAP Issue(javax.xml.ws.soap)</li>
+ <li>Web Service SOAP Issue (javax.xml.ws.soap)</li>
<li>Other - If selected, you can specify custom exception in the following text box</li>
<p class="image"><img src="images/otherexcep.png" alt=""> <br>
<strong>Figure:</strong> Event Trigger- Other</p>
</ul>
</li>
- <li></li>
-
</ul>
-
+<p>If there are multiple error boundary events, the exception hierarchy is observed. For example,
+for Activity 1 two error boundary events are added in order say Exception and Null pointer exception.
+Then, in this case warning is displayed at the time of model deployment. Note that you can either specify
+super class or sub class of the exception. If you specify both then in that case deployment error is displayed.
+</p>
@@ -780,15 +850,25 @@ The following properties are displayed:
<h2>Validation</h2>
-<p></p>
+The following validation needs to be implemented:(CRNT-29655)
+Non-Boundary Intermediate Events SHOULD have one
+inbound and one outbound sequence flow, otherwise a warning is issued during model deployment.
+
+
+
+
+
+
+
<h2>Example</h2>
<h2>Compatibility</h2>
<p>Automatic binding</p>
<p>Consume on Match</p>
+<p>Bind/Unbind actions</p>
-
+<!-- 29694 -->
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 b18885d..bcfd3ab 100644
--- 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
@@ -51,6 +51,7 @@ Following elements need special treatment either in Eclipse-based modeler or Web
<li><a href="#spc">Importing Eclipse Models having non-Java Conform IDs</a></li>
<li><a href="#read">Read-only Models</a></li>
<li><a href="#in">Access Points</a></li>
+ <li><a href="#eve">Events</a></li>
</ul>
<h3 id="gate">Representation of Gateways created in Eclipse-based Modeler</h3>
<p>Gateways need to have correct interpretation when you import the Eclipse-based model with gateways in
@@ -177,6 +178,97 @@ of the chapter <a href="models/model-props.html">Model Properties</a>.
point is the return value of the completion method. Only these access points are displayed in the
Web-based modeler.</p>
+
+<h3 id="eve">Events</h3>
+
+<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>
+
+
+<h4>Event Action Types</h4>
+
+<p>Only one event action can be defined per event in Web-based modeler.</p>
+
+<table>
+ <tr>
+ <th>Eclipse Action Type</th>
+ <th>Handler Types</th>
+ <th>Web-based Modeler Action Type</th>
+ <th>Web-based Modeler Alternative</th>
+ </tr>
+ <tr>
+ <td>Abort Process</td>
+ <td>Timer, On Exception
+ </td>
+ <td>Follows Exception Flow.
+ A validation is performed whether a connection exists and a warning message is displayed in the UI.
+ Also, on model deployment a warning/error message is displayed.
+ </td>
+ <td>Create a model with exception flow to an End Event.</td>
+ </tr>
+ <tr>
+ <td>Abort Activity</td>
+ <td>Timer, On Exception</td>
+ <td>Follows Exception Flow</td>
+ <td>Set the Interrupt flag on the Event General Properties.</td>
+ </tr>
+ <tr>
+ <td>Delegate Activity</td>
+ <td>Timer, On Exception, On Activity State Change, On Assignment</td>
+ <td>Not supported</td>
+ <td>Delegation should be modeled with a Sequence Flow to another Task executed by a
+ different Participant. </td>
+ </tr>
+ <tr>
+ <td>Send Mail</td>
+ <td>Timer, On Exception, On Activity State Change, On Assignment</td>
+ <td>Follow Exception Flow</td>
+ <td>Create a model with exception flow to a Mail Application</td>
+ </tr>
+ <tr>
+ <td>Process Trigger</td>
+ <td>Timer, On Exception, On Activity State Change, On Assignment</td>
+ <td>Follow Exception Flow</td>
+ <td>Create a model with exception flow to a subprocess.</td>
+ </tr>
+ <tr>
+ <td>Set Data</td>
+ <td>Timer, On Exception, On Activity State Change, On Assignment</td>
+ <td>Follow Exception Flow</td>
+ <td>This can be modeled with Route Activities or Message Transformation Applications</td>
+ </tr>
+ <tr>
+ <td>Activate Activity</td>
+ <td>Timer, On Exception, On Assignment</td>
+ <td>Not supported</td>
+ <td>No Alternative</td>
+
+ </tr>
+ <tr>
+ <td>Complete Activity</td>
+ <td>Timer, On Exception,</td>
+ <td>Follow Exception Flow</td>
+ <td>No Alternative</td>
+ </tr>
+ <tr>
+ <td>Schedule Activity</td>
+ <td>Timer, On Exception, On Activity State Change</td>
+ <td>Not supported</td>
+ <td>No Alternative</td>
+ </tr>
+ <tr>
+ <td>Exclude User</td>
+ <td>On Assignment,</td>
+ <td>Not supported</td>
+ <td>No Alternative</td>
+ </tr>
+</table>
+
+
+
+
+
<h2 id="analogy">Analogy of Models Created in the Eclipse-based Modeler with the Web-based Modeler
</h2>
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-modeler-preface.html b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-modeler-preface.html
index 1cb7798..da458d6 100644
--- a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-modeler-preface.html
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-modeler-preface.html
@@ -19,7 +19,7 @@
</script>
<h1>Introduction</h1>
-<p>The Business Process Modeling perspective uses the <a href="http://www.bpmn.org/">Business Process Model and Notation (BPMN)</a>
+<p>The Business Process Modeling perspective uses the <a href="http://www.bpmn.org/">Business Process Model and Notation 2.0 (BPMN)</a>
standards. The business process modelers' and integrators can use it to create intuitive business
process workflows in Web-based environment. The business process diagrams are supported using various elements.
Such as swim lanes, activities, gateways, data objects etc. These elements of a business