summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorVrishali Doke2012-08-28 05:42:36 (EDT)
committer Stephan Born2012-08-28 05:42:36 (EDT)
commitf57739085481ad13a93f2d4edd9ddbd4d403f4d0 (patch)
tree1a432d1ab0389ea31a82a7ee685cc9416148551b
parent86390812fa915e009b39703fcc8dee6cb9ccb18c (diff)
downloadorg.eclipse.stardust.documentation-f57739085481ad13a93f2d4edd9ddbd4d403f4d0.zip
org.eclipse.stardust.documentation-f57739085481ad13a93f2d4edd9ddbd4d403f4d0.tar.gz
org.eclipse.stardust.documentation-f57739085481ad13a93f2d4edd9ddbd4d403f4d0.tar.bz2
CRNT-25597 - Adjusted TOC and files for Pepper structure
git-svn-id: http://emeafrazerg/svn/ipp/product/trunk/stardust/documentation@58724 8100b5e0-4d52-466c-ae9c-bdeccbdeaf6b
-rw-r--r--org.eclipse.stardust.docs.analyst/analysttoc.xml29
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/mg-defdesk-14.htm112
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/mg-defdesk-16.htm124
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/mg-defdesk-18.htm191
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/mg-defdesk-5.htm4
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/mg-internationalization.html277
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/mg-modeler-views.html6
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/mg-modelreport.htm42
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/mg-preferences.html302
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/model-views/views-bookmark.html49
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/model-views/views-cheat.html56
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/model-views/views-outline.html4
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/model-views/views-repository.html49
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/model-views/views-simplify.html64
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/model-views/views-traversal.html46
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pattern-support.html183
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-connect-sybol.htm100
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-events.htm214
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-gateways.htm100
19 files changed, 432 insertions, 1520 deletions
diff --git a/org.eclipse.stardust.docs.analyst/analysttoc.xml b/org.eclipse.stardust.docs.analyst/analysttoc.xml
index 40b36a1..a1ca2c1 100644
--- a/org.eclipse.stardust.docs.analyst/analysttoc.xml
+++ b/org.eclipse.stardust.docs.analyst/analysttoc.xml
@@ -10,18 +10,13 @@
Contributors:
SunGard CSA LLC - initial API and implementation and/or initial documentation
-->
-<toc label="Business Analyst Handbooks" link_to="toc.xml#analysttoc">
- <topic label="Analyst Modeling Guide" href="html/handbooks/modelling_analyst/mg-preface.htm">
+<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 Analyst Perspective" href="html/handbooks/modelling_analyst/mg-modeler-views.html" >
- <topic label="Outline view" href="html/handbooks/modelling_analyst/model-views/views-outline.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 label="Cheat Sheet View" href="html/handbooks/modelling_analyst/model-views/views-cheat.html"/>
- <topic label="@productnameonly@ Process Model Repository" href="html/handbooks/modelling_analyst/model-views/views-repository.html"/>
- <topic label="@productnameonly@ Process Model Bookmarks" href="html/handbooks/modelling_analyst/model-views/views-bookmark.html"/>
- <topic label="@productnameonly@ Process Model Traversal" href="html/handbooks/modelling_analyst/model-views/views-traversal.html"/>
- <topic label="Simplifying the Modeler View" href="html/handbooks/modelling_analyst/model-views/views-simplify.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"/>
@@ -34,26 +29,24 @@
</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 label="Working with Transitions" href="html/handbooks/modelling_analyst/mg-defdesk-5.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="Specifying Arbitrary Link Types" href="html/handbooks/modelling_analyst/mg-defdesk-14.htm" />
<topic label="Using Annotations" href="html/handbooks/modelling_analyst/mg-defdesk-15.htm" />
- <topic label="Swim Lanes Usage" href="html/handbooks/modelling_analyst/mg-pools-lanes.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 label="Modeling Pattern Support" href="html/handbooks/modelling_analyst/pattern-support.html" />
- <topic label="Retrieving Diagrams from Model Information" href="html/handbooks/modelling_analyst/mg-defdesk-16.htm" />
- <topic href="html/handbooks/modelling_analyst/mg-modelreport.htm" label="Process Model Report">
- </topic>
<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 label="Debugging Process Definitions" href="html/handbooks/modelling_analyst/mg-defdesk-18.htm" />
- <topic label="Native Language Support" href="html/handbooks/modelling_analyst/mg-internationalization.html" />
</topic>
<topic label="@productname@ File Formats">
<topic label="The Model File Format" href="html/handbooks/modelling_analyst/mg-xml-1.htm" />
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/mg-defdesk-14.htm b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/mg-defdesk-14.htm
deleted file mode 100644
index 291836f..0000000
--- a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/mg-defdesk-14.htm
+++ /dev/null
@@ -1,112 +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>Specifying Arbitrary Link Types</title>
-<script language="JavaScript" src="../../styles/naviLine.js"
- type="text/javascript"></script>
-</head>
-<body>
-<script language="JavaScript" type="text/javascript">
-<!--
- writeNavigation("Using Annotations","PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/toc.html",
- "mg-defdesk-10.htm","mg-defdesk-15.htm",
- "../../toc.html","Business Analyst Handbooks",
- "mg-preface.htm","The Modeling Guide",
- "mg-modeler-preface.html","The Process Workbench");
- -->
-</script>
-
-<h1>Specifying Arbitrary Link Types</h1>
-<p>You can establish arbitrary links between two resources by
-connecting these with a graphical link. This link does not have any
-impact on the runtime behavior of a deployed process model but may be
-used to emphasize semantic relationships at modeling time.</p>
-<p>Each link has a type being characterized by its:</p>
-<ul>
- <li>name,</li>
- <li>semantics,</li>
- <li>left and right resource types participating in this link,</li>
- <li>left and right roles,</li>
- <li>left and right cardinalities and</li>
- <li>attributes for its graphical representation.</li>
-</ul>
-<p>The predefined link between a role belonging to an organization
-and this organization is such a link type, too. The modeler can,
-however, define his own link types which suit the semantics of his
-model.</p>
-<h2>Creating a New Link Type</h2>
-<p>To create a new link type:</p>
-<ul>
- <li>Select the model element in the <strong>Outline</strong>
- view and in its pop-up menu choose the option <strong>New Link
- Type</strong>.</li>
- <li>In the properties dialog of the new link type appearing on
- the screen, enter the required parameters.</li>
-</ul>
-<p class="image"><img src="images/mg-defdesk-65.png" alt=""> <br>
-<strong>Figure:</strong> Creation of a Link Type</p>
-<p>The new link type is now visible in the <strong>Outline
-View</strong>:</p>
-<p class="image"><img src="images/mg-link-type-in-outline.png"
- alt="" /> <br>
-<strong>Figure:</strong> The new Link Type in the Outline View</p>
-<h3>General Parameters</h3>
-<p>The following <strong>Source Types</strong> and <strong>Target
-Types</strong> are provided:</p>
-<ul>
- <li>Activity</li>
- <li>Data</li>
- <li>Role</li>
- <li>Process Definition</li>
- <li>Transition</li>
- <li>Organization</li>
- <li>Participant</li>
-</ul>
-<p>For the <strong>Source Cardinality</strong> and the <strong>Target
-Cardinality</strong> choose:</p>
-<ul>
- <li>*:1</li>
- <li>*:N</li>
-</ul>
-<h3>Visualization</h3>
-<p>The properties dialog of the link type also allows you to
-choose between different standard visualizations of the links, offering
-different colors, lines and shapes appearing at both ends of the link.
-To explore the possibilities and choose the visualization you wish</p>
-<ul>
- <li>switch to the visualization properties by clicking on <strong>Visualization</strong>
- on the left side of the dialog,</li>
- <li>then fill in the fields with the options available in the
- pull-down menus.</li>
-</ul>
-<p class="image"><img src="images/mg-defdesk-66.png" alt=""> <br>
-<strong>Figure:</strong> Visualization Properties for Link Types</p>
-<h3>Using Custom Link Types</h3>
-<p>Once defined, each user-defined link type can be used as a
-predefined link type to establish graphical connections and
-corresponding links in the resource part of a workflow model. @productname@
-will automatically add your link types to the resource symbol context
-menus and will maintain the constraints specified by the link type's
-cardinalities and types.</p>
-<p>The pop-up menu of the role in our example has been
-supplemented with the link <tt>Supervision</tt>. When linked to another
-role the relationship between the two participants will be represented
-as shown in the figures below.</p>
-
-<p class="image"><img src="images/mg-connect-roles-link-type.png"
- alt=""> <br>
-<strong>Figure:</strong> Use of User-Defined Link Types in Diagrams</p>
-<p class="image"><img src="images/mg-defdesk-68.jpg" alt=""> <br>
-<strong>Figure:</strong> Representation of Generic Links in Diagrams</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-16.htm b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/mg-defdesk-16.htm
deleted file mode 100644
index 68f009d..0000000
--- a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/mg-defdesk-16.htm
+++ /dev/null
@@ -1,124 +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>Retrieving Diagrams from Model Information</title>
-<script language="JavaScript" src="../../styles/naviLine.js"
- type="text/javascript"></script>
-</head>
-<body>
-<script language="JavaScript" type="text/javascript">
-<!--
- writeNavigation("Process Model Report","PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/toc.html",
- "pattern-support.html","mg-modelreport.htm",
- "../../toc.html","Business Analyst Handbooks",
- "mg-preface.htm","The Modeling Guide",
- "mg-modeler-preface.html","The Process Workbench");
- -->
-</script>
-<h1>Retrieving Diagrams from Model Information</h1>
-<p>@productname@ offers several reverse-engineering facilities which allow the
-modeler to retrieve information from the model and have <a
- href="model-views/views-diagrams.html">diagrams</a> - or their parts -
-reconstructed in new diagrams in an automated way.</p>
-<h2>Dragging Elements from the Tree Views</h2>
-<p>The easiest way to use already defined elements of a model is to drag
-an individual component (an activity, a participant, an application, etc.) from
-the <strong>Outline</strong> view area to the diagram canvas and drop it there.</p>
-<p class="image"><img src="images/mg-defdesk-70.png" alt="Drag and Drop">
-<br>
-<strong>Figure:</strong> Drag-and-Drop Functionality</p>
-<p>After you have dragged a symbol to the diagram canvas, all the
-connections to other symbols present in this diagram will be retrieved from the
-model repository and restored automatically.</p>
-<h2>Creating Organization Hierarchies</h2>
-<p>Entire hierarchies or their branches can be reconstructed in a diagram
-to visualize the organizational structures defined in the model. To have a
-diagram of an organization hierarchy generated:</p>
-<ul>
- <li>Right-click a white area in the diagram of the model to bring up
- a pop-up menu.</li>
- <li>Choose the option <strong>Create Organization Hierarchy</strong>.
- </li>
- <li>Select the organization you wish to be the top of your hierarchy
- in the appearing dialog.</li>
- <li>Close the dialog by pushing <strong>OK</strong>.</li>
-</ul>
-
-<p class="image"><img src="images/mg-defdesk-71.png" alt=""> <br>
-<strong>Figure:</strong> Generating a Diagram visualizing an
-Organization Hierarchy</p>
-
-<p>If there are more than one organizations in the diagram, you see
-a list of organizations to choose from, as shown below:</p>
-<p class="image"><img src="images/mg-defdesk-71a.png" alt="">
-<br>
-<strong>Figure:</strong>Organization Hierarchy for more than one
-organizations</p>
-
-<h2>Creating Activity/Transition Graphs</h2>
-<p>Entire activity/transition graphs can be reconstructed in a diagram to
-visualize the series of activities defined in the model. To have a diagram with
-an activity graph generated:</p>
-<ul>
- <li>Right-click a white area in the diagram of a process definition
- to bring up a pop-up menu.</li>
- <li>Choose the option <strong>Create Activity Graph</strong><em>.</em>
- </li>
- <li>Select the activity you wish to be the starting point of your
- activity graph in the appearing dialog.</li>
- <li>Click <strong>OK</strong> to close the dialog.</li>
-</ul>
-<p class="image"><img src="images/mg-defdesk-72.png" alt=""> <br>
-<strong>Figure:</strong> Generating a Diagram visualizing an Activity/Transition
-Graph</p>
-<h3>Restrictions in Lanes and Pools</h3>
-<p>Note that the option <strong>Create activity graph </strong> is available
-only if you are working on expanded lanes. If you are working on one or more
-collapsed lanes, <strong>Create activity graph </strong> is not available.</p>
-<p>Also note that in the <strong>Create activity graph </strong> dialog box,
-the <strong>OK</strong> button is enabled only if you select an activity in the
-dialog box. The <strong>OK</strong> button is disabled if no activity is
-selected in the dialog box.</p>
-<h2>Traversing a Model</h2>
-<p>The model traversal allows to traverse a path (a linear structure)
-starting from a selected element in a diagram or the <strong>Outline </strong>view.</p>
-<p>The <a href="model-views/views-traversal.html">@productname@ Model
-Traversal View</a> updates its content each time you perform one step forward in
-your traversal path by double-clicking a selected element in the list of <strong>Linked
-Objects</strong>. To return to your previous position, push the <strong>Pop</strong>
-button in the view. When your traversal path has been determined, select the
-elements and click the diagram canvas to place them in the diagram one by one.</p>
-<p>&nbsp;</p>
-<p class="image"><img src="images/mg-model-traversal.png"
- alt="Generating a Traversal Path Diagram"> <br>
-<strong>Figure:</strong> Generating a Traversal Path Diagram</p>
-<!-- <h2 >
- Retrieving a Single Symbol</h2>
-<P >
-Another reverse engineering feature allows you to browse through available symbols and pick up one to be built in your diagram. This option can be accessed by <span class="Stil2">choosing
-Symbol for model element</span> in the pop-up menu pertaining to the diagram canvas.</P>
-<P >
-Symbols which cannot be used in the current scope - in the current diagram - will not be displayed in the dialog and may not be selected.</P>
--->
-<h2>Restoring Connections from Model</h2>
-<p>Each time a symbol is dragged into the diagram canvas, a check is
-performed on the base of the current model information to find out whether there
-are connections which have not yet been drawn between this symbol and any of the
-symbols visible in this diagram.</p>
-<p>An explicit reload of all connections may, however, prove to be
-necessary. Use the option <strong>Reload Connections</strong> available in the
-diagram canvas pop-up menu. In the upcoming dialog, you can choose which
-connections should be drawn.</p>
-<p class="image"><img src="images/mg-defdesk-75.png" alt=""> <br>
-<strong>Figure:</strong> Reloading Connections from 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-18.htm b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/mg-defdesk-18.htm
deleted file mode 100644
index c4ab5ea..0000000
--- a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/mg-defdesk-18.htm
+++ /dev/null
@@ -1,191 +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>Debugging Process Definitions</title>
-<script language="JavaScript" src="../../styles/naviLine.js" type="text/javascript"></script>
-</head>
-<body>
-<script language="JavaScript" type="text/javascript">
-<!--
- writeNavigation("Native Language Support","PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/toc.html",
- "mg-deploy-model.html","mg-internationalization.html" ,
- "../../toc.html","Business Analyst Handbooks",
- "mg-preface.htm","The Modeling Guide",
- "mg-modeler-preface.html","The Process Workbench");
- -->
-</script>
-
-<h1>Debugging Process Definitions</h1>
-<p>Process definitions can be - even before they have been deployed - debugged in the
-modeling environment. To work with the debugger change to the debug perspective by
-choosing <strong>Window</strong> &gt; <strong>Open Perspective</strong> &gt; <strong>Other...</strong>
-and from the list select the <strong>@productname@ Test Perspective</strong> perspective.</p>
-<p>It is only possible to debug your model if it is consistent. A consistency check
-will be performed automatically with the start of the debugger. Note that the model should
-not be changed during debugging, because the engine will not notice a model change after
-the debugging started.</p>
-<p>For information about debugging in multi-model environment, please refer to the
-section <a href="PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/handbooks/modelling/mg-defdesk-18.htm#debug">
-Debugging in Multi-model Environment</a> of the
-<a href="PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/handbooks/handbooks.htm">Developer Handbook.</a>
-</p>
-
-<h2>Starting the Debugger</h2>
-<p>There are several possibilities to start the debugger:</p>
-<ul>
- <li><a href="#d_config">from the main menu by setting up a configuration</a></li>
- <li><a href="#d_noconfig">from the main menu with the predefined
- configuration</a></li>
- <li><a href="#d_diagram">from the diagram</a></li>
- <li><a href="#d_outline">from the outline view</a></li>
-</ul>
-
-<h4 id="d_config">Starting the Debugger by setting up a Configuration</h4>
-<p>In the main menu select the debug icon (the green bug) and choose <strong>Open
-Debug Dialog...</strong> from the pull-down menu.</p>
-<p class="image"><img src="images/debug-open-debug-dialog.png"
- alt="Open the Debug Dialog"> <br>
-<strong>Figure:</strong> Open the Debug Dialog</p>
-<p>A dialog comes up in which you set the configurations for your debug application.
-To create a new debug configuration:</p>
-<ol>
- <li>Select <strong>@productnameonly@ Process Model</strong> on the left side of the
- dialog.</li>
- <li>Click the new configuration icon <img src="images/debug-config-icon.png"
- alt="">.</li>
- <li>Choose the <strong>Main</strong> tab and fill in the name for the debug
- configuration, the project name, the model name and the process you want to debug.</li>
- <li>Click <strong>Apply</strong>.</li>
-</ol>
-<p class="image"><a href="images/mg-debug-config_orgSize.png" target="_blank"> <img
- src="images/mg-debug-config.png" alt=""></a> <br>
-<strong>Figure:</strong> Debugger Configurations</p>
-<p>Now press the <strong>Debug</strong> button.</p>
-<h4 id="d_noconfig">Starting the Debugger with the @productname@ predefined Configuration</h4>
-<p>In the main menu select the debug icon and choose <strong>Debug As &gt;
-Debug @productnameonly@ Process</strong> from the pull-down menu.</p>
-<p>&nbsp;</p>
-<p class="image"><img src="images/mg-start-debug-1.png" alt=""> <br>
-<strong>Figure:</strong> Starting the Debugger with predefined Configuration</p>
-
-<h4 id="d_diagram">Starting the Debugger from the Diagram</h4>
-<p>In the open diagram of your process right-click the canvas and select <strong>Debug</strong>
-from the context menu.</p>
-<p>&nbsp;</p>
-<p class="image"><img src="images/mg-start-debug-2.png"
- alt="Starting the Debugger from the Diagram"> <br>
-<strong>Figure:</strong> Starting the Debugger from the Diagram</p>
-<h4 id="d_outline">Starting the Debugger from the Outline View</h4>
-<p>In the Outline View right-click the process to debug and select <strong>Debug</strong>
-from the pop-up menu.</p>
-<p class="image"><img src="images/mg-debug.png"
- alt="Starting the Debugger from the Outline View"> <br>
-<strong>Figure:</strong> Starting the Debugger from the Outline View</p>
-
-<h2>The @productname@ Debug Perspective</h2>
-<p>The Debug Perspective is supplemented with several views to work with:</p>
-<ul>
- <li>the <a href="#debugView">Debug view</a></li>
- <li>the <a href="#worklist">Worklist view</a></li>
- <li>the <a href="#breakpoints">Breakpoints view</a></li>
- <li>the <a href="#variableView">Variables view</a></li>
- <li>the <a href="#diagram">Diagram view</a></li>
-</ul>
-<p>&nbsp;</p>
-<p class="image"><a href="images/mg-defdesk-debug-1_orgSize.png" target="_blank">
-<img src="images/mg-defdesk-debug-1.png" alt=""></a> <br>
-<strong>Figure:</strong> The Debug Perspective</p>
-<h3 id="debugView">The Debug View</h3>
-<p>This view allows you to manage the debugging or running of a process of your
-workflow. It displays the stack frame for the suspended <a
- href="mg-basics-13.htm#activityThread">activity threads</a> for each target you are
-debugging. Each thread in your process appears as a node in the tree. If the thread is
-suspended, its stack frames are shown as child elements.</p>
-<p>To resume the execution of a suspended thread, select the thread or its stack
-frame. Click the <strong>Resume</strong> button (the green arrow) in the toolbar or press
-the F8 key. The thread resumes its execution, and stack frames are no longer displayed for
-the thread.</p>
-<p>For more detailed information on the <strong>Debug</strong> view, refer to the
-Eclipse Help.</p>
-<p>&nbsp;</p>
-<p class="image"><img src="images/mg-defdesk-debug-2.png" alt=""> <br>
-<strong>Figure:</strong> The Debug View</p>
-<h3 id="worklist">The Worklist View</h3>
-<p>The <strong>Worklist</strong> view is grouped by the <a href="mg-basics-9.htm">participants
-and users</a>, who perform the interactive activity instances. When the debugger starts the
-process execution, activities are instantiated. If the execution of the process instance
-arrives at an interactive activity which is assigned to a performer - a role, an
-organisation, a user or a user group - a work item representing an instance of this
-activity is added to the worklist tree of this performer.</p>
-<p>You can activate the current activity instance either by double-clicking on its
-symbol or by clicking on the red-gear icon in the toolbar. In the tree all the roles that
-already performed activites remain visible.</p>
-<p>&nbsp;</p>
-<p class="image"><img src="images/mg-defdesk-debug-3.png" alt="The Worklist View">
-<br>
-<strong>Figure:</strong> The Worklist View</p>
-<h3 id="breakpoints">The Breakpoints View</h3>
-<p>The Breakpoints view lists all the breakpoints you have set in the workbench
-projects. You can double-click a breakpoint to display its location in the editor. In this
-view, you can also enable or disable breakpoints, delete them, or add new ones. For more
-detailed information on working with breakpoints refer to the Eclipse Help.</p>
-<p>&nbsp;</p>
-<p class="image"><img src="images/mg-debug-breakpoints.png" alt=""> <br>
-<strong>Figure:</strong> The Breakpoints View</p>
-<h3 id="variableView">The Variable View</h3>
-<p>In the <strong>Variables</strong> view you can examine the contents of your process
-variables and data values. For more detailed information on debugging variables refer to
-the Eclipse Help.</p>
-<p class="image"><img src="images/mg-defdesk-debug-variables.png" alt=""> <br>
-<strong>Figure:</strong> The Variables View</p>
-<h3 id="diagram">The Diagram View</h3>
-<p>In the <strong>Diagram</strong> view of the debugger you can visually follow the
-process of your debugging. Likewise, the <a href="model-views/views-diagrams.html">diagrams</a>
-in the <strong>Workflow</strong> perspective a graph of activities and its connections is
-displayed. In this view the activities get different colors depending on their current
-state.</p>
-<p>When an activity is in suspended mode, its border is yellow. As soon as it is
-selected the border becomes blue.</p>
-<p class="image"><img src="images/mg-debug-activity-modes.png" alt=""> <br>
-<strong>Figure:</strong> States of Activities shown in different Border Colors</p>
-<p>After the activity is completed, its border becomes green and the activity to be
-executed next becomes yellow bordered. Proceeding the next activity by pushing the green
-arrow button or double-clicking on it in the <strong>@productname@ Worklist</strong> will
-process the data and load the dialog representing the successive interactive activity.</p>
-<p class="image"><img src="images/mg-debug-activity-modes-2.png" alt=""> <br>
-<strong>Figure:</strong> A Completed and a Suspended Activity</p>
-<p></p>
-
-<h3>Starting and stopping the Debugger</h3>
-<p>To start the debugging you can either:</p>
-<ul>
- <li>In the <a href="#debugView">Debug view</a>, select the activity instance to
- start with and press the green arrow button in the tool bar.</li>
- <li>In the <a href="#worklist">Worklist View</a> view, double-click the activity
- in the tree.</li>
-</ul>
-<p>Having arrived at the last activity in process there remains a simulated workflow
-thread in the <a href="#debugView">Debug view</a> to make it possible to review your
-process variables. To complete the process, press the green <strong>Resume</strong> button
-in the toolbar. By using the red square button in the toolbar you can exit the Debugger
-any time.</p>
-<p>You can debug not only linear processes but also processes with splits and joins
-and even subprocesses.</p>
-<p>Be aware that it is only possible to debug one process.</p>
-<p class="image"><img src="images/mg-debug-terminate.png" alt=""> <br>
-<strong>Figure:</strong> Exiting the Debugger</p>
-<h3>Annotation</h3>
-<p>Please notice that if you are working with Swing Panels the panel opens in the
-background behind the Eclipse Workbench and you have to open the workflow-session with the
-taskbar to bring it to the front.</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/mg-defdesk-5.htm
index 9520683..7ac69f3 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/mg-defdesk-5.htm
@@ -6,7 +6,7 @@
<link rel="STYLESHEET" href="../../styles/carnot.css"
charset="ISO-8859-1" type="text/css">
-<title>Working with Transitions</title>
+<title>Working with Gateways</title>
<script language="JavaScript" src="../../styles/naviLine.js"
type="text/javascript"></script>
</head>
@@ -21,7 +21,7 @@
-->
</script>
-<h1>Working with Transitions</h1>
+<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
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/mg-internationalization.html b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/mg-internationalization.html
deleted file mode 100644
index c59bb3b..0000000
--- a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/mg-internationalization.html
+++ /dev/null
@@ -1,277 +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>Native Language Support</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-defdesk-18.htm","",
- "../../toc.html","Business Analyst Handbooks",
- "mg-preface.htm","The Modeling Guide",
- "mg-modeler-preface.html","The Process Workbench");
- -->
-</script>
-
-<h1>Native Language Support for Model Elements</h1>
-<p>Internationalization of model information is provided via Java
-properties files in Native Language Support (NLS) - bundles. It is
-possible to internationalize names and descriptions of model objects.
-All localization information for one model will be contained within one
-NLS bundle.</p>
-<h2>Supported Model Elements</h2>
-<p>Specification of internationalization information is supported
-for the names of the following model elements with the corresponding
-scope ID and the property names, which can be internationalized:</p>
-<table id='id'>
- <tr>
- <th>Model Element</th>
- <th>Scope ID</th>
- <th>Property Name</th>
- </tr>
- <tr>
- <td>Model</td>
- <td>Model</td>
- <td>Description, Name</td>
- </tr>
- <tr>
- <td>Data</td>
- <td>Data</td>
- <td>Description, Name</td>
- </tr>
- <tr>
- <td>Role</td>
- <td>Role</td>
- <td>Description, Name</td>
- </tr>
- <tr>
- <td>Organization</td>
- <td>Organization</td>
- <td>Description, Name</td>
- </tr>
- <tr>
- <td>Conditional Performer</td>
- <td>CondPerformer</td>
- <td>Description, Name</td>
- </tr>
- <tr>
- <td>Application</td>
- <td>Application</td>
- <td>Description, Name</td>
- </tr>
- <tr>
- <td>Process Definition</td>
- <td>Process</td>
- <td>Description, Name</td>
- </tr>
- <tr>
- <td>Diagram</td>
- <td>Diagram</td>
- <td>Name</td>
- </tr>
- <tr>
- <td>Activity</td>
- <td>Activity</td>
- <td>Description, Name</td>
- </tr>
- <tr>
- <td>Trigger</td>
- <td>Trigger</td>
- <td>Description, Name</td>
- </tr>
- <tr>
- <td>Data Path</td>
- <td>DataPath</td>
- <td>Name</td>
- </tr>
- <tr>
- <td>Data Mapping</td>
- <td>DataMapping</td>
- <td>Name</td>
- </tr>
- <tr>
- <td>Quality Assurance Codes</td>
- <td>QualityAssuranceCode</td>
- <td>Description, Name</td>
- </tr>
-</table>
-<p>The according entries in the language bundles apply to the follwing pattern:</p>
-<pre>&lt;scope id&gt;.&lt;model element id&gt;.Name=
-&lt;scope id&gt;.&lt;model element id&gt;.Description=</pre>
-<p>For example:</p>
-<pre>
-Process.SalesProcess.Name=Verkaufsprozess
-Process.SalesProcess.Description=Verkaufsprozess mit Dateneingabe
-</pre>
-<p>For specific entries like quality assurance codes, the
-id of the specific entry is added as well, e.g.:</p>
-<pre>
-QualityAssuranceCode.ValidationError.Description=Fehler beim Validieren
-QualityAssuranceCode.ValidationError.Name=ValidierungsFehler
-</pre>
-<p>For details on internationalizing Quality Assurance Codes
-refer to section
-<a href="qac">Translating Quality Assurance Codes</a>.</p>
-<h2>Creating Language Bundles</h2>
-<p>You can create language bundles in the properties page of the model.
-Make sure a source folder exists in your project to place the
-bundle. If no source folder is found, the following error message is
-shown on top of the dialog:</p>
-<p class="image"><img src="images/no-source-folder-error.png"
- alt="No Source Folder Error Message"> <br>
-<strong>Figure:</strong> No Source Folder Error Message</p>
-<p>In this case create one by selecting <strong>File &gt;
-New &gt; Source Folder</strong>.</p>
-<h3>Creating new Locales</h3>
-<p>To add locales to a model:</p>
-<ul>
- <li>Open the properties dialog of the model.</li>
- <li>Select <strong>Language Bundles</strong>.</li>
- <li>Specify an NLS <strong>Bundle Basename</strong> for the model.</li>
- <li>Click on the <strong>NLS</strong> list.</li>
- <li>Double-click in the entry field beneath the <strong>NLS</strong>
- entry.</li>
- <li>Click the arrow appearing on the right side of the entry
- field.</li>
- <li>A list pops up, where you can choose the language.</li>
- <li>Add other locales if needed.</li>
- <li>Click <strong>Apply</strong>.</li>
-</ul>
-<p class="image"><img src="images/mg-nls-bundle.png"
- alt="Select Language Bundle"> <br>
-<strong>Figure:</strong> Properties Dialog Settings</p>
-<p class="image"><img src="images/mg-nls-languages.png"
- alt="Selected Languages"> <br>
-<strong>Figure:</strong> List of Selected Locales</p>
-<p>You find the properties files for your languages in the source
-folder of your project. Their name is created with the bundle basename
-and the appendix of the according locale, e.g.:</p>
-<p class="image"><img src="images/mg-nls-file-structure.png" alt="">
-<br>
-<strong>Figure:</strong> The Properties Files in the Source Folder</p>
-<p>Please note that once you created a bundle, you cannot change
-the bundlename afterwards. Editing the name would create a new bundle
-with the modified name.</p>
-<h3>Deleting Language Bundles</h3>
-<p>To delete a locale, select it in the list and enter the <strong>Delete</strong>
-button. A confirmation dialog will pop up to make sure you really want
-to delete this locale and all its properties.</p>
-<p class="image"><img src="images/mg-nls-delete.png" alt="Delete">
-<br>
-<strong>Figure:</strong> Deleting a Locale</p>
-<div class="note"><strong>Note</strong><br>&nbsp;<br>
-In case a language bundle defined in the modeler cannot be deleted, use the
-following workaround:
-<ol>
- <li>Restart the Eclipse environment.</li>
- <li>Manually delete the resource bundle file from its location in
- the tree in the Package Explorer.</li>
-</ol></div>
-
-<!-- <h4>Restore</h4>
-<p><strong>Restore Defaults</strong> button...undo redo????<p> -->
-
-<h2>Adding Translations for Identifiable Elements</h2>
-<p>In the properties pages of all identifiable model elements
-supporting internationalization, listed in the table of supported model
-elements above, you can set locale specific names and in some cases
-descriptions.</p>
-<p>In the properties pages of the model elements:</p>
-<ul>
- <li>Select <strong>General &gt; Internationalization</strong>.</li>
- <li>Now you see a tabular view of all available locales and the
- display Strings specified for each locale.</li>
- <li>Edit the String values for the different locales.</li>
-</ul>
-<p class="image"><img src="images/mg-nls-properties-dialog.png"
- alt="I18N Settings in the Properties Dialog"> <br>
-<strong>Figure:</strong> I18N Settings in the Properties Dialog</p>
-<p>The locales available for certain model elements will be
-determined based on searching the classpath for the relevant properties
-files compatible with the NLS base name specified for the model.</p>
-<p class="note"><strong>Note</strong><br> Note that using configuration variables for the
-internationalized values is not supported!</p>
-<h3 id="qac">Translating Quality Assurance Codes</h3>
-<p>Quality Assurance Codes can be internationalized in the model property page.</p>
-<ol>
- <li>Open the model property page and go to section
- <strong>Quality Assurance Codes</strong>.</li>
- <li>Under the specific error codes in the tree you find entries for
- <strong>Internationalization</strong>.</li>
- <li>Click on the appropriate error code <strong>Internationalization</strong>
- to open the dialog where you can enter translations for the specific
- code.</li>
-</ol>
-<p class="image"><img src="images/mg-nls-qa-code.png"
- alt="I18N of Quality Assurance Codes"> <br>
-<strong>Figure:</strong> I18N of Quality Assurance Codes</p>
-<h2>Update of NLS Bundles</h2>
-<p>The following modifications and actions will result in an
-automatic update of the NLS bundles associated with the model:</p>
-<table id='id_1'>
- <tr>
- <th>Model modification</th>
- <th>Resulting NLS file update action</th>
- </tr>
- <tr>
- <td>Model element creation</td>
- <td>The corresponding keys will be added to the NLS properties
- files.</td>
- </tr>
- <tr>
- <td>Modification of model element Id</td>
- <td>The NLS keys for all existing bundles will be updated
- correspondingly. If the resulting new key should collide with existing
- NLS keys, a dialog allowing to resolve the potential conflict will be
- displayed.</td>
- </tr>
- <tr>
- <td>Model element deletion</td>
- <td>The corresponding NLS entries (key-value pairs) will be
- removed from the NLS bundles.</td>
- </tr>
-</table>
-<h2>Validation</h2>
-<p>If there is at least one NLS-String provided for a model element,
-NLS Strings must be provided for all locales supported. Violations of
-this rule will be flagged with an inconsistency warning.<br />
-&nbsp;</p>
-<p class="image"><img src="images/mg-nls-validation.png"
- alt="Validation Warning"> <br>
-<strong>Figure:</strong> Warning for missing NLS String</p>
-<p>Per default, the String of the default language bundle is used. In case no
-NLS Strings are provided at all for a model element,
-this is interpreted as not wanting to internationalize the
-corrresponding String and no validation warning or error is flagged.</p>
-<h2>External Editing of NLS-Bundles</h2>
-<p>NLS bundles consist of normal properties files. You can directly
-modify these files with an editor of your choice. You find the
-properties files in the <tt>src</tt> folder of your project, named
-<tt>&lt;basename&gt;_&lt;locale&gt;.properties</tt>.</p>
-<p>To ensure synchronicity of model and display information and
-resource bundle files, the Workflow Modeler will listen to changes of
-the NLS bundle files and update its internal caches when necessary.</p>
-<p>Note that the NLS bundles are created and maintained by the
-modeler with a defined ordering, corresponding to the ordering of the
-model outline. When modifying the resource bundle files, it is important
-to respect this ordering.</p>
-<h2>Runtime Support</h2>
-<p>The Infinity Workflow Execution Perspective and the Infinity Administration
-Portal will use the information specified in the NLS bundle when
-displaying or referencing the corresponding model elements at runtime.
- internationalized String is found for the model element or locale
-needed, the model element will be displayed with the name specified
-directly in the model.</p>
-<!--<h2>Internationalization of Modeling Features</h2>-->
-<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/mg-modeler-views.html
index 000ceb4..65e113c 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/mg-modeler-views.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 Analyst 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-preferences.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 Analyst 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-modelreport.htm b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/mg-modelreport.htm
deleted file mode 100644
index 168e807..0000000
--- a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/mg-modelreport.htm
+++ /dev/null
@@ -1,42 +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>Process Model Report</title>
-<script language="JavaScript" src="../../styles/naviLine.js"
- type="text/javascript"
-></script>
-</head>
-<body>
-<script language="JavaScript" type="text/javascript">
-<!--
- writeNavigation("Deploying a Workflow Model","PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/toc.html",
- "mg-defdesk-16.htm","mg-ref-elements.htm",
- "../../toc.html","Business Analyst Handbooks",
- "mg-preface.htm","The Modeling Guide",
- "mg-modeler-preface.html","The Process Workbench");
- -->
-</script>
-<h1>Process Model Report</h1>
-<p>The process model report offers static information derived from
-the model definition. You can start the Process Model Report from the main
-toolbar via the <strong>Process Model Report</strong> button.</p>
-
-<p class="image"><img src="images/mg-report-button.png"
- alt="Starting Model Process Report"/></p>
-<p>For details refer to chapter
-<a href="PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/handbooks/modelling/mg-modelreport.htm">
-Process Model Report</a> of the
-<a href="PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/handbooks/handbooks.htm">
-Developers Handbook</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-preferences.html b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/mg-preferences.html
deleted file mode 100644
index 8805d85..0000000
--- a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/mg-preferences.html
+++ /dev/null
@@ -1,302 +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>Setting @productname@ Preferences</title>
-<script language="JavaScript" src="../../styles/naviLine.js"
- type="text/javascript"></script>
-</head>
-<body>
-<script language="JavaScript" type="text/javascript">
-<!--
- writeNavigation("The Analyst Perspective","PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/toc.html",
- "","mg-modeler-views.html",
- "../../toc.html","Business Analyst Handbooks",
- "mg-preface.htm","The Modeling Guide",
- "mg-modeler-preface.html","The Process Workbench");
- -->
-</script>
-<h1>Setting @productname@ Preferences</h1>
-<p>The @productnameonly@ Process Workbench offers the ability to set @productname@
-specific preferences, which can be set in the Preferences dialog.</p>
-<h2>Setting the Preferences</h2>
-<p>To open the @productname@ Preferences dialog:</p>
-<ul>
- <li>In the main menu choose <strong>Windows</strong> &gt; <strong>Preferences...</strong></li>
- <li>In the Preferences dialog tree select <strong>@productname@</strong>.</li>
-</ul>
-<p class="image"><img src="images/mg-preferences.png" alt="Preferences Dialog"><br>
-<strong>Figure:</strong> Open the @productname@ Preferences Dialog</p>
-<p>Now set your @productname@ specific preferences, which comprise:</p>
-<ul>
- <li><a href="#autoValidation">Enable Auto Validation</a></li>
- <li><a href="#autoID">Enable Auto Id Generation</a></li>
- <li><a href="#autoSub">Enable Auto Name Generation of Subprocess
- Activities</a></li>
- <li><a href="#focus">Focus for newly created model elements</a></li>
- <li><a href="#autoSwitch">Automatically Switching to Manual Activity</a></li>
- <li><a href="#reportFormat">Process Model Report Format</a></li>
- <li><a href="#license">License</a></li>
-</ul>
-<p>Expand @productname@ to open the following options for AuditTrail, Simulation
-and @productname@ Portal:</p>
-<ul>
- <li><a href="#prefAuditTrail">AuditTrail Databases</a></li>
- <li><a href="#concurrency">Concurrency Management Preferences</a></li>
- <li><a href="#deployment">Deployment</a></li>
- <li><a href="#drawing">Drawing Preferences</a></li>
- <li><a href="#simulation">Simulation</a></li>
- <li><a href="#prefWebPortals">@productname@ Portal</a></li>
-</ul>
-<h3 id="autoValidation">Enable Auto Validation</h3>
-<p>You can choose that a validation check on your workflow model is
-automatically performed in the <strong>Process Workbench</strong> after
-modifications. Enable or disable the <strong>Auto Validation</strong> option in
-the Preferences dialog. To get more information on validating a workflow model
-please refer to the chapter <a href="models/model-validation.html">Workflow
-Model Validation</a>.</p>
-<h3 id="autoID">Enable Auto Id Generation</h3>
-<p>By default, an option is set for automatic id generating. If you type in
-the name for your model element, the ID is generated automatically by using its
-name. To build the id, the spaces of the name are left out and the first letter
-of each word is changed to an uppercase letter, if it is a lowercase letter.</p>
-<p class="image"><img src="images/mg-auto-id-generation-1.png" alt=""></p>
-<p>You can disable the default auto id generation by deselecting this
-option. In case the auto id generation is disabled in an element properties
-page, the id entry field is enabled and you can enter an arbitrary id:</p>
-<p class="image"><img src="images/mg-auto-id-generation-2.png" alt=""></p>
-<p>Please take care to use characters valid for @productname@ element Ids, which
-is described in the section <a href="mg-basics-12.htm#id">ID</a> of the chapter
-<a href="mg-basics-12.htm">Representation of Model Elements</a>.</p>
-<h3 id="autoSub">Enable Auto Name Generation of Subprocess Activities</h3>
-<p>If you assign a process to a subprocess activity, you have the option:</p>
-<ul>
- <li>keep the name of the activity or</li>
- <li>to give the activity the name of this process.</li>
-</ul>
-<p>By default the automatic naming of the subprocess activity is enabled.
-Please refer to section <a href="mg-defdesk-4.htm#subprocess">Subprocess
-Activities</a> of the <a href="mg-defdesk-4.htm">Specifying Activities</a> chapter
-for more detailed information.</p>
-<h3 id="focus">Focus for newly created model elements</h3>
-<p>Via this option you can determine how elements will be focused after they
-have been created. You have the choice between:</p>
-<ul>
- <li><a href="#selectEle">Select element/symbol</a></li>
- <li><a href="#propDialog">Open Property Dialog</a></li>
- <li><a href="#editBox">Open Edit Box</a></li>
-</ul>
-<p class="image"><img src="images/focus-preference.png" alt=""></p>
-<h4 id="selectEle">Select element/symbol</h4>
-<p>The <strong>Select element/symbol</strong> option is the default behavior
-for newly created elements. When created in the diagram, the element or symbol
-will be selected there. In case the element is created in the Outline view, it
-will be selected in the Outline view.</p>
-<h4 id="propDialog">Open Property Dialog</h4>
-<p>The option <strong>Open Property Dialog</strong> will open the property
-dialog of a newly created element, so that you can edit its properties
-immediately.</p>
-<h4 id="editBox">Open Edit Box</h4>
-<p>The option <strong>Open Edit Box</strong> causes the newly created
-element to be selected in the Outline view with its name in edit mode. So
-optionally you can change the name immediately. If the tree containing the
-element is collapsed, it will be expanded to set the focus on the element.</p>
-<h3 id="autoSwitch">Automatical Switching to Manual Activity</h3>
-<p>You can choose, if the implementation of an activity should automatically
-switch to a manual activity after you assigned a performer. You have the
-options:</p>
-<ul>
- <li><strong>Always</strong></li>
- <li><strong>Never</strong></li>
- <li><strong>Show warning</strong></li>
-</ul>
-<h3 id="reportFormat">Process Model Report Format</h3>
-<p>Choose between the following formats for your process model report:</p>
-<ul>
- <li><strong>HTML</strong></li>
- <li><strong>PDF</strong></li>
- <li><strong>Prompt</strong></li>
-</ul>
-<h3 id="license">License</h3>
-<p>Browse to the path where your license file resides.</p>
-<p>If you want to go back to the default settings, click <strong>Restore
-Defaults</strong>.</p>
-<h3 id="prefAuditTrail">AuditTrail Databases</h3>
-<p>Add, reset or delete AuditTrail Databases.</p>
-<p class="image"><img src="images/mg-preferences-audittrail.png"
- alt="Preferences - Audit Trail"> <br>
-<strong>Figure:</strong> Set AuditTrail Databases</p>
-<h3 id="concurrency">Concurrency Management Preferences</h3>
-<p>In case you are working in
-<strong>Concurrency Management Mode</strong>,
-you can set the following preferences for handling the concurrency control:</p>
-<ul>
- <li><Strong>Automatically Update Collaborative Modeling Feed</Strong> -
- if set, with every update the Collaborative Modeling Feed table is refreshed
- automatically. This eliminates the need to click the <strong>Refresh</strong>
- button for each update in the Collaborative Modeling Feed View.</li>
- <li><strong>Enable Refresh Job</strong> - enable a refresh job to periodically refresh
- informations from the repository.</li>
- <li><strong>Refresh Rate in Seconds</strong> - the period to perform the refresh.
- Please note that the value must be an
- Integer between 30 and 7200 (seconds).</li>
- <li><strong>Enable Retry</strong> - enable a retry in case of connection failure.
- Please note that the value must be an
- Integer between 30 and 7200 (seconds).</li>
- <li><strong>Retry Rate in Seconds</strong> - the retry rate in seconds.</li>
-</ul>
-<p class="image"><img src="images/mg-preferences-concurrency.png" alt="Concurrency Settings">
-<br><strong>Figure:</strong> Setting Concurrency Management Preferences</p>
-<p>Please refer to the <a href="concurrency/con-preface.html">Collaborative Modeling</a>
-guide for detailed information on this mode.</p>
-<h3 id="deployment">Deployment</h3>
-<p>In the <strong>Deployment</strong> section, you can change the following
-predefined settings:</p>
-<ul>
- <li>Checkbox <strong>Always deploy new version</strong>:<br>
- You have the option to determine, if in case of model deployment,
- always a new version should be deployed. In that case, no
- model management dialog will open during model deployment.<br>&nbsp;</li>
- <li>Credentials:<br>
- In case the entry fields for <strong>ID</strong> and <strong>Password</strong>
- are not empty, the login dialog during the deployment will be skipped
- and those values as well as the values for
- <strong>Realm</strong>, <strong>Partition</strong> and <strong>ID</strong>
- are taken in case they exist. Default entries for <strong>ID</strong> and
- <strong>Password</strong> are <tt>motu</tt>/<tt>motu</tt>.</li>
-</ul>
-<p class="image"><img src="images/mg-pref-deployment.png"
- alt=""> <br>
-<strong>Figure:</strong> Deployment Preferences</p>
-<h3 id="drawing">Drawing Preferences</h3>
-<p class="image"><img src="images/mg-preferences-drawing.png"
- alt="Drawing Preferences"> <br>
-<strong>Figure:</strong> Drawing Preferences</p>
-<ul>
- <li><a href="#fork">View Fork on Traversal</a></li>
- <li><a href="#snapGrid">Enable Snap To Grid</a></li>
- <li><a href="#modelDirection">Default Modeling Direction</a></li>
- <li><a href="#classicMode">Default Drawing Mode</a></li>
- <li><a href="#autoDistribute">Auto Distribute</a></li>
- <li><a href="#splitype">Default Split Type</a></li>
- <li><a href="#jointype">Default Join Type</a></li>
-</ul>
-<h4 id="fork">View Fork on Traversal</h4>
-<p>You can enable this option to see how the Engine traverses during
-transition conditions. 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>
-<h4 id="snapGrid">Enable Snap To Grid</h4>
-<p>To facilitate the positioning of your elements in the diagram during
-modeling, you have the option to let your elements snap to a grid. In the <strong>Preferences</strong>
-dialog you can define the size of this grid and a factor for the grid to be
-visible in the following entry fields:</p>
-<ul>
- <li><strong>Snap Grid in Pixel</strong></li>
- <li><strong>Visible Grid Factor</strong></li>
-</ul>
-<p>In the <strong>Snap Grid in Pixel</strong> entry field enter a value for
-the size of the grid elements in your diagram. The default size is set to 5
-pixel.</p>
-<p>You might want to have a more detailed grid for your elements to be
-snapped to than visible. Enter a factor in the <strong>Visible Grid
-Factor</strong> field for the grid to be displayed. Thus the size of the visible grid
-will be the size of the snap to grid times the specified factor. The default
-factor is <tt>4</tt>.</p>
-<p>Please refer to the section <a href="model-views/views-diagrams.html#gridOption">Grid
-Option</a> of the chapter <a href="model-views/views-diagrams.html">Working with Diagrams</a>
-for detailed information about this functionality.</p>
-<h4 id="modelDirection">Default Modeling Direction</h4>
-<p>You can choose a default modeling direction like <strong>Vertical</strong>
-or <strong>Horizontal</strong>. It is recommended to use the vertical modeling
-direction, which is set as default value.</p>
-<h4 id="classicMode">Default Drawing Mode</h4>
-<p>Choose whether you want to set the default drawing mode to <strong>Classic</strong>
-or <strong>BPMN</strong>. If you want to work with pools and lanes, choose the <strong>BPMN</strong>
-mode.</p>
-<h4 id="autoDistribute">Auto Distribute</h4>
-<p>With the <strong>Auto Distribute</strong> preference you choose the
-behavior of created symbols in your diagram. When working with a grid, you have
-the options:</p>
-<ul>
- <li><strong>Snap the last selected symbol to grid</strong></li>
- <li><strong>Snap all symbols to grid</strong></li>
- <li><strong>Prompt</strong></li>
-</ul>
-<h4 id="splitype">Default Split Type</h4>
-<p>The default type value for newly created split gateway is configurable using the
-<strong>Default Split Type</strong> option. </p>
-
- <p>If <strong>Prompt</strong> is selected, upon creating a split, the user is
- prompted to select the split behavior. It also prompts whether to use the same type
- in the future actions. However, the default value for the split behavior is
- XOR.</p>
-<p class="image"><img src="images/splitbehavior.png" alt="Select Split Behavior"></img>
-<br>
-<strong>Figure:</strong> Select Split Behavior</p>
-<p>Note if you click Cancel, the default split type gets applied.</p>
-
-<h4 id="jointype">Default Join Type</h4>
-
-<p>The default type value for newly created join gateway is configurable using the
-<strong>Default Join Type</strong> option. </p>
-
- <p>If <strong>Prompt</strong> is selected, upon creating a join, the user is
- prompted to select the join behavior. It also prompts whether to use the same type
- in the future actions. However, the default value for the join behavior is
- XOR.</p>
-
-<p class="image"><img src="images/joinbehavior.png" alt="Select Join Behavior"></img>
-<br>
-<strong>Figure:</strong> Select Join Behavior
-</p>
-<p>Note if you click Cancel, the default join type gets applied.</p>
-
-
-<h3 id="multipackage">Multi Package Modeling Preferences</h3>
-<p>This preference option can be used to mark elements as public or private.
-It means that the applications and type declaration are available for import by
-reference if set to public. By default, the Public preference is selected. But
-if you have set it as private then the Visibility Public property of all
-the non-interactive applications and
-type declaration is not set. In this case, if you want to make it public you should set the
-preference as Public. For more information, refer to the <a href="mg-defdesk-6.htm#prop">
-Properties</a> section of the chapter<a href="mg-defdesk-6.htm"> Specifying Applications</a>.
-</p>
-<p class="image"><img src="images/mg-preferences-multipackage.png"
- alt="Preferences - Multi Package Modelling Preferences"> <br>
-<strong>Figure:</strong> Multi Package Modeling Preferences</p>
-
-
-
-<h3 id="simulation">Simulation</h3>
-<p>Select <strong>Simulation &gt; Statistics Overlays</strong> to enable or
-disable the option to show statistics overlays for:</p>
-<ul>
- <li>Participants</li>
- <li>Applications</li>
- <li>Activities</li>
- <li>Transitions</li>
-</ul>
-<p class="image"><img src="images/mg-preferences-simulation.png"
- alt="Preferences - Simulation"> <br>
-<strong>Figure:</strong> Set Simulation Preferences</p>
-<p>Please refer to the <a href="PLUGINS_ROOT/org.eclipse.stardust.docs.simulation/html/simulation/toc.html">
- Developer Simulation Guide</a> for details on the Simulation feature.</p>
-<h3 id="prefWebPortals">@productname@ Portal</h3>
-<p>Choose, whether you want to be warned on use of the internal Web browser.</p>
-<p class="image"><img src="images/mg-preferences-webportals.png"
- alt="Preferences - @productname@ Portal">
-<strong>Figure:</strong> @productname@ Portal Option</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-bookmark.html b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/model-views/views-bookmark.html
deleted file mode 100644
index fc6aba3..0000000
--- a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/model-views/views-bookmark.html
+++ /dev/null
@@ -1,49 +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 Analyst Perspective</title>
-<script language="JavaScript" src="../../../styles/naviLine.js" type="text/javascript"></script>
-</head>
-<body>
-<script language="JavaScript" type="text/javascript">
-<!--
-writeNavigation("@productnameonly@ Process Model Traversal","PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/toc.html",
- "views-repository.html","views-traversal.html",
- "../../../toc.html","Business Analyst Handbooks",
- "../mg-preface.htm","The Modeling Guide",
- "../mg-modeler-preface.html","The Process Workbench",
- "../mg-modeler-views.html","Analyst Perspective - Views");
--->
-</script>
-
-<h1>The @productnameonly@ Process Model Bookmarks</h1>
-<p>If the <strong>@productnameonly@ Process Model Bookmarks</strong> view is not already open,
-choose <strong>Window &gt; Show View &gt; Other...</strong> in the main menu and from the
-upcoming dialog <strong>@productnameonly@ Process Model Bookmarks</strong>.</p>
-<p>&nbsp;</p>
-<p class="image"><img src="../images/mg-appendix-5.png" alt=""> <br>
-<strong>Figure:</strong> Opening the @productnameonly@ Process Model Bookmarks View</p>
-<p>The <strong>@productnameonly@ Process Model Bookmarks</strong> view has been conceived to
-give you the opportunity to cluster the components of your model in arbitrarily organized
-groups of tools. The upper tree view organizes the elements of the model by categories,
-e.g. by participants, processes or data. By using bookmarks you can organize e.g. the most
-frequently used components under a bookmark with an arbitrary name.</p>
-<p class="image"><img src="../images/mg-bookmark-view.png" alt=""> <br>
-<strong>Figure:</strong> Adding a New Bookmark</p>
-<p>A newly created bookmark can be renamed by right-clicking on the bookmark and
-choosing <strong>Rename</strong> from the pop-up menu. You can now drag an activity, a
-participant, a data or an application symbol from the <strong>Outline</strong> view onto
-the bookmarks symbol and drop it there.</p>
-<p class="image"><img src="../images/mg-bookmark-view-2.png" alt=""> <br>
-<strong>Figure:</strong> Dragging-and-Dropping Elements to the Bookmark</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-cheat.html b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/model-views/views-cheat.html
deleted file mode 100644
index 37c7756..0000000
--- a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/model-views/views-cheat.html
+++ /dev/null
@@ -1,56 +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>Cheat Sheet View</title>
-<script language="JavaScript" src="../../../styles/naviLine.js" type="text/javascript"></script>
-</head>
-<body>
-<script language="JavaScript" type="text/javascript">
-<!--
-writeNavigation("@productnameonly@ Process Model Repository","PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/toc.html",
- "views-diagrams.html","views-repository.html",
- "../../../toc.html","Business Analyst Handbooks",
- "../mg-preface.htm","The Modeling Guide",
- "../mg-modeler-preface.html","The Process Workbench",
- "../mg-modeler-views.html","Analyst Perspective - Views");
--->
-</script>
-
-<h1>The Cheat Sheet View</h1>
-<p>@productname@ provides you with cheat sheets as additional help to
-guide you through the steps of working with the workflow modeler. The
-<strong>Analyst Quick Start Tutorial</strong> cheat sheet demonstrates the basic steps of building a
-workflow model with a process definition and its elements in the <strong>@productname@
-Analyst Perspective</strong>.</p>
-<p>If you newly open the @productname@ Analyst Perspective, the @productname@ Analyst Cheat
-Sheet view opens automatically. In case the @productname@ Developer Cheat Sheet is open, select
-the task <strong>Switch to @productname@ Analyst Cheat Sheet</strong> and <strong>Start
-working on this task</strong> to switch to the Analyst Cheat Sheet:</p>
-<p class="image"><img src="../images/mg-cheatsheet-switch.png" alt=""> <br>
-<strong>Figure:</strong> Switch to the @productname@ Analyst Cheat Sheet.</p>
-<p>To open the Analyst Cheat Sheet view explicitly, perform the following steps:</p>
-<ul>
- <li>In the main menu select <strong>Help &gt; Cheat Sheets ...</strong></li>
- <li>Select <strong>@productname@ &gt; The @productname@ Analyst Cheat Sheet</strong>.</li>
-</ul>
-<p class="image"><img src="../images/mg-open-cheatsheet.png" alt=""> <br>
-<strong>Figure:</strong> Open the @productname@ Analyst Cheat Sheet.</p>
-<p>Now the Cheat Sheet view opens. Choose the @productname@ Analyst Quick Start Tutorial:</p>
-<p class="image"><img src="../images/mg-cheatsheet.png" alt=""> <br>
-<strong>Figure:</strong> The Analyst Quick Start Tutorial.</p>
-<p>To start the Cheat Sheet select <strong>Start working on this task</strong>:</p>
-<p class="image"><img src="../images/mg-cheatsheet-start.png" alt=""> <br>
-<strong>Figure:</strong> Start with the Quick Start Tutorial.</p>
-<p>For detailed information on how to work with cheat sheets please refer to the <strong>Workbench
-User Guide / Working with cheat sheets</strong> of the <strong>Eclipse Help</strong>.</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-outline.html b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/model-views/views-outline.html
index d34452d..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/views-outline.html
@@ -5,7 +5,7 @@
<meta http-equiv="Content-Style-Type" content="text/css">
<link rel="STYLESHEET" href="../../../styles/carnot.css" charset="ISO-8859-1" type="text/css">
-<title>Outline View</title>
+<title>Panels</title>
<script language="JavaScript" src="../../../styles/naviLine.js" type="text/javascript"></script>
</head>
<body>
@@ -20,7 +20,7 @@ writeNavigation("Working with Diagrams","PLUGINS_ROOT/org.eclipse.stardust.docs.
-->
</script>
-<h1>The Outline View</h1>
+<h1>Panels</h1>
<p>The <strong>Outline</strong> view organizes elements of the model in tree-like
structures. The <strong>Outline</strong> view area organizes elements into applications,
data, participants and processes.</p>
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/model-views/views-repository.html b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/model-views/views-repository.html
deleted file mode 100644
index b46eb06..0000000
--- a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/model-views/views-repository.html
+++ /dev/null
@@ -1,49 +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>@productnameonly@ Process Model Repository</title>
-<script language="JavaScript" src="../../../styles/naviLine.js" type="text/javascript"></script>
-</head>
-<body>
-<script language="JavaScript" type="text/javascript">
-<!--
-writeNavigation("@productnameonly@ Process Model Bookmarks","PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/toc.html",
- "views-cheat.html","views-bookmark.html",
- "../../../toc.html","Business Analyst Handbooks",
- "../mg-preface.htm","The Modeling Guide",
- "../mg-modeler-preface.html","The Process Workbench",
- "../mg-modeler-views.html","Analyst Perspective - Views");
--->
-</script>
-
-<h1>The @productnameonly@ Process Model Repository</h1>
-<p>The <strong>@productnameonly@ Process Model Repository</strong> view lists all process
-models in a selected project. You can choose between a sticky and an open selection. By
-choosing <strong>Sticky Project</strong> you freeze the currently open project to keep its
-model listed, while by choosing <strong>Selection Project</strong> the listing changes to
-the project where the actual folder is.</p>
-<p>&nbsp;</p>
-<p class="image"><img src="../images/mg-appendix-1.png" alt=""> <br>
-<strong>Figure:</strong> The @productnameonly@ Process Model Repository</p>
-<p>In the listing of the models you find their version trees. To open the model,
-double-click the version number you want to work with. To create a new version of your
-model, right-click the version number of your model und choose <strong>Versionize</strong>
-in the pop-up menu. The open version changes its status to a released version, a new
-version is created as its successor and opened in the <strong>Workflow Modeler</strong>.
-You can also copy a version by selecting <strong>Copy Version</strong>. In the upcoming
-dialog, type in the ID for the copied version. To delete a version, choose <strong>Delete</strong>
-in the pop-up menu.</p>
-<p>&nbsp;</p>
-<p class="image"><img src="../images/mg-appendix-2.jpg" alt=""> <br>
-<strong>Figure:</strong> Versionizing a Model in the @productnameonly@ Process Model Repository</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-simplify.html b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/model-views/views-simplify.html
deleted file mode 100644
index 6a17416..0000000
--- a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/model-views/views-simplify.html
+++ /dev/null
@@ -1,64 +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>Simplifying the Modeler View</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",
- "views-traversal.html","",
- "../../../toc.html","Business Analyst Handbooks",
- "../mg-preface.htm","The Modeling Guide",
- "../mg-modeler-preface.html","The Process Workbench",
- "../mg-modeler-views.html","Analyst Perspective - Views");
--->
-
-</script>
-
-<h1>Simplifying the Modeler View</h1>
-<h3>Using the Development Perspective</h3>
-<p>In some cases you like to work with both perspectives, the Analyst and the Development perspective.
-The Development perspective is a more powerful designer that may help overcome any restrictions
-you have with the Analyst Perspective. Please refer to the chapter
-<a href="PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/handbooks/modelling/mg-modeler-views.html">
-The Development Perspective</a> in the
-<a href="PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/handbooks/handbooks.htm">Developer Handbooks</a>
-for a detailed description on the functionality of the Development perspective.</p>
-<p>To switch between the perspectives,
-click the <strong>Perspective</strong> icon on the upper left side of the workbench and choose
-the perspective.</p>
-<p class="image"><img src="../images/perspective-icon.png" alt=""> <br>
-<strong>Figure:</strong> Switch to another perspective.</p>
-
-<h3>Removing Command Icons for your Current Perspective</h3>
-<p>To remove command icons for your current perspective, that you do not need,
-right-click the @productname@ Development or Analyst Perspective icon. Choose
-<strong>Customize</strong>.</p>
-<p class="image"><img src="../images/perspective-customize.png" alt=""> <br>
-<strong>Figure:</strong> Select Customize.</p>
-<p>In the <strong>Customize</strong> dialog select the <strong>Commands</strong> tab.
-In the <strong>Available command groups</strong> section, you can deselect commands
-you are not intended to use. As a business analyst you won't need most of these commands.</p>
-<p class="image"><img src="../images/perspective-commands.png" alt=""> <br>
-<strong>Figure:</strong> Deselect command icons.</p>
-<p>Once you have changed any perspective layout or customization you want to persist
-the settings to the next time you use the workbench. You can save your settings by
-right-clicking the perspective icon and selecting <strong>Save as..</strong>.
-In the upcoming dialog, leave the default entries and click <strong>OK</strong>.</p>
-<p class="image"><img src="../images/perspective-save.png" alt=""> <br>
-<strong>Figure:</strong> Save the perspective settings.</p>
-<p class="note"><strong>Note</strong><br>
-Occasionally Eclipse can crash. To ensure that your settings persist, restart Eclipse.</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-traversal.html b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/model-views/views-traversal.html
deleted file mode 100644
index 92d9d84..0000000
--- a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/model-views/views-traversal.html
+++ /dev/null
@@ -1,46 +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>@productnameonly@ Process Model Traversal</title>
-<script language="JavaScript" src="../../../styles/naviLine.js" type="text/javascript"></script>
-</head>
-<body>
-<script language="JavaScript" type="text/javascript">
-<!--
-writeNavigation("Simplifying the Modeler View","PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/toc.html",
- "views-bookmark.html","views-simplify.html",
- "../../../toc.html","Business Analyst Handbooks",
- "../mg-preface.htm","The Modeling Guide",
- "../mg-modeler-preface.html","The Process Workbench",
- "../mg-modeler-views.html","Analyst Perspective - Views");
--->
-
-</script>
-
-<h1>The @productnameonly@ Process Model Traversal</h1>
-<p>If the <strong>@productnameonly@ Process Model Traversal</strong> view is not already open,
-choose <strong>Window &gt; Show View &gt; Other...</strong> in the main menu and from the
-upcoming dialog <strong>@productnameonly@ Process Model Traversal</strong>.</p>
-<p class="image"><img src="../images/mg-appendix-3.png" alt=""> <br>
-<strong>Figure:</strong> Opening the @productnameonly@ Process Model Traversal View</p>
-<p>In the <strong>@productnameonly@ Process Model Traversal</strong> view you can traverse a
-path starting from a selected element in a diagram or the <strong>Outline</strong> view.
-In the left area the list of <strong>Linked Objects</strong> depending on the selected
-element is displayed. The view updates its content each time you perform one step forward
-in your traversal path by double-clicking a selected element in the list of <strong>Linked
-Objects</strong>. To return to your previous position, push the <strong>Pop</strong> button in the
-view. When your traversal path has been determined, select the elements and click on the
-diagram canvas to place them in the diagram one by one.</p>
-<p class="image"><img src="../images/mg-appendix-4.png" alt=""> <br>
-<strong>Figure:</strong> The @productnameonly@ Process Model Traversal View</p>
-<script language="JavaScript" type="text/javascript">
-<!--
-writeFooter();
--->
-</script>
-</body>
-</html>
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pattern-support.html b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pattern-support.html
deleted file mode 100644
index ad2e7be..0000000
--- a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pattern-support.html
+++ /dev/null
@@ -1,183 +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" type="text/css">
-<title>Modeling Pattern Support</title>
-<script src="../../styles/naviLine.js" type="text/javascript"></script>
-</head>
-<body>
-<script type="text/javascript">
-<!--
- writeNavigation("Retrieving Diagrams from Model Information","PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/toc.html",
- "process-effort-calculation.html","mg-defdesk-16.htm",
- "../../toc.html","Business Analyst Handbooks",
- "mg-preface.htm","The Modeling Guide",
- "mg-modeler-preface.html","The Process Workbench");
- -->
-</script>
-<h1>Modeling Pattern Support</h1>
-<p>Modeling patterns provide the ability to create complex models faster and
-to use and reuse modeling pattern.</p>
-<p>@productname@ is shipped with some predefined modeling
-patterns. An Eclipse view, the <strong>Patterns View</strong> is provided, where
-you can select patterns and add them via drag &amp; drop into a model diagram.
-The model elements of the pattern are copied into the underlying process
-definition. A wizard is invoked which allows parameterization of the pattern.
-This dialog contains entry field for parameters specifying the individual
-pattern. This could be for example the number of activities or the type of
-activities.</p>
-<h2>The @productname@ Patterns View</h2>
-<p>You can achieve the predefined patterns from the list in the <strong>Patterns
-Views</strong>. To open the <strong>Patterns Views</strong>, select <strong>Window
-&gt; Show View &gt; @productname@ &gt; Patterns View</strong>.</p>
-<p class="image"><img src="images/patterns-open-view.png" alt="Open View">
-<br>
-<strong>Figure:</strong> Open the Patterns View</p>
-<p>In this view you can choose predefined patterns from the categories <strong>Basic
-Control Flow Pattern</strong> and <strong>Advanced Branching and Synchronization
-Patterns</strong>, which are described in detail in the following section. The patterns
-can be dragged and dropped to a process diagram. In most cases you can set
-parameters, which will be requested in an opening dialog.</p>
-<p>On the right side of the view you can see a description and an example
-diagram for the pattern you selected.</p>
-<p class="image"><img src="images/patterns-view.png" alt="The Patterns View">
-<br>
-<strong>Figure:</strong> The Patterns View</p>
-<h2>Generic Patterns</h2>
-<h3>Basic Control Flow Pattern</h3>
-<p>@productname@ provides the following basic control flow
-patterns:</p>
-<ul>
- <li><a href="#sequ">Sequence</a></li>
- <li><a href="#loop">Loop</a></li>
- <li><a href="#pSplit">Parallel Split</a></li>
- <li><a href="#splitSynch">Parallel Split and Synchronization</a></li>
- <li><a href="#choice">Exclusive Choice</a></li>
- <li><a href="#choiceMerge">Exclusive Choice and Merge</a></li>
-</ul>
-<h4 id="sequ">Sequence</h4>
-<p>This pattern consists of a sequence of activities. In the <strong>Sequence
-Template</strong> dialog you can set the following parameters:</p>
-<ul>
- <li>number of activities</li>
- <li>activity type (default <tt>Application Activity</tt>)</li>
- <li>orientation (default <tt>Vertical</tt>)</li>
-</ul>
-<p class="image"><img src="images/patterns-sequence-params.png"
- alt="Sequence Pattern Parameters"> <br>
-<strong>Figure:</strong> Enter Parameters for the Sequence Pattern</p>
-<p>An example Sequence pattern with 3 application activities and vertical orientation
-would look like the following:</p>
-<p class="image"><img src="images/patterns-sequence-result.png"
- alt="Sequence Pattern Result"> <br>
-<strong>Figure:</strong> Example Sequence Pattern added to the Diagram.</p>
-<h4 id="loop">Loop</h4>
-<p>This pattern consists of a sequence of N activities and a loop transition
-back to the first. In the <strong>Loop Template</strong> dialog you can set the
-following parameters:</p>
-<ul>
- <li>number of activities in the "loop body"</li>
- <li>activity type (default <tt>Application Activity</tt>)</li>
- <li>loop condition</li>
- <li>orientation (default <tt>Vertical</tt>)</li>
-</ul>
-<p class="image"><img src="images/patterns-loop-params.png"
- alt="Loop Pattern Parameters"> <br>
-<strong>Figure:</strong> Enter Loop Parameters for the Pattern</p>
-<p>An example Loop pattern with 2 activities, the loop condition <tt>State="R"</tt>
-and vertical orientation would look like the following:</p>
-<p class="image"><img src="images/patterns-loop-result.png"
- alt="Loop Pattern Result"> <br>
-<strong>Figure:</strong> Example Loop Pattern added to the Diagram.</p>
-<h4 id="pSplit">Parallel Split</h4>
-<p>This pattern consists of a start activity which spawns via <tt>AND</tt>
-to N threads. In the <strong>AND Split Template</strong> dialog you can set the
-following parameters:</p>
-<ul>
- <li>number of threads (N)</li>
- <li>activity type (default <tt>Application Activity</tt>)</li>
-</ul>
-<p class="image"><img src="images/patterns-split-params.png"
- alt="Parallel Split Pattern Parameters"> <br>
-<strong>Figure:</strong> Enter Parallel Split Parameters for the Pattern</p>
-<p>An example Parallel Split pattern with 3 route activities
-would look like the following:</p>
-<p class="image"><img src="images/patterns-split-result.png"
- alt="Parallel Split Pattern Result"> <br>
-<strong>Figure:</strong> Example Parallel Split Pattern added to the Diagram.</p>
-<h4 id="splitSynch">Parallel Split and Synchronization</h4>
-<p>This pattern consists of a start activity which spawns via <tt>AND</tt>
-to N threads with one activity each and joins via AND to one end activity. In
-the <strong>AND Split Template</strong> dialog you can set the following
-parameters:</p>
-<ul>
- <li>number of threads (N)</li>
- <li>activity type (default <tt>Application Activity</tt>)</li>
-</ul>
-<p class="image"><img src="images/patterns-split-sychn-params.png"
- alt="Parallel Split and Synchronization Pattern Parameters"> <br>
-<strong>Figure:</strong> Enter Parallel Split and Synchronization Parameters for
-the Pattern</p>
-<p>An example Parallel Split and Synchronization pattern with 3 application activities
-would look like the following:</p>
-<p class="image"><img src="images/patterns-split-sychn-result.png"
- alt="Parallel Split and Synchronization Pattern Result"> <br>
-<strong>Figure:</strong> Example Parallel Split and Synchronization Pattern
-added to the Diagram.</p>
-<h4 id="choice">Exclusive Choice</h4>
-<p>This pattern consists of a start activity which spawns via <tt>XOR</tt>
-to <tt>ONE</tt> other threads out of N possible. In the <strong>Exclusive Choice Template</strong> dialog you can
-set the following parameters:</p>
-<ul>
- <li>number of activities</li>
- <li>type of activity (default: <tt>Application Activity</tt>)</li>
-</ul>
-<p class="image"><img src="images/patterns-choice-params.png"
- alt="Exclusive Choice Pattern Parameters"> <br>
-<strong>Figure:</strong> Enter Exclusive Choice Parameters for the Pattern</p>
-<p>An example Exclusive Choice pattern with 2 application activities
-would look like the following:</p>
-<p class="image"><img src="images/patterns-choice-result.png"
- alt="Exclusive Choice Pattern Result"> <br>
-<strong>Figure:</strong> Example Exclusive Choice Pattern added to the Diagram.</p>
-<h4 id="choiceMerge">Exclusive Choice and Merge</h4>
-<p>Start activity which spawns via <tt>XOR</tt> to N threads with one
-activity each and joins via <tt>XOR</tt> to one end activity. In the <strong>Exclusive
-Choice and Merge Template</strong> dialog you can set the following parameters:</p>
-<ul>
- <li>number of activities</li>
- <li>type of activity (default: <tt>Application Activity</tt>)</li>
-</ul>
-<p class="image"><img src="images/patterns-choice-merge-params.png"
- alt="Exclusive Choice and Merge Pattern Parameters"> <br>
-<strong>Figure:</strong> Enter Exclusive Choice and Merge Parameters for the
-Pattern</p>
-<p>An example Exclusive Choice and Merge pattern with 2 application activities
-would look like the following:</p>
-<p class="image"><img src="images/patterns-choice-merge-result.png"
- alt="Exclusive Choice and Merge Pattern Result"> <br>
-<strong>Figure:</strong> Example Exclusive Choice and Merge Pattern added to the
-Diagram.</p>
-<h3>Advanced Branching and Synchronization Patterns</h3>
-<h4>Dynamic Spawn</h4>
-<p>This is a pattern to dynamically spawn a subprocess for a list of entries
-and pass the entries to the subprocess, execute those and join them again.</p>
-<p>In the <strong>Dynamic Spawn</strong> dialog you can
-choose the implementation process to be set for the subprocess activity:</p>
-<p class="image"><img src="images/patterns-spawn-params.png"
- alt="Exclusive Choice Pattern Parameters"> <br>
-<strong>Figure:</strong> Enter the Implementation Process for the Subprocess Activity.</p>
-<p>An example Dynamic Spawn pattern would look like the following:</p>
-<p class="image"><a href="images/patterns-spawn-result_orgSize.png" target="_blank">
-<img src="images/patterns-spawn-result.png"
- alt="Exclusive Choice Pattern Result"></a><br>
-<strong>Figure:</strong> Example Dynamic Spawn Pattern added to the Diagram.</p>
-<script type="text/javascript">
-<!--
-writeFooter();
--->
-</script>
-</body>
-</html>
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-connect-sybol.htm b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-connect-sybol.htm
new file mode 100644
index 0000000..a7dc0d0
--- /dev/null
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-connect-sybol.htm
@@ -0,0 +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>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 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>Working with Gateways</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/pep-events.htm b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-events.htm
new file mode 100644
index 0000000..e29a62d
--- /dev/null
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-events.htm
@@ -0,0 +1,214 @@
+<!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">
+<!--
+ 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>
+<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>
+ <li><a href="#pool">Default Pool</a></li>
+ <li><a href="#lane">Default Lane</a>
+ <ul>
+ <li><a href="#create">Creating Lanes</a></li>
+ <li><a href="#fly">Lane Flyout Menu - Deleting Lane</a></li>
+
+ <li><a href="#col">Collapsing and Expanding Lanes</a></li>
+ </ul></li>
+ <li><a href="#prop">Viewing Lane Properties</a></li>
+ <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>
+
+
+
+<p class="image"><img src="images/swimlane.png"
+ alt="Swim Lanes" /> <br>
+<strong>Figure:</strong> Swim Lanes</p>
+
+<h2 id="pool">Default Pool</h2>
+<p>A pool serves as a graphical container. By default, the Default Pool is provided for modeling.
+The default pool demarcates the diagram boundaries.
+It cannot be deleted or renamed.
+ It is not possible to create other pools in a process diagram.
+The Default Pool contains a Default Lane. It must at least include one lane.
+All lanes for a process should exist within the Default Pool.
+You cannot add symbol directly to the Default Pool. If a symbol is dropped on the Default Pool,
+the error message is displayed.
+</p>
+<h2 id="lane">Default Lane</h2>
+<p>By default, the Default Lane is provided inside the Default Pool.
+You can drop symbols only
+inside lanes.</p>
+
+<h3 id="create">Creating Lanes</h3>
+<p> A pool can have more than one lane. To create a lane, click the icon <strong>Create Swimlane</strong> in the toolbar.
+The lane is added to the Default Pool and to the right of the last lane.
+The name to each newly added lane is assigned
+based on the sequence in which lanes are added. For example, Lane 2, Lane 3 , Lane 4 and so on.</p>
+
+<p class="image"><img src="images/create-swim.png"
+ alt="Swim Lane Icon" /> <br>
+<strong>Figure:</strong> Swim Lane Icon</p>
+
+<h3 id="fly">Lane Flyout Menu - Deleting Lane</h3>
+<p>The lane flyout menu - Delete Lane icon is displayed when you hover the mouse over the lane header or
+when the cursor is five to ten
+pixels inside the four edges of the lane.
+</p>
+<p class="image"><img src="images/del-lane.png"
+ alt="Lane Flyout Menu - Delete Lane" /> <br>
+<strong>Figure:</strong> Lane Flyout Menu - Delete Lane</p>
+<p>If you want to delete the lane, hover the mouse over the lane and click the <strong>Delete Lane</strong> icon in the
+lane flyout menu. The delete confirmation dialog is displayed. Click Yes to delete the lane and all symbols in it. Deleting the
+lane also deletes symbols and in and out mappings across it.</p>
+<p class="image"><img src="images/del-lane-confirm.png"
+ alt="Delete Lane Confirmation Dialog" /> <br>
+
+<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>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>
+<h3 id="col">Collapsing and Expanding Lanes</h3>
+<p>Click the collapse lane icon displayed in the upper-right corner of the lane header to collapse the lane.
+ </p>
+<p class="image"><img src="images/mini-lane.png"
+ alt="Collapse Lane Icon" /> <br>
+<strong>Figure:</strong> Collapse Lane Icon</p>
+<p>To expand the lane, click the Expand lane icon displayed in the upper-right corner of the collapsed lane header.</p>
+<p class="image"><img src="images/expand.png"
+ alt="Expand Lane Icon" /> <br>
+<strong>Figure:</strong> Expand Lane Icon</p>
+<h2 id="prop">Viewing Lane Properties</h2>
+<p>To view the properties of any lane, click the lane header. The properties of the lane are displayed
+at the right of the lanes.
+
+ </p>
+<p class="image"><img src="images/lane-prop.png"
+ alt="Lane Properties" /> <br>
+<strong>Figure:</strong> Lane Properties</p>
+<p>Following are the lane properties:</p>
+<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>
+ <li>Description - Specify the description.</li>
+ <li>Participant - By default, <strong>None</strong> option is displayed. All the participants defined in the
+ loaded model are listed in this drop-down list.
+ To assign a lane participant, select any participant from the Participant drop-down list.
+ 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>
+<h3>Hide Property Panel </h3>
+<p>Click the <strong>Hide Property Panel</strong> icon displayed at the top right corner of the window.
+</p>
+<p class="image"><img src="images/hide.png"
+ alt="Hide Property Panel" /> <br>
+<strong>Figure:</strong> Hide Property Panel</p>
+
+<h3>Show Property Panel</h3>
+<p>Similarly, click the <strong>Show Property Panel</strong> icon to view it again.
+<p class="image"><img src="images/show.png"
+ alt="Show Property Panel" /> <br>
+<strong>Figure:</strong> Show Property Panel</p>
+
+<h2 id="sym">Symbols in Lanes</h2>
+<p>All symbols of model elements such as activities, applications, data and participants are tied to lanes.
+Their entire bounding box fit into lanes. Newly created symbols are added in a lane.
+Existing symbols can be dragged across lanes.
+
+</p>
+
+<h2 id="ges">Symbol Gestures</h2>
+<p>To work with symbols, you can use following gestures.</p>
+<h4>Clicking and Dragging a Symbol</h4>
+<p>Click on the symbol in the toolbar and place it in the lane.
+Then, click on symbol and drag it from one lane to any another lane.
+The connections
+to symbols remain intact.</p>
+<h4>Hovering the Mouse Over the Symbol</h4>
+<p>When you hover the mouse in the proximity of any symbol in the lane the Flyout Menu is displayed.
+Also, when you hover the mouser over the symbol its outline changes to red color.</p>
+ <p class="image"><img src="images/hover-menu.png"
+ 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>
+ <p class="image"><img src="images/doubl-clik.png"
+ alt="Double-click on Activity Symbol" /> <br>
+<strong>Figure:</strong> Double-click on Activity Symbol</p>
+
+<h4>Clicking a Symbol</h4>
+<p>When you click any symbol in the swim lane, the Property panel of that symbol is displayed at
+the right side of the swim lane. Also, the symbol gets selected and you can move the symbol across lanes.</p>
+
+
+<h2 id="ele">Dragging and Dropping of Elements from Outline</h2>
+<p>You can drag elements from model Outline and drop it on any swim lane in canvas.</p>
+<table>
+<tr>
+ <th>Element</th>
+ <th>Drop Target</th>
+ <th>Result</th>
+</tr>
+<tr>
+ <td>Structured Type</td>
+ <td>Swim Lane</td>
+ <td>Creates a new data of structured type</td>
+</tr>
+<tr>
+ <td>Data</td>
+ <td>Swim Lane</td>
+ <td>Adds data to the lane for connection</td>
+</tr>
+<tr>
+ <td>Application</td>
+ <td>Swim Lane</td>
+ <td>Creates new application activity</td>
+</tr>
+<tr>
+ <td>Participant</td>
+ <td>Swim Lane</td>
+ <td></td>
+</tr>
+<tr>
+ <td>Process</td>
+ <td>Swim Lane</td>
+ <td>Creates a subprocess activity</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/pep-gateways.htm b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-gateways.htm
new file mode 100644
index 0000000..a7dc0d0
--- /dev/null
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-gateways.htm
@@ -0,0 +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>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 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>Working with Gateways</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>