summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorVrishali Doke2012-08-30 06:13:53 (EDT)
committer Stephan Born2012-08-30 06:13:53 (EDT)
commit7ef46ca198f975ceb48f08774bddaafd6322aea0 (patch)
treeaa4a554db43758f3a7e74fa1243c54ad5510f70c
parent9b25c32e970653dac4b4b2ccf41419f59186acb3 (diff)
downloadorg.eclipse.stardust.documentation-7ef46ca198f975ceb48f08774bddaafd6322aea0.zip
org.eclipse.stardust.documentation-7ef46ca198f975ceb48f08774bddaafd6322aea0.tar.gz
org.eclipse.stardust.documentation-7ef46ca198f975ceb48f08774bddaafd6322aea0.tar.bz2
CRNT-25597 - Pepper guide structure
git-svn-id: http://emeafrazerg/svn/ipp/product/trunk/stardust/documentation@58795 8100b5e0-4d52-466c-ae9c-bdeccbdeaf6b
-rw-r--r--org.eclipse.stardust.docs.analyst/analysttoc.xml99
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/create-act-fly.pngbin0 -> 7883 bytes
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/create-act.pngbin0 -> 3638 bytes
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/del-act.pngbin0 -> 6333 bytes
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/mg-copy-paste-elements.html721
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/mg-import-1.htm365
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/mg-preface.htm75
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/mg-ref-elements.htm45
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/mg-xml-1.htm150
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/model-views/pep-diagrams.html (renamed from org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/model-views/views-diagrams.html)0
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/model-views/pep-panles.html (renamed from org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/model-views/views-outline.html)0
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/models/model-clean.html110
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/models/model-save.html (renamed from org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/models/model-element-refs.html)0
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/models/model-upgrade.html60
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/models/model-validation.html89
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/models/pep-deploy-model.html (renamed from org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/mg-deploy-model.html)0
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-activities.htm (renamed from org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/mg-defdesk-4.htm)535
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-annotation.htm (renamed from org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/mg-defdesk-15.htm)100
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-application.htm (renamed from org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/mg-defdesk-6.htm)200
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-con-sequence.htm (renamed from org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/mg-defdesk-5.htm)558
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-data-flow.htm (renamed from org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/mg-defdesk-8.htm)168
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-data.htm (renamed from org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/mg-defdesk-7.htm)186
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-modeler-preface.html (renamed from org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/mg-modeler-preface.html)401
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-org-struct.htm (renamed from org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/mg-defdesk-10.htm)1070
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-perspective-overview.html (renamed from org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/mg-modeler-views.html)6
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-pools-lanes.htm (renamed from org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/mg-pools-lanes.htm)56
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-session-log.htm180
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/process-effort-calculation.html126
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/property-page-authorization.html472
29 files changed, 1889 insertions, 3883 deletions
diff --git a/org.eclipse.stardust.docs.analyst/analysttoc.xml b/org.eclipse.stardust.docs.analyst/analysttoc.xml
index a1ca2c1..325fdd3 100644
--- a/org.eclipse.stardust.docs.analyst/analysttoc.xml
+++ b/org.eclipse.stardust.docs.analyst/analysttoc.xml
@@ -11,58 +11,49 @@
SunGard CSA LLC - initial API and implementation and/or initial documentation
-->
<toc label="Business Process Modeling Handbook" link_to="toc.xml#analysttoc">
- <topic label="Business Process Modeling guide" href="html/handbooks/modelling_analyst/mg-preface.htm">
- <topic label="The Process Workbench" href="html/handbooks/modelling_analyst/mg-modeler-preface.html">
- <topic label="Setting @productname@ Preferences" href="html/handbooks/modelling_analyst/mg-preferences.html" />
- <topic label="The Business Process Modeling Perspective" href="html/handbooks/modelling_analyst/mg-modeler-views.html" >
- <topic label="Panels" href="html/handbooks/modelling_analyst/model-views/views-outline.html"/>
- <topic label="Working with Diagrams" href="html/handbooks/modelling_analyst/model-views/views-diagrams.html"/>
- </topic>
- <topic label="Working with Models" href="html/handbooks/modelling_analyst/models/model-preface.html">
- <topic label="Model Upgrade" href="html/handbooks/modelling_analyst/models/model-upgrade.html"/>
- <topic label="Creating and Deleting Models" href="html/handbooks/modelling_analyst/models/model-handling.html"/>
- <topic label="Model Properties" href="html/handbooks/modelling_analyst/models/model-props.html"/>
- <topic label="Workflow Model Validation" href="html/handbooks/modelling_analyst/models/model-validation.html"/>
- <topic label="Importing and Exporting Models" href="html/handbooks/modelling_analyst/models/model-import.html"/>
- <topic label="Element References" href="html/handbooks/modelling_analyst/models/model-element-refs.html"/>
- <topic label="Cleaning Up Models" href="html/handbooks/modelling_analyst/models/model-clean.html"/>
- </topic>
- <topic label="Working with Process Definitions" href="html/handbooks/modelling_analyst/pep-process.htm" />
- <topic label="Specifying Activities" href="html/handbooks/modelling_analyst/mg-defdesk-4.htm" />
- <topic href="html/handbooks/modelling_analyst/pep-connect-sybol.htm" label="Connecting Symbols">
- </topic>
- <topic label="Working with Gateways" href="html/handbooks/modelling_analyst/pep-gateways.htm" />
- <topic label="Specifying Applications" href="html/handbooks/modelling_analyst/mg-defdesk-6.htm" />
- <topic label="Specifying Data" href="html/handbooks/modelling_analyst/mg-defdesk-7.htm" />
- <topic label="Specifying Data Mappings" href="html/handbooks/modelling_analyst/mg-defdesk-8.htm" />
- <topic label="Modeling the Organizational Structure" href="html/handbooks/modelling_analyst/mg-defdesk-10.htm" />
- <topic label="Using Annotations" href="html/handbooks/modelling_analyst/mg-defdesk-15.htm" />
- <topic href="html/handbooks/modelling_analyst/mg-pools-lanes.htm" label="Swim Lanes Usage">
- </topic>
- <topic href="html/handbooks/modelling_analyst/pep-events.htm" label="Working with Events">
- </topic>
- <topic label="Copying and Pasting Modeled Elements" href="html/handbooks/modelling_analyst/mg-copy-paste-elements.html" />
- <topic label="Authorization" href="html/handbooks/modelling_analyst/property-page-authorization.html" />
- <topic label="Project Effort Calculation" href="html/handbooks/modelling_analyst/process-effort-calculation.html" />
- <topic href="html/handbooks/modelling_analyst/mg-ref-elements.htm" label="Referencing Model Elements">
- </topic>
- <topic label="Deploying a Workflow Model" href="html/handbooks/modelling_analyst/mg-deploy-model.html" />
- </topic>
- <topic label="@productname@ File Formats">
- <topic label="The Model File Format" href="html/handbooks/modelling_analyst/mg-xml-1.htm" />
- </topic>
- <topic label="Importing other File Formats">
- <topic label="Importing Models from other Formats" href="html/handbooks/modelling_analyst/mg-import-1.htm" />
- </topic>
- <topic label="Collaborative Modeling" href="html/handbooks/modelling_analyst/concurrency/con-preface.html">
- <topic label="Introduction" href="html/handbooks/modelling_analyst/concurrency/con-introduction.html"/>
- <topic label="Concurrency Control" href="html/handbooks/modelling_analyst/concurrency/con-control.html"/>
- <topic label="Locking and Unlocking Model Elements" href="html/handbooks/modelling_analyst/concurrency/con-locking.html"/>
- <topic label="Committing Changes" href="html/handbooks/modelling_analyst/concurrency/con-commit.html"/>
- <topic label="Reverting Changes" href="html/handbooks/modelling_analyst/concurrency/con-revert.html"/>
- <topic label="Updating Model and Model Elements" href="html/handbooks/modelling_analyst/concurrency/con-update.html"/>
- <topic label="Working with Model Elements in Concurrency Mode" href="html/handbooks/modelling_analyst/concurrency/con-editing.html"/>
- <topic label="Watching Collaborative Modeling Activities" href="html/handbooks/modelling_analyst/concurrency/con-vcs-view.html"/>
- </topic>
- </topic>
+ <topic href="html/handbooks/modelling_analyst/pep-modeler-preface.html" label="The Process Workbench">
+ <topic href="html/handbooks/modelling_analyst/pep-perspective-overview.html" label="The Business Process Modeling Perspective">
+ <topic href="html/handbooks/modelling_analyst/model-views/pep-panles.html" label="Panels">
+ </topic>
+ <topic href="html/handbooks/modelling_analyst/model-views/pep-diagrams.html" label="The Diagram Canvas">
+ </topic>
+ </topic>
+ <topic href="html/handbooks/modelling_analyst/models/model-preface.html" label="Working with Models">
+ <topic href="html/handbooks/modelling_analyst/models/model-props.html" label="Model Properties">
+ </topic>
+ <topic href="html/handbooks/modelling_analyst/models/model-handling.html" label="Creating and Deleting Models">
+ </topic>
+ <topic href="html/handbooks/modelling_analyst/models/model-import.html" label="Importing Models">
+ </topic>
+ <topic href="html/handbooks/modelling_analyst/models/model-save.html" label="Saving Models">
+ </topic>
+ <topic href="html/handbooks/modelling_analyst/models/pep-deploy-model.html" label="Deploying a Process Model">
+ </topic>
+ </topic>
+ <topic href="html/handbooks/modelling_analyst/pep-process.htm" label="Working with Process Definitions">
+ </topic>
+ <topic href="html/handbooks/modelling_analyst/pep-activities.htm" label="Specifying Activities">
+ </topic>
+ <topic href="html/handbooks/modelling_analyst/pep-con-sequence.htm" label="Working with Sequence Flow">
+ </topic>
+ <topic href="html/handbooks/modelling_analyst/pep-application.htm" label="Specifying Application">
+ </topic>
+ <topic href="html/handbooks/modelling_analyst/pep-data.htm" label="Specifying Data">
+ </topic>
+ <topic href="html/handbooks/modelling_analyst/pep-data-flow.htm" label="Specifying Data Flow">
+ </topic>
+ <topic href="html/handbooks/modelling_analyst/pep-gateways.htm" label="Working with Gateways">
+ </topic>
+ <topic href="html/handbooks/modelling_analyst/pep-org-struct.htm" label="Modeling Organization Structure">
+ </topic>
+ <topic href="html/handbooks/modelling_analyst/pep-events.htm" label="Working with Events">
+ </topic>
+ <topic href="html/handbooks/modelling_analyst/pep-pools-lanes.htm" label="Swim Lanes Usage">
+ </topic>
+ <topic href="html/handbooks/modelling_analyst/pep-session-log.htm" label="Modeling Session Log">
+ </topic>
+ </topic>
+
+
+
</toc>
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/create-act-fly.png b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/create-act-fly.png
new file mode 100644
index 0000000..d75818f
--- /dev/null
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/create-act-fly.png
Binary files differ
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/create-act.png b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/create-act.png
new file mode 100644
index 0000000..68e25f7
--- /dev/null
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/create-act.png
Binary files differ
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/del-act.png b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/del-act.png
new file mode 100644
index 0000000..9c76129
--- /dev/null
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/del-act.png
Binary files differ
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/mg-copy-paste-elements.html b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/mg-copy-paste-elements.html
deleted file mode 100644
index 6464d6d..0000000
--- a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/mg-copy-paste-elements.html
+++ /dev/null
@@ -1,721 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<link rel="STYLESHEET" href="../../styles/carnot.css"
- charset="ISO-8859-1" type="text/css">
-<title>Copying and Pasting Modeled Elements</title>
-<script language="JavaScript" src="../../styles/naviLine.js"
- type="text/javascript"></script>
-</head>
-<body>
-<script language="JavaScript" type="text/javascript">
-<!--
- writeNavigation("Authorization","PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/toc.html",
- "mg-pools-lanes.htm","property-page-authorization.html",
- "../../toc.html","Business Analyst Handbooks",
- "mg-preface.htm","The Modeling Guide",
- "mg-modeler-preface.html","The Process Workbench");
- -->
-</script>
-<h1>Copying and Pasting Modeled Elements</h1>
-<p>To define new model elements similar to ones you already modeled,
-you can use copies of these already modeled elements as a basis. In the
-@productnameonly@ Process Workbench you can copy, paste or cut model elements in
-the Outline view or diagram canvas by options in the context-menu or by
-key-strokes. You can move or copy model elements between process
-definitions as well as between models.</p>
-<p>If you want to use similar activities with a rather complex
-configuration, you don't have to recreate them entirely in the target
-process definition or model. Undo is possible for all operations. To
-revoke your copy, paste or cut action please select <strong>Edit
-&gt; Undo</strong> or use the <strong>Ctrl-Z</strong> key-stroke.</p>
-<ul>
- <li><a href="#clipBoard">Clipboard and Copy Sets</a></li>
- <li><a href="#copy">Copying Elements</a></li>
- <li><a href="#cut">Cutting Elements</a></li>
- <li><a href="#paste">Pasting Elements</a></li>
- <!-- <li><a href="#refactor">Refactoring</a></li> -->
- <li><a href="#reference">Copying By Reference or By Value</a></li>
- <li><a href="#useCases">Example Use Cases</a></li>
- <li><a href="#tables">Overview of Gestures</a></li>
-</ul>
-<h2 id="clipBoard">Clipboard and Copy Sets</h2>
-<p>The set of elements are copied to and pasted from the @productname@
-clipboard. This clipboard can also be used across model boundaries. The
-clipboard content is called a <strong>copy set</strong>.</p>
-<p>Copy sets of the following elements are supported:</p>
-<ul>
- <li>Structured Types</li>
- <li>Data</li>
- <li>Applications</li>
- <li>Participants</li>
- <li>Process definitions</li>
- <li>Process and model diagrams</li>
- <li>Fragments of activity-transition graphs in process definitions</li>
-</ul>
-<p>Process models can be copied via copying the XPDL files.</p>
-<p>A copy set may contain an arbitrary number of model elements of
-arbitrary type, which could be for example three data, two participants
-and an application:</p>
-<p class="image"><img src="images/cp-copy-set-example.png"
- alt="Copy Set Example with Elements of Arbitrary Type" /><br>
-<strong>Figure:</strong> Copy Set Example with Elements of Arbitrary
-Type</p>
-<h2 id="copy">Copying Elements</h2>
-<p>You have the possibility to copy elements from the <a
- href="#outline">Outline View</a> or from the <a href="#diagram">Diagram
-Canvas</a>.</p>
-<h3 id="outline">Copying from the Outline View</h3>
-<p>In the Outline view copying is possible for the following types:</p>
-<ul>
- <li>Structured Types</li>
- <li>Applications</li>
- <li>Data</li>
- <li>Participants</li>
- <li>Processes</li>
- <li>Diagrams</li>
- <li>Activities</li>
- <li>Triggers</li>
-</ul>
-<p>To copy one or more elements in the Outline view do the
-following:</p>
-<ul>
- <li>Right-click one or more elements to be copied in the Outline
- view.</li>
- <li>Select <strong>Copy Element</strong>.</li>
-</ul>
-<p class="image"><img class="noborder"
- src="images/cp-copy-role-in-outline.png"
- alt="Copying an Element in the Outline View" /><br>
-<strong>Figure:</strong> Copying an Element in the Outline View</p>
-<!-- TODO screenshot -->
-<h3 id="diagram">Copying from the Diagram</h3>
-<p>In diagrams copying is possible for the following types:</p>
-<ul>
- <li>Lanes</li>
- <li>Activities</li>
- <li>Applications</li>
- <li>Data</li>
- <li>Participants</li>
- <li>Triggers</li>
- <li>Process Definitions</li>
-</ul>
-<p>To copy one or more elements in the diagram canvas do the
-following:</p>
-<ul>
- <li>Right-click one or more elements to be copied in the Outline
- view.</li>
- <li>Select <strong>Copy Element</strong>.</li>
-</ul>
-<p class="image"><img src="images/cp-copy-element-in-diagram.png"
- alt="Copying an Element in the Diagram" /><br>
-<strong>Figure:</strong> Copying an Element in the Diagram</p>
-<p>Please note that the copying option is not available if the
-selection contains unsupported element types like gateways. All
-necessary gateways will be added automatically after the copying
-process, but cannot be copied explicitly.</p>
-<h2 id="cut">Cutting Elements</h2>
-<p>Cutting Elements is possible for the same elements as for copying
-elements as described in the sections above.</p>
-<h3>Cutting Elements from the Outline View</h3>
-<p>To cut one or more elements in the Outline view do the following:</p>
-<ul>
- <li>Right-click one or more elements to be cut in the Outline
- view.</li>
- <li>Select <strong>Cut Element</strong>.</li>
-</ul>
-<p class="image"><img src="images/cp-cut-elements-in-outline.png"
- alt="Cutting Elements in the Outline View" /><br>
-<strong>Figure:</strong> Cutting Elements in the Outline View</p>
-<h3>Cutting Elements in Diagrams</h3>
-<p>To cut one or more elements in the diagram canvas do the
-following:</p>
-<ul>
- <li>Select one or more elements you want to be cut from the
- diagram canvas.</li>
- <li>Right-click and choose <strong>Cut Element</strong>.</li>
-</ul>
-<p class="image"><img src="images/cp-cut-elements-in-diagram.png"
- alt="Cutting Elements in a Diagram" /><br>
-<strong>Figure:</strong> Cutting Elements in a Diagram</p>
-<p>Please note that the cut option is not available if the selection
-contains unsupported element types like gateways. All necessary gateways
-will be added automatically during the subsequent paste process, but
-cannot be cut explicitly.</p>
-
-<h2 id="paste">Pasting Elements</h2>
-<p>You can paste elements to the Outline View or to the diagram
-canvas, depending on where you cut or copied them. The <strong>Paste
-Element</strong> option for process definition diagrams is only enabled for
-diagrams of the same process definition.</p>
-<p>Note that the <strong>Paste Element</strong> option is only
-enabled for the group nodes like Data, Applications or Participants, if
-all top level elements in the clipboard are of the corresponding type.</p>
-<ul>
- <li><a href="#pasteOutline">Pasting to the Outline View</a></li>
- <li><a href="#pasteDiagram">Pasting to the Diagram</a></li>
- <li><a href="#semantics">Paste Semantics and Name/ID
- Collisions</a></li>
-</ul>
-<p>Pasting elements from the copy set to</p>
-<h3 id="pasteOutline">Pasting to the Outline View</h3>
-<p>To paste an element to the Outline View:</p>
-<ul>
- <li>Click the process or model to copy your element(s) to.</li>
- <li>Select <strong>Paste Element</strong>.</li>
-</ul>
-<p class="image"><img class="noborder"
- src="images/cp-paste-role-to-outline.png"
- alt="Pasting an Element to the Outline View" /><br>
-<strong>Figure:</strong> Pasting an Element to the Outline View</p>
-<h3 id="pasteDiagram">Pasting to the Diagram</h3>
-<p>To paste one or more elements in the diagram canvas do the
-following:</p>
-<ul>
- <li>Right-click on the diagram canvas.</li>
- <li>Select <strong>Paste Element</strong>.</li>
-</ul>
-<p class="image"><img src="images/cp-paste-element-in-diagram.png"
- alt="Pasting an Element in the Diagram" /><br>
-<strong>Figure:</strong> Pasting an Element in the Diagram</p>
-<h3 id="semantics">Paste Semantics and Name/ID Collisions</h3>
-<p>Elements copied into an arbitrary element ("target element") of
-the process model strucuture (e.g. activities into a process definition)
-will be put semantically under this element independently of their
-origin. This way, an activity-transition network from one process
-definition can be copied into another process definition. If a name or
-ID collision with existing elements occurs, a dialog pops up with name
-and ID proposals:</p>
-<p class="image"><img class="noborder"
- src="images/cp-paste-element-dialog.png" alt="Dialog" /><br>
-<strong>Figure:</strong> Change Name and ID of the Element.</p>
-<p>When copying and pasting elements with relationships to general
-model elements like participants or applications, you have to decide
-whether to copy by reference to this elements or to copy by value. This
-is described in detail in the following section.</p>
-<h2 id="reference">Copying By Reference or By Value</h2>
-<p>Model elements have hierarchical and other relationships to other
-model elements. Copy and paste operations maintain the hierarchical
-relationships as specified in the previous sections.</p>
-<p>In case elements are selected to be copied into another model,
-the selected elements may have references to other elements that are not
-selected explicitly. To prevent inconsistencies, all those referenced
-elements are also collected. If some or all of those elements already
-exist in the target model, a dialog opens where you can decide whether
-to copy by reference or by value. All elements selected in this dialog
-will be used from the target model and the according references are
-transferred to those. To copy the referenced elements from the source
-model to the target model, enable the according checkboxes.</p>
-<p>By default, all checkboxes for data, applications and
-participants are checked to be copied by reference. Enabling the
-checkboxes makes the tree item(s) editable with a default name and ID of
-"Copy of X/CopyOfX".</p>
-<ol>
- <li>Enable the elements to be copied by value.</li>
- <li>Enter a new name or leave the suggested name as <tt>CopyOf&lt;name&gt;</tt>
- and id as <tt>CopyOf&lt;id&gt;</tt> accordingly.</li>
-</ol>
-<p class="image"><img src="images/cp-how-to-copy-dialog.png" alt="" /><br>
-<strong>Figure:</strong> Choose the Elements to be copied by Reference
-or by Value.</p>
-<p>In case the suggested names <tt>CopyOf&lt;name&gt;</tt> or <tt>CopyOf&lt;id&gt;</tt>
-are already in use, you have to choose a new name and id. The duplicate
-name or id is marked red and the <strong>OK</strong> button is enabled:</p>
-<p class="image"><img src="images/cp-how-to-copy-dialog-red.png"
- alt="" /><br>
-<strong>Figure:</strong> Choose the Elements to be copied by Reference
-or by Value.</p>
-
-<h2 id="useCases">Example Use Cases</h2>
-<h3 id="moveCase">Moving Model Elements between Process Definitions</h3>
-<p>When processes change in a way that, for example, activities are
-now executed at a different stage in the process flow, it is possibly
-that the new execution point lies in a different process definition, for
-example a subprocess. In the modeler you can cut out the activities and
-paste them into the desired target process definition with the
-activities keeping all their configuration settings like events,
-participants, data paths, etc.</p>
-<p>In the following example two activities are shifted to another
-process definition by cutting them out and pasting them in the diagram
-of the new process definition. This process definition is then assigned
-as subprocess in the starting process definition.</p>
-<ol>
- <li>Select the set of elements to be shifted:
- <p class="image"><img src="images/cp-select-set-of-activities.png"
- alt="Select Activities and needed Elements." /><br>
- <strong>Figure:</strong> Select Elements.</p>
- </li>
- <li>Right-click and select <strong>Cut Element</strong>.
- <p class="image"><img src="images/cp-cut-set-of-activities.png"
- alt="Cutting out the selected Elements." /><br>
- <strong>Figure:</strong> Cutting out the selected Elements.</p>
- </li>
- <li>Open the diagram of the new process definition.</li>
- <li>Right-click on the canvas and select <strong>Paste
- Element</strong>.
- <p class="image"><img class="noborder"
- src="images/cp-paste-set-of-activities.png" alt="Pasting" /><br>
- <strong>Figure:</strong> Paste Activities and Elements to New Process
- Definition.</p>
- </li>
-</ol>
-<p>Now the element cut out from the diagram of the first process
-definition are pasted to the new process definition:</p>
-<p class="image"><img src="images/cp-shiftet-set-of-activities.png"
- alt="Pasted Activities in the New Process Definition." /><br>
-<strong>Figure:</strong> Pasted Activities in the New Process
-Definition.</p>
-<p>In the starting process definition you can now add a subprocess
-activity and assign the new process definition:</p>
-<ol>
- <li>Add a new activity and connect it to the precedent activity.</li>
- <li>Right-click and select <strong>Subprocess</strong>.</li>
- <li>Choose the process definition containing the copied elements.</li>
-</ol>
-<p class="image"><img src="images/cp-assign-subprocess.png"
- alt="Assign Subprocess" /><br>
-<strong>Figure:</strong> Assign the New Process to the Subprocess
-Activity.</p>
-
-
-<!-- delayed:
-
-<h3 id="refactorCase">Refactoring of Coherent Activities</h3>
-<p>As the number of activities in a process definition grows the need might arise to move some activities to a new
-subprocess in order to maintain a certain level of manageability. Select a number of coherent activities and move
-them to a new subprocess. A new process definition is then created and the activities in the old process definition
-are replaced with a subprocess acitivity that represents the newly created process.</p>
- -->
-<h2 id="tables">Overview of Gestures</h2>
-<p>The following section gives an overview of the operation
-gestures:</p>
-<ul>
- <li><a href="#copyOverview">Copy Gestures</a></li>
- <li><a href="#pasteOverview">Paste Gestures</a></li>
- <li><a href="#cutOverview">Cut Gestures</a></li>
-</ul>
-<h3 id="copyOverview">Copy Gestures</h3>
-<p>Copying is initiated by the following gestures on the following
-elements:</p>
-<table id='id'>
- <tr>
- <th>Elements/Gesture</th>
- <th>CTRL-C Keystroke</th>
- <th>Popup Menu Entry</th>
- </tr>
- <tr>
- <td>Structured Type</td>
- <td>
- <ul>
- <li>Model outline has focus.</li>
- <li>Structured type node(s) in outline tree is selected.</li>
- <li>CTRL-C is pressed.</li>
- </ul>
- </td>
- <td>
- <ul>
- <li>Model outline has focus.</li>
- <li>Copy item in popup menu for the structured type(s) node in
- outline tree is selected.</li>
- </ul>
- </td>
- </tr>
- <tr>
- <td>Data</td>
- <td>
- <ul>
- <li>Model outline has focus.</li>
- <li>Data node(s) in outline tree is selected.</li>
- <li>CTRL-C is pressed.</li>
- </ul>
- </td>
- <td>
- <ul>
- <li>Model outline has focus.</li>
- <li>Copy item in popup menu for the data node(s) in outline tree
- is selected.</li>
- </ul>
- </td>
- </tr>
- <tr>
- <td>Applications</td>
- <td>
- <ul>
- <li>Model outline has focus.</li>
- <li>Application node(s) in outline tree is selected.</li>
- <li>CTRL-C is pressed.</li>
- </ul>
- </td>
- <td>
- <ul>
- <li>Model outline has focus.</li>
- <li>Copy item in popup menu for application node(s) in outline.</li>
- </ul>
- </td>
- </tr>
- <tr>
- <td>Participants</td>
- <td>
- <ul>
- <li>Model outline has focus.</li>
- <li>Participant node(s) in outline tree is selected.</li>
- <li>CRTL-C is pressed.</li>
- </ul>
- </td>
- <td>
- <ul>
- <li>Model outline has focus.</li>
- <li>Copy item in popup menu for the participant node(s) in
- outline.</li>
- </ul>
- </td>
- </tr>
- <tr>
- <td>Process Definitions</td>
- <td>
- <ul>
- <li>Model outline has focus.</li>
- <li>Process Definition node(s) in outline tree is selected.</li>
- <li>CTRL-C is pressed.</li>
- </ul>
- </td>
- <td>
- <ul>
- <li>Model outline has focus.</li>
- <li>Copy item in popup menu for the process definition node(s)
- in outline.</li>
- </ul>
- </td>
- </tr>
- <tr>
- <td>Process and model diagrams</td>
- <td>
- <ul>
- <li>Model outline has focus.</li>
- <li>Diagram node(s) in outline tree is selected.</li>
- <li>CTRL-C is pressed.</li>
- </ul>
- </td>
- <td>
- <ul>
- <li>Model outline has focus.</li>
- <li>Copy item in popup menu for the diagram node(s) in outline.</li>
- </ul>
- </td>
- </tr>
- <tr>
- <td>Fragments of activity-transition graphs in process
- definitions</td>
- <td>
- <ul>
- <li>Process diagram has focus.</li>
- <li>Model elements to be copied are selected via their symbols
- in the diagram (e.g. using the rubberband or multiple mouse clicks)</li>
- <li>CTRL-C is pressed.</li>
- </ul>
- </td>
- <td>
- <ul>
- <li>Process diagram has focus.</li>
- <li>Model elements to be copied are selected via their symbols
- in the diagram (e.g. using the rubberband or multiple mouse clicks)</li>
- <li>Copy item in popup menu the diagram is selected.</li>
- </ul>
- </td>
- </tr>
-</table>
-<br>
-<h3 id="pasteOverview">Paste Gestures</h3>
-<p>Pasting is initiated by the following gestures on the following
-elements:</p>
-<table id='id_1'>
- <tr>
- <th>Elements/Gesture</th>
- <th>CTRL-V Keystroke</th>
- <th>Popup Menu Entry</th>
- </tr>
- <tr>
- <td>Structured Types</td>
- <td>
- <ul>
- <li>Model outline has scope.</li>
- <li>Copy/ies of the structured types elements in the clipboard
- are copied in the structured types section of the process model.</li>
- </ul>
- </td>
- <td>
- <ul>
- <li>Model outline has scope.</li>
- <li>Paste item in popup menu for model or Structured Types
- category node in the outline tree is selected*.</li>
- <li>Copy/ies of the data model elements in the copy set are
- copied under the Structured Types category of the process model.</li>
- </ul>
- </td>
- </tr>
- <tr>
- <td>Data</td>
- <td>
- <ul>
- <li>Model outline has scope.</li>
- <li>Copy/ies of the data model elements in the clipboard are
- copied in the data section of the process model.</li>
- </ul>
- </td>
- <td>
- <ul>
- <li>Model outline has scope.</li>
- <li>Paste item in popup menu for model or Data category node in
- the outline tree is selected*.</li>
- <li>Copy/ies of the data model elements in the copy set are
- copied under the Data category of the process model.</li>
- </ul>
- </td>
- </tr>
- <tr>
- <td>Applications</td>
- <td>
- <ul>
- <li>Model outline has scope.</li>
- <li>Copy/ies of the application elements in the clipboard are
- copied in the data section of the process model.</li>
- </ul>
- </td>
- <td>
- <ul>
- <li>Model outline has scope.</li>
- <li>Paste item in popup menu for model or Application category
- node in the outline tree is selected*.</li>
- <li>Copy/ies of the application model elements in the copy set
- are copied under the Applications category of the process model.</li>
- </ul>
- </td>
- </tr>
- <tr>
- <td>Participants</td>
- <td>
- <ul>
- <li>Model outline has scope.</li>
- <li>Copy/ies of the participant elements in the clipboard are
- copied in the data section of the process model.</li>
- </ul>
- </td>
- <td>
- <ul>
- <li>Model outline has scope.</li>
- <li>Paste item in popup menu for model or Participants category
- node in the outline tree is selected*.</li>
- <li>Copy/ies of the data model elements in the copy set are
- copied under the Participants section of the process model.</li>
- </ul>
- </td>
- </tr>
- <tr>
- <td>Process Definitions</td>
- <td>
- <ul>
- <li>Model outline has scope.</li>
- <li>Copy/ies of the process definition elements in the clipboard
- are copied in the data section of the process model.</li>
- </ul>
- </td>
- <td>
- <ul>
- <li>Model outline has scope.</li>
- <li>Paste item in popup menu for model in the outline tree is
- selected*.</li>
- <li>Copy/ies of the process definitions elements in the copy set
- are copied in the under the process model.</li>
- </ul>
- </td>
- </tr>
- <tr>
- <td>Process and model diagrams</td>
- <td>
- <ul>
- <li>Model outline has scope.</li>
- <li>Copy/ies of the diagram elements in the clipboard are copied
- in the data section of the process model.</li>
- </ul>
- </td>
- <td>
- <ul>
- <li>Model outline has scope.</li>
- <li>Paste item in popup menu for the process definition or model
- node in outline tree is selected**.</li>
- <li>Copy/ies of the diagrams in the clipboard are copied under
- the process definition or model.</li>
- </ul>
- </td>
- </tr>
- <tr>
- <td>Fragments of activity-transition graphs in process
- definitions</td>
- <td>
- <ul>
- <li>Diagram has scope.</li>
- </ul>
- </td>
- <td></td>
- </tr>
-</table>
-<br>
-<h4>Note</h4>
-<p>Please note that the CTRL-V keystroke only works in a target
-diagram where at least one mouse-click has already been performed. If it
-is not working for that reason just click in the target diagram before
-using the CTRL-V keystroke.</p>
-<h3 id="cutOverview">Cut Gestures</h3>
-<p>Cutting is initiated by the following gestures on the following
-elements:</p>
-<table id='id_2'>
- <tr>
- <th>Elements/Gesture</th>
- <th>CTRL-X Keystroke</th>
- <th>Popup Menu Entry</th>
- </tr>
- <tr>
- <td>Structured Types</td>
- <td>
- <ul>
- <li>Model outline has focus.</li>
- <li>Structured types node(s) in outline tree is selected.</li>
- <li>CTRL-X is pressed.</li>
- </ul>
- </td>
- <td>
- <ul>
- <li>Model outline has focus.</li>
- <li>Cut item in popup menu for the structured types node(s) in
- outline tree is selected.</li>
- </ul>
- </td>
- </tr>
- <tr>
- <td>Data</td>
- <td>
- <ul>
- <li>Model outline has focus.</li>
- <li>Data node(s) in outline tree is selected.</li>
- <li>CTRL-X is pressed.</li>
- </ul>
- </td>
- <td>
- <ul>
- <li>Model outline has focus.</li>
- <li>Cut item in popup menu for the data node(s) in outline tree
- is selected.</li>
- </ul>
- </td>
- </tr>
- <tr>
- <td>Applications</td>
- <td>
- <ul>
- <li>Model outline has focus.</li>
- <li>Application node(s) in outline tree is selected.</li>
- <li>CTRL-X is pressed.</li>
- </ul>
- </td>
- <td>
- <ul>
- <li>Model outline has focus.</li>
- <li>Cut item in popup menu for application node(s) in outline.</li>
- </ul>
- </td>
- </tr>
- <tr>
- <td>Participants</td>
- <td>
- <ul>
- <li>Model outline has focus.</li>
- <li>Participant node(s) in outline tree is selected.</li>
- <li>CRTL-X is pressed.</li>
- </ul>
- </td>
- <td>
- <ul>
- <li>Model outline has focus.</li>
- <li>Cut item in popup menu for the participant node(s) in
- outline.</li>
- </ul>
- </td>
- </tr>
- <tr>
- <td>Process Definitions</td>
- <td>
- <ul>
- <li>Model outline has focus.</li>
- <li>Process Definition node(s) in outline tree is selected.</li>
- <li>CTRL-X is pressed.</li>
- </ul>
- </td>
- <td>
- <ul>
- <li>Model outline has focus.</li>
- <li>Cut item in popup menu for the process definition node(s) in
- outline.</li>
- </ul>
- </td>
- </tr>
- <tr>
- <td>Process and model diagrams</td>
- <td>
- <ul>
- <li>Model outline has focus.</li>
- <li>Diagram node(s) in outline tree is selected.</li>
- <li>CTRL-X is pressed.</li>
- </ul>
- </td>
- <td>
- <ul>
- <li>Model outline has focus.</li>
- <li>Cut item in popup menu for the diagram node(s) in outline.</li>
- </ul>
- </td>
- </tr>
- <tr>
- <td>Fragments of activity-transition graphs in process
- definitions</td>
- <td>
- <ul>
- <li>Process diagram has focus.</li>
- <li>Model elements to be copied are selected via their symbols
- in the diagram (e.g. using the rubberband or multiple mouse clicks)</li>
- <li>CTRL-X is pressed.</li>
- </ul>
- </td>
- <td>
- <ul>
- <li>Process diagram has focus.</li>
- <li>Model elements to be copied are selected via their symbols
- in the diagram (e.g. using the rubberband or multiple mouse clicks).</li>
- <li>Cut item in popup menu the diagram is selected.</li>
- </ul>
- </td>
- </tr>
-</table>
-<br>
-<!-- delayed:
-<h3 id="refactorOverview">Refactor Gestures</h3>
-<table>
-<tr><th>Elements/Gesture</th>
-<th>Popup Menu Entry</th>
-</tr>
-<tr><td>Fragments of activity-transition graphs in process definitions</td>
-<td><ul>
-<li>Process diagram has focus.</li>
-<li>Model elements to be refactored are selected via their symbols in the diagram
-(e.g. using the rubberband or multiple mouse clicks).</li>
-<li>Refactor category in popup menu the diagram is selected.</li>
-<li>Extract subprocess item in submenu is selected.</li>
-</ul></td></tr></table>-->
-
-<script language="JavaScript" type="text/javascript">
-<!--
-writeFooter();
--->
-</script>
-</body>
-</html>
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/mg-import-1.htm b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/mg-import-1.htm
deleted file mode 100644
index d7b7b1c..0000000
--- a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/mg-import-1.htm
+++ /dev/null
@@ -1,365 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd"><HTML>
-<HEAD>
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../../styles/carnot.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE> Importing Models from other Formats</TITLE>
-<script language="JavaScript" src="../../styles/naviLine.js" type="text/javascript"></script>
-</head>
-<body>
-<script language="JavaScript">
-<!--
- writeNavigation("","PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/toc.html", "mg-xml-1.htm","", "../../toc.html","Business Analyst Handbooks", "mg-preface.htm","The Modeling Guide");
- -->
-</script>
-
-<h1 >
- Importing Models from other Formats</h1>
-<P >
-The @productname@ Workbench provides import facilities for process models stored in other formats. With the current release, @productname@ supports import from:</P>
-<UL>
-<LI >
-ARIS&#174; Toolset 6.1 by IDS Scheer AG</LI>
-</UL>
-<P >
-To import a model from an existing model definition in an external XML format, you have to choose an existing model version as your target model. The newly imported model elements have to be merged with the elements already existing in the chosen model version.</P>
-<P >
-To import an external .xml file:</P>
-<UL>
-<LI >
-Open or create a model version in the
- <strong>@productname@ Model Repository</strong></LI>
-<LI >In the main menu choose
- <strong>File</strong> &gt; <strong>Import...</strong></LI>
-<li>From the list, select <strong>@productname@ Model</strong></li>
-</UL>
-<P >
-In the upcoming dialog you select the .xml file you intend to import from the <strong>Model Types</strong> list. @productname@ will analyze the differences between the imported model elements and the model elements already contained in the currently opened model version and display these changes in a migration dialog.</P>
-<P >
-After that, @productname@ will parse the model information and list all parsing errors and inconsistencies found in the imported model elements in a corresponding dialog.</P>
-<P >
-Once you confirm the inconsistency dialog, you may either commit or reject these changes. If the changes are committed, they will be applied on the currently opened model version. This operation can only be undone by immediately closing the model without saving the applied changes.</P>
-<P >
-Note that the migration dialog even allows to select some detected changes to be applied while selecting others not to be applied using the check boxes in the migration dialog for any model element. (See <a href="mg-import-export.htm#importElements">Importing Elements</a> for more details).</P>
-
-<h3 >Mapping Rules for ARIS&#174; Toolset</h3>
-<p >The following mapping rules are used to map elements in an ARIS&#174; Toolset model to elements of process models:</p>
-
-<TABLE BORDER="1" id='id'>
- <TR>
- <TH ROWSPAN="1" COLSPAN="1">
- <P >
- @productname@ Model Element</P>
- </TH>
- <TH ROWSPAN="1" COLSPAN="1">
- <P > ARIS&#174; Toolset Model Element</P>
- </TH>
- </TR>
- <TR>
- <TD ROWSPAN="1" COLSPAN="1">
- <P >
- Process</P>
- </TD>
- <TD ROWSPAN="1" COLSPAN="1">
- <P >
- Model</P>
- </TD>
- </TR>
- <TR>
- <TD ROWSPAN="1" COLSPAN="1">
- <P >
- Activity</P>
- </TD>
- <TD ROWSPAN="1" COLSPAN="1">
- <P >
- Function</P>
- </TD>
- </TR>
- <TR>
- <TD ROWSPAN="1" COLSPAN="1">
- <P >
- Subprocess</P>
- </TD>
- <TD ROWSPAN="1" COLSPAN="1">
- <P >
- Function with Linked Model</P>
- </TD>
- </TR>
- <TR>
- <TD ROWSPAN="1" COLSPAN="1">
- <P >
- Transition</P>
- </TD>
- <TD ROWSPAN="1" COLSPAN="1">
- <P >
- Event</P>
- </TD>
- </TR>
- <TR>
- <TD ROWSPAN="1" COLSPAN="1">
- <P >
- Role</P>
- </TD>
- <TD ROWSPAN="1" COLSPAN="1">
- <P >
- Position</P>
- </TD>
- </TR>
- <TR>
- <TD ROWSPAN="1" COLSPAN="1">
- <P >
- Organisation</P>
- </TD>
- <TD ROWSPAN="1" COLSPAN="1">
- <P >
- Organisation Unit</P>
- </TD>
- </TR>
- <TR>
- <TD ROWSPAN="1" COLSPAN="1">
- <P >
- Data</P>
- </TD>
- <TD ROWSPAN="1" COLSPAN="1">
- <P >
- Info</P>
- </TD>
- </TR>
- <TR>
- <TD ROWSPAN="1" COLSPAN="1">
- <P >
- Join/Split</P>
- </TD>
- <TD ROWSPAN="1" COLSPAN="1">
- <P >
- Rules</P>
- </TD>
- </TR>
- <TR>
- <TD ROWSPAN="1" COLSPAN="1">
- <P >
- Application</P>
- </TD>
- <TD ROWSPAN="1" COLSPAN="1">
- <P >
- Application System</P>
- </TD>
- </TR>
- <TR>
- <TD ROWSPAN="1" COLSPAN="1">
- <P >
- Trigger</P>
- </TD>
- <TD ROWSPAN="1" COLSPAN="1">
- <P >
- Starting Event</P>
- </TD>
- </TR>
- <TR>
- <TD ROWSPAN="1" COLSPAN="1">
- <P >
- Data Mapping</P>
- </TD>
- <TD ROWSPAN="1" COLSPAN="1">
- <P >
- -</P>
- </TD>
- </TR>
- <TR>
- <TD ROWSPAN="1" COLSPAN="1">
- <P >
- Transition Condition</P>
- </TD>
- <TD ROWSPAN="1" COLSPAN="1">
- <P >
- -</P>
- </TD>
- </TR>
- <TR>
- <TD ROWSPAN="1" COLSPAN="1">
- <P >
- Completion Method</P>
- </TD>
- <TD ROWSPAN="1" COLSPAN="1">
- <P >
- -</P>
- </TD>
- </TR>
-</TABLE>
-<!-- <h3 > Mapping Rules for Income Process Designer</h3>
-<P >
-The following mapping rules are used to map elements in an Income project to elements of process models:</P>
-<TABLE BORDER="1">
- <TR>
- <TH ROWSPAN="1" COLSPAN="1">
- <P >
- @productname@ Model Element</P>
- </TH>
- <TH ROWSPAN="1" COLSPAN="1">
- <P >
- Income Process Designer Model Element</P>
- </TH>
- </TR>
- <TR>
- <TD ROWSPAN="1" COLSPAN="1">
- <P >
- Process</P>
- </TD>
- <TD ROWSPAN="1" COLSPAN="1">
- <P >
- Behavior Model</P>
- </TD>
- </TR>
- <TR>
- <TD ROWSPAN="1" COLSPAN="1">
- <P >
- Activity</P>
- </TD>
- <TD ROWSPAN="1" COLSPAN="1">
- <P >
- Activity</P>
- </TD>
- </TR>
- <TR>
- <TD ROWSPAN="1" COLSPAN="1">
- <P >
- Subprocess</P>
- </TD>
- <TD ROWSPAN="1" COLSPAN="1">
- <P >
- Refinements defined for activities</P>
- </TD>
- </TR>
- <TR>
- <TD ROWSPAN="1" COLSPAN="1">
- <P >
- Transition</P>
- </TD>
- <TD ROWSPAN="1" COLSPAN="1">
- <P >
- Connection</P>
- </TD>
- </TR>
- <TR>
- <TD ROWSPAN="1" COLSPAN="1">
- <P >
- Role</P>
- </TD>
- <TD ROWSPAN="1" COLSPAN="1">
- <P >
- Role</P>
- </TD>
- </TR>
- <TR>
- <TD ROWSPAN="1" COLSPAN="1">
- <P >
- Organisation</P>
- </TD>
- <TD ROWSPAN="1" COLSPAN="1">
- <P >
- -</P>
- </TD>
- </TR>
- <TR>
- <TD ROWSPAN="1" COLSPAN="1">
- <P >
- Data</P>
- </TD>
- <TD ROWSPAN="1" COLSPAN="1">
- <P >
- Object type</P>
- </TD>
- </TR>
- <TR>
- <TD ROWSPAN="1" COLSPAN="1">
- <P >
- Join/Split</P>
- </TD>
- <TD ROWSPAN="1" COLSPAN="1">
- <P >
- Activity / Object store combinations</P>
- </TD>
- </TR>
- <TR>
- <TD ROWSPAN="1" COLSPAN="1">
- <P >
- Application</P>
- </TD>
- <TD ROWSPAN="1" COLSPAN="1">
- <P >
- Document (interactive)</P>
- </TD>
- </TR>
- <TR>
- <TD ROWSPAN="1" COLSPAN="1">
- <P >
- Trigger</P>
- </TD>
- <TD ROWSPAN="1" COLSPAN="1">
- <P >
- -</P>
- </TD>
- </TR>
- <TR>
- <TD ROWSPAN="1" COLSPAN="1">
- <P >
- Data Mapping</P>
- </TD>
- <TD ROWSPAN="1" COLSPAN="1">
- <P >
- Object type defined for an object store</P>
- </TD>
- </TR>
- <TR>
- <TD ROWSPAN="1" COLSPAN="1">
- <P >
- Transition Condition</P>
- </TD>
- <TD ROWSPAN="1" COLSPAN="1">
- <P >
- Kind of objects defined for object store outgoing connections</P>
- </TD>
- </TR>
- <TR>
- <TD ROWSPAN="1" COLSPAN="1">
- <P >
- Completion Method</P>
- </TD>
- <TD ROWSPAN="1" COLSPAN="1">
- <P >
- -</P>
- </TD>
- </TR>
-</TABLE>
-<P > Generally,<span class="Stil1"> output of an Income activity corresponds with the logical AND behavior and output of an Income object store corresponds with </span> the logical OR behavior. To model an OR conjunction it is necessary to use an object store element.</P>
-<p class="image"><img SRC="images/mg-import-1.jpg" width="444" height="154">
-<br><strong>Figure:</strong> Income OR Split followed by OR Join</P>
-<p class="image"><a href="images/mg-import-2_orgSize.png" target="_blank"><IMG SRC="images/mg-import-2.png"></a>
-<br><strong>Figure:</strong> @productname@ OR Split followed by OR Join</P>
-<P align="center">For AND conjunctions every outgoing connection from an activity should traverse an object store.</P>
-<p class="image"><img SRC="images/mg-import-3.jpg">
-<br><strong>Figure:</strong> Income AND Split followed by AND Join</p>
-<p class="image"><a href="images/mg-import-4_orgSize.png" target="_blank">
- <IMG SRC="images/mg-import-4.png"></a>
-<br><strong>Figure:</strong> @productname@ AND Split followed by AND Join</P>
-<P >
-To represent an Income AND split followed by an Income OR split, the importer creates a @productname@ activity for each object store that connects activities in that kind of scenario.</P>
-<p class="image"><img SRC="images/mg-import-5.jpg" width="349" height="287">
-<br><strong>Figure:</strong> Income AND Split followed by OR Split</P>
-<p class="image"><a href="images/mg-import-6_orgSize.png" target="_blank">
- <IMG SRC="images/mg-import-6.png"></a>
-<br><strong>Figure:</strong> @productname@ AND Split followed by OR Split</P>
-<P >
-To represent an Income OR join followed by an Income AND join, the importer creates a @productname@ activity for each object store that connects activities in that kind of scenario.</P>
- <p class="image"><img SRC="images/mg-import-7.jpg" width="507" height="230">
-<br><strong>Figure:</strong> Income OR Join followed by AND Join</p>
-<p class="image"><a href="images/mg-import-8_orgSize.png" target="_blank"><IMG SRC="images/mg-import-8.png"></a>
-<br><strong>Figure:</strong> @productname@ OR Join followed by AND Join</P>-->
-<script language="JavaScript">
-<!--
-writeFooter();
--->
-</script>
-</body>
-</html>
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/mg-preface.htm b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/mg-preface.htm
deleted file mode 100644
index 528c8cc..0000000
--- a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/mg-preface.htm
+++ /dev/null
@@ -1,75 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-
-<link rel="STYLESHEET" href="../../styles/carnot.css"
- charset="ISO-8859-1" type="text/css">
-<title>The Modeling Guide</title>
-<script language="JavaScript" src="../../styles/naviLine.js"
- type="text/javascript"></script>
-</head>
-<body>
-<script language="JavaScript" type="text/javascript">
-<!--
- writeNavigation("","PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/toc.html",
- "","",
- "../../toc.html","Business Analyst Handbooks");
- -->
-</script>
-
-<h1>Preface</h1>
-<h2>Survey</h2>
-<p>In this section you get a general survey on what this book is
-about.</p>
-
-<h3>Audience</h3>
-<p>The Analyst Modeling Guide explains the basic concepts of the
-@productname@ Engine and provides an in-depth view of how to model
-your business processes with @productname@. It is intended to be read by
-people who do process modeling with @productname@.</p>
-
-<h3>How this book is organized</h3>
-<p>The book is organized into the following chapters:</p>
-<ol>
-<!-- <li>In <a href="mg-basics-preface.htm">Workflow Basics</a> the
- main concepts of modeling processes and executing them are explained.</li>-->
- <li>The chapter <a href="mg-modeler-preface.html">The
- @productname@ Workbench</a> serves as a user guide to model processes
- with the @productname@ Workbench.</li>
- <li>In the chapter <a href="mg-xml-1.htm">The Model File
- Format</a> describes the model file formats and their handling.</li>
- <li>The chapter <a href="mg-import-1.htm">Importing Models
- from Other File Formats</a> describes the import facilities for process
- models stored in other formats.</li>
- <li><a href="concurrency/con-preface.html">Collaborative Modeling</a>
- describes working with models in concurrency management mode.</li>
-</ol>
-
-<h3>Related Documents</h3>
-<ul>
- <li>The
- <a href="PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/handbooks/installation/ig-preface.htm">
- Developer Installation Guide</a> provides instructions on installing @productname@
- and required configurations.</li>
-</ul>
-
-<h3>Contact Us</h3>
-<p>Your opinions and recommendations are always welcome. Our
-technical documentation team relies heavily on your feedback. Feel free
-to contact us:</p>
-<p>SunGard Systeme GmbH<br>
-Technical Documentation<br>
-Solmsstr. 18<br>
-D-60486 Frankfurt am Main<br>
-Germany<br>
-e-mail IPP.Documentation@sungard.com</p>
-
-<script language="JavaScript" type="text/javascript">
-<!--
-writeFooter();
--->
-</script>
-</body>
-</html>
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/mg-ref-elements.htm b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/mg-ref-elements.htm
deleted file mode 100644
index ec6302f..0000000
--- a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/mg-ref-elements.htm
+++ /dev/null
@@ -1,45 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd"><HTML>
-<HEAD>
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../../styles/carnot.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE> Referencing Model Elements</TITLE>
-<script language="JavaScript" src="../../styles/naviLine.js" type="text/javascript"></script>
-</head>
-<body>
-<script language="JavaScript">
-<!--
- writeNavigation("Deploying a Workflow Model","PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/toc.html",
- "mg-modelreport.htm","mg-deploy-model.html",
- "../../toc.html","Business Analyst Handbooks",
- "mg-preface.htm","The Modeling Guide",
- "mg-modeler-preface.html","The Process Workbench");
- -->
-</script>
-
-<h1>
-Referencing Model Elements</h1>
-<p>@productname@ enables you to refer model elements using the file connection.
-For more information, please refer to the following sections of the <a
- href="PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/handbooks/handbooks.htm">Developers Handbook</a>.</p>
-
-<ul>
-
- <li><a href="PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/handbooks/modelling/mg-registry.html#fileConn">
-Referencing Model Elements</a></li>
- <li><a href="PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/handbooks/modelling/mg-registry.html#file">
-Creating a File Connection</a></li>
- <li><a href="PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/handbooks/modelling/mg-registry.html#impref">
-Usage of Elements Imported by Reference</a></li>
- <li><a href="PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/handbooks/modelling/mg-registry.html#manageref">
-Managing References to Other Models</a></li>
-</ul>
-
-<script language="JavaScript">
-<!--
-writeFooter();
--->
-</script>
-</body>
-</html>
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/mg-xml-1.htm b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/mg-xml-1.htm
deleted file mode 100644
index 40a6e43..0000000
--- a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/mg-xml-1.htm
+++ /dev/null
@@ -1,150 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-
-<link rel="STYLESHEET" href="../../styles/carnot.css"
- charset="ISO-8859-1" type="text/css">
-<title>The Model File Format</title>
-<script language="JavaScript" src="../../styles/naviLine.js"
- type="text/javascript"></script>
-</head>
-<body>
-<script language="JavaScript" type="text/javascript">
-<!--
- writeNavigation("Importing Models from other Formats","PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/toc.html",
- "mg-modeler-preface.html","mg-import-1.htm","../../toc.html","Business Analyst Handbooks",
- "mg-preface.htm","The Modeling Guide");
- -->
-</script>
-
-<h1>The Model File Format</h1>
-<p>Process models are stored in the <strong>XML Process
-Definition Language (XPDL)</strong> format of the Workflow Management Coalition
-(WfMC). This format is uniformly used in the whole @productnameonly@ Process
-Engine. Momentarily also the native @productname@ file format is supported
-for backward compatibility. The @productname@ Workbench is capable of
-loading and saving models in both formats. The models can be converted
-between these formats by saving them with extension <tt>.xpdl</tt> or <tt>.cwm</tt>
-respectively. You find a description of both file formats in the <a
- href="PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/tocschema.html">@productname@
-Schema Documentation</a> of the <a
- href="PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/handbooks/handbooks.htm">
-@productname@ Developers Handbooks</a>.</p>
-<p>All model elements in the sense of chapter Workflow Basics are
-represented as XML elements with a descriptive name. A process
-definition is e.g. defined in an XML element <tt>processDefinition</tt>.
-The model itself is considered a model element ,too and appears as root
-element model of the XML representation.</p>
-<p>All model elements viewed as XML share some common features as
-described in the following table:</p>
-<table border="1" id='id'>
- <tr>
- <th rowspan="1" colspan="1">Property</th>
- <th rowspan="1" colspan="1">XML Representation</th>
- <th rowspan="1" colspan="1">Comment</th>
- </tr>
- <tr>
- <td rowspan="1" colspan="1">
- <p>OID</p>
- </td>
- <td rowspan="1" colspan="1">
- <p>oid attribute</p>
- </td>
- <td rowspan="1" colspan="1">
- <p>Unique inside the model. Automatically generated.</p>
- </td>
- </tr>
- <tr>
- <td rowspan="1" colspan="1">
- <p>ID</p>
- </td>
- <td rowspan="1" colspan="1">
- <p>id attribute</p>
- </td>
- <td rowspan="1" colspan="1">
- <p>Normally unique inside the parent scope.</p>
- </td>
- </tr>
- <tr>
- <td rowspan="1" colspan="1">
- <p>Name</p>
- </td>
- <td rowspan="1" colspan="1">
- <p>name attribute</p>
- </td>
- <td rowspan="1" colspan="1">
- <p>A human readable name.</p>
- </td>
- </tr>
- <tr>
- <td rowspan="1" colspan="1">
- <p>Predefined</p>
- </td>
- <td rowspan="1" colspan="1">
- <p>predefined attribute</p>
- </td>
- <td rowspan="1" colspan="1">
- <p>Marks the element as predefined. Can't be edited in the Process
- Workbench.</p>
- </td>
- </tr>
- <tr>
- <td rowspan="1" colspan="1">
- <p>Description</p>
- </td>
- <td rowspan="1" colspan="1">
- <p>description sub element</p>
- </td>
- <td rowspan="1" colspan="1">
- <p>An optional human readable description of the model element.</p>
- </td>
- </tr>
- <tr>
- <td rowspan="1" colspan="1">
- <p>Dynamic Attribute</p>
- </td>
- <td rowspan="1" colspan="1">
- <p>attribute sub element</p>
- </td>
- <td rowspan="1" colspan="1">
- <p>An arbitrary dynamic attribute. Used for tool specific
- information or information for pluggable types.</p>
- </td>
- </tr>
-</table>
-<p>Please refer to the <a href="PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/tocschema.html">
-@productname@ Schema Documentation</a> for details on the standard @productname@ formats.</p>
-<h2>Editing @productname@ XPDL Models with External Tools</h2>
-<p>In general models produced or modified by the @productname@ modeler
-can be edited with other tools that supports XPDL 1.0
-standard. However, the @productname@ modeler is maintaining
-specific information for most of the model elements in an <strong>ExtendedAttribute</strong>
-with the name <tt>&quot;CarnotExt&quot;</tt>.</p>
-<p>In certain cases, these elements may refer to standard
-identifiers. For example the diagram information is stored exclusively
-in the extended attribute, however it has references to workflow objects
-defined in the standard XPDL part.</p>
-<p>A concrete example is the <tt>carnot:Symbol
-(Kind="ACTIVITY")</tt>. This symbol has a live reference to the actual
-activity, and namely the field <tt>ModelElement</tt> contains the Id of
-the activity that it refers to. Similarly affected are <tt>carnot:Connection
-(Kind="TRANSITION")</tt> that refers a transition as well as the <tt>carnot:Symbols</tt>
-with the kind "DATA", "ROLE", "APPLICATION" or "PROCESS".</p>
-<p>When modifying the <strong>Id</strong> of a workflow element or
-deleting the element that is referenced by such a diagram symbol, please
-take care to synchronize the respective reference (attribute
-"ModelElement") in the <tt>carnot:Symbol</tt> or <tt>carnot:Connection</tt>.
-If such synchronization is not performed then dangling references may
-result or references can point to an element of a
-different type. In the latter case, the @productname@ modeler
-will no longer be able to load the model due to ClassCastExceptions.</p>
-
-<script language="JavaScript" type="text/javascript">
-<!--
-writeFooter();
--->
-</script>
-</body>
-</html>
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/model-views/views-diagrams.html b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/model-views/pep-diagrams.html
index 37039e0..37039e0 100644
--- a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/model-views/views-diagrams.html
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/model-views/pep-diagrams.html
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/model-views/views-outline.html b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/model-views/pep-panles.html
index 4d35ae9..4d35ae9 100644
--- a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/model-views/views-outline.html
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/model-views/pep-panles.html
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/models/model-clean.html b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/models/model-clean.html
deleted file mode 100644
index ab7a20e..0000000
--- a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/models/model-clean.html
+++ /dev/null
@@ -1,110 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../../../styles/carnot.css" charset="ISO-8859-1"
- type="text/css">
-<title>Element References</title>
-<script language="JavaScript" src="../../../styles/naviLine.js"
- type="text/javascript"></script>
-</head>
-<body>
-<script language="JavaScript" type="text/javascript">
-
-<!--
- writeNavigation("","PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/toc.html",
- "model-element-refs.html","",
- "../../../toc.html","Business Analyst Handbooks",
- "../mg-preface.htm","The Modeling Guide",
- "../mg-modeler-preface.html","The Process Workbench",
- "model-preface.html","Working With Models");
- -->
- </script>
-
-<h1>Cleaning up Models</h1>
-
-<ul>
- <li><a href="#Intro">Introduction</a></li>
- <li><a href="#Why">Why to Cleanup the Model</a></li>
- <li><a href="#cleaup">What happens during the Cleanup Process</a></li>
- <!-- <li><a href="#notCleaned">What doesn't get Cleaned up</a></li>
- <li><a href="#algorithm">The Algorithm used and Cleanup Speed</a></li>
--->
- <li><a href="#Example">Example of a Model before and after the
- Cleanup</a></li>
- <li><a href="#Steps">Step by step Cleanup Process</a></li>
-</ul>
-
-<h2 id="Intro">Introduction</h2>
-<p>As models become older, the changes from version to version often
-leave behind a lot of garbage in the form of old data objects or
-applications that are not used anymore. Usually they are kept, because
-nobody finds the time to verify if they can be deleted safely.</p>
-<h2 id="Why">Why to Cleanup the Model</h2>
-<p>Although the unused elements won't crash the Eclipse, they may
-carry other overload like java classes, configuration data, strings and
-other data types associated with them. By cleaning up, you will increase
-the overall speed and efficiency of the model. It would also mean that
-you are viewing the most recent version of the model excluding the old
-garbage.</p>
-<h2 id="cleaup">What happens during the Cleanup Process</h2>
-<p>The cleanup process searches for TypeDeclarations, Data,
-Participants and Applications that are unused. It doesn't check if that
-model element has symbols or not. It verifies that every element has a
-reference. It also doesn't check for Adminstrator and predefined Datas
-(It is always retained).</p>
-<!--
-<h2 id="notCleaned">What doesn't get Cleaned up</h2>
-
-<h2 id="algorithm">The Algorithm used and Cleanup Speed</h2>
--->
-<h2 id="Example">Example of a Model before and after the Cleanup</h2>
-<ul><li>Model you want to cleanup:</li></ul>
-<p class="image"><a href="images/cleanup1_org.png" target="_blank"><img
- src="images/cleanup1.png" alt=""></a><br>
-<strong>Figure:</strong>Original Model with unused elements</p>
-<ul><li>The Model after cleanup.</li></ul>
-<p class="image"><a href="images/cleanup5_org.png" target="_blank"><img
- src="images/cleanup5.png" alt=""></a><br>
-<strong>Figure:</strong>The Model after cleanup:</p>
-
-<h2 id="Steps">Step by step Cleanup Process</h2>
-<ul>
- <li>Open the Model you want to cleanup.
- <p class="image"><a href="images/cleanup1_org.png" target="_blank"><img
- src="images/cleanup1.png" alt=""></a><br>
- <strong>Figure:</strong>Original Model with unused elements</p></li>
-
- <li>Right click on the Model in Outline view, click on Cleanup
- Model
- <p class="image"><img src="images/cleanup2.png" alt=""><br>
- <strong>Figure:</strong>Select Cleanup Option</p>
-
-
- <li>You will see a list of elements in search window. Select the
- elements that you want to clean, and click on delete.
- <p class="image"><img src="images/cleanup3.png" alt=""><br>
- <strong>Figure:</strong>Select Cleanup Option</p>
- </li>
-
- <li>You will see a confirmation dialog box as shown below. Click
- the OK button.
-
- <p class="image"><img src="images/cleanup4.png" alt=""><br>
- <strong>Figure:</strong>Confirm Cleanup Option</p>
- </li>
-
- <li>You will see the Model after cleanup.
- <p class="image"><a href="images/cleanup5_org.png" target="_blank"><img
- src="images/cleanup5.png" alt=""></a><br>
- <strong>Figure:</strong>The Model after cleanup</p>
- </li>
-</ul>
- <script language="JavaScript" type="text/javascript">
- <!--
- writeFooter();
- -->
- </script>
-</body>
-</html>
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/models/model-element-refs.html b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/models/model-save.html
index fb926b0..fb926b0 100644
--- a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/models/model-element-refs.html
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/models/model-save.html
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/models/model-upgrade.html b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/models/model-upgrade.html
deleted file mode 100644
index 3630753..0000000
--- a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/models/model-upgrade.html
+++ /dev/null
@@ -1,60 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../../../styles/carnot.css" charset="ISO-8859-1"
- type="text/css">
-<title>Model Upgrade</title>
-<script language="JavaScript" src="../../../styles/naviLine.js"
- type="text/javascript"></script>
-</head>
-<body>
-<script language="JavaScript" type="text/javascript">
-<!--
- writeNavigation("Creating and Deleting Models",
- "PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/toc.html",
- "","model-handling.html",
- "../../../toc.html","Business Analyst Handbooks",
- "../mg-preface.htm","The Modeling Guide",
- "../mg-modeler-preface.html","The Process Workbench",
- "model-preface.html","Working With Models");
- -->
-</script>
-<h1>Model Upgrade</h1>
-<p>To perform an upgrade of an existing process model you have to
-distinguish between models older tha @productname@ version 3.0 or later versions.
-Eclipse is not able to read process model versions older than 3.0. In case you
-use a model with a version older than 3.0, it is recommended to use the
-sysconsole command to upgrade the model.</p>
-<h2 id="sysconsole">Upgrading with the Sysconsole Command Tool</h2>
-<p>Please ask your administrator to perform the upgrade or refer to the <a
- href="PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/handbooks/handbooks.htm">
-Developer Handbook</a> for more information. ( <a
- href="PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/handbooks/operation/ag-preface.htm">
-Operation Guide</a> - <a
- href="PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/handbooks/operation/commandline/ag-commandline-2.htm">
-The Sysconsole Command</a>).</p>
-<h2>Upgrading in Eclipse Environment</h2>
-<p>In case you import a model in Eclipse with an earlier @productname@ version
-than you use, you will be prompted and asked if you want to upgrade to the later
-version:</p>
-<p class="image"><img src="images/mg-upgrade-dialog.png"
- alt="Upgrade Model Dialog"></p>
-<p>In case you select <strong>No</strong> and the version is older than
-4.7.0, a warning dialog will open to indicate that this model version is
-unsupported:</p>
-<p class="image"><img src="images/model-upgrade-warning.png"
- alt="Upgrade Model Warning"><br>
-<strong>Figure:</strong> Upgrade Model Warning Dialog</p>
-<p>You can select <strong>Upgrade now</strong> to perform the upgrade then
-and open the diagram of the model. In case you choose <strong>Close
-editor</strong>, the model is loaded, but the diagram cannot be edited.</p>
-
-<script language="JavaScript" type="text/javascript">
-<!--
-writeFooter();
--->
-</script>
-</body>
-</html>
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/models/model-validation.html b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/models/model-validation.html
deleted file mode 100644
index 640f370..0000000
--- a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/models/model-validation.html
+++ /dev/null
@@ -1,89 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../../../styles/carnot.css" charset="ISO-8859-1"
- type="text/css">
-<title>Workflow Model Validation</title>
-<script language="JavaScript" src="../../../styles/naviLine.js"
- type="text/javascript"></script>
-</head>
-<body>
-<script language="JavaScript" type="text/javascript">
-<!--
- writeNavigation("Importing and Exporting Models",
- "PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/toc.html",
- "model-props.html","model-import.html",
- "../../../toc.html","Business Analyst Handbooks",
- "../mg-preface.htm","The Modeling Guide",
- "../mg-modeler-preface.html","The Process Workbench",
- "model-preface.html","Working With Models");
- -->
-</script>
-
-<h1>Workflow Model Validation</h1>
-<h2>Auto Validation</h2>
-<p>By default, a validation check on your workflow model is automatically
-performed by the @productname@ workbench after modifications. You can
-disable the auto validation by changig the enabling option in the Preferences
-dialog, as described in the section <a href="../mg-preferences.html#autoValidation">Auto
-Validation</a>.</p>
-<h2>Explicit Validation</h2>
-<p>To start a validation of your model by hand, right-click your model in
-the <a href="../model-views/views-outline.html">Outline View</a> and select <strong>Validate
-Model</strong> from the pop-up menu.</p>
-<p class="image"><img src="images/mg-validate-model.png" alt=""> <br>
-<strong>Figure:</strong> Validation of a Model</p>
-<p>The errors and warnings are listed in the <a href="#problemsView">Problems
-view</a>. They are also indicated in the <a href="../model-views/views-outline.html">Outline
-view</a> with signs on the corresponding item symbols, like an exclamation mark for
-a warning or a cross for an error.</p>
-<p class="image"><img src="images/mg-error-icons.png" alt=""> <br>
-<strong>Figure:</strong> Icons to Denote the Type of Problem</p>
-<h2 id="problemsView">The Problems View</h2>
-<p>If a validation is performed the errors and warnings will then be logged
-in the<strong> Problems</strong> view. If the <strong>Problems</strong> view is
-not already opened in your perspective, add it by clicking on <strong>Window</strong>
-&gt; <strong>Show View</strong> &gt; <strong>Other...</strong> &gt; <strong>Basic</strong>
-&gt; <strong>Problems</strong>.</p>
-<p class="image"><a href="images/mg-problems-view_orgSize.png"
- target="_blank"> <img src="images/mg-problems-view.png" alt=""></a> <br>
-<strong>Figure:</strong> The Problems View</p>
-<h3>Open the property page of the concerned element</h3>
-<p>In some cases you may like to edit the concerned model element directly. You can open the
-property page of the concerned model element by double-clicking on the
-according error or warning entry.</p>
-<p class="image"><img src="images/problems-view-open-dialog.png" alt=""> <br>
-<strong>Figure:</strong> Double-click an error entry to open the according element property dialog.</p>
-<h3>Using the Quick Fix functionality</h3>
-<p>Some errors provide a quick-fix functionality for quickly fixing
-the issue. To use this functionality, right-click the error
-entry and select <strong>Quick Fix</strong> or simply use <strong>Crtl-1</strong>,
- for example:</p>
-<p class="image"><img src="images/teamlead-error-quick-fix-1.png"
- alt="Team Leader Connection Error"> <br>
-<strong>Figure:</strong> Select Quick Fix to fix the Error.</p>
-<p>The <strong>Quick Fix</strong> dialog opens, where you can fix the
-according error, e.g.:</p>
-<p class="image"><img src="images/teamlead-error-quick-fix-2.png"
- alt="Quick Fix Dialog"> <br>
-<strong>Figure:</strong> Quick Fix Dialog</p>
-<h3>Filtering the entries</h3>
-<p>In the <strong>Problems</strong> view you can filter the problems that
-are displayed, to view only warnings and errors of a special type or associated
-with a particular resource. On the toolbar, click the <strong>Filter</strong>
-button and make your choices in the <strong>Filters</strong> dialog.</p>
-<p class="image"><a href="images/mg-filters_orgSize.png" target="_blank">
-<img src="images/mg-filters.png" alt=""></a> <br>
-<strong>Figure:</strong> Filtering Items</p>
-<p>For more information about the <strong>Problems</strong> view, see the
-Workbench User Guide of the Eclipse Help.</p>
-
-<script language="JavaScript" type="text/javascript">
-<!--
-writeFooter();
--->
-</script>
-</body>
-</html>
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/mg-deploy-model.html b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/models/pep-deploy-model.html
index 23da721..23da721 100644
--- a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/mg-deploy-model.html
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/models/pep-deploy-model.html
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/mg-defdesk-4.htm b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-activities.htm
index 347d9e1..5b9dba4 100644
--- a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/mg-defdesk-4.htm
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-activities.htm
@@ -1,98 +1,145 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-
-<link rel="STYLESHEET" href="../../styles/carnot.css" charset="ISO-8859-1" type="text/css">
-<title>Specifying Activities</title>
-<script language="JavaScript" src="../../styles/naviLine.js" type="text/javascript"></script>
-</head>
-<body>
-<script language="JavaScript" type="text/javascript">
-<!--
- writeNavigation("Working with Transitions","PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/toc.html",
- "mg-defdesk-3.htm","mg-defdesk-5.htm",
- "../../toc.html","Business Analyst Handbooks",
- "mg-preface.htm","The Modeling Guide",
- "mg-modeler-preface.html","The Process Workbench");
- -->
-</script>
-
-<h1>Specifying Activities</h1>
-<p>As explained in the chapter <a href="mg-basics-5.htm">Activities</a> a series of
-activities connected with one another by transitions constitutes the core of the process.
-</p>
-<p>An activity is represented in the <strong>Process Workbench</strong> in two
-different ways. In the <strong>Outline</strong> view it is represented by a small gear
-pictogram. In diagrams you will see an activity depicted as a box possibly with transition
-symbols.</p>
-<p>&nbsp;</p>
-<p class="image"><img src="images/mg-defdesk-17.png" alt=""> <br>
-<strong>Figure:</strong> A Representation of an Activity</p>
-<h2>Creating and Deleting Activities</h2>
-<p>To create an activity you can either:</p>
-<ul>
- <li>In the diagram toolbar palette select <strong>Activites</strong> under <strong>Items</strong>
- and click on the canvas to place the activity symbol there. The created activity will
- also appear in the tree view under the process definition symbol in the <strong>Outline</strong>
- view.</li>
-</ul>
-<p class="image"><img src="images/mg-create-activity.png" alt=""> <br>
-<strong>Figure:</strong> Creation of an Activity</p>
-<ul>
- <li>In the <strong>Outline</strong> view select the process definition to which
- you want to add an activity. From its pop-up menu choose <strong>New Activity</strong>.
- The created activity will appear in the tree view under the process definition symbol.
- Subsequently, you can drag the activity symbol to the diagram canvas to create an
- activity symbol there.</li>
-</ul>
-<p>When deleting activities you must make a distinction between deleting an activity
-from the model information or only deleting a symbol from a diagram. To do the first -
-delete an activity from model - you proceed as follows:</p>
-<ul>
- <li>Having selected the symbol of the activity in the <strong>Outline</strong>
- view, choose the option <strong>Delete </strong> in the pop-up menu of this process
- definition.</li>
- <li>Having selected the symbol of the activity in a process definition diagram,
- choose the option <strong>Delete</strong> in the pop-up menu of this activity.</li>
-</ul>
-<p>The option <strong>Delete Symbol </strong> in the pop-up menu called from within
-the diagram canvas will only remove the activity symbol from the diagram.</p>
-<h2>Modifying Activity Properties</h2>
-<p>The properties of an activity are accessible in its properties dialog. To open
-this dialog, right-click the activity symbol - in the <strong>Outline</strong> view or
-diagram - and select the option <strong>Properties</strong>. Double-clicking on the
-activity symbol will open this dialog as well.</p>
-<p>Activity characteristics are bundled into the following categories, each
-represented in an own tabbed pane:</p>
-<ul>
- <li><a href="#general">General</a></li>
- <li><a href="#display">Display</a></li>
- <li><a href="#controlFlow">Control Flow</a></li>
- <li><a href="#in">In Data Mappings</a></li>
- <li><a href="#out">Out Data Mappings</a></li>
- <li><a href="#controlling">Controlling</a></li>
- <li><a href="#simulation">Simulation</a></li>
- <li><a href="#effort">Effort Planning</a></li>
-</ul>
-
-<h3 id="general">General</h3>
-<p>Next to a name, an ID and a description, general properties of an activity
-comprise the following checkbox options:</p>
-<ul>
- <li><strong>Auto Id Generation</strong><br><br>
- Overwrites the option for automatic Id generation set in <a
- href="mg-preferences.html">@productname@ Preferences</a>.<br><br></li>
- <li><strong>Allows Abort by Participant</strong><br><br>
- Determines whether the assigned participant may abort instances of this
- activity in the @productname@ Portal.<br>
- Note that only the activity itself is aborted, not the root process hierarchy.
- The process instances will continue as if this activity had been completed.<br>
- This option affects the Process Portal activity operations only. It does not
- influence the @productname@ API usage.<br><br></li>
- <li><strong>Hibernate Initially</strong> (Hibernate On Creation)<br><br>
- Determines whether the activity instance should directly change its state to
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<meta http-equiv="Content-Style-Type" content="text/css">
+
+<link rel="STYLESHEET" href="../../styles/carnot.css" charset="ISO-8859-1" type="text/css">
+<title>Specifying Activities</title>
+<script language="JavaScript" src="../../styles/naviLine.js" type="text/javascript"></script>
+</head>
+<body>
+<script language="JavaScript" type="text/javascript">
+<!--
+ writeNavigation("Working with Transitions","PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/toc.html",
+ "mg-defdesk-3.htm","mg-defdesk-5.htm",
+ "../../toc.html","Business Analyst Handbooks",
+ "mg-preface.htm","The Modeling Guide",
+ "mg-modeler-preface.html","The Process Workbench");
+ -->
+</script>
+
+<h1>Specifying Activities</h1>
+<ul>
+ <li><a href="#add">Adding Activities</a></li>
+ <li><a href="#del">Deleting Activities</a></li>
+ <li><a href="#fly">Activity Flyout Menu</a></li>
+ <li><a href="#mod">Viewing and Modifying Activity Properties</a></li>
+
+</ul>
+
+<h2 id="add">Adding Activities</h2>
+<p>
+To add activities, you can either:
+</p>
+<ul>
+ <li>In the toolbar, click <strong>Create Activity</strong> icon and drop it to swim lanes</li>
+ <p class="image"><img src="images/create-act.png" alt=""> <br>
+<strong>Figure:</strong> Create Activity Icon</p>
+
+</ul>
+<p>OR</p>
+
+<ul>
+<li>Hover the mouse in proximity of already added activity in swimlanes and click the <strong>Activity</strong> icon in the flyout menu</li>
+<p class="image"><img src="images/create-act-fly.png" alt=""> <br>
+<strong>Figure:</strong> Create Activity - Flyout Menu</p>
+
+<li>Drop it in the swim lane</li>
+
+</ul>
+
+<h2 id="del">Deleting Activities</h2>
+<p>To delete activities, perform the following steps:</p>
+
+<ol>
+ <li>Hover the mouse in the proximity of the activity</li>
+ <li>Click the <strong>Delete</strong> icon in the flyout menu of the activity</li>
+
+
+ <p class="image"><img src="images/del-act.png" alt=""> <br>
+<strong>Figure:</strong> Delete Activity - Flyout Menu</p>
+
+
+</ol>
+
+
+
+
+<!--
+<p>As explained in the chapter <a href="mg-basics-5.htm">Activities</a> a series of
+activities connected with one another by transitions constitutes the core of the process.
+</p>
+<p>An activity is represented in the <strong>Process Workbench</strong> in two
+different ways. In the <strong>Outline</strong> view it is represented by a small gear
+pictogram. In diagrams you will see an activity depicted as a box possibly with transition
+symbols.</p>
+<p>&nbsp;</p>
+<p class="image"><img src="images/mg-defdesk-17.png" alt=""> <br>
+<strong>Figure:</strong> A Representation of an Activity</p>
+<h2>Creating and Deleting Activities</h2>
+<p>To create an activity you can either:</p>
+<ul>
+ <li>In the diagram toolbar palette select <strong>Activites</strong> under <strong>Items</strong>
+ and click on the canvas to place the activity symbol there. The created activity will
+ also appear in the tree view under the process definition symbol in the <strong>Outline</strong>
+ view.</li>
+</ul>
+<p class="image"><img src="images/mg-create-activity.png" alt=""> <br>
+<strong>Figure:</strong> Creation of an Activity</p>
+<ul>
+ <li>In the <strong>Outline</strong> view select the process definition to which
+ you want to add an activity. From its pop-up menu choose <strong>New Activity</strong>.
+ The created activity will appear in the tree view under the process definition symbol.
+ Subsequently, you can drag the activity symbol to the diagram canvas to create an
+ activity symbol there.</li>
+</ul>
+<p>When deleting activities you must make a distinction between deleting an activity
+from the model information or only deleting a symbol from a diagram. To do the first -
+delete an activity from model - you proceed as follows:</p>
+<ul>
+ <li>Having selected the symbol of the activity in the <strong>Outline</strong>
+ view, choose the option <strong>Delete </strong> in the pop-up menu of this process
+ definition.</li>
+ <li>Having selected the symbol of the activity in a process definition diagram,
+ choose the option <strong>Delete</strong> in the pop-up menu of this activity.</li>
+</ul>
+<p>The option <strong>Delete Symbol </strong> in the pop-up menu called from within
+the diagram canvas will only remove the activity symbol from the diagram.</p>
+<h2>Modifying Activity Properties</h2>
+<p>The properties of an activity are accessible in its properties dialog. To open
+this dialog, right-click the activity symbol - in the <strong>Outline</strong> view or
+diagram - and select the option <strong>Properties</strong>. Double-clicking on the
+activity symbol will open this dialog as well.</p>
+<p>Activity characteristics are bundled into the following categories, each
+represented in an own tabbed pane:</p>
+<ul>
+ <li><a href="#general">General</a></li>
+ <li><a href="#display">Display</a></li>
+ <li><a href="#controlFlow">Control Flow</a></li>
+ <li><a href="#in">In Data Mappings</a></li>
+ <li><a href="#out">Out Data Mappings</a></li>
+ <li><a href="#controlling">Controlling</a></li>
+ <li><a href="#simulation">Simulation</a></li>
+ <li><a href="#effort">Effort Planning</a></li>
+</ul>
+
+<h3 id="general">General</h3>
+<p>Next to a name, an ID and a description, general properties of an activity
+comprise the following checkbox options:</p>
+<ul>
+ <li><strong>Auto Id Generation</strong><br><br>
+ Overwrites the option for automatic Id generation set in <a
+ href="mg-preferences.html">@productname@ Preferences</a>.<br><br></li>
+ <li><strong>Allows Abort by Participant</strong><br><br>
+ Determines whether the assigned participant may abort instances of this
+ activity in the @productname@ Portal.<br>
+ Note that only the activity itself is aborted, not the root process hierarchy.
+ The process instances will continue as if this activity had been completed.<br>
+ This option affects the Process Portal activity operations only. It does not
+ influence the @productname@ API usage.<br><br></li>
+ <li><strong>Hibernate Initially</strong> (Hibernate On Creation)<br><br>
+ Determines whether the activity instance should directly change its state to
hibernated after creation - thus ending the synchronous flow here.<br><br></li>
<li><strong>Supports relocation</strong><br><br>
Determines if relocation is supported for this activity and it can
@@ -114,152 +161,152 @@ comprise the following checkbox options:</p>
Developer Handbooks</a>.</li>
</ul>
<p class="image"><img src="images/mg-defdesk-18.png" alt="General Activity Properties">
-<br>
-<strong>Figure:</strong> General Activity Properties</p>
-<p>Please note that IDs containing
- hyphens, blanks or dots and IDs starting with digits are not supported.</p>
-<h3 id="display">Display</h3>
-<p>For this property a checkbox is provided to mark activities as auxiliary
-from a business perspective. This option is disabled by default, except for the route activities.
-Auxiliary activities marked as <strong>Is Auxiliary Activity</strong>
-will be treated equivalent to route activities in the process history.</p>
-<p class="image"><img src="images/activity-props-display.png"
- alt="Display Option"> <br>
-<strong>Figure:</strong> Is Auxiliary Activity Option</p>
-<p>For route activities, this option
-is set to <strong>Is Auxiliary Activity</strong> per default.</p>
-<h3 id="controlFlow">Control Flow</h3>
-<p>Control flow options define the split, join and loop behavior around the
-activity.</p>
-<p class="image"><img src="images/mg-defdesk-19.png" alt="Control Flow Options">
-<br>
-<strong>Figure:</strong> Control Flow Options</p>
-<p><strong>Join</strong> behavior specifies the runtime behavior in case of multiple transitions from
-the predecessor activity leading to the chosen activity. The following options are
-offered:</p>
-<ul>
- <li>All incoming transitions are required to be processed for the execution of
- the activity (join with the <strong>AND</strong> option).</li>
- <li>If one incoming transition is processed the chosen activity is instantiated
- (join with the<strong> XOR</strong> option). If multiple incoming transitions are
- processed at runtime the chosen activity is instantiated multiple times.</li>
-</ul>
-<p><strong>Split</strong> behavior specifies how multiple transitions to the following activities are
-to be executed:</p>
-<ul>
- <li>all (split with the <strong>AND</strong> option)</li>
- <li>or one of them (split with <strong>XOR</strong> option).</li>
-</ul>
-<p>See also <a href="mg-basics-6.htm">Control Flow</a> for basic informations.</p>
-
-<p><strong>Loop </strong>behavior specifies how an activity is repeated
-until the loop condition is fulfilled. During the runtime execution of loop activity
-the specific part of the workflow is repeated.
-<p> When an activity enters the loop, one or more instances of the activity are created and performed.
-On termination of the activity instance, the loop condition is evaluated and based on the result
- a new activity instance is created. This is repeated until the loop gets terminated and then
-the subsequent activity is performed, if any.</p>
-<p> None indicates that the activity is performed exactly once regardless of the evaluation of the condition.
-The following loop conditions can be applied when the activity needs to be performed more than once. </p>
-
-<ul>
- <li> While - indicates that the condition is evaluated before the creation of an activity
- instance. If the condition evaluation result is TRUE, an activity instance is created and performed.
- If FALSE, the workflow continues and the next activity is performed. Using "while" loop it
- is possible that no activity instance is created.</li>
- <li> Repeat - indicates that the condition is evaluated at the completion of the activity instance.
- If the condition evaluation result is TRUE, the loop ends and the next activity is performed.
- If FALSE, a new instance of the activity is created and repeated.</li>
-
-</ul>
-<p> The syntax language for the loop condition parameter is carnotEL. Currently, the single line format
-is supported. The following figure explains the While loop condition.</p>
-<p>&nbsp</p>
-<p class ="image"><img src = "images/while-loop.png" alt="">
-<br>
-<strong>Figure:</strong>While Loop Condition</p>
-
-<p> More elaborate cycles in the model should be modeled
-explicitly by cycles in the activity/transition graph. See figure below.</p>
-<p class="image"><a href="images/mg-defdesk-trans-cycle_orgSize.png" target="_blank">
-<img src="images/mg-defdesk-trans-cycle.png" alt=""></a> <br>
-<strong>Figure:</strong> Transition in a Cycle</p>
-<p>In this example transition conditions influence the process flow. Please refer to
-<a href="mg-defdesk-5.htm#transitionConditions">Specifying Transition Conditions</a>.</p>
-
-<h3 id="in">In Data Mappings</h3>
-<p>The activity properties dialog allows you to add and remove data mappings
-belonging to this activity. The In data mapping maps workflow data to the input of the
-activity. Refer to <a href="mg-defdesk-7.htm">Specifying Data</a> for more information on
-mapping data to applications via an activity.</p>
-
-<h3 id="out">Out Data Mappings</h3>
-<p>The activity properties dialog allows you to add and remove data mappings
-belonging to this activity. The Out data mapping maps workflow data to the output of the
-activity. Refer to <a href="mg-defdesk-7.htm">Specifying Data</a> for more information on
-mapping data to applications via an activity.</p>
-
-<h3 id="controlling">Controlling Properties</h3>
-<p>The @productname@ Analyst Edition provides activities with the following controlling
-properties:</p>
-<ul>
- <li>Measure</li>
- <li>Target Measure Quantity</li>
- <li>Difficulty</li>
- <li>Target Processing Time</li>
- <li>Target Execution Time</li>
- <li>Target Idle Time</li>
- <li>Target Waiting Time</li>
- <li>Target Queue Depth</li>
- <li>Target Cost Per Execution</li>
- <li>Target Cost Per Second</li>
- <li>Resource Performance Calculation</li>
-</ul>
-<br />
-<p class="image"><img src="images/mg-act-controlling.png" alt=""> <br>
-<strong>Figure:</strong> Controlling Properties</p>
-<h4 id="resource">Resource Performance Calculation</h4>
-<p>This property has the default
-value <tt>include</tt> for interactive activities and <tt>not include</tt> for
-non-interactive activities. It is used in the Business Control Center view
-<a href="PLUGINS_ROOT/org.eclipse.stardust.docs.enduser/html/handbooks/execution-clients/bcc_renovated/views/bcc-views-resource.html">
-Resource Performance</a> view,
-where all activities having this controlling property set to <tt>include</tt> are
-included into the calculation.</p>
-<h3 id="simulation">Simulation</h3>
-<p>In this section you can specify simulation configurations, as described detailed in
-the chapter <a
- href="PLUGINS_ROOT/org.eclipse.stardust.docs.simulation/html/simulation/simulation-configurations.html">
-Simulation Configurations</a> of the <a
- href="PLUGINS_ROOT/org.eclipse.stardust.docs.simulation/html/simulation/toc.html">
-Developer Simulation Guide</a>.)</p>
-<h3 id="effort">Effort Planning</h3>
-<p>In this section you can specify the subprocess refinement required.</p>
-<p class="image"><img src="images/activitiy-prop-effort.png"
- alt="Effort Planning Prop"> <br>
-<strong>Figure:</strong> Setting the Subprocess Refinement Required.</p>
-<p>Pease refer to the chapter <a href="process-effort-calculation.html">Project
-Effort Calculation</a> for detailed information on Project Effort calculations.</p>
-
-<h2 id="subprocess">Subprocess Activities</h2>
-<p>To define an activity as a subprocess:</p>
-<ul>
- <li>Right-click the symbol in the diagram canvas and choose <strong>Subprocess</strong>.</li>
- <li>Select the process you want to define as subprocess.</li>
-</ul>
-<p class="image"><img src="images/mg-select-subprocess.png"
- alt="Setting the Implementation to Subprocess"> <br>
-<strong>Figure:</strong> Setting the Implementation to Subprocess</p>
-<p>For details on configuring subprocess activities, refer to chapter
-<a href="PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/handbooks/modelling/mg-subprocesses.html">
-Configuring Subprocess Activities</a>
-of the
-<a href="PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/handbooks/handbooks.htm">
-Developer Handbooks</a>.</p>
-<script language="JavaScript" type="text/javascript">
-<!--
-writeFooter();
--->
-</script>
-</body>
-</html>
+<br>
+<strong>Figure:</strong> General Activity Properties</p>
+<p>Please note that IDs containing
+ hyphens, blanks or dots and IDs starting with digits are not supported.</p>
+<h3 id="display">Display</h3>
+<p>For this property a checkbox is provided to mark activities as auxiliary
+from a business perspective. This option is disabled by default, except for the route activities.
+Auxiliary activities marked as <strong>Is Auxiliary Activity</strong>
+will be treated equivalent to route activities in the process history.</p>
+<p class="image"><img src="images/activity-props-display.png"
+ alt="Display Option"> <br>
+<strong>Figure:</strong> Is Auxiliary Activity Option</p>
+<p>For route activities, this option
+is set to <strong>Is Auxiliary Activity</strong> per default.</p>
+<h3 id="controlFlow">Control Flow</h3>
+<p>Control flow options define the split, join and loop behavior around the
+activity.</p>
+<p class="image"><img src="images/mg-defdesk-19.png" alt="Control Flow Options">
+<br>
+<strong>Figure:</strong> Control Flow Options</p>
+<p><strong>Join</strong> behavior specifies the runtime behavior in case of multiple transitions from
+the predecessor activity leading to the chosen activity. The following options are
+offered:</p>
+<ul>
+ <li>All incoming transitions are required to be processed for the execution of
+ the activity (join with the <strong>AND</strong> option).</li>
+ <li>If one incoming transition is processed the chosen activity is instantiated
+ (join with the<strong> XOR</strong> option). If multiple incoming transitions are
+ processed at runtime the chosen activity is instantiated multiple times.</li>
+</ul>
+<p><strong>Split</strong> behavior specifies how multiple transitions to the following activities are
+to be executed:</p>
+<ul>
+ <li>all (split with the <strong>AND</strong> option)</li>
+ <li>or one of them (split with <strong>XOR</strong> option).</li>
+</ul>
+<p>See also <a href="mg-basics-6.htm">Control Flow</a> for basic informations.</p>
+
+<p><strong>Loop </strong>behavior specifies how an activity is repeated
+until the loop condition is fulfilled. During the runtime execution of loop activity
+the specific part of the workflow is repeated.
+<p> When an activity enters the loop, one or more instances of the activity are created and performed.
+On termination of the activity instance, the loop condition is evaluated and based on the result
+ a new activity instance is created. This is repeated until the loop gets terminated and then
+the subsequent activity is performed, if any.</p>
+<p> None indicates that the activity is performed exactly once regardless of the evaluation of the condition.
+The following loop conditions can be applied when the activity needs to be performed more than once. </p>
+
+<ul>
+ <li> While - indicates that the condition is evaluated before the creation of an activity
+ instance. If the condition evaluation result is TRUE, an activity instance is created and performed.
+ If FALSE, the workflow continues and the next activity is performed. Using "while" loop it
+ is possible that no activity instance is created.</li>
+ <li> Repeat - indicates that the condition is evaluated at the completion of the activity instance.
+ If the condition evaluation result is TRUE, the loop ends and the next activity is performed.
+ If FALSE, a new instance of the activity is created and repeated.</li>
+
+</ul>
+<p> The syntax language for the loop condition parameter is carnotEL. Currently, the single line format
+is supported. The following figure explains the While loop condition.</p>
+<p>&nbsp</p>
+<p class ="image"><img src = "images/while-loop.png" alt="">
+<br>
+<strong>Figure:</strong>While Loop Condition</p>
+
+<p> More elaborate cycles in the model should be modeled
+explicitly by cycles in the activity/transition graph. See figure below.</p>
+<p class="image"><a href="images/mg-defdesk-trans-cycle_orgSize.png" target="_blank">
+<img src="images/mg-defdesk-trans-cycle.png" alt=""></a> <br>
+<strong>Figure:</strong> Transition in a Cycle</p>
+<p>In this example transition conditions influence the process flow. Please refer to
+<a href="mg-defdesk-5.htm#transitionConditions">Specifying Transition Conditions</a>.</p>
+
+<h3 id="in">In Data Mappings</h3>
+<p>The activity properties dialog allows you to add and remove data mappings
+belonging to this activity. The In data mapping maps workflow data to the input of the
+activity. Refer to <a href="mg-defdesk-7.htm">Specifying Data</a> for more information on
+mapping data to applications via an activity.</p>
+
+<h3 id="out">Out Data Mappings</h3>
+<p>The activity properties dialog allows you to add and remove data mappings
+belonging to this activity. The Out data mapping maps workflow data to the output of the
+activity. Refer to <a href="mg-defdesk-7.htm">Specifying Data</a> for more information on
+mapping data to applications via an activity.</p>
+
+<h3 id="controlling">Controlling Properties</h3>
+<p>The @productname@ Analyst Edition provides activities with the following controlling
+properties:</p>
+<ul>
+ <li>Measure</li>
+ <li>Target Measure Quantity</li>
+ <li>Difficulty</li>
+ <li>Target Processing Time</li>
+ <li>Target Execution Time</li>
+ <li>Target Idle Time</li>
+ <li>Target Waiting Time</li>
+ <li>Target Queue Depth</li>
+ <li>Target Cost Per Execution</li>
+ <li>Target Cost Per Second</li>
+ <li>Resource Performance Calculation</li>
+</ul>
+<br />
+<p class="image"><img src="images/mg-act-controlling.png" alt=""> <br>
+<strong>Figure:</strong> Controlling Properties</p>
+<h4 id="resource">Resource Performance Calculation</h4>
+<p>This property has the default
+value <tt>include</tt> for interactive activities and <tt>not include</tt> for
+non-interactive activities. It is used in the Business Control Center view
+<a href="PLUGINS_ROOT/org.eclipse.stardust.docs.enduser/html/handbooks/execution-clients/bcc_renovated/views/bcc-views-resource.html">
+Resource Performance</a> view,
+where all activities having this controlling property set to <tt>include</tt> are
+included into the calculation.</p>
+<h3 id="simulation">Simulation</h3>
+<p>In this section you can specify simulation configurations, as described detailed in
+the chapter <a
+ href="PLUGINS_ROOT/org.eclipse.stardust.docs.simulation/html/simulation/simulation-configurations.html">
+Simulation Configurations</a> of the <a
+ href="PLUGINS_ROOT/org.eclipse.stardust.docs.simulation/html/simulation/toc.html">
+Developer Simulation Guide</a>.)</p>
+<h3 id="effort">Effort Planning</h3>
+<p>In this section you can specify the subprocess refinement required.</p>
+<p class="image"><img src="images/activitiy-prop-effort.png"
+ alt="Effort Planning Prop"> <br>
+<strong>Figure:</strong> Setting the Subprocess Refinement Required.</p>
+<p>Pease refer to the chapter <a href="process-effort-calculation.html">Project
+Effort Calculation</a> for detailed information on Project Effort calculations.</p>
+
+<h2 id="subprocess">Subprocess Activities</h2>
+<p>To define an activity as a subprocess:</p>
+<ul>
+ <li>Right-click the symbol in the diagram canvas and choose <strong>Subprocess</strong>.</li>
+ <li>Select the process you want to define as subprocess.</li>
+</ul>
+<p class="image"><img src="images/mg-select-subprocess.png"
+ alt="Setting the Implementation to Subprocess"> <br>
+<strong>Figure:</strong> Setting the Implementation to Subprocess</p>
+<p>For details on configuring subprocess activities, refer to chapter
+<a href="PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/handbooks/modelling/mg-subprocesses.html">
+Configuring Subprocess Activities</a>
+of the
+<a href="PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/handbooks/handbooks.htm">
+Developer Handbooks</a>.</p> -->
+<script language="JavaScript" type="text/javascript">
+<!--
+writeFooter();
+-->
+</script>
+</body>
+</html>
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/mg-defdesk-15.htm b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-annotation.htm
index 3c699b0..4ad4a56 100644
--- a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/mg-defdesk-15.htm
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-annotation.htm
@@ -1,55 +1,55 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd"><HTML>
-<HEAD>
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../../styles/carnot.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE> Using Annotations</TITLE>
-<script language="JavaScript" src="../../styles/naviLine.js" type="text/javascript"></script>
-</head>
-<body>
-<script language="JavaScript">
-<!--
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd"><HTML>
+<HEAD>
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
+<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
+
+<LINK REL="STYLESHEET" HREF="../../styles/carnot.css" CHARSET="ISO-8859-1" TYPE="text/css">
+<TITLE> Using Annotations</TITLE>
+<script language="JavaScript" src="../../styles/naviLine.js" type="text/javascript"></script>
+</head>
+<body>
+<script language="JavaScript">
+<!--
writeNavigation("Swim Lanes Usage","PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/toc.html",
"mg-defdesk-14.htm","mg-pools-lanes.htm",
"../../toc.html","Business Analyst Handbooks",
"mg-preface.htm","The Modeling Guide",
"mg-modeler-preface.html","The Process Workbench");
- -->
-</script>
-
-<h1 >
- Using Annotations</h1>
-<P >
-Annotations are used as multiple-line textual comments attached to the selected model element(s). Unlike the rest of the diagram symbols, which are meaningful elements throughout the model, annotations have their meaning principally within the context of the diagram in which they are placed. In this way a symbol can be annotated by different text pieces in different diagrams. </P>
-<P >
-There are no limitations concerning the number of annotations referring to one model element (neither per diagram nor per model). Annotations can refer to all classes of model elements, including both product components as well as the relationships between them (transitions and connections).</P>
-<h2>Creating an Annotation</h2>
-<p>To create an annotation:</p>
-<ul>
- <li>Select <strong>Annotations &gt; Annotation</strong> in the diagram toolbar palette.</li>
- <li>Place the annotation on the diagram canvas and fill in the annotation text.</li>
-</ul>
- <p class="image"><img src="images/mg-defdesk-create-annotation.png" alt="Create Annotation">
- <br><strong>Figure:</strong> Creating an Annotation</p>
-<p>To link the annotation to a model element:</p>
-<ul>
- <li>Right-click the model element and select <strong>Connect</strong>.</li>
-</ul>
- <p class="image"><img src="images/mg-defdesk-connect-annotation.png" alt="Connect Annotation">
- <br><strong>Figure:</strong> Connecting an Annotation</p>
-<ul>
- <li>Click the model element to connect the annotation to.</li>
-</ul>
- <p class="image"><img src="images/mg-defdesk-connect-annotation-2.png" alt="Connect Annotation">
- <br><strong>Figure:</strong> Connecting to a Model Element</p>
-<P >
-Annotation text is displayed in a box and can be entered after the annotation symbol has been created. It supports copy and paste functionality conventional for the platform and leaves the decision where the return carriages should be placed to the user (no automatic reformatting).</P>
-<P>If you want to add text as annotation to the diagram without connecting it to a symbol and not displayed in a box, just choose <strong>Annotations &gt; Text</strong> in the diagram menu and place the text on the diagram canvas with the mouse.</P>
-<script language="JavaScript">
-<!--
-writeFooter();
--->
-</script>
-</body>
-</html>
+ -->
+</script>
+
+<h1 >
+ Using Annotations</h1>
+<P >
+Annotations are used as multiple-line textual comments attached to the selected model element(s). Unlike the rest of the diagram symbols, which are meaningful elements throughout the model, annotations have their meaning principally within the context of the diagram in which they are placed. In this way a symbol can be annotated by different text pieces in different diagrams. </P>
+<P >
+There are no limitations concerning the number of annotations referring to one model element (neither per diagram nor per model). Annotations can refer to all classes of model elements, including both product components as well as the relationships between them (transitions and connections).</P>
+<h2>Creating an Annotation</h2>
+<p>To create an annotation:</p>
+<ul>
+ <li>Select <strong>Annotations &gt; Annotation</strong> in the diagram toolbar palette.</li>
+ <li>Place the annotation on the diagram canvas and fill in the annotation text.</li>
+</ul>
+ <p class="image"><img src="images/mg-defdesk-create-annotation.png" alt="Create Annotation">
+ <br><strong>Figure:</strong> Creating an Annotation</p>
+<p>To link the annotation to a model element:</p>
+<ul>
+ <li>Right-click the model element and select <strong>Connect</strong>.</li>
+</ul>
+ <p class="image"><img src="images/mg-defdesk-connect-annotation.png" alt="Connect Annotation">
+ <br><strong>Figure:</strong> Connecting an Annotation</p>
+<ul>
+ <li>Click the model element to connect the annotation to.</li>
+</ul>
+ <p class="image"><img src="images/mg-defdesk-connect-annotation-2.png" alt="Connect Annotation">
+ <br><strong>Figure:</strong> Connecting to a Model Element</p>
+<P >
+Annotation text is displayed in a box and can be entered after the annotation symbol has been created. It supports copy and paste functionality conventional for the platform and leaves the decision where the return carriages should be placed to the user (no automatic reformatting).</P>
+<P>If you want to add text as annotation to the diagram without connecting it to a symbol and not displayed in a box, just choose <strong>Annotations &gt; Text</strong> in the diagram menu and place the text on the diagram canvas with the mouse.</P>
+<script language="JavaScript">
+<!--
+writeFooter();
+-->
+</script>
+</body>
+</html>
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/mg-defdesk-6.htm b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-application.htm
index 981d975..c1a7d20 100644
--- a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/mg-defdesk-6.htm
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-application.htm
@@ -1,100 +1,100 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-
-<link rel="STYLESHEET" href="../../styles/carnot.css" charset="ISO-8859-1" type="text/css">
-<title>Specifying Applications</title>
-<script language="JavaScript" src="../../styles/naviLine.js" type="text/javascript"></script>
-</head>
-<body>
-<script language="JavaScript" type="text/javascript">
-<!--
- writeNavigation("Specifying Data","PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/toc.html",
- "mg-defdesk-5.htm","mg-defdesk-7.htm","../../toc.html","Business Analyst Handbooks",
- "mg-preface.htm","The Modeling Guide",
- "mg-modeler-preface.html","The Process Workbench");
- -->
-</script>
-
-<h1>Specifying Applications</h1>
-<p>Activities performed within the context of a business process may have to execute
-application logic. This application logic is defined by a concept called application. For
-more details on applications refer to <a href="mg-basics-7.htm">Applications</a>.</p>
-<p>This section will explain how to work with applications in the <strong>Process
-Workbench</strong>.</p>
-
-<h2>Creating Applications</h2>
-<p>To create an application you can either:</p>
-<ul>
- <li>In the toolbar palette of the <a href="model-views/views-diagrams.html">diagram</a>
- select <strong>Application</strong> under <strong>Items</strong>. The application is
- created by subsequently clicking on the diagram canvas and appears also in the <strong>Outline</strong>
- view.</li>
-</ul>
-<p class="image"><img src="images/mg-create-application.png" alt=""><br />
-</p>
-<ul>
- <li>Or in the <strong>Application</strong> section of the <a
- href="model-views/views-outline.html">Outline view</a> area, choose <strong>New
- Application</strong> from the pop-up menu. The created application will appear in the <strong>Outline</strong>
- view and can be dragged to the diagram canvas.</li>
-</ul>
-<p>Next, open the application properties dialog by double-clicking on the
-applications symbol. Choose an ID and a name for the application.
-Please note that IDs containing
-hyphens, blanks or dots and IDs starting with digits are not supported.
-Using the Visibility Public option, you can also specify whether you want to import applications
-by reference when referenced in another model.
- <p class="image"><img src="images/visibility.png"
- alt="General Properties of an application"> <br>
-<strong>Figure:</strong> General Properties</p>
- <p> For more information, please refer to <a href="mg-preferences.html#multipackage">
- Multi Package Modeling Preferences</a> section of <a href="mg-preferences.html">Setting @productname@ Preferences</a> chapter.
-Edit the
-application type specific properties. </p>
-
-
-<h2>Modifying Applications</h2>
-<p>To modify an application, double-click the application symbol in the <a
- href="model-views/views-outline.html">Outline view</a> or in a <a
- href="model-views/views-diagrams.html">diagram</a>. The properties dialog
- opens where you can perform your changes.</p>
-<h3>Controlling</h3>
-<p>An application provides the following controlling properties:</p>
-<ul>
- <li>Cost Center</li>
- <li>Actual Cost Per Second</li>
-</ul>
-<p class="image"><img src="images/mg-appl-controlling.png" alt=""> <br>
-<strong>Figure:</strong> Controlling Properties of an Application</p>
-<h3>Simulation</h3>
-<p>In this section you can specify simulation configurations, as described detailed in the chapter
- <a href="PLUGINS_ROOT/org.eclipse.stardust.docs.simulation/html/simulation/simulation-configurations.html">
- Simulation Configurations</a>
-of the
- <a href="PLUGINS_ROOT/org.eclipse.stardust.docs.simulation/html/simulation/toc.html">
- Developer Simulation Guide</a>.)
-<h3>Effort Planning</h3>
-<p>In this section you can set the following Process Effort properties:</p>
-<p class="image"><img src="images/application-effort-planning-props.png" alt=""> <br>
-<strong>Figure:</strong> Effort Planning Properties of an Application</p>
-<p>Please refer to the chapter <a href="process-effort-calculation.html">Project Effort Calculation</a> for
-detailed information on this functionality.</p>
-
-<h2>Deleting Applications</h2>
-<p>To delete an application, use the option <strong>Delete </strong>in the
-application's pop-up menu in a diagram. In the <strong>Outline</strong> view, use the
-corresponding option <strong>Delete</strong>.</p>
-<p>To remove an application symbol from the diagram, choose the option <strong>Delete
-Symbol</strong> in the application's pop-up menu. After this operation the application will still
-be part of the model.</p>
-
-<script language="JavaScript" type="text/javascript">
-<!--
-writeFooter();
--->
-</script>
-</body>
-</html>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<meta http-equiv="Content-Style-Type" content="text/css">
+
+<link rel="STYLESHEET" href="../../styles/carnot.css" charset="ISO-8859-1" type="text/css">
+<title>Specifying Applications</title>
+<script language="JavaScript" src="../../styles/naviLine.js" type="text/javascript"></script>
+</head>
+<body>
+<script language="JavaScript" type="text/javascript">
+<!--
+ writeNavigation("Specifying Data","PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/toc.html",
+ "mg-defdesk-5.htm","mg-defdesk-7.htm","../../toc.html","Business Analyst Handbooks",
+ "mg-preface.htm","The Modeling Guide",
+ "mg-modeler-preface.html","The Process Workbench");
+ -->
+</script>
+
+<h1>Specifying Applications</h1>
+<p>Activities performed within the context of a business process may have to execute
+application logic. This application logic is defined by a concept called application. For
+more details on applications refer to <a href="mg-basics-7.htm">Applications</a>.</p>
+<p>This section will explain how to work with applications in the <strong>Process
+Workbench</strong>.</p>
+
+<h2>Creating Applications</h2>
+<p>To create an application you can either:</p>
+<ul>
+ <li>In the toolbar palette of the <a href="model-views/views-diagrams.html">diagram</a>
+ select <strong>Application</strong> under <strong>Items</strong>. The application is
+ created by subsequently clicking on the diagram canvas and appears also in the <strong>Outline</strong>
+ view.</li>
+</ul>
+<p class="image"><img src="images/mg-create-application.png" alt=""><br />
+</p>
+<ul>
+ <li>Or in the <strong>Application</strong> section of the <a
+ href="model-views/views-outline.html">Outline view</a> area, choose <strong>New
+ Application</strong> from the pop-up menu. The created application will appear in the <strong>Outline</strong>
+ view and can be dragged to the diagram canvas.</li>
+</ul>
+<p>Next, open the application properties dialog by double-clicking on the
+applications symbol. Choose an ID and a name for the application.
+Please note that IDs containing
+hyphens, blanks or dots and IDs starting with digits are not supported.
+Using the Visibility Public option, you can also specify whether you want to import applications
+by reference when referenced in another model.
+ <p class="image"><img src="images/visibility.png"
+ alt="General Properties of an application"> <br>
+<strong>Figure:</strong> General Properties</p>
+ <p> For more information, please refer to <a href="mg-preferences.html#multipackage">
+ Multi Package Modeling Preferences</a> section of <a href="mg-preferences.html">Setting @productname@ Preferences</a> chapter.
+Edit the
+application type specific properties. </p>
+
+
+<h2>Modifying Applications</h2>
+<p>To modify an application, double-click the application symbol in the <a
+ href="model-views/views-outline.html">Outline view</a> or in a <a
+ href="model-views/views-diagrams.html">diagram</a>. The properties dialog
+ opens where you can perform your changes.</p>
+<h3>Controlling</h3>
+<p>An application provides the following controlling properties:</p>
+<ul>
+ <li>Cost Center</li>
+ <li>Actual Cost Per Second</li>
+</ul>
+<p class="image"><img src="images/mg-appl-controlling.png" alt=""> <br>
+<strong>Figure:</strong> Controlling Properties of an Application</p>
+<h3>Simulation</h3>
+<p>In this section you can specify simulation configurations, as described detailed in the chapter
+ <a href="PLUGINS_ROOT/org.eclipse.stardust.docs.simulation/html/simulation/simulation-configurations.html">
+ Simulation Configurations</a>
+of the
+ <a href="PLUGINS_ROOT/org.eclipse.stardust.docs.simulation/html/simulation/toc.html">
+ Developer Simulation Guide</a>.)
+<h3>Effort Planning</h3>
+<p>In this section you can set the following Process Effort properties:</p>
+<p class="image"><img src="images/application-effort-planning-props.png" alt=""> <br>
+<strong>Figure:</strong> Effort Planning Properties of an Application</p>
+<p>Please refer to the chapter <a href="process-effort-calculation.html">Project Effort Calculation</a> for
+detailed information on this functionality.</p>
+
+<h2>Deleting Applications</h2>
+<p>To delete an application, use the option <strong>Delete </strong>in the
+application's pop-up menu in a diagram. In the <strong>Outline</strong> view, use the
+corresponding option <strong>Delete</strong>.</p>
+<p>To remove an application symbol from the diagram, choose the option <strong>Delete
+Symbol</strong> in the application's pop-up menu. After this operation the application will still
+be part of the model.</p>
+
+<script language="JavaScript" type="text/javascript">
+<!--
+writeFooter();
+-->
+</script>
+</body>
+</html>
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/mg-defdesk-5.htm b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-con-sequence.htm
index 7ac69f3..684add6 100644
--- a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/mg-defdesk-5.htm
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-con-sequence.htm
@@ -1,281 +1,281 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-
-<link rel="STYLESHEET" href="../../styles/carnot.css"
- charset="ISO-8859-1" type="text/css">
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<meta http-equiv="Content-Style-Type" content="text/css">
+
+<link rel="STYLESHEET" href="../../styles/carnot.css"
+ charset="ISO-8859-1" type="text/css">
<title>Working with Gateways</title>
-<script language="JavaScript" src="../../styles/naviLine.js"
- type="text/javascript"></script>
-</head>
-<body>
-<script language="JavaScript" type="text/javascript">
-<!--
- writeNavigation("Specifying Applications","PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/toc.html",
- "mg-defdesk-4.htm","mg-defdesk-6.htm",
- "../../toc.html","Business Analyst Handbooks",
- "mg-preface.htm","The Modeling Guide",
- "mg-modeler-preface.html","The Process Workbench");
- -->
-</script>
-
+<script language="JavaScript" src="../../styles/naviLine.js"
+ type="text/javascript"></script>
+</head>
+<body>
+<script language="JavaScript" type="text/javascript">
+<!--
+ writeNavigation("Specifying Applications","PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/toc.html",
+ "mg-defdesk-4.htm","mg-defdesk-6.htm",
+ "../../toc.html","Business Analyst Handbooks",
+ "mg-preface.htm","The Modeling Guide",
+ "mg-modeler-preface.html","The Process Workbench");
+ -->
+</script>
+
<h1>Working with Gateways</h1>
-<p>Transitions determine the sequence of activities. A transition
-connects an activity with its successor activity. It also allows to set
-a condition - only if this condition is fulfilled at runtime the
-transition is processed and the next activity will be executed.</p>
-
-<h2>Creating Transitions</h2>
-<p>To create a transition between two activities:</p>
-<ol>
- <li>Right-click the predecessor activity.</li>
- <li>Select <strong>Connect</strong> from the context menu.</li>
- <li>Click the subsequent activity.</li>
-</ol>
-<p>&nbsp;</p>
-<p class="image"><img src="images/mg-create-transition-context.png"
- alt=""> <br>
-<strong>Figure:</strong> Creating a Transition between Activities</p>
-<p>If you have created at least one link type with target and source
-type <tt>Activity</tt>, you have the choice to select between the custom
-link types and the standard transition. Please refer to chapter <a
- href="mg-defdesk-14.htm">Specifying Arbitrary Link Types</a> for
-information on custom link types.</p>
-<p class="image"><img src="images/mg-connexion-selection.png" alt="">
-<br>
-<strong>Figure:</strong> Select the Type of Transition</p>
-<h2>Routing Options</h2>
-<p>To draw a transition, you can choose the way it will connect an
-element to another. You have the following three options:</p>
-<ul>
- <li><a href="#default">Default</a></li>
- <li><a href="#shortest">Shortest Path</a></li>
- <li><a href="#manhattan">Manhattan</a></li>
- <li><a href="#explicit">Explicit</a></li>
-</ul>
-<p>To select the routing option:</p>
-<ul>
- <li>Right-click the symbol of the transition.</li>
- <li>Select <strong>Routing</strong>.</li>
- <li>Choose the routing type in the provided list.</li>
-</ul>
-<p class="image"><img src="images/mg-select-routing.png" alt="">
-<br>
-<strong>Figure:</strong> Select Routing Option</p>
-<h3 id="default">Default</h3>
-<p>The option <strong>Default</strong> sets the default value
-according to the type of transition.</p>
-<p><strong>Manhattan</strong> routing is set as default for
-transitions of the following elements:</p>
-<ul>
- <li>Activity transitions</li>
- <li>Trigger</li>
-</ul>
-<p>The <strong>Shortest Path</strong> routing option is set as
-default for transitions of the following elements:</p>
-<ul>
- <li>Data</li>
- <li>Applications</li>
- <li>Participants</li>
-</ul>
-<h3 id="shortest">Shortest Path</h3>
-<p>This option draws the shortest path between two elements. If
-there is no element between these two elements this means a direct
-straight line.</p>
-<p class="image"><img src="images/mg-routing-shortest.png" alt="">
-<br>
-<strong>Figure:</strong> Shortest Path with no Obstacle</p>
-<p>In case an element is between, the shortest path around this
-element is drawn to avoid overlapping.</p>
-<p class="image"><img src="images/mg-routing-shortest-2.png" alt="">
-<br>
-<strong>Figure:</strong> Shortest Path with Obstacle</p>
-<h3 id="manhattan">Manhattan</h3>
-<p>The Manhattan routing option uses a combination of vertical and
-horizontal lines to connect the symbols.</p>
-<p class="image"><img src="images/mg-routing-manhattan.png" alt="">
-<br>
-<strong>Figure:</strong> Transition with Manhattan Routing Option</p>
-<h3 id="explicit">Explicit</h3>
-<p>The Explicit Routing option gives the possibility to adjust the
-transition line. When you click the transition line, a dragging cross
-appears as bendpoint in the middle of the line. You can drag this
-bendpoint to another place on the canvas. While dragging a bendpoint, a
-new bendpoint is created for each of the two lines divided by this
-bendpoint. In this way you can create as many bendpoints you need.</p>
-<p class="image"><img src="images/mg-routing-explicit.png" alt="">
-<br>
-<strong>Figure:</strong> Transition with Explicit Routing Option</p>
-<h4>Moving several bendpoints</h4>
-<p>You can select several bendpoints and move them synchronously:</p>
-<ul>
- <li>Hold the Crtl key and click on the bendpoints to be included
- in the selection.</li>
- <li>The color of the selected bendpoints will change to red.</li>
- <li>To unselect a bendpoint click it again (still holding the Crtl
- key). Its color will change back to black.</li>
- <li>To unselect the whole selection click somewhere on the canvas.</li>
- <li>To move the selected bendpoints pick one of them and drag it
- to a desired position.</li>
-</ul>
-<p class="image"><img
- src="images/mg-routing-explicit-move-bendpoints.png" alt=""> <br>
-<strong>Figure:</strong> Move Bendpoints</p>
-<h2>Cyclic Transitions</h2>
-<p>You can also create cyclic transitions. This means that an
-activity cycle involves repetitive execution of one or more activities
-until a condition is met.</p>
-<p>To create a cyclic transition between activities:</p>
-<ul>
- <li>Open the activity properties dialog of the predecessor join
- activity.</li>
- <li>Change to <strong>Control Flow</strong> in the properties
- menu and choose<strong> XOR</strong> as split behavior.</li>
- <li>Then open the properties dialog of the subsequent split
- activity and choose <strong>XOR</strong> as join control flow behavior.</li>
- <li>Right-click the split symbol of the predecessor activity.</li>
- <li>Select <strong>Connect</strong> in the context-menu.</li>
- <li>Click the join symbol of the subsequent activity.</li>
-</ul>
-<p>&nbsp;</p>
-<p class="image"><a href="images/mg-defdesk-cyclic_orgSize.png"
- target="_blank"> <img src="images/mg-defdesk-cyclic.png" alt=""></a>
-<br>
-<strong>Figure:</strong> Cyclic Transition</p>
-<p>In this example the last activity <tt>Start_Campaign</tt> is
-only instantiated if the data <strong>Status</strong> has the value 1
-(see also <a href="#transitionConditions">Specifying Transition
-Conditions</a> ) or else the process continues with <tt>Order Media</tt>.</p>
-<h2>Deleting Transitions and Transition Symbols</h2>
-<p>To delete a transition, use the option <strong>Delete</strong>
-in the transition's pop-up menu.</p>
-<p>To remove a transition symbol from the diagram, choose the
-option <strong>Delete Symbol</strong> in the transition's context menu.
-After this operation the transition between the two activities will
-still exist in the model.</p>
-<h3>Restore Transition Symbols</h3>
-<p>Having removed transition symbols, you can always restore them
-in your diagram:</p>
-<ul>
- <li>Right-click your diagram canvas.</li>
- <li>Choose the <strong>Reload Connections</strong> option in the
- context menu.</li>
- <li>In the upcoming <strong>Available Connections</strong> dialog
- select the connections to restore.</li>
-</ul>
-<p class="image"><img src="images/mg-defdesk-75.png"
- alt="Reload Connections"> <br>
-<strong>Figure:</strong> Reload Connections</p>
-<h2 id="conditions">Setting Transition Conditions</h2>
-<p>The properties of a transition are accessible in its properties dialog. To open
-this dialog, right-click the transition symbol in a model diagram and select the option <strong>Properties</strong>.</p>
-<p>Besides name and id the general properties of a transition include a condition
-type option, a condition expression field and a description. The
-<strong>Fork on traversal</strong> option of a transition controls
-the synchronicity and concurrency behavior during the execution of the corresponding
-process instances. Please refer to the section
-<a href="PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/handbooks/concepts/workflow-basics/mg-basics-13.htm#activityThread">
-Activity Thread</a> of the chapter
-<a href="PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/handbooks/concepts/workflow-basics/mg-basics-13.htm">
-Runtime Behavior</a> for detailed information on the <strong>Fork on Traversal</strong>
-functionality.</p>
-<p>You can set the <tt>View Fork on Traversal</tt> flag on the
-<a href="PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/handbooks/modelling/mg-preferences.html#drawing">Drawing Preferences</a> page
-to visualize how @productname@ Engine traverses during transition conditions.</p> <p>Please note if setting the ID, that IDs containing
- hyphens, blanks or dots and IDs starting with digits are not supported.</p>
-
-<h3>Setting the Condition Type</h3>
-<p>In the <strong>Condition Type</strong> field you can select the types
-<tt>OTHERWISE</tt> or <tt>CONDITION</tt>:</p>
-<p class="image"><img src="images/transition-condition-type.png"
- alt="Select the Condition Type."> <br>
-<strong>Figure:</strong> Select the Condition Type.</p>
-<p>Please note that switching between those types will remove transition
-conditions already entered.</p>
-<h4>CONDITION</h4>
-<p>The condition type <tt>CONDITION</tt> enables entering code in the <strong>
-Condition Expression</strong> editor. The return value of this expression will be
-checked to be <tt>true</tt>.</p>
-<h4>OTHERWISE</h4>
-<p>If the condition type <tt>OTHERWISE</tt> is selected, the transition
-is only evaluated to <tt>true</tt>, if all the other conditions on the split have
-the value <tt>false</tt>. The <strong>Condition Expression</strong> editor is
-disabled.</p>
-<h3 id="transitionConditions">Specifying Transition Conditions</h3>
-<p>In the <strong>Condition Expression</strong> field you can specify a condition. The transition
-is then only traversed and the next activity performed if this condition is fulfilled.</p>
-<p>Transition conditions are specified if the successor activity is only to be
-performed under particular circumstances. Please refer to the chapter <a
- href="mg-basics-6.htm#transcond">Transition Conditions</a> of the Basics <a
- href="mg-basics-6.htm">Control Flow</a> chapter for detailed information on the
-operators and variables that can be used in transition conditions.</p>
-<p>If the return value of a transition condition is <tt>true</tt>, the transition
-will always be traversed and the successor activity executed. To specify a transition
-condition, open the transition's properties dialog and enter a predicate in the
-<strong>Condition Expression</strong> field:</p>
-<p class="image"><img src="images/mg-defdesk-transition-cond.png"
- alt="Setting a Transition Condition"> <br>
-<strong>Figure:</strong> Setting a Transition Condition</p>
-<p>In this example it will be checked whether the state of the SupportCaseData is
-neither closed nor rejected. The value is referenced via the dereferentiation path
-<tt>SupportCaseData.Product.State</tt>.</p>
-<p>A JavaScript based editor is provided, e.g. to add arithmetic, relational and
-logical operators as well as string matching operators.</p>
-<p>You can combine operators and values retrieved via dereferentiation paths with
-JavaScript language. Here are some examples for possible transition
-conditions:</p>
-<pre>Primitive.charAt(2)=="A"</pre>
-<pre>
-function toUpper(stringArg) {
- return stringArg.toUpperCase();
-}
-
-Primitive == toUpper(SupportCaseData.Name)</pre>
-<pre>
-var id=0;
-for (var i = 0; i &lt; 10; i++) {
- id = id*10 + i;
-}
-SupportCaseData.Id == id
-</pre>
-<p>Errors and warnings are indicated in a transition condition
-on the left side of the expression. A tooltip gives detailed information
-about the kind of error or warning.</p>
-<p class="image"><img src="images/trans-cond-error.png"
- alt="Indicated Error in Transition Condition"> <br>
-<strong>Figure:</strong> Indicated Error in Transition Condition</p>
-<h4>Data proposal</h4>
-<p>Pressing <tt>Ctrl-Space</tt> in the transition condition editor
-provides you with a list to choose from all available
-data, e.g.:</p>
-<p class="image"><img src="images/tc-data-proposal.png"
- alt="Default Proposals for Data."> <br>
-<strong>Figure:</strong> Default Proposals for Data.</p>
-<h4>Code completion</h4>
-<p>While typing the expression, you can press <tt>Ctrl-Space</tt> to
-show and choose from proposals for available methods:</p>
-<p class="image"><img src="images/tc-method-proposal.png"
- alt="Default Proposals for Methods."> <br>
-<strong>Figure:</strong> Default Proposals for Methods.</p>
-<h4>Not indicated errors</h4>
-<p>Please be aware that no errors or warnings will be displayed in
-case you use an unsupported assignment to a @productname@ variable, because
-the validation of the JavaScript code is correct. For
-example, if you enter <tt>SupportCaseData.Product.State="R"</tt>
-instead of <tt>SupportCaseData.Product.State=="R"</tt>, there will be no
-warning and during the process an assignment instead a comparison will
-tried to be performed, which fails.</p>
-<h4>Undefined return values</h4>
-<p>In case the return value of a transition condition is undefined, for example
-when all code is commented out, the transition condition will be evaluated
-as <tt>TRUE</tt> at runtime.</p>
-
-<script language="JavaScript" type="text/javascript">
-<!--
-writeFooter();
--->
-</script>
-</body>
-</html>
+<p>Transitions determine the sequence of activities. A transition
+connects an activity with its successor activity. It also allows to set
+a condition - only if this condition is fulfilled at runtime the
+transition is processed and the next activity will be executed.</p>
+
+<h2>Creating Transitions</h2>
+<p>To create a transition between two activities:</p>
+<ol>
+ <li>Right-click the predecessor activity.</li>
+ <li>Select <strong>Connect</strong> from the context menu.</li>
+ <li>Click the subsequent activity.</li>
+</ol>
+<p>&nbsp;</p>
+<p class="image"><img src="images/mg-create-transition-context.png"
+ alt=""> <br>
+<strong>Figure:</strong> Creating a Transition between Activities</p>
+<p>If you have created at least one link type with target and source
+type <tt>Activity</tt>, you have the choice to select between the custom
+link types and the standard transition. Please refer to chapter <a
+ href="mg-defdesk-14.htm">Specifying Arbitrary Link Types</a> for
+information on custom link types.</p>
+<p class="image"><img src="images/mg-connexion-selection.png" alt="">
+<br>
+<strong>Figure:</strong> Select the Type of Transition</p>
+<h2>Routing Options</h2>
+<p>To draw a transition, you can choose the way it will connect an
+element to another. You have the following three options:</p>
+<ul>
+ <li><a href="#default">Default</a></li>
+ <li><a href="#shortest">Shortest Path</a></li>
+ <li><a href="#manhattan">Manhattan</a></li>
+ <li><a href="#explicit">Explicit</a></li>
+</ul>
+<p>To select the routing option:</p>
+<ul>
+ <li>Right-click the symbol of the transition.</li>
+ <li>Select <strong>Routing</strong>.</li>
+ <li>Choose the routing type in the provided list.</li>
+</ul>
+<p class="image"><img src="images/mg-select-routing.png" alt="">
+<br>
+<strong>Figure:</strong> Select Routing Option</p>
+<h3 id="default">Default</h3>
+<p>The option <strong>Default</strong> sets the default value
+according to the type of transition.</p>
+<p><strong>Manhattan</strong> routing is set as default for
+transitions of the following elements:</p>
+<ul>
+ <li>Activity transitions</li>
+ <li>Trigger</li>
+</ul>
+<p>The <strong>Shortest Path</strong> routing option is set as
+default for transitions of the following elements:</p>
+<ul>
+ <li>Data</li>
+ <li>Applications</li>
+ <li>Participants</li>
+</ul>
+<h3 id="shortest">Shortest Path</h3>
+<p>This option draws the shortest path between two elements. If
+there is no element between these two elements this means a direct
+straight line.</p>
+<p class="image"><img src="images/mg-routing-shortest.png" alt="">
+<br>
+<strong>Figure:</strong> Shortest Path with no Obstacle</p>
+<p>In case an element is between, the shortest path around this
+element is drawn to avoid overlapping.</p>
+<p class="image"><img src="images/mg-routing-shortest-2.png" alt="">
+<br>
+<strong>Figure:</strong> Shortest Path with Obstacle</p>
+<h3 id="manhattan">Manhattan</h3>
+<p>The Manhattan routing option uses a combination of vertical and
+horizontal lines to connect the symbols.</p>
+<p class="image"><img src="images/mg-routing-manhattan.png" alt="">
+<br>
+<strong>Figure:</strong> Transition with Manhattan Routing Option</p>
+<h3 id="explicit">Explicit</h3>
+<p>The Explicit Routing option gives the possibility to adjust the
+transition line. When you click the transition line, a dragging cross
+appears as bendpoint in the middle of the line. You can drag this
+bendpoint to another place on the canvas. While dragging a bendpoint, a
+new bendpoint is created for each of the two lines divided by this
+bendpoint. In this way you can create as many bendpoints you need.</p>
+<p class="image"><img src="images/mg-routing-explicit.png" alt="">
+<br>
+<strong>Figure:</strong> Transition with Explicit Routing Option</p>
+<h4>Moving several bendpoints</h4>
+<p>You can select several bendpoints and move them synchronously:</p>
+<ul>
+ <li>Hold the Crtl key and click on the bendpoints to be included
+ in the selection.</li>
+ <li>The color of the selected bendpoints will change to red.</li>
+ <li>To unselect a bendpoint click it again (still holding the Crtl
+ key). Its color will change back to black.</li>
+ <li>To unselect the whole selection click somewhere on the canvas.</li>
+ <li>To move the selected bendpoints pick one of them and drag it
+ to a desired position.</li>
+</ul>
+<p class="image"><img
+ src="images/mg-routing-explicit-move-bendpoints.png" alt=""> <br>
+<strong>Figure:</strong> Move Bendpoints</p>
+<h2>Cyclic Transitions</h2>
+<p>You can also create cyclic transitions. This means that an
+activity cycle involves repetitive execution of one or more activities
+until a condition is met.</p>
+<p>To create a cyclic transition between activities:</p>
+<ul>
+ <li>Open the activity properties dialog of the predecessor join
+ activity.</li>
+ <li>Change to <strong>Control Flow</strong> in the properties
+ menu and choose<strong> XOR</strong> as split behavior.</li>
+ <li>Then open the properties dialog of the subsequent split
+ activity and choose <strong>XOR</strong> as join control flow behavior.</li>
+ <li>Right-click the split symbol of the predecessor activity.</li>
+ <li>Select <strong>Connect</strong> in the context-menu.</li>
+ <li>Click the join symbol of the subsequent activity.</li>
+</ul>
+<p>&nbsp;</p>
+<p class="image"><a href="images/mg-defdesk-cyclic_orgSize.png"
+ target="_blank"> <img src="images/mg-defdesk-cyclic.png" alt=""></a>
+<br>
+<strong>Figure:</strong> Cyclic Transition</p>
+<p>In this example the last activity <tt>Start_Campaign</tt> is
+only instantiated if the data <strong>Status</strong> has the value 1
+(see also <a href="#transitionConditions">Specifying Transition
+Conditions</a> ) or else the process continues with <tt>Order Media</tt>.</p>
+<h2>Deleting Transitions and Transition Symbols</h2>
+<p>To delete a transition, use the option <strong>Delete</strong>
+in the transition's pop-up menu.</p>
+<p>To remove a transition symbol from the diagram, choose the
+option <strong>Delete Symbol</strong> in the transition's context menu.
+After this operation the transition between the two activities will
+still exist in the model.</p>
+<h3>Restore Transition Symbols</h3>
+<p>Having removed transition symbols, you can always restore them
+in your diagram:</p>
+<ul>
+ <li>Right-click your diagram canvas.</li>
+ <li>Choose the <strong>Reload Connections</strong> option in the
+ context menu.</li>
+ <li>In the upcoming <strong>Available Connections</strong> dialog
+ select the connections to restore.</li>
+</ul>
+<p class="image"><img src="images/mg-defdesk-75.png"
+ alt="Reload Connections"> <br>
+<strong>Figure:</strong> Reload Connections</p>
+<h2 id="conditions">Setting Transition Conditions</h2>
+<p>The properties of a transition are accessible in its properties dialog. To open
+this dialog, right-click the transition symbol in a model diagram and select the option <strong>Properties</strong>.</p>
+<p>Besides name and id the general properties of a transition include a condition
+type option, a condition expression field and a description. The
+<strong>Fork on traversal</strong> option of a transition controls
+the synchronicity and concurrency behavior during the execution of the corresponding
+process instances. Please refer to the section
+<a href="PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/handbooks/concepts/workflow-basics/mg-basics-13.htm#activityThread">
+Activity Thread</a> of the chapter
+<a href="PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/handbooks/concepts/workflow-basics/mg-basics-13.htm">
+Runtime Behavior</a> for detailed information on the <strong>Fork on Traversal</strong>
+functionality.</p>
+<p>You can set the <tt>View Fork on Traversal</tt> flag on the
+<a href="PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/handbooks/modelling/mg-preferences.html#drawing">Drawing Preferences</a> page
+to visualize how @productname@ Engine traverses during transition conditions.</p> <p>Please note if setting the ID, that IDs containing
+ hyphens, blanks or dots and IDs starting with digits are not supported.</p>
+
+<h3>Setting the Condition Type</h3>
+<p>In the <strong>Condition Type</strong> field you can select the types
+<tt>OTHERWISE</tt> or <tt>CONDITION</tt>:</p>
+<p class="image"><img src="images/transition-condition-type.png"
+ alt="Select the Condition Type."> <br>
+<strong>Figure:</strong> Select the Condition Type.</p>
+<p>Please note that switching between those types will remove transition
+conditions already entered.</p>
+<h4>CONDITION</h4>
+<p>The condition type <tt>CONDITION</tt> enables entering code in the <strong>
+Condition Expression</strong> editor. The return value of this expression will be
+checked to be <tt>true</tt>.</p>
+<h4>OTHERWISE</h4>
+<p>If the condition type <tt>OTHERWISE</tt> is selected, the transition
+is only evaluated to <tt>true</tt>, if all the other conditions on the split have
+the value <tt>false</tt>. The <strong>Condition Expression</strong> editor is
+disabled.</p>
+<h3 id="transitionConditions">Specifying Transition Conditions</h3>
+<p>In the <strong>Condition Expression</strong> field you can specify a condition. The transition
+is then only traversed and the next activity performed if this condition is fulfilled.</p>
+<p>Transition conditions are specified if the successor activity is only to be
+performed under particular circumstances. Please refer to the chapter <a
+ href="mg-basics-6.htm#transcond">Transition Conditions</a> of the Basics <a
+ href="mg-basics-6.htm">Control Flow</a> chapter for detailed information on the
+operators and variables that can be used in transition conditions.</p>
+<p>If the return value of a transition condition is <tt>true</tt>, the transition
+will always be traversed and the successor activity executed. To specify a transition
+condition, open the transition's properties dialog and enter a predicate in the
+<strong>Condition Expression</strong> field:</p>
+<p class="image"><img src="images/mg-defdesk-transition-cond.png"
+ alt="Setting a Transition Condition"> <br>
+<strong>Figure:</strong> Setting a Transition Condition</p>
+<p>In this example it will be checked whether the state of the SupportCaseData is
+neither closed nor rejected. The value is referenced via the dereferentiation path
+<tt>SupportCaseData.Product.State</tt>.</p>
+<p>A JavaScript based editor is provided, e.g. to add arithmetic, relational and
+logical operators as well as string matching operators.</p>
+<p>You can combine operators and values retrieved via dereferentiation paths with
+JavaScript language. Here are some examples for possible transition
+conditions:</p>
+<pre>Primitive.charAt(2)=="A"</pre>
+<pre>
+function toUpper(stringArg) {
+ return stringArg.toUpperCase();
+}
+
+Primitive == toUpper(SupportCaseData.Name)</pre>
+<pre>
+var id=0;
+for (var i = 0; i &lt; 10; i++) {
+ id = id*10 + i;
+}
+SupportCaseData.Id == id
+</pre>
+<p>Errors and warnings are indicated in a transition condition
+on the left side of the expression. A tooltip gives detailed information
+about the kind of error or warning.</p>
+<p class="image"><img src="images/trans-cond-error.png"
+ alt="Indicated Error in Transition Condition"> <br>
+<strong>Figure:</strong> Indicated Error in Transition Condition</p>
+<h4>Data proposal</h4>
+<p>Pressing <tt>Ctrl-Space</tt> in the transition condition editor
+provides you with a list to choose from all available
+data, e.g.:</p>
+<p class="image"><img src="images/tc-data-proposal.png"
+ alt="Default Proposals for Data."> <br>
+<strong>Figure:</strong> Default Proposals for Data.</p>
+<h4>Code completion</h4>
+<p>While typing the expression, you can press <tt>Ctrl-Space</tt> to
+show and choose from proposals for available methods:</p>
+<p class="image"><img src="images/tc-method-proposal.png"
+ alt="Default Proposals for Methods."> <br>
+<strong>Figure:</strong> Default Proposals for Methods.</p>
+<h4>Not indicated errors</h4>
+<p>Please be aware that no errors or warnings will be displayed in
+case you use an unsupported assignment to a @productname@ variable, because
+the validation of the JavaScript code is correct. For
+example, if you enter <tt>SupportCaseData.Product.State="R"</tt>
+instead of <tt>SupportCaseData.Product.State=="R"</tt>, there will be no
+warning and during the process an assignment instead a comparison will
+tried to be performed, which fails.</p>
+<h4>Undefined return values</h4>
+<p>In case the return value of a transition condition is undefined, for example
+when all code is commented out, the transition condition will be evaluated
+as <tt>TRUE</tt> at runtime.</p>
+
+<script language="JavaScript" type="text/javascript">
+<!--
+writeFooter();
+-->
+</script>
+</body>
+</html>
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/mg-defdesk-8.htm b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-data-flow.htm
index 500f464..837df20 100644
--- a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/mg-defdesk-8.htm
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-data-flow.htm
@@ -1,84 +1,84 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd"><HTML>
-<HEAD>
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../../styles/carnot.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE> Specifying Data Mappings</TITLE>
-<script language="JavaScript" src="../../styles/naviLine.js" type="text/javascript"></script>
-</head>
-<body>
-<script language="JavaScript">
-<!--
- writeNavigation("Modeling the Organizational Structure","PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/toc.html", "mg-defdesk-7.htm","mg-defdesk-10.htm", "../../toc.html","Business Analyst Handbooks", "mg-preface.htm","The Modeling Guide", "mg-modeler-preface.html","The Process Workbench");
- -->
-</script>
-
-<h1 >
- Data Mappings</h1>
-<p>In the diagram containing the activity and the data element you can map the data as the activity's input/output.</p>
-<h2 >
- Data Mapping Connection</h2>
-<P >
-After data mappings are created they render automatically in the <strong>Process Workbench</strong> as connections between the activity symbol and the data symbol. There is at most one data mapping connection between an activity and a data, summarizing all existing data mappings for them. The data mapping direction is indicated by arrows: </P>
-<UL>
-<LI >
-If there is an In data mapping to the activity the connection is labeled with an arrow to the activity.</LI>
-<LI >
-If there is an Outdata mapping to the data the connection is labelled with an arrow to the data.</LI>
-<LI >
-If there are data mappings for both directions, both arrows are drawn.</LI>
-</UL>
-<p class="image"><IMG SRC="images/mg-defdesk-29.png">
-<br><strong>Figure:</strong> An In Data Mapping Connection</p>
-<P >
-There is a shortcut to create a first data mapping between an activity and a data: in the diagram containing the activity and the data element you can map the data as the activity's input/output. To do this, proceed as follows:</P>
-<ul>
- <li>Right-click the data.</li>
- <li>Select <strong>Connect</strong> in the context menu.</li>
- <li>Click the activity.</li>
-</ul>
-<p class="image"><img SRC="images/mg-connect-data-mapping.png">
-<br><strong>Figure:</strong> Create a In Data Mapping</p>
-<p>An In data mapping is created, visualized by a data mapping connection.</p>
-<p>If you have created at least one link type with source type <strong>Data</strong> and
-target type <strong>Activity</strong>, you have the choice to select
-between these custom link types and the standard data mapping connection type. Please refer to chapter
- <a href="mg-defdesk-14.htm">Specifying Arbitrary Link Types</a> for information on custom
- link types.</p>
-<p class="image"><img SRC="images/mg-connect-data-mapping-select.png">
-<br><strong>Figure:</strong> Select the Link Type for Data Mapping</p>
-<P >To create an Out data mapping, this works the other way around:</p>
-<ul>
- <li>Right-click the activity first.</li>
- <li>Select <strong>Connect</strong> in the context menu.</li>
- <li>Click the data.</li>
-</ul>
-<p class="image"><img SRC="images/mg-connect-out-data-mapping.png">
-<br><strong>Figure:</strong> Create an Out Data Mapping</p>
-<p>In case of process interface context, please refer to the section
-<a href="PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/handbooks/modelling/mg-defdesk-8.htm#PI">Data Mappings in Process Interface Context
-</a> of the chapter <a href="PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/handbooks/modelling/mg-defdesk-8.htm">
-Data Mappings</a> in the <a
- href="PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/handbooks/handbooks.htm">Developers Handbook</a>.</p>
-
-<h2>
- Deleting Data Mappings</h2>
-
-<p>A data mapping can be deleted by</p>
-<UL>
-<li> selecting it in the diagram view and choosing <strong>Delete</strong> from the pop-up menu.
-To delete only the symbol, choose <strong>Delete Symbol </strong>or </li>
-<li>
-by selecting it in the data mapping properties pane of the activity's properties dialog and pressing the <strong>Delete</strong> button.
-</li>
-
-</UL>
-
-<script language="JavaScript">
-<!--
-writeFooter();
--->
-</script>
-</body>
-</html>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd"><HTML>
+<HEAD>
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
+<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
+
+<LINK REL="STYLESHEET" HREF="../../styles/carnot.css" CHARSET="ISO-8859-1" TYPE="text/css">
+<TITLE> Specifying Data Mappings</TITLE>
+<script language="JavaScript" src="../../styles/naviLine.js" type="text/javascript"></script>
+</head>
+<body>
+<script language="JavaScript">
+<!--
+ writeNavigation("Modeling the Organizational Structure","PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/toc.html", "mg-defdesk-7.htm","mg-defdesk-10.htm", "../../toc.html","Business Analyst Handbooks", "mg-preface.htm","The Modeling Guide", "mg-modeler-preface.html","The Process Workbench");
+ -->
+</script>
+
+<h1 >
+ Data Mappings</h1>
+<p>In the diagram containing the activity and the data element you can map the data as the activity's input/output.</p>
+<h2 >
+ Data Mapping Connection</h2>
+<P >
+After data mappings are created they render automatically in the <strong>Process Workbench</strong> as connections between the activity symbol and the data symbol. There is at most one data mapping connection between an activity and a data, summarizing all existing data mappings for them. The data mapping direction is indicated by arrows: </P>
+<UL>
+<LI >
+If there is an In data mapping to the activity the connection is labeled with an arrow to the activity.</LI>
+<LI >
+If there is an Outdata mapping to the data the connection is labelled with an arrow to the data.</LI>
+<LI >
+If there are data mappings for both directions, both arrows are drawn.</LI>
+</UL>
+<p class="image"><IMG SRC="images/mg-defdesk-29.png">
+<br><strong>Figure:</strong> An In Data Mapping Connection</p>
+<P >
+There is a shortcut to create a first data mapping between an activity and a data: in the diagram containing the activity and the data element you can map the data as the activity's input/output. To do this, proceed as follows:</P>
+<ul>
+ <li>Right-click the data.</li>
+ <li>Select <strong>Connect</strong> in the context menu.</li>
+ <li>Click the activity.</li>
+</ul>
+<p class="image"><img SRC="images/mg-connect-data-mapping.png">
+<br><strong>Figure:</strong> Create a In Data Mapping</p>
+<p>An In data mapping is created, visualized by a data mapping connection.</p>
+<p>If you have created at least one link type with source type <strong>Data</strong> and
+target type <strong>Activity</strong>, you have the choice to select
+between these custom link types and the standard data mapping connection type. Please refer to chapter
+ <a href="mg-defdesk-14.htm">Specifying Arbitrary Link Types</a> for information on custom
+ link types.</p>
+<p class="image"><img SRC="images/mg-connect-data-mapping-select.png">
+<br><strong>Figure:</strong> Select the Link Type for Data Mapping</p>
+<P >To create an Out data mapping, this works the other way around:</p>
+<ul>
+ <li>Right-click the activity first.</li>
+ <li>Select <strong>Connect</strong> in the context menu.</li>
+ <li>Click the data.</li>
+</ul>
+<p class="image"><img SRC="images/mg-connect-out-data-mapping.png">
+<br><strong>Figure:</strong> Create an Out Data Mapping</p>
+<p>In case of process interface context, please refer to the section
+<a href="PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/handbooks/modelling/mg-defdesk-8.htm#PI">Data Mappings in Process Interface Context
+</a> of the chapter <a href="PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/handbooks/modelling/mg-defdesk-8.htm">
+Data Mappings</a> in the <a
+ href="PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/handbooks/handbooks.htm">Developers Handbook</a>.</p>
+
+<h2>
+ Deleting Data Mappings</h2>
+
+<p>A data mapping can be deleted by</p>
+<UL>
+<li> selecting it in the diagram view and choosing <strong>Delete</strong> from the pop-up menu.
+To delete only the symbol, choose <strong>Delete Symbol </strong>or </li>
+<li>
+by selecting it in the data mapping properties pane of the activity's properties dialog and pressing the <strong>Delete</strong> button.
+</li>
+
+</UL>
+
+<script language="JavaScript">
+<!--
+writeFooter();
+-->
+</script>
+</body>
+</html>
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/mg-defdesk-7.htm b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-data.htm
index 267bbc8..3d649aa 100644
--- a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/mg-defdesk-7.htm
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-data.htm
@@ -1,93 +1,93 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-
-<link rel="STYLESHEET" href="../../styles/carnot.css" charset="ISO-8859-1" type="text/css">
-<title>Specifying Data</title>
-<script language="JavaScript" src="../../styles/naviLine.js" type="text/javascript"></script>
-</head>
-<body>
-<script language="JavaScript" type="text/javascript">
-<!--
- writeNavigation("Data Mappings","PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/toc.html",
- "mg-defdesk-6.htm","mg-defdesk-8.htm","../../toc.html","Business Analyst Handbooks",
- "mg-preface.htm","The Modeling Guide","mg-modeler-preface.html","The Process Workbench");
- -->
-</script>
-
-<h1>Specifying Data</h1>
-<p>Activities performed within the context of a business process may require data as
-their input or deliver data as output. This way activities manipulate workflow relevant
-data and transfer these data among themselves. The properties of these workflow data have
-to be defined in the model. For more details on workflow data refer to <a
- href="mg-basics-8.htm">Workflow Data</a>.</p>
-<p>This section will explain how to work with workflow data in the <strong>Process
-Workbench</strong>.</p>
-<p class="image"><img src="images/mg-defdesk-25.png" alt=""> <br>
-<strong>Figure:</strong> Representations of Data in the Outline View and Diagram of the
-Process Workbench</p>
-
-<h2>Creating Data</h2>
-<p>To create a data you can either:</p>
-<ul>
- <li>In the <a href="model-views/views-diagrams.html">diagram</a> toolbar palette
- select <strong>Data</strong> under <strong>Items</strong>. The data is created by
- subsequently clicking on the diagram canvas and will appear in the <a
- href="model-views/views-outline.html">Outline view</a>.</li>
-</ul>
-<p class="image"><img src="images/mg-create-data-1.png" alt=""> <br>
-<strong>Figure:</strong> Creating a Data Element</p>
-<ul>
- <li>Or in the <strong>Data </strong>section of the <strong>Outline</strong>
- view area, select <strong>New Data</strong> from the pop-up menu. The created data
- will appear in the <strong>Outline</strong> tree view and can be dragged to the
- diagram canvas.</li>
-</ul>
-<p class="image"><img src="images/mg-create-data.png" alt=""> <br>
-<strong>Figure:</strong> Creating a Data Element</p>
-
-<h2>Modifying Data</h2>
-<p>To modify a data, choose the data symbol in the <a
- href="model-views/views-outline.html">Outline view</a> tree or in a <a
- href="model-views/views-diagrams.html">diagram</a>. Then open the data properties
-dialog by double-clicking on it or by choosing <strong>Properties</strong> from the
-context menu.</p>
-<p>In the <strong>General</strong> page set the <strong>Name</strong> and <strong>ID</strong>
-of the data. Please note that IDs containing
-hyphens, blanks or dots and IDs starting with digits are not supported. To change the
-data type click the <strong>Data Type</strong> tab and select
-one of the suggested data types, like <tt>Text</tt>, <tt>Numeric</tt> or <tt>Complex
-Object</tt>.</p>
-<p class="image"><img src="images/mg-datatype.png" alt=""> <br>
-<strong>Figure:</strong> Setting Properties of a Data Element</p>
-<h3>Simulation</h3>
-<p>In this section you can specify simulation configurations, as described detailed in the chapter
- <a href="PLUGINS_ROOT/org.eclipse.stardust.docs.simulation/html/simulation/simulation-configurations.html">
- Simulation Configurations</a>
-of the
- <a href="PLUGINS_ROOT/org.eclipse.stardust.docs.simulation/html/simulation/toc.html">
- Developer Simulation Guide</a>.)
-<h3>Effort Planning</h3>
-<p>In this section you can set the following Process Effort properties:</p>
-<p class="image"><img src="images/data-prop-effort.png" alt=""> <br>
-<strong>Figure:</strong> Effort Planning Properties of an Data Element</p>
-<p>Please refer to the chapter <a href="process-effort-calculation.html">Project Effort Calculation</a> for
-detailed information on this functionality.</p>
-
-<h2>Deleting Data</h2>
-<p>To delete a data, use the option <strong>Delete</strong> in the data's pop-up
-menu in a <a href="model-views/views-diagrams.html">diagram</a> or in the <a
- href="model-views/views-outline.html">Outline view</a> tree area.</p>
-<p>To remove a data symbol from the diagram, choose the option <strong>Delete
-Symbol</strong> in the data's pop-up menu. After this operation the data and the data mappings
-between activities and the data will still be part of the model.</p>
-
-<script language="JavaScript" type="text/javascript">
-<!--
-writeFooter();
--->
-</script>
-</body>
-</html>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<meta http-equiv="Content-Style-Type" content="text/css">
+
+<link rel="STYLESHEET" href="../../styles/carnot.css" charset="ISO-8859-1" type="text/css">
+<title>Specifying Data</title>
+<script language="JavaScript" src="../../styles/naviLine.js" type="text/javascript"></script>
+</head>
+<body>
+<script language="JavaScript" type="text/javascript">
+<!--
+ writeNavigation("Data Mappings","PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/toc.html",
+ "mg-defdesk-6.htm","mg-defdesk-8.htm","../../toc.html","Business Analyst Handbooks",
+ "mg-preface.htm","The Modeling Guide","mg-modeler-preface.html","The Process Workbench");
+ -->
+</script>
+
+<h1>Specifying Data</h1>
+<p>Activities performed within the context of a business process may require data as
+their input or deliver data as output. This way activities manipulate workflow relevant
+data and transfer these data among themselves. The properties of these workflow data have
+to be defined in the model. For more details on workflow data refer to <a
+ href="mg-basics-8.htm">Workflow Data</a>.</p>
+<p>This section will explain how to work with workflow data in the <strong>Process
+Workbench</strong>.</p>
+<p class="image"><img src="images/mg-defdesk-25.png" alt=""> <br>
+<strong>Figure:</strong> Representations of Data in the Outline View and Diagram of the
+Process Workbench</p>
+
+<h2>Creating Data</h2>
+<p>To create a data you can either:</p>
+<ul>
+ <li>In the <a href="model-views/views-diagrams.html">diagram</a> toolbar palette
+ select <strong>Data</strong> under <strong>Items</strong>. The data is created by
+ subsequently clicking on the diagram canvas and will appear in the <a
+ href="model-views/views-outline.html">Outline view</a>.</li>
+</ul>
+<p class="image"><img src="images/mg-create-data-1.png" alt=""> <br>
+<strong>Figure:</strong> Creating a Data Element</p>
+<ul>
+ <li>Or in the <strong>Data </strong>section of the <strong>Outline</strong>
+ view area, select <strong>New Data</strong> from the pop-up menu. The created data
+ will appear in the <strong>Outline</strong> tree view and can be dragged to the
+ diagram canvas.</li>
+</ul>
+<p class="image"><img src="images/mg-create-data.png" alt=""> <br>
+<strong>Figure:</strong> Creating a Data Element</p>
+
+<h2>Modifying Data</h2>
+<p>To modify a data, choose the data symbol in the <a
+ href="model-views/views-outline.html">Outline view</a> tree or in a <a
+ href="model-views/views-diagrams.html">diagram</a>. Then open the data properties
+dialog by double-clicking on it or by choosing <strong>Properties</strong> from the
+context menu.</p>
+<p>In the <strong>General</strong> page set the <strong>Name</strong> and <strong>ID</strong>
+of the data. Please note that IDs containing
+hyphens, blanks or dots and IDs starting with digits are not supported. To change the
+data type click the <strong>Data Type</strong> tab and select
+one of the suggested data types, like <tt>Text</tt>, <tt>Numeric</tt> or <tt>Complex
+Object</tt>.</p>
+<p class="image"><img src="images/mg-datatype.png" alt=""> <br>
+<strong>Figure:</strong> Setting Properties of a Data Element</p>
+<h3>Simulation</h3>
+<p>In this section you can specify simulation configurations, as described detailed in the chapter
+ <a href="PLUGINS_ROOT/org.eclipse.stardust.docs.simulation/html/simulation/simulation-configurations.html">
+ Simulation Configurations</a>
+of the
+ <a href="PLUGINS_ROOT/org.eclipse.stardust.docs.simulation/html/simulation/toc.html">
+ Developer Simulation Guide</a>.)
+<h3>Effort Planning</h3>
+<p>In this section you can set the following Process Effort properties:</p>
+<p class="image"><img src="images/data-prop-effort.png" alt=""> <br>
+<strong>Figure:</strong> Effort Planning Properties of an Data Element</p>
+<p>Please refer to the chapter <a href="process-effort-calculation.html">Project Effort Calculation</a> for
+detailed information on this functionality.</p>
+
+<h2>Deleting Data</h2>
+<p>To delete a data, use the option <strong>Delete</strong> in the data's pop-up
+menu in a <a href="model-views/views-diagrams.html">diagram</a> or in the <a
+ href="model-views/views-outline.html">Outline view</a> tree area.</p>
+<p>To remove a data symbol from the diagram, choose the option <strong>Delete
+Symbol</strong> in the data's pop-up menu. After this operation the data and the data mappings
+between activities and the data will still be part of the model.</p>
+
+<script language="JavaScript" type="text/javascript">
+<!--
+writeFooter();
+-->
+</script>
+</body>
+</html>
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/pep-modeler-preface.html
index 54bc625..785e98e 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/pep-modeler-preface.html
@@ -1,51 +1,51 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../../styles/carnot.css" charset="ISO-8859-1"
- type="text/css">
-<title>The Process Workbench</title>
-<script language="JavaScript" src="../../styles/naviLine.js"
- type="text/javascript"></script>
-</head>
-<body>
-<script language="JavaScript" type="text/javascript">
-<!--
- writeNavigation("The Model File Format","PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/toc.html",
- "","mg-xml-1.htm",
- "../../toc.html","Business Analyst Handbooks",
- "mg-preface.htm","The Modeling Guide");
- -->
-</script>
-<h1>The Process Workbench</h1>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<meta http-equiv="Content-Style-Type" content="text/css">
+<link rel="STYLESHEET" href="../../styles/carnot.css" charset="ISO-8859-1"
+ type="text/css">
+<title>The Process Workbench</title>
+<script language="JavaScript" src="../../styles/naviLine.js"
+ type="text/javascript"></script>
+</head>
+<body>
+<script language="JavaScript" type="text/javascript">
+<!--
+ writeNavigation("The Model File Format","PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/toc.html",
+ "","mg-xml-1.htm",
+ "../../toc.html","Business Analyst Handbooks",
+ "mg-preface.htm","The Modeling Guide");
+ -->
+</script>
+<h1>The Process Workbench</h1>
<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 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
-process are provided as graphically represented building blocks.
-The role of a modeler is to put them together in a workflow diagram. Each building block
-is described by an element-specific set of properties and its relationships or
-connection to other elements of the process model. Both must be specified by modeler at build time.</p>
-
+ 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
+process are provided as graphically represented building blocks.
+The role of a modeler is to put them together in a workflow diagram. Each building block
+is described by an element-specific set of properties and its relationships or
+connection to other elements of the process model. Both must be specified by modeler at build time.</p>
+
+
+<p>For information about how to install @productname@, please refer to the chapter
+<a href="PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/handbooks/installation/ig-installer.htm">@productname@
+Installation</a> of the
+<a href="PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/handbooks/installation/ig-preface.htm">
+Developer Installation Guide</a>.</p>
-<p>For information about how to install @productname@, please refer to the chapter
-<a href="PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/handbooks/installation/ig-installer.htm">@productname@
-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 the Eclipse Modeler and the Business Process Modeler
</h2>
-
-<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,
+
+<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
-@productname@ Process Platform. However, some of the model elements are not supported in
-Business Process Modeling perspective. For those unsupported elements, you should use @productname@ Process Platform's
+@productname@. However, some of the model elements are not supported in
+Business Process Modeling perspective. For those unsupported elements, you should use @productname@'s
Eclipse-based modeler. </p>
<h3>Supported Elements</h3>
@@ -134,8 +134,9 @@ Eclipse-based modeler. </p>
-<h3>Unsupported Elements</h3>
-<p>Unsupported elements are displayed in My Process Models pane and Process Diagrams view but you
+<h3>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>
@@ -181,163 +182,163 @@ can only edit General Properties of these elements. </p>
<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>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>
- </tr>
- <tr>
- <td>Folder</td>
- <td>Data</td>
- </tr>
- <tr>
- <td>Folder List </td>
- <td>Data</td>
- </tr>
- <tr>
- <td>Entity Bean </td>
- <td>Data</td>
- </tr>
- <tr>
- <td>Hibernate Data</td>
- <td>Data</td>
- </tr>
- <tr>
- <td>XML Document </td>
- <td>Data</td>
- </tr>
- <tr>
- <td>Serializable Data </td>
- <td>Data </td>
- </tr>
- <tr>
- <td>DMS Application </td>
- <td>Application </td>
- </tr>
- <tr>
- <td>JMS Application </td>
- <td>Application</td>
- </tr>
- <tr>
- <td>Mail Application </td>
- <td>Application </td>
- </tr>
- <tr>
- <td>Message Parsing Application </td>
- <td>Application </td>
- </tr>
- <tr>
- <td>Message Serialization Application </td>
- <td>Application </td>
- </tr>
- <tr>
- <td>Plain Java Application </td>
- <td>Application </td>
- </tr>
- <tr>
- <td>Session Bean Application </td>
- <td>Application </td>
- </tr>
- <tr>
- <td>Spring Bean Application </td>
- <td>Application </td>
- </tr>
- <tr>
- <td>XSL Message Transformation Application </td>
- <td>Application</td>
- </tr>
- <tr>
- <td>External Web Application </td>
- <td>Application </td>
- </tr>
- <tr>
- <td>JFC Application </td>
- <td>Application </td>
- </tr>
- <tr>
- <td>JSF Application </td>
- <td>Application </td>
- </tr>
+<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>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>
+ </tr>
+ <tr>
+ <td>Folder</td>
+ <td>Data</td>
+ </tr>
+ <tr>
+ <td>Folder List </td>
+ <td>Data</td>
+ </tr>
+ <tr>
+ <td>Entity Bean </td>
+ <td>Data</td>
+ </tr>
+ <tr>
+ <td>Hibernate Data</td>
+ <td>Data</td>
+ </tr>
+ <tr>
+ <td>XML Document </td>
+ <td>Data</td>
+ </tr>
+ <tr>
+ <td>Serializable Data </td>
+ <td>Data </td>
+ </tr>
+ <tr>
+ <td>DMS Application </td>
+ <td>Application </td>
+ </tr>
+ <tr>
+ <td>JMS Application </td>
+ <td>Application</td>
+ </tr>
+ <tr>
+ <td>Mail Application </td>
+ <td>Application </td>
+ </tr>
+ <tr>
+ <td>Message Parsing Application </td>
+ <td>Application </td>
+ </tr>
+ <tr>
+ <td>Message Serialization Application </td>
+ <td>Application </td>
+ </tr>
+ <tr>
+ <td>Plain Java Application </td>
+ <td>Application </td>
+ </tr>
+ <tr>
+ <td>Session Bean Application </td>
+ <td>Application </td>
+ </tr>
+ <tr>
+ <td>Spring Bean Application </td>
+ <td>Application </td>
+ </tr>
+ <tr>
+ <td>XSL Message Transformation Application </td>
+ <td>Application</td>
+ </tr>
+ <tr>
+ <td>External Web Application </td>
+ <td>Application </td>
+ </tr>
+ <tr>
+ <td>JFC Application </td>
+ <td>Application </td>
+ </tr>
+ <tr>
+ <td>JSF Application </td>
+ <td>Application </td>
+ </tr>
+
-
-</table>
-
+</table>
+
<!--
-
-<h2>Content</h2>
-<ul>
- <li><a href="mg-preferences.html">Setting @productname@ Preferences</a></li>
- <li class="expand" onclick="openClose(this, 'persp')">
- <a href="mg-modeler-views.html">The Analyst Perspective</a>
- <li class="noicon" id="persp" style="display: none;">
- <ul>
- <li><a href="model-views/views-outline.html">Outline view</a></li>
- <li><a href="model-views/views-diagrams.html">Working with Diagrams</a></li>
- <li><a href="model-views/views-cheat.html">Cheat Sheet View</a></li>
- <li><a href="model-views/views-repository.html">@productnameonly@ Process Model Repository</a></li>
- <li><a href="model-views/views-bookmark.html">@productnameonly@ Process Model Bookmarks</a></li>
- <li><a href="model-views/views-traversal.html">@productnameonly@ Process Model Traversal</a></li>
- <li><a href="model-views/views-simplify.html">Simplifying the Modeler View</a></li>
- </ul></li>
- <li class="expand" onclick="openClose(this, 'model')">
- <a href="models/model-preface.html">Working with Models</a></li>
- <li class="noicon" id="model" style="display: none;">
- <ul>
- <li><a href="models/model-upgrade.html">Model Upgrade</a></li>
- <li><a href="models/model-handling.html">Creating and Deleting Models</a></li>
- <li><a href="models/model-props.html">Model Properties</a></li>
- <li><a href="models/model-validation.html">Workflow Model Validation</a></li>
- <li><a href="models/model-import.html">Importing and Exporting Models</a>
- <li><a href="models/model-element-refs.html">Element References</a></li>
- <li><a href="models/model-clean.html">Cleaning Up Models</a></li>
- </ul></li>
- <li><a href="mg-defdesk-3.htm">Working with Process Definitions</a></li>
- <li><a href="mg-defdesk-4.htm">Specifying Activities</a></li>
- <li><a href="mg-defdesk-5.htm">Working with Transitions</a></li>
- <li><a href="mg-defdesk-6.htm">Specifying Applications</a></li>
- <li><a href="mg-defdesk-7.htm">Specifying Data</a></li>
- <li><a href="mg-defdesk-8.htm">Specifying Data Mappings</a></li>
- <li><a href="mg-defdesk-10.htm">Modeling the Organizational
- Structure</a></li>
- <li><a href="mg-defdesk-14.htm">Specifying Arbitrary Link Types</a></li>
- <li><a href="mg-defdesk-15.htm">Using Annotations</a></li>
- <li><a href="mg-pools-lanes.htm">Pools and Lanes Usage</a></li>
- <li><a href="mg-copy-paste-elements.html">Copying and Pasting
- Modeled Elements</a></li>
- <li><a href="property-page-authorization.html">Property Page
- Authorization</a></li>
- <li><a href="process-effort-calculation.html">Project Effort
- Calculation</a></li>
- <li><a href="pattern-support.html">Modeling Pattern Support</a></li>
- <li><a href="mg-defdesk-16.htm">Retrieving Diagrams from Model
- Information</a></li>
- <li><a href="mg-modelreport.htm">Process Model Report</a></li>
- <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>
+
+<h2>Content</h2>
+<ul>
+ <li><a href="mg-preferences.html">Setting @productname@ Preferences</a></li>
+ <li class="expand" onclick="openClose(this, 'persp')">
+ <a href="mg-modeler-views.html">The Analyst Perspective</a>
+ <li class="noicon" id="persp" style="display: none;">
+ <ul>
+ <li><a href="model-views/views-outline.html">Outline view</a></li>
+ <li><a href="model-views/views-diagrams.html">Working with Diagrams</a></li>
+ <li><a href="model-views/views-cheat.html">Cheat Sheet View</a></li>
+ <li><a href="model-views/views-repository.html">@productnameonly@ Process Model Repository</a></li>
+ <li><a href="model-views/views-bookmark.html">@productnameonly@ Process Model Bookmarks</a></li>
+ <li><a href="model-views/views-traversal.html">@productnameonly@ Process Model Traversal</a></li>
+ <li><a href="model-views/views-simplify.html">Simplifying the Modeler View</a></li>
+ </ul></li>
+ <li class="expand" onclick="openClose(this, 'model')">
+ <a href="models/model-preface.html">Working with Models</a></li>
+ <li class="noicon" id="model" style="display: none;">
+ <ul>
+ <li><a href="models/model-upgrade.html">Model Upgrade</a></li>
+ <li><a href="models/model-handling.html">Creating and Deleting Models</a></li>
+ <li><a href="models/model-props.html">Model Properties</a></li>
+ <li><a href="models/model-validation.html">Workflow Model Validation</a></li>
+ <li><a href="models/model-import.html">Importing and Exporting Models</a>
+ <li><a href="models/model-element-refs.html">Element References</a></li>
+ <li><a href="models/model-clean.html">Cleaning Up Models</a></li>
+ </ul></li>
+ <li><a href="mg-defdesk-3.htm">Working with Process Definitions</a></li>
+ <li><a href="mg-defdesk-4.htm">Specifying Activities</a></li>
+ <li><a href="mg-defdesk-5.htm">Working with Transitions</a></li>
+ <li><a href="mg-defdesk-6.htm">Specifying Applications</a></li>
+ <li><a href="mg-defdesk-7.htm">Specifying Data</a></li>
+ <li><a href="mg-defdesk-8.htm">Specifying Data Mappings</a></li>
+ <li><a href="mg-defdesk-10.htm">Modeling the Organizational
+ Structure</a></li>
+ <li><a href="mg-defdesk-14.htm">Specifying Arbitrary Link Types</a></li>
+ <li><a href="mg-defdesk-15.htm">Using Annotations</a></li>
+ <li><a href="mg-pools-lanes.htm">Pools and Lanes Usage</a></li>
+ <li><a href="mg-copy-paste-elements.html">Copying and Pasting
+ Modeled Elements</a></li>
+ <li><a href="property-page-authorization.html">Property Page
+ Authorization</a></li>
+ <li><a href="process-effort-calculation.html">Project Effort
+ Calculation</a></li>
+ <li><a href="pattern-support.html">Modeling Pattern Support</a></li>
+ <li><a href="mg-defdesk-16.htm">Retrieving Diagrams from Model
+ Information</a></li>
+ <li><a href="mg-modelreport.htm">Process Model Report</a></li>
+ <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> -->
-<script language="JavaScript" type="text/javascript">
-<!--
-writeFooter();
--->
-</script>
-</body>
-</html>
+<script language="JavaScript" type="text/javascript">
+<!--
+writeFooter();
+-->
+</script>
+</body>
+</html>
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/mg-defdesk-10.htm b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-org-struct.htm
index 7db6fa4..5aa58ec 100644
--- a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/mg-defdesk-10.htm
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-org-struct.htm
@@ -1,535 +1,535 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-
-<link rel="STYLESHEET" href="../../styles/carnot.css" charset="ISO-8859-1" type="text/css">
-<title>Modeling the Organizational Structure</title>
-<script language="JavaScript" src="../../styles/naviLine.js" type="text/javascript"></script>
-</head>
-<body>
-<script language="JavaScript" type="text/javascript">
-<!--
- writeNavigation("Specifying Arbitrary Link Types","PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/toc.html",
- "mg-defdesk-8.htm","mg-defdesk-14.htm",
- "../../toc.html","Business Analyst Handbooks",
- "mg-preface.htm","The Modeling Guide",
- "mg-modeler-preface.html","The Process Workbench");
- -->
-</script>
-<h1>Modeling the Organizational Structure</h1>
-<p>Interactive Activities are assigned to participants - roles or organizations.
-Users assigned to these roles or organizations perform the work represented by an activity
-instance. Being assigned one or more activity instances, a user can perform these
-activities by completing the work items in his worklist.</p>
-<p>Hence, there is a distinction between</p>
-<ul>
- <li>roles and organizations, which are visible both in the modeling as well as
- in the runtime environment,</li>
- <li>users who are visible only in the runtime environment and</li>
- <li>modelers who are visible only in the modeling environment.</li>
-</ul>
-<p>Consequently, in your modeling environment you use roles and organizations.
-Individual human performers are created and assigned to these roles only in the
-<a href="PLUGINS_ROOT/org.eclipse.stardust.docs.enduser/html/handbooks/execution-clients/carnot-clients.html">
-@productname@ Portal</a>, the
-<a href="PLUGINS_ROOT/org.eclipse.stardust.docs.enduser/html/handbooks/swing-portal/swing-portal.html">
-@productname@ Swing Portal</a>, console administration tools or via embedding application.</p>
-<p>The following sections describe the usage of participants in
-the Process workbench:</p>
-<ul>
- <li><a href="#rep">Representation in the Process Workbench</a></li>
- <li><a href="#org">Organizations</a></li>
- <li><a href="#role">Roles</a></li>
- <li><a href="#condPerformers">Conditional Performers</a></li>
- <li><a href="#associate">Establishing Associations between Organizational Elements</a></li>
-</ul>
-<h3>Participant IDs</h3>
-<p>Please note that IDs containing hyphens, blanks or dots and IDs starting with
-digits are not supported.</p>
-<p>IDs for participants have to be unique within all model participants like roles, organizations
-or conditional performer. When trying to add a duplicate ID, this is indicated in
-the participant properties page:</p>
-<p class="image"><img src="images/error-duplicate-id-prop.png" alt=""> <br>
-<strong>Figure:</strong> Duplicate ID indicated in Properties Page.</p>
-<p>The <strong>Problems View</strong> also shows the following error entry:</p>
-<p class="image"><img src="images/error-duplicate-id-org.png" alt=""> <br>
-<strong>Figure:</strong> Duplicate ID indicated in Problems View.</p>
-
-<h2 id="rep">Representation in the Process Workbench</h2>
-<p>In the <strong>Process Workbench</strong>, a participant may be represented,
-depending on the type of resource, by one of the symbols:</p>
-<ul>
- <li><img class="noborder" src="images/role-icon.png" alt=""> - Role</li>
- <li><img class="noborder" src="images/cond-perf-icon.png" alt=""> - Conditional Performer</li>
- <li><img class="noborder" src="images/organization-icon.png" alt=""> - Organization</li>
-</ul>
-<p>Participants are represented in the Outline view as in the following
-figure:</p>
-<p class="image"><img src="images/participants-outline.png" alt=""> <br>
-<strong>Figure:</strong> Representations of Participants in the Outline View</p>
-<p>In diagram, participants are represented as displayed in the following
-figure:</p>
-<p class="image"><img src="images/participants-diagram.png" alt=""> <br>
-<strong>Figure:</strong> Participants represented in a Diagram.</p>
-
-<h2 id="org">Organizations</h2>
-<p>An organization element represents a group of resources. For example, a department or any organizational unit.
-This section describes which properties are provided and how to work with organization elements in the modeler.</p>
-<h3>Creating and Deleting Organizations</h3>
-<p>To create an organization you can either:</p>
-<ul>
- <li>Select <strong>Participants</strong> in the diagram <a
- href="model-views/views-diagrams.html#toolbarPalette">toolbar palette</a> and from the
- pop-up menu <strong>Organization</strong>. Then move the cursor to the diagram canvas
- to place the organization symbol there. The organization is created by subsequently
- clicking on the canvas.</li>
- <li>In the <strong>Participants</strong> section of the <a
- href="model-views/views-outline.html">Outline view</a> area, select <strong>New
- &gt; New Organization</strong> from the pop-up menu. The created organization will appear in
- the tree view.</li>
- <li>Or in the <strong>Outline</strong> view, select the model and from its pop-up
- menu <strong>New Participant &gt; New Organization</strong>.</li>
-</ul>
-<p>When deleting organizations, you must make a distinction between deleting an
-organization from the model information or only deleting a symbol from a diagram. To do
-the first - delete an organization from the model - you proceed as follows:</p>
-<ul>
- <li>Having selected the symbol of the organization in the <strong>Participants</strong>
- tree of the <strong>Outline</strong> view, choose the option <strong>Delete</strong>
- in the pop-up menu of this organization.</li>
- <li>Having selected the symbol of the organization in a diagram, choose the
- option <strong>Delete </strong> in the pop-up menu of this organization.</li>
-</ul>
-<p>The option <strong>Delete Symbol</strong> in the pop-up menu called from within
-the diagram canvas will only remove the organization symbol from the diagram.</p>
-<h3>General Properties</h3>
-<p>The <strong>General</strong> properties entry contains:</p>
-<ul>
- <li>ID - please note that the ID has to be unique within all model participants. IDs containing
- hyphens, blanks or dots and IDs starting with digits are not supported.</li>
- <li>Name</li>
- <li>Internationalization</li>
-</ul>
-<h3 id="binding">Department Binding</h3>
-<p>It is possible for organizations to add a department scope which is
-evaluated at runtime. This department scope is described as a data path
- to process data which returns a scope key to identify a department representing
- this scope.</p>
-<p>In the <strong>Department Binding</strong> section you can determine
-that the organization is allowed to support departments by enabling the checkbox
-<strong>Organization supports departments.</strong>.</p>
-<p class="image"><img src="images/mg-org-prop-binding.png" alt="Runtime Binding">
-<br>
-<strong>Figure:</strong> Department Binding</p>
-<p>Once the checkbox is enabled, a new field opens, where you can enter
-data for the department OID. It is possible to select one of the following
-two data types:</p>
-<ul>
- <li>a primitive data of type <tt>String</tt> without access path.
- <p class="image"><img src="images/mg-org-prop-depart-2.png" alt=""></p></li>
- <li>a structured data and an access path evaluating to String.
- <p class="note"><strong>Note</strong><br>
- the data path should be an element (type String) of the structured data and not be using
- methods as dereferentiation path.</p>
- <p class="image"><img src="images/mg-org-prop-depart-1.png" alt=""></p></li>
-</ul>
-<h3 id="contrOrg">Controlling Parameters for Organizations</h3>
-<p>The following controlling parameter is provided for organizations:</p>
-<ul>
- <li><strong>Cost Center</strong></li>
-</ul>
-<p class="image"><img src="images/org-controlling.png"
-alt="Organization Controlling Parameter"><br>
-<strong>Figure:</strong> Organization Controlling Parameter</p>
-<h3 id="task">Task Assignment</h3>
-<p>In the properties dialog of the organization you can choose how the task assignment
-is performed:</p>
-<ul>
- <li>Select <strong>Task Assignment</strong> in the properties dialog.</li>
- <li>Choose the mode for task assigment. You have the choice of <tt>Choose
- Assignment</tt> or <tt>Assign Automatically</tt>.</li>
-</ul>
-<p class="image"><img src="images/mg-task-assignment-org.png" alt="Task Assignment">
-<br>
-<strong>Figure:</strong> Task Assignment of an Organization</p>
-<h3>Simulation</h3>
-<p>In this section you can specify simulation configurations, as described detailed in the chapter
- <a href="PLUGINS_ROOT/org.eclipse.stardust.docs.simulation/html/simulation/simulation-configurations.html">
- Simulation Configurations</a>
-of the
- <a href="PLUGINS_ROOT/org.eclipse.stardust.docs.simulation/html/simulation/toc.html">
- @productname@ Developer Simulation Guide</a>.)</p>
-<h3>Effort Planning</h3>
-<p>In this section you can set the organization complexity for project effort calculation:</p>
-<p class="image"><img src="images/organization-prop-effort.png" alt=""> <br>
-<strong>Figure:</strong> Effort Planning Property of an Organization</p>
-<p>Please refer to the chapter <a href="process-effort-calculation.html">Project Effort Calculation</a> for
-detailed information on this functionality.</p>
-<h2 id="role">Roles</h2>
-
-<p>A role denotes the responsibility assigned to the participants. Following
-sections provide information on how to work with roles.</p>
-
-
-<h3>Creating and Deleting Roles</h3>
-<p>To create a role you can either:</p>
-<ul>
- <li>Select <strong>Participants</strong> in the diagram <a
- href="model-views/views-diagrams.html#toolbarPalette">toolbar palette</a> and from the
- pop-up menu <strong>Role</strong>. Then move the cursor to the diagram canvas to place
- the role symbol there. The role is created by subsequently clicking on the canvas.</li>
- <li>In the <strong>Participants</strong> section of the <a
- href="model-views/views-outline.html">Outline view</a> area, select <strong>New
- &gt; New Role</strong> from the pop-up menu. The created role will appear in the tree view.</li>
- <li>Or in the <strong>Outline</strong> view, select the model and from its pop-up
- menu <strong>New Participant &gt; New Role</strong>.</li>
-</ul>
-<p>When deleting roles you must make a distinction between deleting a role from the
-model information or only deleting a symbol from a diagram. To do the first - delete a
-role from the model - you proceed as follows:</p>
-<ul>
- <li>Having selected the symbol of the role in the <strong>Participants</strong>
- tree of the Outline view, choose the option <strong>Delete </strong> in the pop-up
- menu of this role.</li>
- <li>Having selected the symbol of the role in a diagram, choose the option <strong>Delete
- </strong> in the pop-up menu of this role.</li>
-</ul>
-<p>The option <strong>Delete Symbol </strong> in the pop-up menu called from within
-the diagram canvas will only remove the role symbol from the diagram.</p>
-<h3>General Properties</h3>
-<p>The <strong>General</strong> properties entry contains:</p>
-<ul>
- <li>ID - please note that the ID has to be unique within all model participants. IDs containing
- hyphens, blanks or dots and IDs starting with digits are not supported.</li>
- <li>Name</li>
- <li>Internationalization</li>
- <li>Cardinality</li>
-</ul>
-<h4 id="cardinality">Cardinality</h4>
-<p>You can define the cardinality of roles in the properties dialog. Type in the
-maximum users that can be assigned to this role in the <strong>Cardinality</strong> entry
-field.</p>
-<p class="image"><img src="images/mg-role-cardinality.png" alt="Cardinality"> <br>
-<strong>Figure:</strong> Setting the Cardinality<br /></p>
-<h3 id="contrRole">Controlling Parameters for Roles</h3>
-<p>The following controlling parameters are provided for roles:</p>
-<ul>
- <li><strong>Working Weeks Per Year:</strong> number of working weeks per year.</li>
- <li><strong>Actual Cost Per Minute:</strong> actual cost per minute.</li>
- <li><strong>Target (System) Worktime Per Day:</strong> target system worktime
- per day in minutes.</li>
- <li><strong>Target Worktime Per Week:</strong> target worktime per week in
- hours.</li>
- <li><strong>Target Queue Depth:</strong></li>
-</ul>
-<p class="image"><img src="images/role-controlling.png"
- alt="Controlling Parameters for Roles"> <br>
-<strong>Figure:</strong> Controlling Parameters for Roles</p>
-<h3>Task Assignment</h3>
-<p>In the properties dialog of the role you can choose how the task assignment is
-performed:</p>
-<ul>
- <li>Select <strong>Task Assignment</strong> in the properties dialog.</li>
- <li>Choose the mode for task assigment. You have the choice of <tt>Choose
- Assignment</tt> or <tt>Assign Automatically</tt>.</li>
-</ul>
-<p class="image"><img src="images/mg-task-assignment.png" alt="Task Assignment">
-<br>
-<strong>Figure:</strong> Task Assignment of a Role</p>
-
-<h3>Simulation</h3>
-<p>In this section you can specify simulation configurations, as described detailed in the chapter
- <a href="PLUGINS_ROOT/org.eclipse.stardust.docs.simulation/html/simulation/simulation-configurations.html">
- Simulation Configurations</a>
-of the
- <a href="PLUGINS_ROOT/org.eclipse.stardust.docs.simulation/html/simulation/toc.html">
- Developer Simulation Guide</a>.)</p>
-<h3>Effort Planning</h3>
-<p>In this section you can set the role complexity for project effort calculation:</p>
-<p class="image"><img src="images/role-prop-effort.png" alt=""> <br>
-<strong>Figure:</strong> Effort Planning Property of a Role</p>
-<p>Please refer to the chapter <a href="process-effort-calculation.html">Project Effort Calculation</a> for
-detailed information on this functionality.</p>
-<h2 id="condPerformers">Conditional Performers</h2>
-<p>The conditional performer is evaluated at runtime and it determines the identity of the actual performer.
-The following sections help you to work with conditional performers.</p>
-<h3>Creating and Deleting Conditional Performers</h3>
-<p>To create a conditional performer you can either:</p>
-<ul>
- <li>Select <strong>Participants</strong> in the diagram <a
- href="model-views/views-diagrams.html#toolbarPalette">toolbar palette</a> and from the
- pop-up menu <strong>Conditional Performer</strong>. Then move the cursor to the
- diagram canvas to place the symbol for the conditional performer there. The
- conditional performer is created by subsequently clicking on the canvas.</li>
- <li>In the Participants section of the <a
- href="model-views/views-outline.html">Outline view</a> area, select <strong>New
- &gt; New Conditional Performer </strong>from the pop-up menu. The created conditional performer
- will appear in the tree view.</li>
- <li>Or in the Outline view, select the model and from its pop-up menu <strong>New
- Participant &gt; New Conditional Performer.</strong></li>
-</ul>
-<p>As described in the chapter <a href="mg-basics-9.htm">Participants and Users</a>,
-the <a href="PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/handbooks/others/glossary.html#oid">OID</a> or respectively
-<a href="PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/handbooks/others/glossary.html#id">ID</a>
-of the performer assigned dynamically at runtime is passed to
-the @productname@ resource.</p>
-
-<h3>Runtime Binding</h3>
-<p>Among the conditional performer's properties, there is also the distinction
-between an individual user of the runtime environment and a performer defined in the
-modeling environment (corresponding to a role or organization) used as a conditional
-performer. This distinction has to be made in the same properties dialog. Click <strong>Runtime
-Binding</strong> to define the performer as a user, organization/role or user group and choose the
-data and optional data path to provide the performer's identity.</p>
-<p>In the <strong>Kind</strong> drop-down list, define the performer as one
-of the following:</p>
-<ul>
- <li>User</li>
- <li>Organization/Role</li>
- <li>User Group</li>
- <li>Organization/Role or User Group</li>
-</ul>
-<p class="image"><img
- src="images/mg-performer-props.png" alt=""><br>
-<strong>Figure:</strong> Specifying a Conditional Performer</p>
-<h4>Oid/Id</h4>
-<p>In the <strong>OID/Id</strong> section, choose the data and data path providing
-the performer identity.</p>
-<p class="image"><img src="images/mg-org-cond-perf-oid.png"
- alt="Conditional Performer Properties"><br>
-<strong>Figure:</strong> Conditional Performer</p>
-
-<p class="note"><strong>Note</strong><br>In case the data is of type <strong>Long</strong>, the value is used to identify the
-OID of the performer, as thus it refers to a user. If the data is of type <strong>String</strong>,
-the value is used to identify the Id of the performer, as this has to be a role in that case.</p>
-<h4>User Realm</h4>
-<p>If the conditional performer is defined as a user, an additional field appears to
-fill in the users
-<a href="PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/handbooks/concepts/admin-concepts/ag-multipartition.htm#realm">
-realm</a> data.</p>
-<p class="image"><img src="images/mg-performer-props-realm.png" alt=""><br>
-<strong>Figure:</strong> Specifying a Conditional Performer as User</p>
-<h4>Using the Last Activity Performer data</h4>
-<p>The <strong>Last Activity Performer</strong> data usage determines that the
-performer is used as a computed value. The algorithm for a specific process
-instance is as follows:</p>
-<ol>
- <li>Select all <tt>COMPLETED</tt> activity instances belonging
- to the specific process instance, ordered descending by the last modification time.</li>
- <li>Traverse the result and select the first interactive activity instance.</li>
- <li>Return the user of that activity.</li>
-</ol>
-<p class="note"><strong>Note</strong><br>
-Please note that in case the activity is the first activity in the work flow,
-there would be no <strong>Last Activity Performer</strong>.
-If an activity other than the first one is unable to retrieve
-the last activity performer due to the transaction isolation level <tt>COMMITMENT</tt>,
-set in the database, enable the <strong>Fork on traversal</strong> flag in the
-transition between the current and the last activities.
-Please refer to the section <a href="mg-basics-13.htm#activityThread">Activity Thread</a> of the
-chapter <a href="mg-basics-13.htm">Runtime Behavior</a> for detailed
-information on the <strong>Fork on Traversal</strong>
-functionality.</p>
-<h3>Simulation</h3>
-<p>In this section you can specify simulation configurations, as described detailed in the chapter
- <a href="PLUGINS_ROOT/org.eclipse.stardust.docs.simulation/html/simulation/simulation-configurations.html">
- Simulation Configurations</a>
-of the
- <a href="PLUGINS_ROOT/org.eclipse.stardust.docs.simulation/html/simulation/toc.html">
- Developer Simulation Guide</a>.</p>
-<h3>Effort Planning</h3>
-<p>In this section you can set the performer complexity for project effort calculation:</p>
-<p class="image"><img src="images/performer-prop-effort.png" alt=""> <br>
-<strong>Figure:</strong> Effort Planning Property of a Conditional Performer</p>
-<p>Please refer to the chapter <a href="process-effort-calculation.html">Project Effort Calculation</a> for
-detailed information on this functionality.</p>
-<h3>Deleting Conditional Performers</h3>
-<p>When deleting conditional performers, you must make a distinction between deleting
-a conditional performer from the model information or only deleting a symbol from a
-diagram. To do the first - delete a conditional performer from the model - you proceed as
-follows:</p>
-<ul>
- <li>Having selected the symbol of the conditional performer in the <strong>Participants</strong>
- tree of the <a href="model-views/views-outline.html">Outline view</a>, choose the
- option <strong>Delete </strong> in the pop-up menu of this conditional performer.</li>
- <li>Having selected the symbol of the conditional performer in a diagram,
- choose the option <strong>Delete</strong> in the pop-up menu of this
- conditional performer.</li>
-</ul>
-<p>The option <strong>Delete Symbol </strong> in the pop-up menu called from within
-the diagram canvas will only remove the symbol for the conditional performer from the
-diagram.</p>
-<h2 id="associate">Establishing Associations between Organizational Elements</h2>
-<p>Organizations are groups of human resources. Consequently, they may contain
-individual roles or subordinate organizations. Like process definitions, organizational
-hierarchies can be modeled in the @productname@ Workbench with the help of diagrams.</p>
-<p>To model your organizations, use either diagrams bound to a process definition or
-model diagrams. A prerequisite for establishing relationships between an organization and
-its members is the existence of these elements: an organization and all its members (roles
-or smaller organizational units). Proceed as follows:</p>
-<ul>
- <li>Place the organization symbol and the symbol representing a member of this
- organization (e.g. a role or another organization) in a diagram.</li>
- <li>Right-click the symbol representing a member.</li>
- <li>Select <strong>Connect</strong> in the context menu.</li>
- <li>Click the organization the member is going to belong to.</li>
-</ul>
-<p class="image"><img src="images/mg-connect-organizations.png" alt=""> <br>
-<strong>Figure:</strong> Making an Organization Part of Another</p>
-<p>To add further members to the organization, repeat these operations for each
-member. An example of an organizational hierarchy diagram is shown below.</p>
-<p class="image"><img src="images/organizational-diagram.png" alt=""> <br>
-<strong>Figure:</strong> A Sample Organizational Diagram</p>
-<h3>Restrictions on Associations</h3>
-<p>The following sections describes the restrictions on associations between organizational elements.</p>
-<h4>Only one relationship to other participants supported</h4>
-<p>Please note that a model participant can only have one relationship like
-<strong>Work For</strong> or <strong>Manager of</strong> to other
-participants. Otherwise the model validation fails and the
-following error message appears in the <strong>Problems</strong>
-view:</p>
-<p class="image"><img src="images/work-for-error-problem-view.png" alt="Problems View"> <br>
-<strong>Figure:</strong> Error indicated in Problems View</p>
-<h4>Only one relationship to other organizations supported</h4>
-<p>An organization should not be part of more than one other organization. Otherwise
-the model validation fails and the
-following error message appears in the <strong>Problems</strong>
-view:</p>
-<p class="image"><img src="images/part-of-error-problem-view.png" alt="Problems View"> <br>
-<strong>Figure:</strong> Error indicated in Problems View</p>
-<h4>Administrator Role cannot be connected</h4>
-<p>Since @productname@ version 5.2. and later, it is not possible
-to connect the <strong>Administrator</strong> role to any
-organization. In case models with @productname@ versions older than 5.2 contain
-such a connection, an error message in the <strong>Problems</strong> view
-indicates this in the following way:</p>
-<p class="image"><img src="images/admin-error-problem-view.png" alt="Problems View"> <br>
-<strong>Figure:</strong> Administrator Assignment Error in Problems View</p>
-<h3 id="scope">Behavior of Scoped Organizations</h3>
-
-<p>Infinilty Platform supoports scoping of roles, orgnizations and departments.
-The following sections describes what happens when the organizations are scoped.</p>
-
-<ul>
- <li><a href="#implicit">Implicitly Scoped Roles</a></li>
- <li><a href="#hierScop">Organizational Hierarchies and Target Departments</a></li>
- <li><a href="#matrix">Matrix Organizations</a></li>
- <li><a href="#deploy">Deployment Restrictions</a></li>
-</ul>
-<h4 id="implicit">Implicitly Scoped Roles</h4>
-<p>Roles are implicitly scoped via the next scoped Organization above.</p>
-<p>When a User is assigned to an (implicitly) scoped Role, the Role
-and the departments for all organizations, the Role has a "Works For" or "Is Manager Of"
-relationship, have to be specified.</p>
-<h4 id="hierScop">Organizational Hierarchies and Target Departments</h4>
-<p>All Organizations and Roles underneath a scoped Organization inherit
-the target departments of this Organization, as long as the suborganization does not define
-a new target department. Hence, for every participant the relevant target department is the scope of the
-next scoped Organization upwards the organizational hierarchy.</p>
-<h4 id="matrix">Matrix Organizations</h4>
-<p>@productname@ only allows pure tree structures for
-organizational hierarchies. Neither Roles nor Organizations may be assigned
-to more than one Organization. Matrix structures can be mapped by disjoint
-organizational structures with possibly different scopes (e.g. branch vs. project),
-whereby users might be assigned to Roles in both structures.</p>
-
-<h4>Matrix Organization - Example</h4>
-<p>
-@productname@ supports the matrix organization structure at runtime. While modelling, you cannot model
-the matrix structure completely.
-The matrix organization structure can be achieved at runtime using the process portals. You need to create
-departments in the Administration perspective to make a complete matrix structure.</p>
-<p>The following diagram displays the sample structure created at the modeler level.
-In the organization structure diagram, we have four organizations - M1 Project Orga, M2 Project Leader Orga, M1 Test Orga and M1 Development Orga.
-Each of these organizations have roles defined. The <b>M1 Project Manager</b> is the manager of <b>M1 Project Organization</b>.
-The <b>M3 Project Member</b> works for <b>M2 Project Leaders Organization</b>.
-These two organizations - the <b>M1 Project Organization</b> and <b>M2 Project Leaders organizations</b> are connected. The <b>M2 Test Engineer Organization</b>
-works for <b>M1 Test organization</b> and <b>M1 Test Manager</b> is the manager of the <b>M1 Test Organization</b>.
-
-We cannot connect one role to multiple organizations directly. That's why we need to create departments and assign users to roles.
-To achieve the same scenario, three red arrows are used to indicate that you need to create department <b>Project A</b> in the <b>M1 Test organization</b> and department
-<b>Project A and Project B</b> in the <b>M2 Leaders Organization</b>.</p>
-
-<p class="image"><img src="images/SamsaModel_MatrixOrgaStructure.png" alt="Sample Matrix Model">
-<br>
-<strong>Figure:</strong> Sample Model for Matrix Organization</p>
-<h4 id="deploy">Deployment Restrictions</h4>
-<p>Note that restrictions exist for deploying a model
-with changes in the department association for existing roles or organizations,
-to a succeeding model version.
-Please refer to the section
-<a href="mg-deploy-model.html#structure">Changes in the organizational structure</a>
-of the
-<a href="mg-deploy-model.html#consistency">Consistency Checks</a>
-part in the chapter
-<a href="mg-deploy-model.html">Deploying a Workflow Model</a>
-for detailed information on which changes are supported and which will lead to
-a consistency error.</p>
-<h3 id="teamLeader">The Team Leader Role</h3>
-<p>A role can be assigned as team leader to an organization. Please refer to the
-section <a href="mg-basics-9.htm#teams">Teams</a> of the chapter
-<a href="mg-basics-9.htm">Participants and Users</a> for
-a detailed description on the definition of a team.</p>
-<p>There can only be one
-team leader per organization. In case no team leader is associated to an organization
-yet, you are offered the following two types of connection:</p>
-<ul>
- <li>Works For</li>
- <li>Manager Of</li>
-</ul>
-<p>The <strong>Works For</strong> connection is a simple assignment of a role to an
-organization, whereas the <strong>Manager Of</strong> connection defines the role to be the
-organizations team leader.</p>
-<p class="image"><img src="images/mg-connect-teamleader.png"
- alt="Team Leader Connection"> <br>
-<strong>Figure:</strong> Connecting a Role as Team Leader</p>
-<p>The connect transition between a team leader and an organization is displayed as a
-dashed line.</p>
-<p class="image"><img src="images/mg-teamleader-transition.png"
- alt="Team Leader Connection"> <br>
-<strong>Figure:</strong> Connect Transition between Team Leader and Organization</p>
-<p>In the
-<a href="PLUGINS_ROOT/org.eclipse.stardust.docs.enduser/html/handbooks/execution-clients/bcc_renovated/business-control-center.html">
-Business Control Center Perspective</a> of the
-<a href="PLUGINS_ROOT/org.eclipse.stardust.docs.enduser/html/handbooks/execution-clients/carnot-clients.html">
-@productname@ Portal</a>,
-the team leader has an overview over the activities
-of all users belonging to the same organization the team leader belongs to.</p>
-<h4>Invalid Teamlead connection</h4>
-<p>In case an organization has an invalid teamlead connection, e.g. it
-has a teamlead connection, but the team leader is not set in the model file,
-an error indicates this in the <strong>Problems View</strong>.</p>
-<p class="image"><img src="images/teamlead-error.png"
- alt="Team Leader Connection Error"> <br>
-<strong>Figure:</strong> Connection Error displayed in the Problems View.</p>
-<p>You have the option to use the provided <strong>Quick Fix</strong>
-functionality for quickly fixing this error. Right-click the error entry and
-choose the <strong>Quick Fix</strong> option in the drop-down menu.</p>
-<p class="image"><img src="images/teamlead-error-quick-fix-1.png"
- alt="Team Leader Connection Error"> <br>
-<strong>Figure:</strong> Select Quick Fix to fix the Error.</p>
-<p>The <strong>Quick Fix</strong> dialog opens, where you can fix the
-teamlead connection for the organization.</p>
-<p class="image"><img src="images/teamlead-error-quick-fix-2.png"
- alt="Quick Fix Dialog"> <br>
-<strong>Figure:</strong> Quick Fix Dialog</p>
-<h2>Assigning Processes Restricted by Role and Organization</h2>
-<p>In case you want the admin user to view all the processses in the model whereas the other user/role
-should start only a specific process. For example, you have a model which contains four
-processes P1, P2, P3 and P4. The process P1 and P2 display the data whereas P3 and P4 update of data.
-The model has two participants that are Admin and Teller.</p>
-<p>Suppose you want the Admin user to start all the four processes and the Teller user to start only two processes
-that are P1 and P2.</p>
-<p>To achieve this, define an organization A and make the roles Admin and Teller Works for organization A. Then
-assign the manual start trigger of P1 and P2 process to organization and manual start trigger of P3 and
-P4 to Admin role.</p>
-
-<script language="JavaScript" type="text/javascript">
-<!--
-writeFooter();
--->
-</script>
-</body>
-</html>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<meta http-equiv="Content-Style-Type" content="text/css">
+
+<link rel="STYLESHEET" href="../../styles/carnot.css" charset="ISO-8859-1" type="text/css">
+<title>Modeling the Organizational Structure</title>
+<script language="JavaScript" src="../../styles/naviLine.js" type="text/javascript"></script>
+</head>
+<body>
+<script language="JavaScript" type="text/javascript">
+<!--
+ writeNavigation("Specifying Arbitrary Link Types","PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/toc.html",
+ "mg-defdesk-8.htm","mg-defdesk-14.htm",
+ "../../toc.html","Business Analyst Handbooks",
+ "mg-preface.htm","The Modeling Guide",
+ "mg-modeler-preface.html","The Process Workbench");
+ -->
+</script>
+<h1>Modeling the Organizational Structure</h1>
+<p>Interactive Activities are assigned to participants - roles or organizations.
+Users assigned to these roles or organizations perform the work represented by an activity
+instance. Being assigned one or more activity instances, a user can perform these
+activities by completing the work items in his worklist.</p>
+<p>Hence, there is a distinction between</p>
+<ul>
+ <li>roles and organizations, which are visible both in the modeling as well as
+ in the runtime environment,</li>
+ <li>users who are visible only in the runtime environment and</li>
+ <li>modelers who are visible only in the modeling environment.</li>
+</ul>
+<p>Consequently, in your modeling environment you use roles and organizations.
+Individual human performers are created and assigned to these roles only in the
+<a href="PLUGINS_ROOT/org.eclipse.stardust.docs.enduser/html/handbooks/execution-clients/carnot-clients.html">
+@productname@ Portal</a>, the
+<a href="PLUGINS_ROOT/org.eclipse.stardust.docs.enduser/html/handbooks/swing-portal/swing-portal.html">
+@productname@ Swing Portal</a>, console administration tools or via embedding application.</p>
+<p>The following sections describe the usage of participants in
+the Process workbench:</p>
+<ul>
+ <li><a href="#rep">Representation in the Process Workbench</a></li>
+ <li><a href="#org">Organizations</a></li>
+ <li><a href="#role">Roles</a></li>
+ <li><a href="#condPerformers">Conditional Performers</a></li>
+ <li><a href="#associate">Establishing Associations between Organizational Elements</a></li>
+</ul>
+<h3>Participant IDs</h3>
+<p>Please note that IDs containing hyphens, blanks or dots and IDs starting with
+digits are not supported.</p>
+<p>IDs for participants have to be unique within all model participants like roles, organizations
+or conditional performer. When trying to add a duplicate ID, this is indicated in
+the participant properties page:</p>
+<p class="image"><img src="images/error-duplicate-id-prop.png" alt=""> <br>
+<strong>Figure:</strong> Duplicate ID indicated in Properties Page.</p>
+<p>The <strong>Problems View</strong> also shows the following error entry:</p>
+<p class="image"><img src="images/error-duplicate-id-org.png" alt=""> <br>
+<strong>Figure:</strong> Duplicate ID indicated in Problems View.</p>
+
+<h2 id="rep">Representation in the Process Workbench</h2>
+<p>In the <strong>Process Workbench</strong>, a participant may be represented,
+depending on the type of resource, by one of the symbols:</p>
+<ul>
+ <li><img class="noborder" src="images/role-icon.png" alt=""> - Role</li>
+ <li><img class="noborder" src="images/cond-perf-icon.png" alt=""> - Conditional Performer</li>
+ <li><img class="noborder" src="images/organization-icon.png" alt=""> - Organization</li>
+</ul>
+<p>Participants are represented in the Outline view as in the following
+figure:</p>
+<p class="image"><img src="images/participants-outline.png" alt=""> <br>
+<strong>Figure:</strong> Representations of Participants in the Outline View</p>
+<p>In diagram, participants are represented as displayed in the following
+figure:</p>
+<p class="image"><img src="images/participants-diagram.png" alt=""> <br>
+<strong>Figure:</strong> Participants represented in a Diagram.</p>
+
+<h2 id="org">Organizations</h2>
+<p>An organization element represents a group of resources. For example, a department or any organizational unit.
+This section describes which properties are provided and how to work with organization elements in the modeler.</p>
+<h3>Creating and Deleting Organizations</h3>
+<p>To create an organization you can either:</p>
+<ul>
+ <li>Select <strong>Participants</strong> in the diagram <a
+ href="model-views/views-diagrams.html#toolbarPalette">toolbar palette</a> and from the
+ pop-up menu <strong>Organization</strong>. Then move the cursor to the diagram canvas
+ to place the organization symbol there. The organization is created by subsequently
+ clicking on the canvas.</li>
+ <li>In the <strong>Participants</strong> section of the <a
+ href="model-views/views-outline.html">Outline view</a> area, select <strong>New
+ &gt; New Organization</strong> from the pop-up menu. The created organization will appear in
+ the tree view.</li>
+ <li>Or in the <strong>Outline</strong> view, select the model and from its pop-up
+ menu <strong>New Participant &gt; New Organization</strong>.</li>
+</ul>
+<p>When deleting organizations, you must make a distinction between deleting an
+organization from the model information or only deleting a symbol from a diagram. To do
+the first - delete an organization from the model - you proceed as follows:</p>
+<ul>
+ <li>Having selected the symbol of the organization in the <strong>Participants</strong>
+ tree of the <strong>Outline</strong> view, choose the option <strong>Delete</strong>
+ in the pop-up menu of this organization.</li>
+ <li>Having selected the symbol of the organization in a diagram, choose the
+ option <strong>Delete </strong> in the pop-up menu of this organization.</li>
+</ul>
+<p>The option <strong>Delete Symbol</strong> in the pop-up menu called from within
+the diagram canvas will only remove the organization symbol from the diagram.</p>
+<h3>General Properties</h3>
+<p>The <strong>General</strong> properties entry contains:</p>
+<ul>
+ <li>ID - please note that the ID has to be unique within all model participants. IDs containing
+ hyphens, blanks or dots and IDs starting with digits are not supported.</li>
+ <li>Name</li>
+ <li>Internationalization</li>
+</ul>
+<h3 id="binding">Department Binding</h3>
+<p>It is possible for organizations to add a department scope which is
+evaluated at runtime. This department scope is described as a data path
+ to process data which returns a scope key to identify a department representing
+ this scope.</p>
+<p>In the <strong>Department Binding</strong> section you can determine
+that the organization is allowed to support departments by enabling the checkbox
+<strong>Organization supports departments.</strong>.</p>
+<p class="image"><img src="images/mg-org-prop-binding.png" alt="Runtime Binding">
+<br>
+<strong>Figure:</strong> Department Binding</p>
+<p>Once the checkbox is enabled, a new field opens, where you can enter
+data for the department OID. It is possible to select one of the following
+two data types:</p>
+<ul>
+ <li>a primitive data of type <tt>String</tt> without access path.
+ <p class="image"><img src="images/mg-org-prop-depart-2.png" alt=""></p></li>
+ <li>a structured data and an access path evaluating to String.
+ <p class="note"><strong>Note</strong><br>
+ the data path should be an element (type String) of the structured data and not be using
+ methods as dereferentiation path.</p>
+ <p class="image"><img src="images/mg-org-prop-depart-1.png" alt=""></p></li>
+</ul>
+<h3 id="contrOrg">Controlling Parameters for Organizations</h3>
+<p>The following controlling parameter is provided for organizations:</p>
+<ul>
+ <li><strong>Cost Center</strong></li>
+</ul>
+<p class="image"><img src="images/org-controlling.png"
+alt="Organization Controlling Parameter"><br>
+<strong>Figure:</strong> Organization Controlling Parameter</p>
+<h3 id="task">Task Assignment</h3>
+<p>In the properties dialog of the organization you can choose how the task assignment
+is performed:</p>
+<ul>
+ <li>Select <strong>Task Assignment</strong> in the properties dialog.</li>
+ <li>Choose the mode for task assigment. You have the choice of <tt>Choose
+ Assignment</tt> or <tt>Assign Automatically</tt>.</li>
+</ul>
+<p class="image"><img src="images/mg-task-assignment-org.png" alt="Task Assignment">
+<br>
+<strong>Figure:</strong> Task Assignment of an Organization</p>
+<h3>Simulation</h3>
+<p>In this section you can specify simulation configurations, as described detailed in the chapter
+ <a href="PLUGINS_ROOT/org.eclipse.stardust.docs.simulation/html/simulation/simulation-configurations.html">
+ Simulation Configurations</a>
+of the
+ <a href="PLUGINS_ROOT/org.eclipse.stardust.docs.simulation/html/simulation/toc.html">
+ @productname@ Developer Simulation Guide</a>.)</p>
+<h3>Effort Planning</h3>
+<p>In this section you can set the organization complexity for project effort calculation:</p>
+<p class="image"><img src="images/organization-prop-effort.png" alt=""> <br>
+<strong>Figure:</strong> Effort Planning Property of an Organization</p>
+<p>Please refer to the chapter <a href="process-effort-calculation.html">Project Effort Calculation</a> for
+detailed information on this functionality.</p>
+<h2 id="role">Roles</h2>
+
+<p>A role denotes the responsibility assigned to the participants. Following
+sections provide information on how to work with roles.</p>
+
+
+<h3>Creating and Deleting Roles</h3>
+<p>To create a role you can either:</p>
+<ul>
+ <li>Select <strong>Participants</strong> in the diagram <a
+ href="model-views/views-diagrams.html#toolbarPalette">toolbar palette</a> and from the
+ pop-up menu <strong>Role</strong>. Then move the cursor to the diagram canvas to place
+ the role symbol there. The role is created by subsequently clicking on the canvas.</li>
+ <li>In the <strong>Participants</strong> section of the <a
+ href="model-views/views-outline.html">Outline view</a> area, select <strong>New
+ &gt; New Role</strong> from the pop-up menu. The created role will appear in the tree view.</li>
+ <li>Or in the <strong>Outline</strong> view, select the model and from its pop-up
+ menu <strong>New Participant &gt; New Role</strong>.</li>
+</ul>
+<p>When deleting roles you must make a distinction between deleting a role from the
+model information or only deleting a symbol from a diagram. To do the first - delete a
+role from the model - you proceed as follows:</p>
+<ul>
+ <li>Having selected the symbol of the role in the <strong>Participants</strong>
+ tree of the Outline view, choose the option <strong>Delete </strong> in the pop-up
+ menu of this role.</li>
+ <li>Having selected the symbol of the role in a diagram, choose the option <strong>Delete
+ </strong> in the pop-up menu of this role.</li>
+</ul>
+<p>The option <strong>Delete Symbol </strong> in the pop-up menu called from within
+the diagram canvas will only remove the role symbol from the diagram.</p>
+<h3>General Properties</h3>
+<p>The <strong>General</strong> properties entry contains:</p>
+<ul>
+ <li>ID - please note that the ID has to be unique within all model participants. IDs containing
+ hyphens, blanks or dots and IDs starting with digits are not supported.</li>
+ <li>Name</li>
+ <li>Internationalization</li>
+ <li>Cardinality</li>
+</ul>
+<h4 id="cardinality">Cardinality</h4>
+<p>You can define the cardinality of roles in the properties dialog. Type in the
+maximum users that can be assigned to this role in the <strong>Cardinality</strong> entry
+field.</p>
+<p class="image"><img src="images/mg-role-cardinality.png" alt="Cardinality"> <br>
+<strong>Figure:</strong> Setting the Cardinality<br /></p>
+<h3 id="contrRole">Controlling Parameters for Roles</h3>
+<p>The following controlling parameters are provided for roles:</p>
+<ul>
+ <li><strong>Working Weeks Per Year:</strong> number of working weeks per year.</li>
+ <li><strong>Actual Cost Per Minute:</strong> actual cost per minute.</li>
+ <li><strong>Target (System) Worktime Per Day:</strong> target system worktime
+ per day in minutes.</li>
+ <li><strong>Target Worktime Per Week:</strong> target worktime per week in
+ hours.</li>
+ <li><strong>Target Queue Depth:</strong></li>
+</ul>
+<p class="image"><img src="images/role-controlling.png"
+ alt="Controlling Parameters for Roles"> <br>
+<strong>Figure:</strong> Controlling Parameters for Roles</p>
+<h3>Task Assignment</h3>
+<p>In the properties dialog of the role you can choose how the task assignment is
+performed:</p>
+<ul>
+ <li>Select <strong>Task Assignment</strong> in the properties dialog.</li>
+ <li>Choose the mode for task assigment. You have the choice of <tt>Choose
+ Assignment</tt> or <tt>Assign Automatically</tt>.</li>
+</ul>
+<p class="image"><img src="images/mg-task-assignment.png" alt="Task Assignment">
+<br>
+<strong>Figure:</strong> Task Assignment of a Role</p>
+
+<h3>Simulation</h3>
+<p>In this section you can specify simulation configurations, as described detailed in the chapter
+ <a href="PLUGINS_ROOT/org.eclipse.stardust.docs.simulation/html/simulation/simulation-configurations.html">
+ Simulation Configurations</a>
+of the
+ <a href="PLUGINS_ROOT/org.eclipse.stardust.docs.simulation/html/simulation/toc.html">
+ Developer Simulation Guide</a>.)</p>
+<h3>Effort Planning</h3>
+<p>In this section you can set the role complexity for project effort calculation:</p>
+<p class="image"><img src="images/role-prop-effort.png" alt=""> <br>
+<strong>Figure:</strong> Effort Planning Property of a Role</p>
+<p>Please refer to the chapter <a href="process-effort-calculation.html">Project Effort Calculation</a> for
+detailed information on this functionality.</p>
+<h2 id="condPerformers">Conditional Performers</h2>
+<p>The conditional performer is evaluated at runtime and it determines the identity of the actual performer.
+The following sections help you to work with conditional performers.</p>
+<h3>Creating and Deleting Conditional Performers</h3>
+<p>To create a conditional performer you can either:</p>
+<ul>
+ <li>Select <strong>Participants</strong> in the diagram <a
+ href="model-views/views-diagrams.html#toolbarPalette">toolbar palette</a> and from the
+ pop-up menu <strong>Conditional Performer</strong>. Then move the cursor to the
+ diagram canvas to place the symbol for the conditional performer there. The
+ conditional performer is created by subsequently clicking on the canvas.</li>
+ <li>In the Participants section of the <a
+ href="model-views/views-outline.html">Outline view</a> area, select <strong>New
+ &gt; New Conditional Performer </strong>from the pop-up menu. The created conditional performer
+ will appear in the tree view.</li>
+ <li>Or in the Outline view, select the model and from its pop-up menu <strong>New
+ Participant &gt; New Conditional Performer.</strong></li>
+</ul>
+<p>As described in the chapter <a href="mg-basics-9.htm">Participants and Users</a>,
+the <a href="PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/handbooks/others/glossary.html#oid">OID</a> or respectively
+<a href="PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/handbooks/others/glossary.html#id">ID</a>
+of the performer assigned dynamically at runtime is passed to
+the @productname@ resource.</p>
+
+<h3>Runtime Binding</h3>
+<p>Among the conditional performer's properties, there is also the distinction
+between an individual user of the runtime environment and a performer defined in the
+modeling environment (corresponding to a role or organization) used as a conditional
+performer. This distinction has to be made in the same properties dialog. Click <strong>Runtime
+Binding</strong> to define the performer as a user, organization/role or user group and choose the
+data and optional data path to provide the performer's identity.</p>
+<p>In the <strong>Kind</strong> drop-down list, define the performer as one
+of the following:</p>
+<ul>
+ <li>User</li>
+ <li>Organization/Role</li>
+ <li>User Group</li>
+ <li>Organization/Role or User Group</li>
+</ul>
+<p class="image"><img
+ src="images/mg-performer-props.png" alt=""><br>
+<strong>Figure:</strong> Specifying a Conditional Performer</p>
+<h4>Oid/Id</h4>
+<p>In the <strong>OID/Id</strong> section, choose the data and data path providing
+the performer identity.</p>
+<p class="image"><img src="images/mg-org-cond-perf-oid.png"
+ alt="Conditional Performer Properties"><br>
+<strong>Figure:</strong> Conditional Performer</p>
+
+<p class="note"><strong>Note</strong><br>In case the data is of type <strong>Long</strong>, the value is used to identify the
+OID of the performer, as thus it refers to a user. If the data is of type <strong>String</strong>,
+the value is used to identify the Id of the performer, as this has to be a role in that case.</p>
+<h4>User Realm</h4>
+<p>If the conditional performer is defined as a user, an additional field appears to
+fill in the users
+<a href="PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/handbooks/concepts/admin-concepts/ag-multipartition.htm#realm">
+realm</a> data.</p>
+<p class="image"><img src="images/mg-performer-props-realm.png" alt=""><br>
+<strong>Figure:</strong> Specifying a Conditional Performer as User</p>
+<h4>Using the Last Activity Performer data</h4>
+<p>The <strong>Last Activity Performer</strong> data usage determines that the
+performer is used as a computed value. The algorithm for a specific process
+instance is as follows:</p>
+<ol>
+ <li>Select all <tt>COMPLETED</tt> activity instances belonging
+ to the specific process instance, ordered descending by the last modification time.</li>
+ <li>Traverse the result and select the first interactive activity instance.</li>
+ <li>Return the user of that activity.</li>
+</ol>
+<p class="note"><strong>Note</strong><br>
+Please note that in case the activity is the first activity in the work flow,
+there would be no <strong>Last Activity Performer</strong>.
+If an activity other than the first one is unable to retrieve
+the last activity performer due to the transaction isolation level <tt>COMMITMENT</tt>,
+set in the database, enable the <strong>Fork on traversal</strong> flag in the
+transition between the current and the last activities.
+Please refer to the section <a href="mg-basics-13.htm#activityThread">Activity Thread</a> of the
+chapter <a href="mg-basics-13.htm">Runtime Behavior</a> for detailed
+information on the <strong>Fork on Traversal</strong>
+functionality.</p>
+<h3>Simulation</h3>
+<p>In this section you can specify simulation configurations, as described detailed in the chapter
+ <a href="PLUGINS_ROOT/org.eclipse.stardust.docs.simulation/html/simulation/simulation-configurations.html">
+ Simulation Configurations</a>
+of the
+ <a href="PLUGINS_ROOT/org.eclipse.stardust.docs.simulation/html/simulation/toc.html">
+ Developer Simulation Guide</a>.</p>
+<h3>Effort Planning</h3>
+<p>In this section you can set the performer complexity for project effort calculation:</p>
+<p class="image"><img src="images/performer-prop-effort.png" alt=""> <br>
+<strong>Figure:</strong> Effort Planning Property of a Conditional Performer</p>
+<p>Please refer to the chapter <a href="process-effort-calculation.html">Project Effort Calculation</a> for
+detailed information on this functionality.</p>
+<h3>Deleting Conditional Performers</h3>
+<p>When deleting conditional performers, you must make a distinction between deleting
+a conditional performer from the model information or only deleting a symbol from a
+diagram. To do the first - delete a conditional performer from the model - you proceed as
+follows:</p>
+<ul>
+ <li>Having selected the symbol of the conditional performer in the <strong>Participants</strong>
+ tree of the <a href="model-views/views-outline.html">Outline view</a>, choose the
+ option <strong>Delete </strong> in the pop-up menu of this conditional performer.</li>
+ <li>Having selected the symbol of the conditional performer in a diagram,
+ choose the option <strong>Delete</strong> in the pop-up menu of this
+ conditional performer.</li>
+</ul>
+<p>The option <strong>Delete Symbol </strong> in the pop-up menu called from within
+the diagram canvas will only remove the symbol for the conditional performer from the
+diagram.</p>
+<h2 id="associate">Establishing Associations between Organizational Elements</h2>
+<p>Organizations are groups of human resources. Consequently, they may contain
+individual roles or subordinate organizations. Like process definitions, organizational
+hierarchies can be modeled in the @productname@ Workbench with the help of diagrams.</p>
+<p>To model your organizations, use either diagrams bound to a process definition or
+model diagrams. A prerequisite for establishing relationships between an organization and
+its members is the existence of these elements: an organization and all its members (roles
+or smaller organizational units). Proceed as follows:</p>
+<ul>
+ <li>Place the organization symbol and the symbol representing a member of this
+ organization (e.g. a role or another organization) in a diagram.</li>
+ <li>Right-click the symbol representing a member.</li>
+ <li>Select <strong>Connect</strong> in the context menu.</li>
+ <li>Click the organization the member is going to belong to.</li>
+</ul>
+<p class="image"><img src="images/mg-connect-organizations.png" alt=""> <br>
+<strong>Figure:</strong> Making an Organization Part of Another</p>
+<p>To add further members to the organization, repeat these operations for each
+member. An example of an organizational hierarchy diagram is shown below.</p>
+<p class="image"><img src="images/organizational-diagram.png" alt=""> <br>
+<strong>Figure:</strong> A Sample Organizational Diagram</p>
+<h3>Restrictions on Associations</h3>
+<p>The following sections describes the restrictions on associations between organizational elements.</p>
+<h4>Only one relationship to other participants supported</h4>
+<p>Please note that a model participant can only have one relationship like
+<strong>Work For</strong> or <strong>Manager of</strong> to other
+participants. Otherwise the model validation fails and the
+following error message appears in the <strong>Problems</strong>
+view:</p>
+<p class="image"><img src="images/work-for-error-problem-view.png" alt="Problems View"> <br>
+<strong>Figure:</strong> Error indicated in Problems View</p>
+<h4>Only one relationship to other organizations supported</h4>
+<p>An organization should not be part of more than one other organization. Otherwise
+the model validation fails and the
+following error message appears in the <strong>Problems</strong>
+view:</p>
+<p class="image"><img src="images/part-of-error-problem-view.png" alt="Problems View"> <br>
+<strong>Figure:</strong> Error indicated in Problems View</p>
+<h4>Administrator Role cannot be connected</h4>
+<p>Since @productname@ version 5.2. and later, it is not possible
+to connect the <strong>Administrator</strong> role to any
+organization. In case models with @productname@ versions older than 5.2 contain
+such a connection, an error message in the <strong>Problems</strong> view
+indicates this in the following way:</p>
+<p class="image"><img src="images/admin-error-problem-view.png" alt="Problems View"> <br>
+<strong>Figure:</strong> Administrator Assignment Error in Problems View</p>
+<h3 id="scope">Behavior of Scoped Organizations</h3>
+
+<p>Infinilty Platform supoports scoping of roles, orgnizations and departments.
+The following sections describes what happens when the organizations are scoped.</p>
+
+<ul>
+ <li><a href="#implicit">Implicitly Scoped Roles</a></li>
+ <li><a href="#hierScop">Organizational Hierarchies and Target Departments</a></li>
+ <li><a href="#matrix">Matrix Organizations</a></li>
+ <li><a href="#deploy">Deployment Restrictions</a></li>
+</ul>
+<h4 id="implicit">Implicitly Scoped Roles</h4>
+<p>Roles are implicitly scoped via the next scoped Organization above.</p>
+<p>When a User is assigned to an (implicitly) scoped Role, the Role
+and the departments for all organizations, the Role has a "Works For" or "Is Manager Of"
+relationship, have to be specified.</p>
+<h4 id="hierScop">Organizational Hierarchies and Target Departments</h4>
+<p>All Organizations and Roles underneath a scoped Organization inherit
+the target departments of this Organization, as long as the suborganization does not define
+a new target department. Hence, for every participant the relevant target department is the scope of the
+next scoped Organization upwards the organizational hierarchy.</p>
+<h4 id="matrix">Matrix Organizations</h4>
+<p>@productname@ only allows pure tree structures for
+organizational hierarchies. Neither Roles nor Organizations may be assigned
+to more than one Organization. Matrix structures can be mapped by disjoint
+organizational structures with possibly different scopes (e.g. branch vs. project),
+whereby users might be assigned to Roles in both structures.</p>
+
+<h4>Matrix Organization - Example</h4>
+<p>
+@productname@ supports the matrix organization structure at runtime. While modelling, you cannot model
+the matrix structure completely.
+The matrix organization structure can be achieved at runtime using the process portals. You need to create
+departments in the Administration perspective to make a complete matrix structure.</p>
+<p>The following diagram displays the sample structure created at the modeler level.
+In the organization structure diagram, we have four organizations - M1 Project Orga, M2 Project Leader Orga, M1 Test Orga and M1 Development Orga.
+Each of these organizations have roles defined. The <b>M1 Project Manager</b> is the manager of <b>M1 Project Organization</b>.
+The <b>M3 Project Member</b> works for <b>M2 Project Leaders Organization</b>.
+These two organizations - the <b>M1 Project Organization</b> and <b>M2 Project Leaders organizations</b> are connected. The <b>M2 Test Engineer Organization</b>
+works for <b>M1 Test organization</b> and <b>M1 Test Manager</b> is the manager of the <b>M1 Test Organization</b>.
+
+We cannot connect one role to multiple organizations directly. That's why we need to create departments and assign users to roles.
+To achieve the same scenario, three red arrows are used to indicate that you need to create department <b>Project A</b> in the <b>M1 Test organization</b> and department
+<b>Project A and Project B</b> in the <b>M2 Leaders Organization</b>.</p>
+
+<p class="image"><img src="images/SamsaModel_MatrixOrgaStructure.png" alt="Sample Matrix Model">
+<br>
+<strong>Figure:</strong> Sample Model for Matrix Organization</p>
+<h4 id="deploy">Deployment Restrictions</h4>
+<p>Note that restrictions exist for deploying a model
+with changes in the department association for existing roles or organizations,
+to a succeeding model version.
+Please refer to the section
+<a href="mg-deploy-model.html#structure">Changes in the organizational structure</a>
+of the
+<a href="mg-deploy-model.html#consistency">Consistency Checks</a>
+part in the chapter
+<a href="mg-deploy-model.html">Deploying a Workflow Model</a>
+for detailed information on which changes are supported and which will lead to
+a consistency error.</p>
+<h3 id="teamLeader">The Team Leader Role</h3>
+<p>A role can be assigned as team leader to an organization. Please refer to the
+section <a href="mg-basics-9.htm#teams">Teams</a> of the chapter
+<a href="mg-basics-9.htm">Participants and Users</a> for
+a detailed description on the definition of a team.</p>
+<p>There can only be one
+team leader per organization. In case no team leader is associated to an organization
+yet, you are offered the following two types of connection:</p>
+<ul>
+ <li>Works For</li>
+ <li>Manager Of</li>
+</ul>
+<p>The <strong>Works For</strong> connection is a simple assignment of a role to an
+organization, whereas the <strong>Manager Of</strong> connection defines the role to be the
+organizations team leader.</p>
+<p class="image"><img src="images/mg-connect-teamleader.png"
+ alt="Team Leader Connection"> <br>
+<strong>Figure:</strong> Connecting a Role as Team Leader</p>
+<p>The connect transition between a team leader and an organization is displayed as a
+dashed line.</p>
+<p class="image"><img src="images/mg-teamleader-transition.png"
+ alt="Team Leader Connection"> <br>
+<strong>Figure:</strong> Connect Transition between Team Leader and Organization</p>
+<p>In the
+<a href="PLUGINS_ROOT/org.eclipse.stardust.docs.enduser/html/handbooks/execution-clients/bcc_renovated/business-control-center.html">
+Business Control Center Perspective</a> of the
+<a href="PLUGINS_ROOT/org.eclipse.stardust.docs.enduser/html/handbooks/execution-clients/carnot-clients.html">
+@productname@ Portal</a>,
+the team leader has an overview over the activities
+of all users belonging to the same organization the team leader belongs to.</p>
+<h4>Invalid Teamlead connection</h4>
+<p>In case an organization has an invalid teamlead connection, e.g. it
+has a teamlead connection, but the team leader is not set in the model file,
+an error indicates this in the <strong>Problems View</strong>.</p>
+<p class="image"><img src="images/teamlead-error.png"
+ alt="Team Leader Connection Error"> <br>
+<strong>Figure:</strong> Connection Error displayed in the Problems View.</p>
+<p>You have the option to use the provided <strong>Quick Fix</strong>
+functionality for quickly fixing this error. Right-click the error entry and
+choose the <strong>Quick Fix</strong> option in the drop-down menu.</p>
+<p class="image"><img src="images/teamlead-error-quick-fix-1.png"
+ alt="Team Leader Connection Error"> <br>
+<strong>Figure:</strong> Select Quick Fix to fix the Error.</p>
+<p>The <strong>Quick Fix</strong> dialog opens, where you can fix the
+teamlead connection for the organization.</p>
+<p class="image"><img src="images/teamlead-error-quick-fix-2.png"
+ alt="Quick Fix Dialog"> <br>
+<strong>Figure:</strong> Quick Fix Dialog</p>
+<h2>Assigning Processes Restricted by Role and Organization</h2>
+<p>In case you want the admin user to view all the processses in the model whereas the other user/role
+should start only a specific process. For example, you have a model which contains four
+processes P1, P2, P3 and P4. The process P1 and P2 display the data whereas P3 and P4 update of data.
+The model has two participants that are Admin and Teller.</p>
+<p>Suppose you want the Admin user to start all the four processes and the Teller user to start only two processes
+that are P1 and P2.</p>
+<p>To achieve this, define an organization A and make the roles Admin and Teller Works for organization A. Then
+assign the manual start trigger of P1 and P2 process to organization and manual start trigger of P3 and
+P4 to Admin role.</p>
+
+<script language="JavaScript" type="text/javascript">
+<!--
+writeFooter();
+-->
+</script>
+</body>
+</html>
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/mg-modeler-views.html b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-perspective-overview.html
index 65e113c..04e7145 100644
--- a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/mg-modeler-views.html
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-perspective-overview.html
@@ -5,21 +5,21 @@
<meta http-equiv="Content-Style-Type" content="text/css">
<link rel="STYLESHEET" href="../../styles/carnot.css" charset="ISO-8859-1" type="text/css">
-<title>The Business Process Modeling Perspective</title>
+<title>The Business Process Modeling Perspective</title>
<script language="JavaScript" src="../../styles/naviLine.js" type="text/javascript"></script>
</head>
<body>
<script language="JavaScript" type="text/javascript">
<!--
writeNavigation("Working with Models","PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/toc.html",
- "mg-modeler-preface.html","models/model-preface.html",
+ "mg-modeler-preface.html","models/model-preface.html",
"../../toc.html","Business Analyst Handbooks",
"mg-preface.htm","The Modeling Guide",
"mg-modeler-preface.html","The Process Workbench");
-->
</script>
-<h1>The Business Process Modeling Perspective</h1>
+<h1>The Business Process Modeling Perspective</h1>
<p>The Analyst Perspective provides a graphical modeling perspective to design
business process models with generic objects.
To open the @productnameonly@ Analyst Perspective select <strong>Window &gt; Open
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/mg-pools-lanes.htm b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-pools-lanes.htm
index ddf1f53..db5af56 100644
--- a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/mg-pools-lanes.htm
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-pools-lanes.htm
@@ -1,30 +1,30 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../../styles/carnot.css" charset="ISO-8859-1"
- type="text/css">
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<meta http-equiv="Content-Style-Type" content="text/css">
+<link rel="STYLESHEET" href="../../styles/carnot.css" charset="ISO-8859-1"
+ type="text/css">
<title>Swim Lanes Usage</title>
-<script language="JavaScript" src="../../styles/naviLine.js"
- type="text/javascript"></script>
-</head>
-<body>
-<script language="JavaScript" type="text/javascript">
-<!--
+<script language="JavaScript" src="../../styles/naviLine.js"
+ type="text/javascript"></script>
+</head>
+<body>
+<script language="JavaScript" type="text/javascript">
+<!--
writeNavigation("Copying and Pasting Modeled Elements",
"PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/toc.html",
"mg-defdesk-15.htm","mg-copy-paste-elements.html",
"../../toc.html","Business Analyst Handbooks",
"mg-preface.htm","The Modeling Guide",
"mg-modeler-preface.html","The Process Workbench");
- -->
-</script>
+ -->
+</script>
<h1>Swim Lanes Usage</h1>
<p>The Business Process Modeling perspective allows the usage of swim lanes for creating models.
The swim lanes are enabled by default for new process and contain a Default Pool and Default Lane.
</p>
-<ul>
+<ul>
<li><a href="#pool">Default Pool</a></li>
<li><a href="#lane">Default Lane</a>
<ul>
@@ -37,7 +37,7 @@ The swim lanes are enabled by default for new process and contain a Default Pool
<li><a href="#sym">Symbols in Lanes</a></li>
<li><a href="#ges">Symbol Gestures</a></li>
<li><a href="#ele">Dragging and Dropping of Elements from Outline</a></li>
-</ul>
+</ul>
@@ -86,7 +86,7 @@ lane also deletes symbols and in and out mappings across it.</p>
<p>Note that when you delete any lane or default lane, when no other lane exists, Lane 1 gets created, automatically. So the rule is,
at least one lane should exist in the process model.
-When you delete any lane, all symbols in the lane are deleted but the according elements still exist in the model.</p>
+</p>
<p>Consider a scenario, where Default Lane, Lane 2 and Lane 3 exist in the model. Delete Default Lane and Lane 2 from the model.
Now, only Lane 3 exists in the model. Delete Lane 3, too. Note that Lane 1 is created automatically.</p>
@@ -109,7 +109,7 @@ at the right of the lanes.
alt="Lane Properties" /> <br>
<strong>Figure:</strong> Lane Properties</p>
<p>Following are the lane properties:</p>
-<ul>
+<ul>
<li>UUID - A unique identifier ID gets generated as an identifier for client server communication.</li>
<li>ID - Default ID of the lane.</li>
<li>Name - Specify name of the lane.</li>
@@ -120,7 +120,7 @@ at the right of the lanes.
The selected participant name is reflected in lane header in parenthesis to the right of the lane name.
Activities automatically get the participant assignment of the lane they are residing in.
</li>
-</ul>
+</ul>
<h3>Hide Property Panel </h3>
<p>Click the <strong>Hide Property Panel</strong> icon displayed at the top right corner of the window.
</p>
@@ -155,7 +155,7 @@ Also, when you hover the mouser over the symbol its outline changes to red color
alt="Mouse Hover - Flyout Menu" /> <br>
<strong>Figure:</strong> Mouse Hover - Flyout Menu</p>
<h4>Double-clicking Symbol</h4>
-<p>To rename the activity or subprocess activity and application, double-click on its symbol in the swim lane.
+<p>To rename the activity or subprocess activity and application, double-click on its symbol name in the swim lane.
</p>
<p class="image"><img src="images/doubl-clik.png"
alt="Double-click on Activity Symbol" /> <br>
@@ -205,10 +205,10 @@ the right side of the swim lane. Also, the symbol gets selected and you can move
-<script language="JavaScript" type="text/javascript">
-<!--
-writeFooter();
--->
-</script>
-</body>
-</html>
+<script language="JavaScript" type="text/javascript">
+<!--
+writeFooter();
+-->
+</script>
+</body>
+</html>
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-session-log.htm b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-session-log.htm
new file mode 100644
index 0000000..6831446
--- /dev/null
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-session-log.htm
@@ -0,0 +1,180 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<meta http-equiv="Content-Style-Type" content="text/css">
+
+<link rel="STYLESHEET" href="../../styles/carnot.css" charset="ISO-8859-1" type="text/css">
+<title>Working with Process Definitions</title>
+<script language="JavaScript" src="../../styles/naviLine.js" type="text/javascript"></script>
+</head>
+<body>
+<script language="JavaScript" type="text/javascript">
+<!--
+ writeNavigation("Specifying Activities","PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/toc.html",
+ "models/model-preface.html","mg-defdesk-4.htm",
+ "../../toc.html","Business Analyst Handbooks",
+ "mg-preface.htm","The Modeling Guide",
+ "mg-modeler-preface.html","The Process Workbench");
+ -->
+</script>
+
+<h1>Working with Process Definitions</h1>
+<p>The Business Process Modeling perspective visualizes the existing process definitions in the
+<strong>My Process Models</strong> panel under model element. You can create, rename and delete process definitions.
+Each process definition has its property panel wherein you can modify its properties.
+A typical process definition contains swim lanes, activities and gateways, applications, events, data and control flows.</p>
+
+
+<p>You can perform following operations on any process definition in the Business Process Modeling perspective:</p>
+<ul>
+ <li><a href="#create">Creating a Process Definition</a></li>
+ <li><a href="#rename">Renaming a Process Definition</a></li>
+ <li><a href="#del">Deleting a Process Definition</a></li>
+ <li><a href="#prop">Modifying Properties of a Process Definition</a></li>
+
+</ul>
+<h2 id="create">Creating a Process Definition</h2>
+<p>Perform the following steps to create a new process definition.</p>
+<ol>
+ <li>Expand the <strong>My Process Models</strong> pane of the Business Process Modeling perspective</li>
+ <li>Create model under the Models node</li>
+ <li>Right-click the newly created model name and select <strong>Create Process</strong>.
+ The Process 1 gets created under the model node.
+ <p class="image"><img src="images/create-process.png" alt=""> <br>
+<strong>Figure:</strong> Creating a Process Definition</p></li>
+
+</ol>
+<h2 id="rename">Renaming a Process Definition</h2>
+
+<p>Perform the following steps to rename the process definition:</p>
+
+
+<ol>
+ <li>Under the Models node, right-click the process name and select <strong>Rename</strong></li>
+ <p class="image"><img src="images/rename-process.png" alt=""> <br>
+<strong>Figure:</strong> Renaming a Process Definition</p>
+
+ <li>Specify the new name. The process is renamed.</li>
+ <p class="image"><img src="images/new-name.png" alt=""> <br>
+<strong>Figure:</strong> Specify New name</p>
+</ol>
+
+<h2 id="del">Deleting a Process Definition</h2>
+<p>Perform the following steps to delete the process definition:</p>
+<ol>
+ <li>Under the Models node, right-click the process name and select <strong>Delete</strong>
+
+
+ <p class="image"><img src="images/delete-pro.png" alt=""> <br>
+<strong>Figure:</strong> Delete Process</p></li>
+ <li>Click <strong>Yes</strong> in the delete <strong>Confirm</strong> dialog box. The process gets deleted.
+ <p class="image"><img src="images/del-pro-confirm.png" alt=""> <br>
+<strong>Figure:</strong> Delete Process - Confirm dialog box</p></li>
+</ol>
+<h2 id="prop">Modifying Properties of a Process Definition</h2>
+<h3>General Properties</h3>
+
+<p>To view the properties of a process definition, perform the following steps:</p>
+
+<ol>
+ <li>Select the process definition under the model node. The properties window is displayed at the top right corner
+ of the swim lane.
+ <p class="image"><img src="images/gen-proc-prop.png" alt=""> <br>
+<strong>Figure:</strong> General Properties of Process Definition</p>
+ </li>
+ <li>Specify the properties:
+ <ul>
+ <li>UUID - A unique identifier ID gets generated as an identifier for client server communication</li>
+ <li>ID - Default ID of the process</li>
+ <li>Name - Specify name of the process</li>
+ <li>Description - Specify the description</li>
+ <li>Default Priority - Specify process priority. By default, it is set to 0. You can specify following
+ values for priority:
+ <ul>
+ <li>1 indicates high priority</li>
+ <li>0 indicates medium priority</li>
+ <li>-1 indicates low priority</li>
+ </ul>
+ </li>
+ </ul></li>
+</ol>
+
+<h3>Process Interface</h3>
+<p></p>
+
+
+<p>To view and modify the process interface properties of a process, perform the following steps: </p>
+<ol>
+ <li>Make sure that property panel of the process definition is open </li>
+ <li>Click the <strong>Process Interface</strong> icon displayed at top right corner of the swim lane</li>
+ <p class="image"><img src="images/proc-int.png" alt=""> <br>
+<strong>Figure:</strong> Process Interface icon</p>
+
+ <li>Select process interface type from the <strong>Type</strong> drop-down list.
+ By default, <strong>No Process Interfaces</strong> option is selected.
+ <p class="image"><img src="images/proc-int-type.png" alt=""> <br>
+<strong>Figure:</strong> Process Interface - Type</p>
+ <ul>
+ <li>Provides Process Interface</li>
+ <li>Implements Process Interface</li>
+
+ </ul>
+</li>
+</ol>
+
+<h4>Provides Process Interface</h4>
+<p></p>
+
+<h4>Implements Process Interface</h4>
+<p></p>
+
+<h3>Data Path</h3>
+<p>TO DO</p>
+
+<h3>Display</h3>
+<p>Perform the following steps to modify the Display properties</p>
+
+<ol>
+ <li>Make sure that property panel of the process definition is open </li>
+ <li>Click the <strong>Display</strong> icon displayed at top right corner of the swim lane
+
+ <p class="image"><img src="images/proc-display-prop.png" alt=""> <br>
+<strong>Figure:</strong> Process - Display Icon</p></li>
+ <li>Select a check box <strong>Is Auxiliary Process</strong> to mark a process as auxiliary from a
+ business perspective. Thus, non-business relevant process instances can be hidden in
+ the Infinity Process Platform Portal. This check box is not selected, by default.
+
+ <p class="image"><img src="images/display.png" alt=""> <br>
+<strong>Figure:</strong> Process - Display</p></li>
+
+</ol>
+
+<h3>Process Attachments</h3>
+
+<p>Perform the following steps to specify process attachments:</p>
+
+<ol>
+ <li>Make sure that property panel of the process definition is open </li>
+ <li>Click the <strong>Process Attachments</strong> icon displayed at top right corner of the swim lane
+ <p class="image"><img src="images/proc-attach.png" alt=""> <br>
+<strong>Figure:</strong> Process Attachments Icon</p></li>
+
+ <li>Select the check box <strong>Process supports attachments</strong></li>
+ <li>
+ Select the check box <strong>Unique per root process instance</strong></li>
+
+</ol>
+<p>For more information, please refer to the chapter
+<a href="PLUGINS_ROOT/org-eclipse.stardust.docs.dev/html/handbooks/modelling/mg-defdesk-3.htm">Working with Process Definition</a>
+
+
+
+
+<script language="JavaScript" type="text/javascript">
+<!--
+writeFooter();
+-->
+</script>
+</body>
+</html>
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/process-effort-calculation.html b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/process-effort-calculation.html
deleted file mode 100644
index 1ef2d28..0000000
--- a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/process-effort-calculation.html
+++ /dev/null
@@ -1,126 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
-<html>
-<head>
-<title>Project Effort Calculation</title>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<LINK REL ="stylesheet" TYPE="text/css" HREF="../../styles/carnot.css" TITLE="Style">
-<script language="JavaScript" src="../../styles/naviLine.js" type="text/javascript"></script>
-</head>
-<body>
-<script language="JavaScript">
-<!--
- writeNavigation("Modeling Pattern Support","PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/toc.html",
- "property-page-authorization.html","pattern-support.html",
- "../../toc.html","Business Analyst Handbooks",
- "mg-preface.htm","The Modeling Guide",
- "mg-modeler-preface.html","The Process Workbench");
- -->
-</script>
-
-<h1>Project Effort Calculation</h1>
-<h2>General</h2>
-<p>In many BPM projects efforts to model, implement, test and roll-out a given
- &quot;to be&quot; process model including</p>
-<ul>
- <li>modeling of specific (sub)processes of the end-to-end value chain to be
- supported,</li>
- <li>configuration of the runtime execution environment for @productname@
- (GUI portal, application server, database, directory service etc.),</li>
- <li>integration of non-interactive services via Web Services, message buses,
- Enterprise Java Beans,</li>
- <li>integration of interactive GUI building blocks for the execution of specific
- activities and</li>
- <li>integration of data sources containing data and business objects accessed
- in the process.</li>
-</ul>
-<p>have to be estimated.</p>
-<p>Efforts for the tasks above can easily be assigned to the different process
- model elementsl such as</p>
-<ul>
- <li>the model itself,</li>
- <li>process definitions and their activities or</li>
- <li>data and application definitions.</li>
-</ul>
-<p>Project effort contributions will occur in the different phases of a project:</p>
-<ul>
- <li>Define Phase</li>
- <li>Design Phase</li>
- <li>Implementation Phase</li>
- <li>Validation Phase</li>
- <li>Rollout Phase</li>
-</ul>
-<p>The process effort calculation feature supports the specification of such effort
- drivers for all project phases, the entry of concrete values for these cost
- drivers and calculation of the resuling efforts</p>
-<p>Two different effort drivers are supported:</p>
-<ul>
- <li><b>&quot;By Key&quot; Effort Drivers</b> <br>
- listing different alternatives all related to a specific effort (e.g. a high-complexity
- subprocess implementation might take 10 days whereby a medium-complex implementation
- might only require 5 days)</li>
- <li><b>&quot;By Quantity&quot; Effort Drivers</b><br>
- where a &quot;per unit&quot; effort has to be multiplied with the volume expected
- (e.g. number of process runtime reports to be created for the process model)<br>
- </li>
-</ul>
-<h2>Configuring Effort Drivers</h2>
-<p>Effort drivers can be specified in the <b>Effort Drivers</b> tab of the
-<b>Effort Planning</b> subpage in the process model property page:</p>
-<p class="image"><a href="images/effort-drivers_orgSize.png" target="_blank">
-<img src="images/effort-drivers.png" alt="Effort Drivers"></a></p>
-<p>A predefined list of &quot;By Key&quot; and &quot;By Quantity&quot; drivers
- for all model element types is provided for every model. This list can be changed
- according to the project needs.</p>
-<h3>Creating &quot;By Key&quot; Drivers</h3>
-<p>A new &quot;By Key&quot; driver for a process model lement can be created by
- selecting the <b>New &quot;By Key&quot; Driver</b> option in the popup-meu for
- the corresponding model element node in the <b>Effort Driver</b> table:</p>
-<p align="center"><img src="images/create-driver-popup-menu.png" alt="Create Driver Popup Menu"></p>
-<h3>Creating &quot;By Quantity&quot; Drivers</h3>
-<p>A new &quot;By Quantity&quot; driver for a process model lement can be created
- by selecting the <b>New &quot;By Quantity&quot; Driver</b> option in the popup-meu
- for the corresponding model element node in the <b>Effort Driver</b> table:</p>
-<p align="center"></p>
-<p align="center"><img src="images/new-by-quantity-driver-popup-option.png" alt=""></p>
-<h3>Editing Effort Drivers</h3>
-<p>You can edit names or values for the different project phases simply by selecting
- and editing the corresponding table cells in the <b>Effort Drivers</b> table:</p>
-<p align="center"><img src="images/editing-driver-values.png" alt=""></p>
-<p>New keys for &quot;By Key&quot; drivers can be added using the <b>New Key</b>
- option in the popup-menu for this driver:</p>
-<p align="center"><img src="images/new-key-popup-menu.png" alt=""></p>
-<h2></h2>
-<h2>Deleting Effort Drivers</h2>
-<p>Effort drivers and keys of &quot;By Key&quot; drivers can be deleted by using
- the corresponding <b>Delete</b> options in the popup-menus for drivers and keys.</p>
-<p align="center"><img src="images/delete-driver-popup-menu.png" alt=""></p>
-<h2>Editing Effort Driver Contributions</h2>
-<p>Once all effort drivers has been defined corresponding GUI elements to enter
- concrete effort distributions for all corresponding effort drivers will occur
- in the <b>Effort Planning</b> subpage of the property pages for all model elements
- effort drivers have been specified, e.g. the process model itself or</p>
-<p align="center"><img src="images/effort-driver-values-model.png" alt=""></p>
-<p>activities</p>
-<p align="center"><img src="images/effort-driver-values-activity.png" alt=""></p>
-<p>Hereby, &quot;By Key&quot; drivers will occur as combo boxes containing all
- keys and &quot;By Value&quot; drivers will occur as entry field to enter the
- concrete value of an effort driver.</p>
-<h2>Calculating Project Effort</h2>
-<p>Once all effort driver contributions are entered in the model, the total effort
- can be obtained by pressing the <b>Calculate Effort</b> in the <b>Effort</b>
- tab of the <b>Effort Planning</b> subpage of the process model property page:</p>
-<p class="image"><a href="images/effort-calculation_orgSize.png" target="_blank">
-<img src="images/effort-calculation.png" alt=""></a></p>
-<h3>Drag &amp; Drop Into Excel</h3>
-<p>The entire table in the <b>Effort</b> tab of the <b>Effort Planning</b>
- subpage of the process model property page can be dragged into a table in Microsoft
- Excel to perform additional calculations (e.g. multiply efforts with resource
- costs to obtain cost estimates).</p>
-<p align="center"><img src="images/excel.png" alt=""></p>
-<script language="JavaScript">
-<!--
-writeFooter();
--->
-</script>
-</body>
-</html>
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/property-page-authorization.html b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/property-page-authorization.html
deleted file mode 100644
index 3d9ced1..0000000
--- a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/property-page-authorization.html
+++ /dev/null
@@ -1,472 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
-<html>
-<head>
-<title>Authorization</title>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<link rel="stylesheet" type="text/css" href="../../styles/carnot.css"
- title="Style">
-<script language="JavaScript" src="../../styles/naviLine.js"
- type="text/javascript"></script>
-</head>
-<body>
-<script language="JavaScript" type="text/javascript">
-<!--
- writeNavigation("Project Effort Calculation",
- "PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/toc.html","mg-copy-paste-elements.html",
- "process-effort-calculation.html","../../toc.html",
- "Business Analyst Handbooks","mg-preface.htm",
- "The Modeling Guide","mg-modeler-preface.html","The Process Workbench");
- -->
-</script>
-
-<h1>Authorization</h1>
-<ul>
- <li><a href="#intro">Declarative Authorization via Model
- Elements and Roles</a></li>
- <li><a href="#relation">Influence of Organizational Relations
- on Declarative Security</a></li>
- <li><a href="#scoped">Declarative Security in a Scoped Environment</a></li>
- <li><a href="#prop">Setting Authorization in Model Element Property
- Pages</a></li>
- <li><a href="#security">Overwriting Default Values of
- Declarative Security Grants</a></li>
-</ul>
-<h2 id="intro">Declarative Authorization via Model Elements and
-Roles</h2>
-<p>In addition to implicit permissions like:</p>
-<ul>
- <li>permission to start a process via manual trigger</li>
- <li>permission to activate and complete an activity via performer
- assignment</li>
- <li>general administrative permissions for the Administrator role</li>
-</ul>
-<p>for the runtime other permissions are specified on model elements
-and assigned to a role or organization.</p>
-<p>These permissions are evaluated for runtime instances of the
-model elements. Furthermore, read and modification permissions can be
-specified for model elements themselves. All permissions, even those to
-access model elements in the modeling environment, can be controlled by
-assigning users to appropriate roles through the directory service (e.g.
-LDAP, MS Active Directory, @productname@ internal user database). Note, that
-permissions cannot be assigned to conditional performers.</p>
-<h3>Enable Security Check</h3>
-<p>To make declarative security effective, make sure that the
-according service guarded property (<a
- href="PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/handbooks/operation/properties/ag-appendix-properties-1.htm#queryGuarded"><i>xxx</i>Service.Guarded</a>)
-is set to <tt>true</tt> (default value).</p>
-<h2 id="relation">Influence of Organizational Relations on
-Declarative Security</h2>
-<p>In case a declarative security grant is modeled for an
-organization, it is implicitly granted for all users having grants for
-one or more roles or organizations with the following properties:</p>
-<ul>
- <li>an organization is a direct or indirect "Part Of" this
- organization.</li>
- <li>a role has a "Works For" association to a role being a direct
- or indirect "Part Of" this organization.</li>
- <li>a role has a "Manager Of" association to a role being a direct
- or indirect "Part Of" this organization.</li>
-</ul>
-<h3>Example</h3>
-<p>For example in the following organizational structure, whenever a
-declarative security grant is modeled for the organization <strong>O1</strong>,
-it will implicitly be granted for all users having grants for
-organization <strong>O3</strong>, <strong>O2</strong> and the roles <strong>Role
-2</strong> and <strong>R1</strong>.</p>
-<p class="image"><img src="images/declarative-security-example.png"
- alt="Organizational Structure"> <br>
-<strong>Figure:</strong> Example Organizational Structure</p>
-<h2 id="scoped">Declarative Security in a Scoped Environment</h2>
-<p>The effect of authorization set for scoped participants
-depends on the model element:</p>
-<ul>
- <li><a href="#dataL">Data</a></li>
- <li><a href="#actL">Activities</a></li>
- <li><a href="#process">Process Definitions</a></li>
-</ul>
-<h4 id="dataL">Data</h4>
-<p>If a grant is given to a scoped participant for a data element,
-then all users assigned to this participant do have execution permission.
-The department is not taken into account.</p>
-<h4 id="actL">Activities</h4>
-<p>Each activity instance stores the department information.
-Thus, it depends on the concrete activity instance, if a user has execution
-permission. In that case, the grant including the department has to match the
-grant permission and the department of the activity instance.</p>
-<h4 id="processL">Process Definitions</h4>
-<p>Department information is not stored in the process instance.
-Instead, the relevant process data defining the department
-is evaluated on demand.</p>
-<p>For example, a process definition permission is granted to a
-role <strong>Role 1</strong>. This role is a scoped role with scope data
-<strong>Data 1</strong> defining the department. If the value of
-<strong>Data 1</strong> is
-executed for a specific process instance, the department required to
-get the execution permission is evaluated.</p>
-
-<h2 id="prop">Setting Authorization in Model Element Property Pages</h2>
-<p>You can set authorization in the property dialogs of the
-following model elements:</p>
-<ul>
- <li><a href="#data">data</a></li>
- <li><a href="#process">process definitions</a></li>
- <li><a href="#activities">activities</a></li>
-</ul>
-<p>In the <strong>Permission</strong> part, all permissions possible
-for the element are listed. Beneath this list, the possible participants
-for a selected permission are displayed with checkboxes. Possible
-participants are all roles, organizations, the administrator and the
-participant pertaining to an activity (<strong>Owner</strong>).
-Additionally the <strong>All</strong> option is provided to give grant
-to everyone. Grants like <strong>Owner</strong> and <strong>All</strong>,
-not pertaining to specific participants, are displayed cursive.</p>
-<p>The permission set by default, is also enabled per default in the
-dialog. It is marked as <tt>default</tt> in brackets after the grant
-name.</p>
-<p>To remove permission from all participants, deselect all provided
-entries.</p>
-<p class="note"><strong>Note</strong><br>
-Be aware that if disabling all permissions and closing the dialog, the
-permission is reset to the default permission and persisted again. After
-reopening the dialog you notice the default permission selected again.</p>
-<p>Please also refer to the section <a href="#security">Overwriting
-default Values of Declarative Security Grants</a> for details on overwriting
-default values.</p>
-<h3>Setting Authorization Properties</h3>
-<p>To set the authorization in the properties dialog of an element:</p>
-<ul>
- <li>In the property page select <strong>Authorization</strong>.</li>
- <li>In the <strong>Authorization</strong> pane you see a list with
- the permissions possible for the element.</li>
- <li>Beneath this list, the possible participants for a selected
- permission are displayed with checkboxes. Enable the checkbox for the
- participant to give the permission to.</li>
-</ul>
-<p>If no participant is selected, the permission is given to the
-default participant provided for this action. The administrator is
-always granted, regardless of the grants set for the authorization
-property.</p>
-<p class="image"><img src="images/bc-authorization-property.png"
- alt="Property Page - Authorization"> <br>
-<strong>Figure:</strong> Setting the Authorization in the Property Page.</p>
-<h3 id="data">Authorization for Data</h3>
-<p>The data property pages provide the following permissions:</p>
-<table>
- <tr>
- <th width="270">Permission</th>
- <th>Default Participant</th>
- <th>Description</th>
- </tr>
- <tr>
- <td>Read Data Values</td>
- <td>All</td>
- <td>Gives permission to get direct data access used in the
- Reporting runtime Data Value View.</td>
- </tr>
- <!-- not implemented yet
- <tr>
- <td>Modify Data Values</td>
- <td>All</td>
- <td>Gives permission to modify data values using APIs.</td>
-
- </tr>-->
-</table>
-<p class="image"><img src="images/bc-authorization-data.png"
- alt="Authorization - Data"> <br>
-<strong>Figure:</strong> Setting the Authorization for Data.</p>
-<p>Please note that this permission is momentarily only implemented
-for direct data access used in Reporting runtime views. Please refer to
-the chapter <a
- href="PLUGINS_ROOT/org.eclipse.stardust.docs.reporting/html/reporting/security.html">
-Declarative Security Usage in @productname@ Services API</a> of the <a
- href="PLUGINS_ROOT/org.eclipse.stardust.docs.reporting/html/reporting/toc.html">
-Business Analysis and Reporting Component</a> guide for detailed information
-on security usage in Reporting.</p>
-
-<h3 id="process">Authorization for Process Definitions</h3>
-<p>The process definition property pages provide the following
-permissions:</p>
-<table>
- <tr>
- <th width="270">Permission</th>
- <th>Default Participant</th>
- <th>Description</th>
- </tr>
- <tr>
- <td>Abort Process Instances</td>
- <td>Administrator</td>
- <td>Gives permission to abort the process instance through
- Administration perspective and APIs.</td>
- </tr>
- <tr>
- <td>Modify Process Instances</td>
- <td>Administrator</td>
- <td>Gives permission to modify processes (e.g. priorities)
- through Business Control Center perspective and APIs.</td>
- </tr>
- <tr>
- <td>Delete Process Instances</td>
- <td>Administrator</td>
- <td>Gives permission to delete processes through Administration
- perspective and APIs.</td>
- </tr>
- <tr>
- <td id="readPI">Read Process Instance Data</td>
- <td>All</td>
- <td>
- <ul>
- <li>Gives permission to to get all the processes the user is
- authorized to read, find first process and get process instance count
- through APIs.</li>
- <li>Allows viewing of processes for which the user has this
- authorization in the following Portal components:
- <ul>
- <li>Business Control Center Perspective - Process Manager View
- (Selected Processes)</li>
- <li>Business Control Center Perspective - Process Search View
- (Activities Search)</li>
- <li>Process Details View - Process History</li>
- <li>Workflow Execution Perspective - Activity Search</li>
- </ul>
- </li>
- <li>Allows viewing process instance data in the following
- Reporting views:
- <ul>
- <li>Process Instances View</li>
- <li>Process Instance State View</li>
- <li>Activity Instances View</li>
- <li>Activity Instances State Change View</li>
- <li>Process Data Values View</li>
- <li>Organization Worklists View</li>
- </ul>
- </li>
- </ul>
- </td>
- </tr>
- <tr>
- <td>Manage Event Handlers</td>
- <td>Administrator</td>
- <td>Gives permission to manipulate and trigger processes through
- Administration perspective and APIs.</td>
- </tr>
-</table>
-<p class="image"><img src="images/bc-authorization-process.png"
- alt="Authorization - Process"> <br>
-<strong>Figure:</strong> Setting the Authorization for a Process
-Definition.</p>
-<h3 id="activities">Authorization for Activities</h3>
-<h4>Non-interactive activities</h4>
-<p>The activity property pages provide the following permissions:</p>
-<table>
- <tr>
- <th width="270">Permission</th>
- <th>Default Participant</th>
- <th>Description</th>
- </tr>
- <tr>
- <td>Delegation to other users</td>
- <td>All</td>
- <td>Gives permission to delegate to participant, default
- performer and user. It also gives permission to suspend an activity
- through @productname@ Portal and APIs.</td>
- </tr>
- <tr>
- <td>Delegation to other departments</td>
- <td>Administrator</td>
- <td>Gives permission to delegate an activity to other departments
- through @productname@ Portal and APIs.</td>
- </tr>
- <tr>
- <td>Manage Event Handlers</td>
- <td>All</td>
- <td>Gives permission to manipulate and trigger the event handler.</td>
- </tr>
- <tr>
- <td>Read Activity Instance Data</td>
- <td>All</td>
- <td>
- <ul>
- <li>Gives permission to read first activity instance, get all
- activity instances the user is authorized to read and its count
- through APIs.</li>
- <li>Allows viewing of activities for which the user has this
- authorization plus the authorization <tt>Read
- Process Instance Data</tt> in the following Portal components:
- <ul>
- <li>Business Control Center Perspective - Process Manager View
- (Selected Activities)</li>
- <li>Business Control Center Perspective - Process Search View
- (Activities Search)</li>
- <li>Process Details View - Process History</li>
- <li>Workflow Execution Perspective - Activity Search</li>
- </ul>
- </li>
- <li>Allows viewing activity instance data in the following
- Reporting views:
- <ul>
- <li>Activity Instances View</li>
- <li>Organization Worklists View</li>
- <li>Activity Instances State Change View</li>
- </ul>
- </li>
- </ul>
- </td>
- </tr>
- <tr>
- <td>Abort Activity Instances</td>
- <td>Administrator</td>
- <td>Gives permission to abort an activity instance through
- @productname@ Portal and APIs.</td>
- </tr>
-</table>
-<p>Please note that additionally to the participant given the
-permission for aborting activity instances, the administrator always has
-the right to abort.</p>
-<p class="image"><img src="images/bc-authorization-activity.png"
- alt="Authorization - Activities"> <br>
-<strong>Figure:</strong> Setting the Authorization for a non-interactive
-Activity.</p>
-<h4>Delegation to other departments</h4>
-<p>The entitlement <strong>Delegation to other departments</strong>
-allows the user to delegate work from one department to another.</p>
-<h4>Delegation to other users vs. Delegation to other departments</h4>
-<p>To determine if an activity delegation succeeds with the
-"Delegation to other users" permission, or requires the "Delegation to
-other departments" permission, depends on the following cases. In case
-the input for delegation is:</p>
-<ol>
- <li>the source participant, represented by a source participant
- and a source department</li>
- <li>the target participant, represented by a target participant
- and a target department</li>
- <li>the default performer of the activity, represented by a
- participant</li>
-</ol>
-<p>then the delegation permissions needed are:</p>
-<ul>
- <li>Delegation is only allowed if both, the source and target
- participant are children of the default participant.</li>
- <li>In case the source and target department share the same parent
- department at default participant level, the delegation only requires
- the "Delegation to other users" permission.</li>
- <li>If the source and target department do not share the same
- parent department at default participant level, the delegation requires
- the "Delegation to other departments" permission.</li>
-</ul>
-
-<h4>Activities implemented as interactive activities</h4>
-<p>Activities that have been implemented as interactive activities
-in the Development perspective, additionally can have the grant <strong>Owner</strong>,
-which represents the participant associated with the activity. This is
-useful for example to restrict the abort functionality for subprocess
-activities. Thus it can be avoided that subprocess activities are
-aborted and thus the whole process is terminated.</p>
-<p>If the activity instance is in the participant worklist of a
-scoped participant, the <strong>Owner</strong> grant is extended to the
-worklist visibilities. The participant and department of the activity
-will then have to match with the logged-in user in order to allow the
-action.</p>
-<p>The property pages for activities implemented as interactive
-activities, provide the following permissions and default participant
-settings:</p>
-<table>
- <tr>
- <th width="270">Permission</th>
- <th>Default Participant</th>
- <th>Description</th>
- </tr>
- <tr>
- <td>Delegation to other users</td>
- <td>All</td>
- <td>Gives permission to delegate to participant, default
- performer and user. It also gives permission to suspend an activity
- through @productname@ Portal and APIs.</td>
- </tr>
- <tr>
- <td>Delegation to other departments</td>
- <td>Administrator</td>
- <td>Gives permission to delegate an activity to other departments
- through @productname@ Portal and APIs.</td>
- </tr>
- <tr>
- <td>Manage Event Handlers</td>
- <td>All</td>
- <td>Gives permission to manipulate and trigger the event handler.</td>
- </tr>
- <tr>
- <td>Read Activity Instance Data</td>
- <td>All</td>
- <td>
- <ul>
- <li>Gives permission to read first activity instance, get all
- activity instances the user is authorized to read and its count
- through APIs.</li>
- <li>Allows viewing of activities for which the user has this
- authorization plus the authorization <tt>Read
- Process Instance Data</tt> in the following Portal components:
- <ul>
- <li>Business Control Center Perspective - Process Manager View
- (Selected Activities)</li>
- <li>Business Control Center Perspective - Process Search View
- (Activities Search)</li>
- <li>Process Details View - Process History</li>
- <li>Workflow Execution Perspective - Activity Search</li>
- </ul>
- </li>
- <li>Allows viewing activity instance data in the following
- Reporting views:
- <ul>
- <li>Activity Instances View</li>
- <li>Organization Worklists View</li>
- <li>Activity Instances State Change View</li>
- </ul>
- </li>
- </ul>
- </td>
- </tr>
- <tr>
- <td>Abort Activity Instances</td>
- <td>Owner</td>
- <td>Gives permission to abort an activity instance through
- @productname@ Portal and APIs.</td>
- </tr>
-</table>
-<p>Please note that additionally to the participant given the
-permission for aborting activity instances, the administrator always has
-the right to abort.</p>
-<p class="image"><img src="images/bc-authorization-int-act.png"
- alt="Authorization - Activities"> <br>
-<strong>Figure:</strong> Setting the Authorization for an interactive
-Activity.</p>
-<h2 id="security">Overwriting default Values of Declarative
-Security Grants</h2>
-<p>Declarative grant default values are configurable at runtime by
-setting the following configuration parameters in your server-side <tt>carnot.properties</tt>
-file:</p>
-<ul>
- <li>InfinityBpm.Engine.Authorization.DefaultPermissions.ActivityInstance.Abort</li>
- <li>InfinityBpm.Engine.Authorization.DefaultPermissions.ProcessInstance.Abort</li>
-</ul>
-<p>This allows to overwrite the default values (empty value, <strong>OWNER</strong>)
-of the declarative grants for activity instance abortion and process
-instance abortion respectively. As values you can set the ID of a role
-or organization pertaining to the process model or a predefined meta
-role like <strong>ALL</strong> or <strong>OWNER</strong>. The value can
-contain a comma-separated list. Note that no whitespaces like spaces or
-tabs are allowed between the listed items.</p>
-<p>For example, setting</p>
-<pre>InfinityBpm.Engine.Authorization.DefaultPermissions.ActivityInstance.Abort = Engineer,Developer</pre>
-<p>will change the grant of the <strong>Abort Activity
-Instance</strong> to the roles with ID <tt>Engineer</tt> and <tt>Developer</tt>.</p>
-<p>Setting</p>
-<pre>InfinityBpm.Engine.Authorization.DefaultPermissions.ProcessInstance.Abort = ALL</pre>
-<p>would change the grant of <strong>Abort Process Instance</strong>
-to all model roles and organizations.</p>
-
-<script language="JavaScript" type="text/javascript">
-<!--
- writeFooter();
---></script>
-</body>
-</html>
-