CRNT-26314 - Added gateway details with route activities

git-svn-id: http://emeafrazerg/svn/ipp/product/trunk/stardust/documentation@59444 8100b5e0-4d52-466c-ae9c-bdeccbdeaf6b

4 files changed, 26 insertions, 4 deletions

diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/eclipse-gateway.png b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/eclipse-gateway.png
new file mode 100644
index 0000000..2ac8265
--- a/dev/null
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/eclipse-gateway.png
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/peper-gate.png b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/peper-gate.png
new file mode 100644
index 0000000..48d13f2
--- a/dev/null
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/peper-gate.png
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-con-sequence.htm b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-con-sequence.htm
index 1bdf428..473b9fa 100644
--- a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-con-sequence.htm
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-con-sequence.htm
@@ -23,7 +23,7 @@
 
 <h1>Working with Sequence Flows</h1>
 <p>The sequence flow determines the execution sequence of activities. A sequence flow
-connects an activity with its successor activity. It also allows setting
+connects an element with its successor element. It also allows setting
 a condition - only if this condition is fulfilled at runtime the
 transition is processed and the next activity is executed.</p>
 <p>This chapter covers the following:</p>
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-gateways.htm b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-gateways.htm
index e1c2282..b7b354d 100644
--- a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-gateways.htm
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-gateways.htm
@@ -19,8 +19,8 @@
 </script>

 

 <h1>Working with Gateways</h1>

-<p>The square in the sequence flow which represents AND and OR is called gateway.

-The Business Process Modeling perspective supports AND and OR types of gateway connections.

+<p>The square in the sequence flow which represents AND and XOR is called gateway.

+The Business Process Modeling perspective supports AND and XOR types of gateway connections.

 You can implicitly join or split the gateway depending on the sequence flow added.

 By default, XOR gateway type is supported.

 You can create unlimited in and out sequence flow connections from gateways. 

@@ -40,6 +40,7 @@ Concepts handbook.</a></p>
 	<li><a href="#add">Adding Gateways</a></li>

 	<li><a href="#use">Using Gateway Flyout Menu</a></li>

 	<li><a href="#view">Viewing and Editing Properties of Gateway</a></li>

+	<li><a href="#gate">Representation of Gateways created in Eclipse-based Modeler</a></li>

 </ul>

 

 <h2 id="add">Adding Gateways</h2>

@@ -172,7 +173,28 @@ icon displayed at top right side of the diagram canvas. </p>
 <p class="image"><img src="images/annotation.png" alt=""> <br>

 <strong>Figure:</strong> Gateway - Add Annotation</p>

 

-<p>To delete the annotation, select the annotation and click <strong>Delete</strong> <img src="images/del-annotation.png"> icon.</p>

+<p>To delete the annotation, select the annotation and click 

+<strong>Delete</strong> <img src="images/del-annotation.png"> icon.</p>

+

+

+<h2 id="gate">Representation of Gateways created in Eclipse-based Modeler</h2>

+<p>Gateways need to have correct interpretation when you import the Eclipse-based model with gateways in 

+Business Process Modeling perspective. In the Business Process Modeling perspective 

+gateways are first class elements. 

+That's why models created in Infinity Process Platform's Eclipse-based modeler having

+gateways should have route activities to represent gateways.

+The model created in Eclipse based modeler should represent gateways in the following way:

+</p>

+

+<p class="image"><img src="images/eclipse-gateway.png" alt=""> <br>

+<strong>Figure:</strong> Gateway in Eclipse based Modeler</p>

+

+<p>When imported in the Business Process Modeling perspective, the model would look like as shown in the 

+following figure:</p>

+

+<p class="image"><img src="images/peper-gate.png" alt=""> <br>

+<strong>Figure:</strong> Gateways interpreted in Business Process Modeling Perspective</p>

+