summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorVrishali Doke2013-02-08 01:36:53 (EST)
committer Sven Rottstock2013-03-11 07:38:07 (EDT)
commitea1b1b4481098ecf548c02487fe7b65e03b7a0b3 (patch)
treec06a5cbdf5f0b7b42e446ffbfa79b2ef5ee6b7c4
parent6916c9e29eb927d6e89a0a5896af2afcfd30eaaf (diff)
downloadorg.eclipse.stardust.documentation-ea1b1b4481098ecf548c02487fe7b65e03b7a0b3.zip
org.eclipse.stardust.documentation-ea1b1b4481098ecf548c02487fe7b65e03b7a0b3.tar.gz
org.eclipse.stardust.documentation-ea1b1b4481098ecf548c02487fe7b65e03b7a0b3.tar.bz2
CRNT-27838 - Updated for screenshots - panels, swimlanes, conditional performer
git-svn-id: http://emeafrazerg/svn/ipp/product/trunk/stardust/documentation@62845 8100b5e0-4d52-466c-ae9c-bdeccbdeaf6b
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/bpm-perspect.pngbin6678 -> 8696 bytes
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/perspec-comp.pngbin57091 -> 55705 bytes
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/perspec.pngbin6593 -> 9047 bytes
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-data-flow.htm15
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-modeler-compatibility.html43
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-org-struct.htm4
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-pools-lanes.htm2
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-struct-type.htm5
8 files changed, 40 insertions, 29 deletions
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/bpm-perspect.png b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/bpm-perspect.png
index 743ae3c..74c9d34 100644
--- a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/bpm-perspect.png
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/bpm-perspect.png
Binary files differ
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/perspec-comp.png b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/perspec-comp.png
index a7c3dc7..94b396b 100644
--- a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/perspec-comp.png
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/perspec-comp.png
Binary files differ
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/perspec.png b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/perspec.png
index 462803a..5d9acb0 100644
--- a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/perspec.png
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/perspec.png
Binary files differ
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-data-flow.htm b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-data-flow.htm
index e16715e..ca05de5 100644
--- a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-data-flow.htm
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-data-flow.htm
@@ -37,9 +37,16 @@ is indicated by arrows:
</ul>
<p>In case multiple data mappings exist between one data and one activity, only the first data mapping
is displayed.</p>
+<p>This chapter covers:</p>
+<ul>
+ <li><a href="#crd">Creating Data Flow Connection</a></li>
+ <li><a href="#ddf">Deleting Data Flow</a></li>
+ <li><a href="#ved">Viewing and Editing Data Flow Properties</a></li>
+ <li><a href="#wef">Data Mappings in Process Interface Context</a></li>
+</ul>
-<h2>Creating Data Flow Connection</h2>
+<h2 id="crd">Creating Data Flow Connection</h2>
<p>You can create data flow connections using two different ways: </p>
<ul>
<li>In the toolbar, click <strong>Create Connector</strong> icon and connect data with activity</li>
@@ -55,13 +62,13 @@ is displayed.</p>
</ul>
-<h2>Deleting Data Flow</h2>
+<h2 id="ddf">Deleting Data Flow</h2>
<p>Hover the mouse in proximity of the data flow connector and click the <strong>Delete</strong> icon.</p>
<p class="image"><img SRC="images/del-df.png">
<br><strong>Figure:</strong> Delete Data Flow</p>
-<h2>Viewing and Editing Data Flow Properties</h2>
+<h2 id="ved">Viewing and Editing Data Flow Properties</h2>
<p>To view and edit properties of data flow, perform the following steps:</p>
<ol>
@@ -91,7 +98,7 @@ is displayed.</p>
</li>
</ol>
-<h2>Data Mappings in Process Interface Context</h2>
+<h2 id="wef">Data Mappings in Process Interface Context</h2>
<p>The Process Interface Context is needed when one model is referring to another model through exposed process interface.
Suppose the referred subprocess has IN parameters defined and it returns the result. Then, in this case. the called process
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 487e1bd..6cdec01 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,7 +51,7 @@ Following elements need special treatment either in Eclipse-based modeler or web
</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
-the 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 (you can drag-and-drop gateway symbol from the toolbar).
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>
@@ -105,7 +105,7 @@ When imported, only those models are displayed properly in the Business Process
<li>A pair of the two </li>
</ul>
<p>In case multiple data mappings exist between one data and one activity, only the first data mapping
-will be displayed.</p>
+is displayed.</p>
<h3 id="conf">Conditional Sequence Flow</h3>
<p>The web-based modeler supports setting conditional sequence flow only from gateways to activities.
However, if you import a model created in Eclipse and it has conditional sequence flow from activity to activity.
@@ -157,11 +157,11 @@ Eclipse-based modeler. </p>
<td>Lifecycle</td>
</tr>
<tr>
- <td>Document</td>
+ <td>Document Data</td>
<td>Data</td>
</tr>
<tr>
- <td>Primitive </td>
+ <td>Primitive Data</td>
<td>Data</td>
</tr>
<tr>
@@ -179,15 +179,31 @@ Eclipse-based modeler. </p>
</tr>
<tr>
- <td>Route Activity</td>
+ <td>None Task</td>
<td>Activity </td>
</tr>
<tr>
- <td>Manual Activity</td>
+ <td>Manual Task</td>
<td>Activity</td>
</tr>
<tr>
- <td>Application Activity</td>
+ <td>User Task</td>
+ <td>Activity</td>
+ </tr>
+ <tr>
+ <td>Service Task</td>
+ <td>Activity</td>
+ </tr>
+ <tr>
+ <td>Script Task</td>
+ <td>Activity</td>
+ </tr>
+ <tr>
+ <td>Send Task</td>
+ <td>Activity</td>
+ </tr>
+ <tr>
+ <td>Receive Task</td>
<td>Activity</td>
</tr>
<tr>
@@ -268,18 +284,7 @@ can only edit General Properties of these elements. </p>
<th width="2%">Element</th>
<th width="2%">Type</th>
</tr>
- <tr>
- <td>JMS Trigger</td>
- <td>Lifecycle</td>
- </tr>
- <tr>
- <td>Mail Trigger</td>
- <td>Lifecycle</td>
- </tr>
- <tr>
- <td>Timer Trigger</td>
- <td>Lifecycle</td>
- </tr>
+
<tr>
<td>Document List </td>
<td>Data</td>
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-org-struct.htm b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-org-struct.htm
index fe2f1b7..afe5330 100644
--- a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-org-struct.htm
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-org-struct.htm
@@ -179,7 +179,7 @@ alt=""><br>
</li>
<li>Data Path - Specify the data path for the selected data</li></ul></li>
<li>Team Lead - Click the Team Lead tab to specify the role that can act as a team lead.
- There can only be one team leader per organization. You can also define the team leader, using the
+ There can be only one team leader per organization. You can also define the team leader, using the
<a href="#set">Set as Manager</a> option.
<ul>
<li>Leader - By default, None is selected. You need to select the role from the drop-down list.
@@ -299,7 +299,7 @@ alt=""><br>
<h2 id="condPerformers">Conditional Performer</h2>
<p>The conditional performer is evaluated at runtime and it determines the identity of the actual performer.
-Conditional performer can be created only at the root node. You cannot create it under Organization node and
+Conditional performer can be created only at the root node, that is, Participant node. You cannot create it under Organization node and
cannot drag and drop under Organization node. The following sections help you to work with conditional performers.</p>
<h3>Creating Conditional Performer</h3>
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-pools-lanes.htm b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-pools-lanes.htm
index fbe1ff5..b88c2ad 100644
--- a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-pools-lanes.htm
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-pools-lanes.htm
@@ -246,7 +246,7 @@ drop the element. In that case, the following message is displayed:</p>
<p class="image"><img src="images/drag-val.png"
alt="Validation Drag and Drop Operation - Element with same ID" /> <br>
<strong>Figure:</strong> Validation Drag and Drop Operation - Element with same ID</p>
-
+<p>You should change the name of the element which changes the ID accordingly, to enable drag and drop operation.</p>
<script language="JavaScript" type="text/javascript">
<!--
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-struct-type.htm b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-struct-type.htm
index 4e7f1e0..7465264 100644
--- a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-struct-type.htm
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-struct-type.htm
@@ -188,9 +188,8 @@ node in the <strong>My Process Models</strong> panel.</p>
<h2 id="ref">Working with Referenced Structured Type</h2>
<p>If the Public Visibility property is selected for the structured type in the referenced model then you
-can refer the structured type in the another model. Note that the structured types
-from the referenced model are read only. You cannot edit the referenced structured types.
-To refer the structure data:
+can refer the structured type in another model.
+To refer the structure type:
</p>
<p>Drag and drop the structured type to referencing process from the <strong>Structured Type</strong> node