summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorVrishali Doke2012-08-29 02:23:21 (EDT)
committer Stephan Born2012-08-29 02:23:21 (EDT)
commit773721290e6c04253b9e587ffff119cc9432d3b8 (patch)
tree422ccf094096b1942de69f72d33c25b9fa19418e
parent9b20f956666fffabe2c5e7c112613a7e6b0fbc8e (diff)
downloadorg.eclipse.stardust.documentation-773721290e6c04253b9e587ffff119cc9432d3b8.zip
org.eclipse.stardust.documentation-773721290e6c04253b9e587ffff119cc9432d3b8.tar.gz
org.eclipse.stardust.documentation-773721290e6c04253b9e587ffff119cc9432d3b8.tar.bz2
CRNT-25558 - Updated analogy of models
git-svn-id: http://emeafrazerg/svn/ipp/product/trunk/stardust/documentation@58747 8100b5e0-4d52-466c-ae9c-bdeccbdeaf6b
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/unsupported-element-msg.pngbin0 -> 11835 bytes
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/mg-modeler-preface.html236
2 files changed, 141 insertions, 95 deletions
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/unsupported-element-msg.png b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/unsupported-element-msg.png
new file mode 100644
index 0000000..f565213
--- /dev/null
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/unsupported-element-msg.png
Binary files differ
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/mg-modeler-preface.html b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/mg-modeler-preface.html
index 60fe2d9..d6ea175 100644
--- a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/mg-modeler-preface.html
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/mg-modeler-preface.html
@@ -19,19 +19,10 @@
-->
</script>
<h1>The Process Workbench</h1>
-<p>This chapter serves as a user guide to model processes with the @productname@
-Process Workbench.</p>
-<!-- <p>In the @productnameonly@ Process Workbench you can construct and manage workflow
-models. It will be used primarily by modelers and integrators. By using it they
-can define their company's business processes in an easy and efficient way: the
-elements of a business process have been provided as graphically represented
-building blocks. The role of a modeler is to put them together in a diagram.
-Each building block is described by an element-specific set of properties and
-its relationships or connections to other elements of the process model. Both
-must be specified by the modeler at build time.</p> -->
+<p>This chapter provides overview of the elements to model processes with the @productname@
+Business Process Modeling perspective.</p>
-
-<p>The Business Process Modeling perspective supports the Business Process Model and Notation (BPMN)
+<p>The Business Process Modeling perspective uses the Business Process Model and Notation (BPMN)
standards. The business process modelers' and integrators can use it to create intuitive business
process workflows. The business process diagrams are supported using various elements.
Such as swim lanes, activities, gateways, data objects etc. These elements of a business
@@ -47,13 +38,145 @@ Installation</a> of the
<a href="PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/handbooks/installation/ig-preface.htm">
Developer Installation Guide</a>.</p>
-<h2>Analogy of Models Created in Eclipse Modeler and Business Process Modeler</h2>
+<h2>Analogy of Models Created in the Eclipse Modeler and the Business Process Modeler
+</h2>
-<p>The @productnameonly@ Process Platform version 7.1 supports creation of workflow models in two ways.
-Firstly, you can create models in Eclipse modeler and secondly, in Business Process Modeler of
+<p>The @productname@ Process Platform supports creation of workflow models in two ways.
+Firstly, you can create models in the @productname@ Process Platform's Eclipse-based modeler and secondly,
+in the Business Process Modeling perspective of
@productname@ Process Platform. However, some of the model elements are not supported in
-Business Process Modeler. For those unsupported elements, you should use Eclipse modeler.</p>
+Business Process Modeling perspective. For those unsupported elements, you should use @productname@ Process Platform's
+Eclipse-based modeler. </p>
+<h3>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>
+ <th width="1%">Element</th>
+ <th width="1%">Type</th>
+ </tr>
+ <tr>
+ <td>Manual Trigger</td>
+ <td>Lifecycle</td>
+ </tr>
+ <tr>
+ <td>Scan Trigger</td>
+ <td>Lifecycle</td>
+ </tr>
+ <tr>
+ <td>Camel Trigger</td>
+ <td>Lifecycle</td>
+ </tr>
+ <tr>
+ <td>End Event</td>
+ <td>Lifecycle</td>
+ </tr>
+ <tr>
+ <td>Document</td>
+ <td>Data</td>
+ </tr>
+ <tr>
+ <td>Primitive </td>
+ <td>Data</td>
+ </tr>
+ <tr>
+ <td>Structured Data</td>
+ <td>Data</td>
+ </tr>
+ <tr>
+ <td>Message Transformation Application</td>
+ <td>Application</td>
+ </tr>
+ <tr>
+ <td>Web Service Application </td>
+ <td>Application</td>
+ </tr>
+ <tr>
+ <td>Camel Application </td>
+ <td>Application</td>
+ </tr>
+ <tr>
+ <td>UI Mashup Application</td>
+ <td>Application</td>
+ </tr>
+ <tr>
+ <td>Route Activity</td>
+ <td>Activity </td>
+ </tr>
+ <tr>
+ <td>Manual Activity</td>
+ <td>Activity</td>
+ </tr>
+ <tr>
+ <td>Application Activity</td>
+ <td>Activity</td>
+ </tr>
+ <tr>
+ <td>Subprocess Activity</td>
+ <td>Activity</td>
+ </tr>
+ <tr>
+ <td>Role</td>
+ <td>Participants </td>
+ </tr>
+ <tr>
+ <td>Organization</td>
+ <td>Participants</td>
+ </tr>
+
+</table>
+
+
+
+
+
<h3>Unsupported Elements</h3>
+<p>Unsupported elements are displayed in My Process Models pane and Process Diagrams 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>
+ <th>Supported</th>
+ <th>Not Supported</th>
+ </tr>
+ <tr>
+ <td>Create</td>
+ <td>-</td>
+ <td>Not Supported</td>
+ </tr>
+ <tr>
+ <td>Edit</td>
+ <td>Only General Properties are editable</td>
+ <td>Other specific properties such as, class name for Java application type are not editable</td>
+ </tr>
+ <tr>
+ <td>View</td>
+ <td>Only General properties are displayed</td>
+ <td>Other specific properties such as, class name for Java application type are not displayed</td>
+ </tr>
+ <tr>
+ <td>Rename</td>
+ <td>Supported</td>
+ <td>-</td>
+ </tr>
+ <tr>
+ <td>Delete</td>
+ <td>Supported</td>
+ <td>-</td>
+ </tr>
+
+</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">
@@ -155,85 +278,8 @@ Business Process Modeler. For those unsupported elements, you should use Eclipse
</tr>
</table>
-<h3>Supported Elements</h3>
-
-<p>Following is the list of supported elements.</p>
-<table width="1%" border="1" id="id_3">
- <tr>
- <th width="1%">Element</th>
- <th width="1%">Type</th>
- </tr>
- <tr>
- <td>Manual Trigger</td>
- <td>Lifecycle</td>
- </tr>
- <tr>
- <td>Scan Trigger</td>
- <td>Lifecycle</td>
- </tr>
- <tr>
- <td>Camel Trigger</td>
- <td>Lifecycle</td>
- </tr>
- <tr>
- <td>End Event</td>
- <td>Lifecycle</td>
- </tr>
- <tr>
- <td>Document</td>
- <td>Data</td>
- </tr>
- <tr>
- <td>Primitive </td>
- <td>Data</td>
- </tr>
- <tr>
- <td>Structured Data</td>
- <td>Data</td>
- </tr>
- <tr>
- <td>Message Transformation Application</td>
- <td>Application</td>
- </tr>
- <tr>
- <td>Web Service Application </td>
- <td>Application</td>
- </tr>
- <tr>
- <td>Camel Application </td>
- <td>Application</td>
- </tr>
- <tr>
- <td>UI Mashup Application</td>
- <td>Application</td>
- </tr>
- <tr>
- <td>Route Activity</td>
- <td>Activity </td>
- </tr>
- <tr>
- <td>Manual Activity</td>
- <td>Activity</td>
- </tr>
- <tr>
- <td>Application Activity</td>
- <td>Activity</td>
- </tr>
- <tr>
- <td>Subprocess Activity</td>
- <td>Activity</td>
- </tr>
- <tr>
- <td>Role</td>
- <td>Participants </td>
- </tr>
- <tr>
- <td>Organization</td>
- <td>Participants</td>
- </tr>
-
-</table>
+<!--
<h2>Content</h2>
<ul>
@@ -286,7 +332,7 @@ Business Process Modeler. For those unsupported elements, you should use Eclipse
<li><a href="mg-deploy-model.html">Deploying a Workflow Model</a></li>
<li><a href="mg-defdesk-18.htm">Debugging Process Definitions</a></li>
<li><a href="mg-internationalization.html">Native Language Support</a></li>
-</ul>
+</ul> -->
<script language="JavaScript" type="text/javascript">
<!--
writeFooter();