summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorVrishali Doke2012-11-01 07:26:12 (EDT)
committer Sven Rottstock2012-11-01 07:26:12 (EDT)
commita9a34ed87610bb5c92223d05b9d8106c1f6fb598 (patch)
tree9f8360dccb659d9b1b1ba973b7f5e0422612f1a2
parent60d86564744458cbbf666f231d967bf07bfe0a4e (diff)
downloadorg.eclipse.stardust.documentation-a9a34ed87610bb5c92223d05b9d8106c1f6fb598.zip
org.eclipse.stardust.documentation-a9a34ed87610bb5c92223d05b9d8106c1f6fb598.tar.gz
org.eclipse.stardust.documentation-a9a34ed87610bb5c92223d05b9d8106c1f6fb598.tar.bz2
CRNT-26515 - Added compatibility restrictions
git-svn-id: http://emeafrazerg/svn/ipp/product/trunk/stardust/documentation@60488 8100b5e0-4d52-466c-ae9c-bdeccbdeaf6b
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/eclipse-gateway.pngbin48936 -> 70176 bytes
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/gateway-eclipse.pngbin0 -> 28140 bytes
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/models/images/warn.pngbin0 -> 4870 bytes
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/models/model-handling.html9
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-modeler-compatibility.html54
5 files changed, 45 insertions, 18 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
index 2ac8265..cd09ac2 100644
--- 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
Binary files differ
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/gateway-eclipse.png b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/gateway-eclipse.png
new file mode 100644
index 0000000..f7ed300
--- /dev/null
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/gateway-eclipse.png
Binary files differ
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/models/images/warn.png b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/models/images/warn.png
new file mode 100644
index 0000000..5cb661b
--- /dev/null
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/models/images/warn.png
Binary files differ
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/models/model-handling.html b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/models/model-handling.html
index 9fbbbff..d12dab5 100644
--- a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/models/model-handling.html
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/models/model-handling.html
@@ -66,7 +66,7 @@ toolbar. The <strong>File Upload</strong> dialog box gets displayed.</p>
<p class="image"><img src="images/file-up.png" alt=""> <br>
<strong>Figure:</strong> File Upload</p>
-<p>Click <strong>Browse</strong> to locate the model file and click <strong>Upload</strong>.</p>
+<p>Click <strong>Browse</strong> to locate the .XPDL file and click <strong>Upload</strong>.</p>
<p>Models created in the Eclipse-based modeler should support BPMN drawing mode. When imported, only those models
are displayed in the Business Modeling Perspective.</p>
@@ -80,6 +80,13 @@ are displayed in the Business Modeling Perspective.</p>
<p>If you click <strong>Continue</strong> the new version of the existing process model gets created and displayed.</p>
+<p>If you perform Delete or Rename operation and click Import, without saving or refreshing the models, then
+the following warning is displayed. You must save all the models prior to import operation.</p>
+
+<p class="image"><img src="images/warn.png" alt=""> <br>
+<strong>Figure:</strong> Import Model - Warning</p>
+
+
<h2 id="savm">Saving All Models</h2>
<p>To save models, click the <strong>Save All Models</strong> <img src="images/save-all.png"> icon
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 00b175d..a128d7e 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
@@ -21,13 +21,14 @@
<p>This chapter covers the following:</p>
<ul>
- <li>Compatibility of Models created in Eclipse-based Modeler with Browser-based Modeler
+ <li>Compatibility of Models created in Eclipse-based Modeler with Web-based Modeler
<ul>
<li>Pools and Lanes Restrictions</li>
<li>Representations of Gateways created in Eclipse-based Modeler</li>
+ <li>Data Flow</li>
</ul></li>
- <li>Analogy of Models Created in the Eclipse Modeler and the Business Process Modeler
+ <li>Analogy of Models Created in the Eclipse-based Modeler with the Web-based Modeler
<ul>
<li>Supported Elements</li>
<li>Unsupported Elements</li>
@@ -36,41 +37,60 @@
</ul>
-<h2>Compatibility of Models created in Eclipse-based Modeler with Browser-based Modeler</h2>
-<p>The <strong>Business Process Modeling</strong> perspective supports browser-based modeling.
-However, when it comes to importing models created in @productname@'s Eclipse-based modeler in the
-browser-based modeler, some restrictions are encountered. To ensure smooth deployment of models in
-browser-based modeler, you need to alter some of the elements in the model before you import.
+<h2>Compatibility of Models created in Eclipse-based Modeler with Web-based Modeler</h2>
+<p>The <strong>Business Process Modeling</strong> perspective supports web-based modeling.
+However, when it comes to importing models created in @productname@'s Eclipse-based modeler to the
+web-based modeler, some restrictions are encountered. To ensure smooth deployment of models in
+web-based modeler, you need to alter some of the elements in the model before you import.
These elements are:</p>
<ul>
<li>Gateways</li>
<li>Drawing Mode - Pools and Lanes</li>
</ul>
-
-
+<ul>
+ <li>Cross Model support</li>
+ <li>Data Flow</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
-Business Process Modeling perspective. In the Business Process Modeling perspective
+the Business Process Modeling perspective. In the Business Process Modeling perspective
gateways are first class elements.
-That's why models created in @productname@'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:
+However there is no first class diagram element for gateways in the Eclipse-based modeler.
+That's why models created in @productname@'s Eclipse-based modeler and to be imported in web-based modeler should have:</p>
+<ul>
+ <li>route activities to represent gateways</li>
+ <li>a route activity with ID = Gateway must be used for each gateway</li>
+ <li>a Control Flow property must have Join and Split types set to the same value</li>
+</ul>
+<p>
+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>
+<strong>Figure:</strong> Route Activity as 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>
+<strong>Figure:</strong> Gateways interpreted in Web-based Modeler</p>
+
+<h3>Representation of Gateways created in Web-based Modeler</h3>
+<p>Gateways added in web-based modeler are displayed in Eclipse-based modeler as route activities.
+The control flow properties of the route activity is set according to the following rules:</p>
+<ul>
+ <li>AND/XOR property follows the explicit definition made in web-based modeler</li>
+ <li>Both Join/Split behavior is set to the gateway type. This means either both are AND or both are XOR.</li>
+</ul>
+
+<p class="image"><img src="images/gateway-eclipse.png" alt=""> <br>
+<strong>Figure:</strong> Gateways interpreted in Eclipse-based Modeler</p>
-<h2>Analogy of Models Created in the Eclipse Modeler and the Business Process Modeler
+<h2>Analogy of Models Created in the Eclipse-based Modeler with the Web-based Modeler
</h2>
<p>The @productname@ supports creation of workflow models in two ways.
@@ -78,7 +98,7 @@ Firstly, you can create models in the @productname@'s Eclipse-based modeler and
in the Business Process Modeling perspective of
@productname@. However, when you import model created in Eclipse-based modeler,
some of the model elements are not supported in
-browser-based modeler. For those unsupported elements, you should use @productname@'s
+web-based modeler. For those unsupported elements, you should use @productname@'s
Eclipse-based modeler. </p>
<h3>Supported Elements</h3>