summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorVrishali Doke2013-09-13 06:43:29 (EDT)
committer Stephan Born2013-10-23 06:42:59 (EDT)
commit43eb025693825fcdf2a471f74bffb32536076701 (patch)
tree7d92db535ab2a771742ae9e6ea1cb0e8e8daf2a0
parent6d029eba3d69406c1a215165ebb545fc0c66d27c (diff)
downloadorg.eclipse.stardust.documentation-43eb025693825fcdf2a471f74bffb32536076701.zip
org.eclipse.stardust.documentation-43eb025693825fcdf2a471f74bffb32536076701.tar.gz
org.eclipse.stardust.documentation-43eb025693825fcdf2a471f74bffb32536076701.tar.bz2
Jira-ID: CRNT-30476
Added restriction for intermediate events git-svn-id: https://svn.csa.sungard.com/repos/ipp2/product/trunk/stardust/documentation@67266 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/pep-modeler-compatibility.html87
-rw-r--r--org.eclipse.stardust.docs.installation/html/other/troubleshooting.html7
2 files changed, 14 insertions, 80 deletions
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 5eac54d..d1ec233 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
@@ -28,10 +28,7 @@
<ul>
<li><a href="#sup">Supported Elements</a></li>
<li><a href="#unsup">Unsupported Elements</a></li>
-
</ul></li>
-
-
</ul>
<h2 id="comp">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.
@@ -60,32 +57,25 @@ gateways are first class elements (you can drag-and-drop gateway symbol from the
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
use the <strong>Convert Gateways</strong> functionality in Eclipse-based modeler.</p>
-
<p>If the model contains gateways, then right-click the process definition in Outline
view and select <strong>Convert Gateways</strong>.</p>
<p class="image"><img src="images/convert-gateway.png" alt=""> <br>
<strong>Figure:</strong> Eclipse-based Modeler - Convert Gateways</p>
<p>A route activity is created as first class element to represent the gateway, which can be imported
in the Business Modeler. </p>
-
<p class="image"><img src="images/eclipse-gateway-route.png" alt=""> <br>
<strong>Figure:</strong> Eclipse Model after Gateway Conversion</p>
<p>The control flow in this route activity is set to the type of the split
or join control flow of the activity the gateway is referring to.</p>
-
<p class="image"><img src="images/control.png" alt=""> <br>
<strong>Figure:</strong> Route Activity - Control Flow</p>
<p>Once you convert gateways, you can import the model in the Web-based Modeler. </p>
-
<p class="image"><img src="images/web-gateway.png" alt=""> <br>
<strong>Figure:</strong> Gateways interpreted in Web-based Modeler</p>
-
-
<p>
For more information on Convert Gateways functionality,
please refer to the chapter
-
- <span class="showReference">
+<span class="showReference">
<a href="PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/handbooks/modelling/convert-gateways.html">Converting Gateways to a Business Modeler-compliant Format</a>
</span><span class="hideReference">
<strong>Converting Gateways to a Business Modeler-compliant Format</strong></span>
@@ -94,33 +84,6 @@ please refer to the chapter
<a href="PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/handbooks/modelling/mg-preface.htm">Modeling Guide</a>.
</span><span class="hideReference">
<strong>Modeling Guide</strong> in the <strong>@productname@ Documentation</strong>.</span></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>
-
- <p class="image"><img src="images/control.png" alt=""> <br>
-<strong>Figure:</strong> Route Activity - Control Flow</p>
-
-
-</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> 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 Web-based Modeler</p>
- -->
<h3 id="weg">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 property of the route activity is set according to the following rules:</p>
@@ -128,18 +91,14 @@ The control flow property of the route activity is set according to the followin
<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>
-
<p>However, note that the route activity used for gateway in Web-based modeler acts as an auxiliary activity and
hence, is not displayed anywhere in @productname@ Portal.</p>
-
<h3 id="swim">Swim Lanes</h3>
<p>Models created in the Eclipse-based modeler should support BPMN drawing mode (pools and lanes).
When imported, only those models are displayed properly in the Business Process Modeling Perspective.
</p>
-
<h3 id="flow">Data Flow</h3>
<p>The Web-based modeler allows only:</p>
<ul>
@@ -155,47 +114,38 @@ However, if you import a model created in Eclipse and it has conditional sequenc
In that case, you can edit the transition condition in Web-based modeler. Also,
you can save, deploy and execute the model in Web-based modeler.
</p>
-
<h3 id="cros">Cross Modeling</h3>
<p>In cross modeling, to maintain the references between the models, the imported referenced model should be kept in the
same project folder. If the imported model resides at any other location then the references are not resolved
by the Eclipse-based modeler and Web-based modeler. </p>
-
-
<h3 id="spc">Importing Eclipse Models having non-Java Conform IDs</h3>
<p>The Eclipse-based models having IDs that are not Java conform identifiers may cause problems when imported
to Web-based modeler. Currently, Web-based modeler cannot handle IDs that are not Java conform identifiers.</p>
-
<h3 id="read">Read-only Models</h3>
<p>For compatibility issues with read-only models, refer to the section
<a href="models/model-props.html#ecompat">Eclipse Compatibility of Read-only Models</a>
of the chapter <a href="models/model-props.html">Model Properties</a>.
-
</p>
-
<h3 id="in">Access Points</h3>
<p>Input access points are parameters of the completion method and output access
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 not supported in Eclipse-based modeler.
+However, if you import a model which contains intermediate events to Eclipse-based modeler,
+it should work as expected. But you should not edit the intermediate events activities including
+transitions.</p>
+<!--
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>
-
+Eclipse-based modeler, the boundary event icon and also the mapping will be visible.
<ul>
<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>
-</ul>
-
+</ul>-->
<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>
@@ -270,14 +220,8 @@ Eclipse-based modeler, the boundary event icon and also the mapping will be visi
<td>No Alternative</td>
</tr>
</table>
-
-
-
-
-
<h2 id="analogy">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.
Firstly, you can create models in the @productname@'s Eclipse-based modeler and secondly,
in the Business Process Modeling perspective of
@@ -286,7 +230,6 @@ in the Business Process Modeling perspective of
Web-based modeler. For those unsupported elements, you should use @productname@'s
Eclipse-based modeler. </p>
<h3 id="sup">Supported Elements</h3>
-
<p>Following is the list of supported elements. That means, you can add, edit, delete and rename these elements.</p>
<table width="1%" border="1" id="id_3">
<tr>
@@ -393,17 +336,11 @@ Eclipse-based modeler. </p>
</tr>
</table>
-
-
-
-
-
<h3 id="unsup">Unsupported Elements</h3>
<p>Unsupported elements are displayed in <strong>My Process Models</strong> panel and
<strong>Process Diagrams</strong> view but you
can only edit General Properties of these elements. </p>
<p>Following table summarizes the operations for unsupported elements:</p>
-
<table>
<tr>
<th>Function</th>
@@ -438,22 +375,15 @@ can only edit General Properties of these elements. </p>
</table>
<p>Also, the message is displayed for each unsupported element in its General Properties page. </p>
-
-
-
<p class="image"><img src="images/unsupported-element-msg.png"
alt=""><br>
<strong>Figure:</strong> Unsupported Model Element</p>
-
-
<p>Following is the list of unsupported model elements.</p>
-
<table width="10%" border="1" id="id_2">
<tr>
<th width="2%">Element</th>
<th width="2%">Type</th>
</tr>
-
<tr>
<td>Document List </td>
<td>Data</td>
@@ -541,7 +471,6 @@ can only edit General Properties of these elements. </p>
</tr> -->
</table>
<p>Following pre-defined primitive data are not supported.</p>
-
<ul>
<li>CURRENT_MODEL</li>
<li>CURRENT_USER</li>
@@ -550,8 +479,6 @@ can only edit General Properties of these elements. </p>
<li>CURRENT_MODEL</li>
</ul>
<p>Note that the Default Diagram is also not supported.</p>
-
-
<script language="JavaScript" type="text/javascript">
<!--
writeFooter();
diff --git a/org.eclipse.stardust.docs.installation/html/other/troubleshooting.html b/org.eclipse.stardust.docs.installation/html/other/troubleshooting.html
index 01d34c3..f50995d 100644
--- a/org.eclipse.stardust.docs.installation/html/other/troubleshooting.html
+++ b/org.eclipse.stardust.docs.installation/html/other/troubleshooting.html
@@ -931,6 +931,7 @@ following:</p>
<li><a href="#relabort">Aborting active activities</a></li>
<li><a href="#relhistory">History of original process instance in portal</a></li>
</ul></li>
+ <li><a href="#imp">Importing models with intermediate events</a></li>
</ul>
<h3 id="primimpl">Restrictions on Switching Primary Implementations for running Processes</h3>
<p>Switching the primary implementation for a running process has the following
@@ -1153,6 +1154,12 @@ properties is only possible if they are modeled as <tt>xsd:string</tt>.</p>
<h4 id="relhistory">History of original process instance in portal</h4>
<p>The history of the original process instance is available and
identifiable only indirectly via the link feature in the @productname@ portal.</p>
+<h3 id="imp">Importing models with intermediate events</h3>
+<p>Intermediate events can be modelled only in Web-based modeler and are not compatible with Eclispe-based modeler.
+However, it is possible to open the models in Eclipse and edit model elements other than intermediate events,
+but no change should be done to the activities with intermediate events including transitions.
+</p>
+
<script language="JavaScript" type="text/javascript">
<!--