summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorVrishali Doke2012-10-15 04:40:58 (EDT)
committer Stephan Born2012-10-15 04:40:58 (EDT)
commit51ca25ce2639f155518e8a3d2f4c341062122e75 (patch)
tree365ed9056f825711b1dbfffadc0c73a1af36c4d9
parent6b8c510e5c8d5e5a7358862b9d0be54b5910e59b (diff)
downloadorg.eclipse.stardust.documentation-51ca25ce2639f155518e8a3d2f4c341062122e75.zip
org.eclipse.stardust.documentation-51ca25ce2639f155518e8a3d2f4c341062122e75.tar.gz
org.eclipse.stardust.documentation-51ca25ce2639f155518e8a3d2f4c341062122e75.tar.bz2
CRNT-26649 - Fixed TOC and navigations for Business Process handbook
git-svn-id: http://emeafrazerg/svn/ipp/product/trunk/stardust/documentation@60024 8100b5e0-4d52-466c-ae9c-bdeccbdeaf6b
-rw-r--r--org.eclipse.stardust.docs.analyst/analysttoc.xml2
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/cr-app.pngbin0 -> 14289 bytes
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/models/model-handling.html13
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/models/model-import.html281
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/models/model-preface.html7
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/models/model-props.html11
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/models/model-save.html51
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/models/pep-deploy-model.html322
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-activities.htm8
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-application.htm38
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-con-sequence.htm6
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-data-flow.htm4
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-data.htm6
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-events.htm9
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-gateways.htm7
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-org-struct.htm8
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-pools-lanes.htm9
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-process.htm6
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-session-log.htm17
19 files changed, 79 insertions, 726 deletions
diff --git a/org.eclipse.stardust.docs.analyst/analysttoc.xml b/org.eclipse.stardust.docs.analyst/analysttoc.xml
index 9345bc9..191cc0f 100644
--- a/org.eclipse.stardust.docs.analyst/analysttoc.xml
+++ b/org.eclipse.stardust.docs.analyst/analysttoc.xml
@@ -36,7 +36,7 @@
</topic>
<topic href="html/handbooks/modelling_analyst/pep-activities.htm" label="Specifying Activities">
</topic>
- <topic href="html/handbooks/modelling_analyst/pep-con-sequence.htm" label="Working with Sequence Flow">
+ <topic href="html/handbooks/modelling_analyst/pep-con-sequence.htm" label="Working with Sequence Flows">
</topic>
<topic href="html/handbooks/modelling_analyst/pep-application.htm" label="Specifying Application">
</topic>
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/cr-app.png b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/cr-app.png
new file mode 100644
index 0000000..ba244c1
--- /dev/null
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/cr-app.png
Binary files differ
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/models/model-handling.html b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/models/model-handling.html
index e38b686..56fba92 100644
--- a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/models/model-handling.html
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/models/model-handling.html
@@ -5,20 +5,17 @@
<meta http-equiv="Content-Style-Type" content="text/css">
<link rel="STYLESHEET" href="../../../styles/carnot.css" charset="ISO-8859-1"
type="text/css">
-<title>Creating and Deleting Models</title>
+<title>Model Operations</title>
<script language="JavaScript" src="../../../styles/naviLine.js"
type="text/javascript"></script>
</head>
<body>
<script language="JavaScript" type="text/javascript">
<!--
- writeNavigation("Model Properties",
- "PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/toc.html",
- "model-upgrade.html","model-props.html",
- "../../../toc.html","Business Analyst Handbooks",
- "../mg-preface.htm","The Modeling Guide",
- "../mg-modeler-preface.html","The Process Workbench",
- "model-preface.html","Working With Models");
+ writeNavigation("Working with Process Definitions","PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/toc.html",
+ "model-props.html","../pep-process.htm",
+ "../../toc.html","Business Process Modeling Handbook",
+ "model-preface.html", "Working with Models");
-->
</script>
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/models/model-import.html b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/models/model-import.html
deleted file mode 100644
index 5071eeb..0000000
--- a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/models/model-import.html
+++ /dev/null
@@ -1,281 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-
-<link rel="STYLESHEET" href="../../../styles/carnot.css"
- charset="ISO-8859-1" type="text/css">
-<title>Importing and Exporting Models</title>
-<script language="JavaScript" src="../../../styles/naviLine.js"
- type="text/javascript"></script>
-</head>
-<body>
-<script language="JavaScript" type="text/javascript">
-<!--
- writeNavigation("Element References",
- "PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/toc.html",
- "model-validation.html","model-element-refs.html",
- "../../../toc.html","Business Analyst Handbooks",
- "../mg-preface.htm","The Modeling Guide",
- "../mg-modeler-preface.html","The Process Workbench",
- "model-preface.html","Working With Models");
- -->
-</script>
-
-<h1>Importing and Exporting Models</h1>
-<p>This chapter comprises the following topics:</p>
-<ul>
- <li><a href="#import">Importing Models</a>
- <ul>
- <li><a href="#importModel">Import a Model from @productname@ XML</a></li>
- <li><a href="#importElements">Import Model Elements from
- @productname@ XML</a></li>
- <li><a href="#importOther">Import Other Formats</a></li>
- </ul></li>
- <li><a href="#export">Exporting Models</a>
- <ul>
- <li><a href="#exportDiagrams">Exporting Diagrams</a></li>
- <li><a href="#deploy">Deploying @productname@ Models</a></li>
- </ul></li>
-</ul>
-
-<h2 id="import">Importing Models</h2>
-<p>When importing a model from an existing model definition in XML
-format, you can choose an existing model as your target model or create
-a new one containing exclusively the imported information. In the first
-case the new information will have to be merged with the information
-already existing in the model, whereas in the latter case a new model
-will automatically be created.</p>
-<h3 id="importModel">Import a Model from @productname@ XML</h3>
-<p>To import an <tt>.xml</tt> or <tt>.xpdl</tt> file in a new model:</p>
-<ul>
- <li>In the Package Explorer right-click the project and choose <strong>Import...</strong>.</li>
- <li>Select <strong>@productnameonly@ Process Platform</strong> &gt; <strong>@productname@
- Process Model</strong>.</li>
- <li>Click <strong>Next</strong>.</li>
-</ul>
-<p class="image"><img src="images/mg-import-model.png" alt="Import">
-<br>
-<strong>Figure:</strong> Import @productname@ Model</p>
-<ul>
- <li>Choose <strong>@productname@ XML</strong> as <strong>Model
- Types</strong><br>
- .</li>
-</ul>
-<p class="image"><img src="images/mg-defdesk-6a.png" alt=""> <br>
-<strong>Figure:</strong> Importing a Model from @productname@ XML</p>
-<ul>
- <li>In the appearing browser choose the file format for the model
- you want to import in the file type list. Please refer to the chapter <a
- href="../mg-xml-1.htm">The Model File Format</a> for more information on
- process model file formats.</li>
-</ul>
-<p class="image"><img src="images/mg-import.png" alt=""></p>
-<ul>
- <li>Supply the name of the file to be imported in the appearing
- browser.</li>
-</ul>
-<p>Note that if the chosen file stores a model with an ID already
-present in the process modeling repository, the import will not be
-performed. Although you can open a model version with the same ID by
-importing model elements (see section <a href="#importElements">Importing
-Model Elements</a>), you will be prompted to commit or reject changes in the
-model during merging of model information performed at this point.</p>
-<h3 id="importElements">Import Model Elements from @productname@ XML</h3>
-<p>Please note that it is important to save your target model before
-importing elements from another model as the changes will be lost
-otherwise.</p>
-<p>To import only parts of another model:</p>
-<ul>
- <li>From the main menu choose <strong>File</strong> &gt; <strong>Import...</strong>.</li>
- <li>Select <strong>@productnameonly@ Process Model Elements</strong>.</li>
- <li>Select <strong>Next</strong>.</li>
-</ul>
-<p class="image"><img src="images/mg-import-model-elements.png"
- alt=""> <br>
-<strong>Figure:</strong> Import Model Elements</p>
-<p>Then browse to the directory where you find the file containing
-the elements to import. It is your responsibility that the imported
-elements form a consistent constellation of model information.</p>
-<p class="image"><img src="images/mg-defdesk-6b.png" alt=""> <br>
-<strong>Figure:</strong> Importing a Model Element</p>
-<p>To start the merging operation the source model and the type of
-the model (@productname@ XML, Aris Model or @productnameonly@ Process Model from Audit
-Trail) have to be chosen. After pressing the <strong>Finish</strong>
-button, the comparison dialog will be opened.<br/>
-&nbsp;</p>
-<p class="image"><img src="images/mg-import-elements.png" alt="">
-<br>
-<strong>Figure:</strong> The Comparison Dialog</p>
-<p>The comparison dialog consists of three areas:</p>
-<ul>
- <li>the <strong>@productname@ Model Differences</strong> tree at the
- top,</li>
- <li>the elements of the <strong>Source Model</strong> to the left,</li>
- <li>the elements of the <strong>Target Model</strong> to the
- right.</li>
-</ul>
-<p>The <strong>Differences </strong>tree shows all differences of
-the two models. Elements that are in the <strong>Target Model</strong>
-but not in the <strong>Source Model </strong>are marked with a green
-plus sign. Elements that are not in the <strong>Target Model</strong>
-but exists in the <strong>Source Model</strong> are marked with a green
-minus sign. Changes will be displayed within the node name of the
-element. The details of a node will be shown in the two areas below if a
-difference node is selected. It is possible to filter the differences
-tree by showing only additive, subtractive or update changes.</p>
-<p align="left"><img src="images/all_changes.gif" alt="">&nbsp;Shows
-all differences.</p>
-<p align="left"><img src="images/additive_changes.gif" alt="">&nbsp;Shows
-all additional elements.</p>
-<p align="left"><img src="images/subtractive_changes.gif" alt="">&nbsp;Shows
-all missing elements.</p>
-<p align="left"><img src="images/update_changes.gif" alt="">&nbsp;Shows
-all changes.</p>
-<p>To transfer a difference from the <strong>Source Model</strong>
-to the <strong>Target Model</strong> it is necessary to select a node in
-the <strong>Differences</strong> tree and press the button:</p>
-<p align="left"><img src="images/mg-copy-nodes.gif" alt="">&nbsp;<strong>Copy
-Selected Nodes from Left to Right.</strong></p>
-<p>The node with all its child nodes (differences) will be
-transferred. By transferring a subtractive difference the selected
-element will be deleted out of the <strong>Target Model</strong>. The
-import of the elements is only accepted after pressing <strong>Commit</strong>.</p>
-<p>You can navigate through the changes by using:</p>
-<ul>
- <li>the <img src="images/mg-next-change.gif" alt=""> <strong>Select
- Next Change</strong> button or</li>
- <li>the <img src="images/mg-previous-change.gif" alt=""> <strong>Select
- Previous Change</strong> button.</li>
-</ul>
-<p>residing in the upper right corner.</p>
-
-<h3 id="importOther">Import Other Formats</h3>
-<p>Please refer to the section <a href="../mg-import-1.htm">Importing
-Models from other Formats</a>.</p>
-<h2 id="export">Exporting Models</h2>
-<p>To export the information from your currently open model to a <tt>.xml</tt>
-or <tt>.xpld</tt> file:</p>
-<ul>
- <li>From the menu bar, choose the option <strong>File</strong>
- &gt; <strong>Export...</strong>.</li>
- <li>In the upcoming dialog choose <strong>@productname@
- Process Model</strong>.</li>
- <li>Click <strong>Next</strong>.</li>
-</ul>
-<p class="image"><img src="images/mg-export-model.png" alt="">
-<br>
-<strong>Figure:</strong> Exporting a Model</p>
-<p>Select the model or models to export from the list and the
-directory where they should be stored.</p>
-<p class="image"><br>
-<img src="images/mg-defdesk-6c.png" alt=""> <br>
-<strong>Figure:</strong> Exporting Models</p>
-<p>If you export a model with the file ending <tt>cwm</tt>, it will
-be automatically stored as <tt>.xml</tt> file, whereas a model with file
-ending <tt>xpdl</tt> will be stored as <tt>.xpdl</tt>. To get more
-information on process model file formats please refer to the chapter <a
- href="../mg-xml-1.htm">The Model File Format</a>.</p>
-<h3 id="exportDiagrams">Exporting Diagrams</h3>
-<p>As a kind of export functionality you can generate reports. That
-means you can export diagrams to an external graphical representation,
-like a JPEG or PNG file.</p>
-<p>To export diagram in the main menu, choose <strong>File
-&gt; Export... &gt; @productnameonly@ Process Model Diagram</strong>.</p>
-<p class="image"><img src="images/mg-export-diagram-1.png" alt="">
-<br>
-<strong>Figure:</strong> Exporting a Diagram</p>
-<p>In the upcoming dialog wizard, select the model you want to
-export from.</p>
-<p class="image"><a href="images/mg-export-diagram-2.png"
- target="_blank"> <img src="images/mg-export-diagram-2.png" alt=""></a>
-<br>
-<strong>Figure:</strong> The Exporting Dialog</p>
-<p>You can optionally browse a process definition to choose.</p>
-<p class="image"><img src="images/mg-export-diagram-3.png" alt="">
-<br>
-<strong>Figure:</strong> List of Process Definitions</p>
-<p>To choose the diagrams you want to export, select them from a
-list provided in a new dialog after pushing the corresponding browse
-button. If no process is selected, all the diagrams found in the model
-are listed. If a process is selected, only the diagrams of this process
-are listed.</p>
-<p class="image"><img src="images/mg-export-diagram-4.png" alt="">
-<br>
-<strong>Figure:</strong> List of Diagrams</p>
-<p>In the section <strong>To File</strong>, browse to a file or
-directory, where you want your diagrams to be stored. If there are more
-than one diagram to export, the browser will ask you for a directory to
-write the image files in. It will use default names for the files, which
-are composed of the name of the model, followed by the name of the
-process and the diagram's name. If there is only one diagram selected,
-the browser prompts you for a filename. In the file format area, choose
-the file format you want your diagrams to be saved as.</p>
-<p>There are also some possibilities to export your diagrams more
-quickly.</p>
-<p>In the Outline view:</p>
-<ul>
- <li>calling <strong>Export All Diagrams</strong> directly for the
- selected model.</li>
-</ul>
-<p class="image"><a href="images/mg-export-diagram-5_orgSize.png"
- target="_blank"> <img src="images/mg-export-diagram-5.png" alt=""></a>
-<br>
-<strong>Figure:</strong> Exporting from Selected Model</p>
-<ul>
- <li>calling <strong>Export All Diagrams</strong> directly for the
- selected process.</li>
-</ul>
-<p class="image"><img src="images/mg-export-diagram-6.png" alt="">
-<br>
-<strong>Figure:</strong> Exporting from Selected Process</p>
-<ul>
- <li>calling <strong>Export All Diagrams</strong> directly for the
- selected diagrams ( <strong>Export Diagram</strong> for one diagram).</li>
-</ul>
-<p class="image"><a href="images/mg-export-diagram-7_orgSize.png"
- target="_blank"> <img src="images/mg-export-diagram-7.png" alt=""></a>
-<br>
-<strong>Figure:</strong> Exporting from Selected Diagram</p>
-
-<p>You can also export your diagram directly from the <a
- href="../model-views/views-outline.html">Outline view</a> by
-right-clicking in the diagram area and selecting <strong>Export
-Diagram</strong> from the pop-up menu.</p>
-<p class="image"><img src="images/mg-export-diagram-8.png" alt="">
-<br>
-<strong>Figure:</strong> Exporting a Diagram</p>
-
-<h3 id="deploy">Deploying @productname@ Models</h3>
-<p>After finishing all your modeling, you should deploy your model
-to the audit trail for process execution. Be sure that a database driver
-is in the classpath and you configured the connection parameters in the
-<tt>carnot.properties</tt> correctly.</p>
-<p>To deploy a model:</p>
-<ul>
- <li>Right-click the model and select <strong>Export...</strong></li>
- <li>In the <strong>Export</strong> dialog choose <strong>@productname@
- Wizards &gt; Deploy @productnameonly@ Process Model</strong>.</li>
- <li>Select <strong>Next</strong>.</li>
-</ul>
-<p class="image"><img src="images/mg-deploy-model-export.png" alt="">
-<br>
-<strong>Figure:</strong> Deploy a Model</p>
-<p>In the <strong>Deploy @productname@ Model Process Wizard</strong>
-select the model(s) to deploy.</p>
-<p class="image"><img src="images/mg-deploy-model.png"
- alt="Deploying a @productnameonly@ Process Model"> <br>
-<strong>Figure:</strong> Deploying a @productnameonly@ Process Model</p>
-<p>Please refer to the chapter
-<a href="../mg-deploy-model.html">Deploying a Workflow Model</a>
-for detailed information on model deployment.</p>
-
-<script language="JavaScript" type="text/javascript">
-<!--
-writeFooter();
--->
-</script></p>
-</body>
-</html>
-
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/models/model-preface.html b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/models/model-preface.html
index 827383c..585bfc8 100644
--- a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/models/model-preface.html
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/models/model-preface.html
@@ -14,8 +14,7 @@
<!--
writeNavigation("Model Properties","PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/toc.html",
"../pep-perspective-overview.html","model-props.html",
- "../../toc.html","Business Process Modeling Handbook",
- "pep-perspective-overview.html", "The Business Process Modeling Perspective");
+ "../../../toc.html","Business Process Modeling Handbook");
-->
</script>
<h1>Working with Models</h1>
@@ -26,9 +25,9 @@ view a validation on the model and upgrade it from earlier versions.</p>
<ul>
<li><a href="model-props.html">Model Properties</a></li>
<li><a href="model-handling.html">Creating and Deleting Models</a></li>
- <li><a href="model-import.html">Importing Models</a>
+ <li><a href="model-import.html">Importing Models</a>
- <li><a href="model-save.html">Saving and Downloading Models</a></li>
+ <li><a href="model-save.html">Saving and Downloading Models</a></li>
<li><a href="pep-deploy-model.html">Deploying a Process Model</a></li>
</ul>
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/models/model-props.html b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/models/model-props.html
index 33a63a7..06f4c46 100644
--- a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/models/model-props.html
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/models/model-props.html
@@ -12,13 +12,10 @@
<body>
<script language="JavaScript" type="text/javascript">
<!--
- writeNavigation("Workflow Model Validation",
- "PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/toc.html",
- "model-handling.html","model-validation.html",
- "../../../toc.html","Business Analyst Handbooks",
- "../mg-preface.htm","The Modeling Guide",
- "../mg-modeler-preface.html","The Process Workbench",
- "model-preface.html","Working With Models");
+ writeNavigation("Model Operations","PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/toc.html",
+ "model-preface.html","model-handling.html",
+ "../../toc.html","Business Process Modeling Handbook",
+ "model-preface.html", "Working with Models");
-->
</script>
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/models/model-save.html b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/models/model-save.html
deleted file mode 100644
index 1ba423c..0000000
--- a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/models/model-save.html
+++ /dev/null
@@ -1,51 +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>Saving and Downloading Models</title>
-<script language="JavaScript" src="../../../styles/naviLine.js"
- type="text/javascript"></script>
-</head>
-<body>
-<script language="JavaScript" type="text/javascript">
-<!--
- writeNavigation("Cleaning up Models",
- "PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/toc.html",
- "model-import.html","model-clean.html",
- "../../../toc.html","Business Analyst Handbooks",
- "../mg-preface.htm","The Modeling Guide",
- "../mg-modeler-preface.html","The Process Workbench",
- "model-preface.html","Working With Models");
- -->
-</script>
-
-<h1>Saving and Downloading Models</h1>
-<p>To get an overview of the references of an element:</p>
-<ul>
- <li>Right-click the element either in the <a
- href="../model-views/views-outline.html">Outline view</a> or in the <a
- href="../model-views/views-diagrams.html">diagram</a>.</li>
- <li>Select <strong>References</strong>.</li>
-</ul>
-<p>You can now examine the list of the references in the <strong>Search
-View</strong>.</p>
-<p class="image"><img src="images/mg-element-references.png" alt=""> <br>
-<strong>Figure:</strong> Overview of References</p>
-<h2 id="refs">Show Elements in Diagram</h2>
-<p>If in the Search view we have elements that have symbols, you can right-click
-on them and select <tt>show in diagram</tt> to show corresponding symbol in
-the diagram, as shown below.</p>
-<p class="image"><img src="images/mg-element-references-show.png" alt=""> <br>
-<strong>Figure:</strong> Show Elements in Diagram</p>
-
-
-<script language="JavaScript" type="text/javascript">
-<!--
-writeFooter();
--->
-</script>
-</body>
-</html>
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/models/pep-deploy-model.html b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/models/pep-deploy-model.html
deleted file mode 100644
index 23da721..0000000
--- a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/models/pep-deploy-model.html
+++ /dev/null
@@ -1,322 +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>Deploying a Workflow Model</title>
-<script language="JavaScript" src="../../styles/naviLine.js"
- type="text/javascript"></script>
-</head>
-<body>
-<script language="JavaScript" type="text/javascript">
-<!--
- writeNavigation("Debugging Process Definitions","PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/toc.html",
- "mg-ref-elements.htm","mg-defdesk-18.htm",
- "../../toc.html","Business Analyst Handbooks",
- "mg-preface.htm","The Modeling Guide",
- "mg-modeler-preface.html","The Process Workbench");
- -->
-</script>
-
-<h1>Deploying a Workflow Model</h1>
-<p>Model deployment makes the process definitions available to the
-runtime environment, so that all processes can be executed according to
-the definitions of this model. To support model version deployment, the
-@productnameonly@ Process Workbench provides a Deploy Model option, which</p>
-<ul>
- <li>executes a consistency check and informs the deployer which
- inconsistencies have been found in the model,</li>
- <li>determines which models have already been deployed to this
- runtime environment as well as whether (or how) the current version
- can be deployed to this environment and which</li>
- <li>writes the model definition to the audit trail database.</li>
-</ul>
-<p>At the time you are deploying a model, all @productname@ daemons
-must not be running. This will apply the first time to deployments
-subsequent to the first model version.</p>
-<ul>
- <li><a href="#modeler">Deploying a Model in the Process Modeler</a></li>
- <li><a href="#login">Login Dialog</a></li>
- <li><a href="#version">Version Deployment</a></li>
- <li><a href="#consistency">Consistency Checks</a></li>
-
-</ul>
-<h2 id="modeler">Deploying a Model in the Process Modeler</h2>
-<p>To deploy a model version proceed as follows:</p>
-<ul>
- <li>Start the server.</li>
- <li>Right-click the model in the Outline view.</li>
- <li>Select <strong>Deploy</strong>.</li>
-</ul>
-<p class="image"><img src="images/deploy-model.png"
- alt="Deploying a @productnameonly@ Process Model"><br>
-<strong>Figure:</strong> Deploying a @productnameonly@ Process Model</p>
-<p>To skip the following dialogs like the login dialog and the version
-dialog, you can set appropriate preferences in the <strong>@productname@ Preferences</strong>,
-like the option to always overwrite model versions and providing the credentials for
-the deployment authentication. Please refer to the section
-<a href="mg-preferences.html#deployment">Deployment</a> of the chapter
-<a href="mg-preferences.html#">Setting @productname@ Preferences</a>
-for detailed information on available deployment preferences.</p>
-<p>For details on deployment settings like using custom environment settings etc., refer
-to chapter
-<a href="PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/handbooks/modelling/mg-deploy-model.html">
-Deploying a Workflow Model</a>
-of the
-<a href="PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/handbooks/handbooks.htm">
-Developer Handbook</a>.</p>
-
-<h3>Adding a Deployment Toolbar Button</h3>
-<p>To be able to quickly start a model deployment from the perspective
-toolbar, @productname@ provides a deployment button, which can be added
-to the currently open perspective in the following way:</p>
-<ol>
- <li>In the main menu, select <strong>Window &gt; Customize Perspective</strong>.</li>
- <li>In the <strong>Customize Perspective</strong>, select the <strong>Commands</strong>
- tab.</li>
- <li>In the <strong>Available command groups</strong> section, select
- <strong>@productname@</strong>.</li>
- <li><strong>OK</strong> the dialog.</li>
-</ol>
-<p class="image"><img src="images/mg-add-deploy-button.png"
- alt="Deploy Icon"><br>
-<strong>Figure:</strong> Add an Icon for Model Deployment to the Toolbar.</p>
-<p>Now a button to start a model deployment is available in the perspective
-toolbar:</p>
-<p class="image"><img src="images/mg-add-deploy-icon.png"
- alt="Deploy Option"><br>
-<strong>Figure:</strong> Model Deployment Option in the Toolbar.</p>
-<p>Note that the deploy option only starts in case a model editor is currently open.
-The deployment then starts with the currently open model.</p>
-<p>For more information on the deployment of multiple models in one audit trail database,
-please refer to <a href="PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/handbooks/modelling/mg-deploy-model.html#multideploy">
-Deploying Multiple Models from One Audit Trail</a> section of the <a href="PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/handbooks/modelling/mg-deploy-model.html">Deploying a Workflow Model</a> chapter
-of the <a
- href="PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/handbooks/handbooks.htm">Developer Handbook.</a>
-</p>
-
-<h3 id="pre">PredefinedModel in Deployment Dialog</h3>
-<p>Note that when you are deploying a model, the <strong>Deploy Model</strong>
-dialog also displays the PredefinedModel. This is the technical model which gets deployed automatically
-at the time of deployment. It gets deployed at the time of first deployment of any other model but
-it is visible in the Deployment dialog if at least one model version is already deployed.
-For more information, please refer to the section
-<a href="PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/handbooks/concepts/executing-workflow/case-concept.html#tech">Predefined Model
-</a> of the <a href="PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/handbooks/concepts/executing-workflow/case-concept.html">
-Case - Grouping Processes</a> chapter of
-the <a href="PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/handbooks/concepts/key-concept.html">Concepts Handbook.</a>
-</p>
-<p class="image"><img src="images/mg-deploy-predefined.png"
- alt="PredefinedModel"><br>
-<strong>Figure:</strong> Model Deployment - PredefinedModel</p>
-
-
-
-
-
-<h2 id="login">Login Dialog</h2>
-<p>In case no default user and password for the deployment login
-are set in the <strong>@productname@ Preferences</strong>,
-a login dialog opens with entry fields for the required credentials.
-Per default, the administrator
-account motu (username: <tt>motu</tt>, password: <tt>motu</tt>)
-is required.
-Please refer to the section
-<a href="mg-preferences.html#deployment">Deployment</a> of the chapter
-<a href="mg-preferences.html#">Setting @productname@ Preferences</a>
-for detailed information on the available deployment preferences.</p>
-
-<h2 id="version">Version Deployment</h2>
-<p>At the time of deployment @productname@ performs a check whether
- the model to be deployed is a version of the existing model(s).
-
-</p>
-<p>A model version dialog opens, where you can choose to
-overwrite a model version or to create a new model version along
-with other optional settings like validity date or deployment
-comment.</p>
-<p class="image"><a href="images/ag-deployment-8_orgSize.jpg"
- target="_blank"> <img src="images/ag-deployment-8.jpg"
- width="650" height="332" alt=""></a> <br>
-<strong>Figure:</strong> Version Deployment to a Runtime Environment
-with Existing Active Model</p>
-<p>You have the option to skip this dialog and use the default
-option to always deploy a new model version, by setting as preference
-in your <strong>@productname@ Preferences</strong>. Please
-refer to the section
-<a href="mg-preferences.html#deployment">Deployment</a> of the chapter
-<a href="mg-preferences.html#">Setting @productname@ Preferences</a>
-for detailed information on how to set this preference.</p>
-<p>Since the check is based on the model ID, it is your
-responsibility to ensure that you deploy a successor version of the
-model already deployed and you do not deploy an entirely different model
-with the same model ID. The ID and the OID of the model version are the
-criteria, which @productname@ analyzes to determine whether you should
-perform version deployment or overwriting.</p>
-
-<p>When deploying a version to a runtime environment with already
-deployed versions, @productname@ automatically chooses between two possible
-operations: version deployment or overwriting.</p>
-<ul>
- <li>Version deployment is chosen if the model to be deployed
- does not have an OID.</li>
- <li>Version overwriting is selected if the model to be deployed
- already has an OID received by a previous deployment operation.</li>
- <li>The version number helps administrators to keep track of
- the model and has only visual semantics.</li>
-</ul>
-<p>Regardless of the selection performed automatically by the
-deployment dialog, you have the option to override the selection
-and manually choose which operation to perform.</p>
-
-<p class="ind"><strong>Note:</strong>
-In production mode, overwriting should be performed with extreme
-caution. If the model to be overwritten contains elements that were
-deleted in the model to be deployed and those model elements have
-corresponding runtime audit trail objects, overwriting can introduce
-serious inconsistencies in the audit trail database.</p>
-<p>Please refer to the chapter
-<a href="PLUGINS_ROOT/org.eclipse.stardust.docs.deployment/html/deploy-model.html">
-Deploying a Workflow Model</a> of the
-<a href="PLUGINS_ROOT/org.eclipse.stardust.docs.deployment/html/toc.html">
-Deployment Guide</a>, which discusses model version deployment
-in detail.</p>
-<p class="image"> <img src="images/ag-deployment-9.png" alt=""> <br>
-<strong>Figure:</strong> Overwriting a Model</p>
-<p>In the figure above, the version 3.0 is being redeployed to the
-audit trail database. @productname@ compares the version ID and OID which
-results in enabling the option <strong>Overwrite</strong> instead of
-version deployment.</p>
-<h2 id="consistency">Consistency Checks</h2>
-
-<p>If the model has consistency deficiencies, the automatic
-consistency check, which otherwise remains invisible to you, will issue
-a list of inconsistencies found. There are two categories of
-inconsistencies:</p>
-<ul>
- <li>Fatal inconsistencies may cause crashes of the @productname@
- runtime environment.</li>
- <li>Minor inconsistencies may cause unexpected behavior.</li>
-</ul>
-<p>For cosistency checks of dependent models, please refer to <a href="PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/handbooks/modelling/mg-deploy-model.html#concheck2">
-Consistency Checks for Dependent Models Deployed in One Audit Trail Partition</a> section of the chapter
-<a href="PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/handbooks/modelling/mg-deploy-model.html">Deploying a Workflow Model</a>
-of the <a
- href="PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/handbooks/handbooks.htm">Developer Handbook.</a>
-</p>
-
-<h3>Consistency Checks for Scoped Participants</h3>
-<p>The following rules apply to version deployment consistency checks
-as well as for overwrite deployment consistency checks:</p>
-<ul>
- <li><a href="#scopedAuth">Scoped participants used for model level grants</a></li>
- <li><a href="#scopedOrg">Unscoped organization followed by scoped organization</a></li>
- <li><a href="#dataPathChange">Changed data or data path for department</a></li>
- <li><a href="#validData">Invalid data types for departments</a></li>
- <li><a href="#structure">Changes in the organizational structure</a></li>
- <li><a href="#dupId">Duplicate Participant ID</a></li>
- <li><a href="#adminRel">Administrator role has relationsship</a></li>
- <li><a href="#superorg">Multiple superorganizations</a></li>
-</ul>
-
-<h4 id="scopedOrg">Unscoped Organization followed by Scoped Organization</h4>
-<p>If in any model of the audit trail a certain organization exists and is unscoped,
-it is not possible to deploy a successor model version that contains this organization
-as a scoped organization. A consistency error occurs, notifying that the organization
-is scoped, but in the audit trail it is unscoped. The deployment fails.</p>
-<p class="image"><img src="images/deploy-valid-scoped-org.png"><br>
-<strong>Figure:</strong> Consistency Error for Scoped Organization former Unscoped</p>
-<p>Likewise it is also not supported to change from a scoped to an unscoped
-organization in model version deployment.</p>
-<h4 id="dataPathChange">Changed Data or Data Path for Department</h4>
-<p>If in any model of the audit trail a certain organization exists and is scoped,
-it is not allowed to deploy a successor model version that contains this organization
-as a scoped organization, but uses a different data or data path to retrieve the
-scope identified. A consistency error occurs, notifying that the ID of the
-data or the data path is different from the data ID of the deployed
-scoped organization in the audit trail. The deployment fails.</p>
-<p class="image"><img src="images/deploy-valid-changed-data.png"><br>
-<strong>Figure:</strong> Consistency Error for Changed Data.</p>
-<h4 id="validData">Invalid Data Types for Departments</h4>
-<p>Only primitive or structured data with type <tt>java.lang.String</tt> are
-allowed. In case other types are used a consistency error occurs, notifying
-that the data type used to retrieve the department for the scoped organization
-is not valid. The deployment fails.</p>
-<p class="image"><img src="images/deploy-valid-data.png"><br>
-<strong>Figure:</strong> Consistency Error for Unsupported Data Type.</p>
-
-<h4 id="structure">Changes in the organizational structure</h4>
-<p>It is not supported to deploy a succeeding version with changes in
-the department association for existing roles or organizations.
-That means that for any scoped organization and its entire subtree
-(all roles and organizations directly or indirectly connected to
-this organization via "Part Of" or "Works For" or "Manager Of") it is not allowed to:</p>
-<ul>
- <li>remove any "Part Of" or "Works For" association for any pair of organizations.</li>
- <li>change any node of any "Part Of" or "Works For" association.</li>
- <li>create new associations to other organizations or roles previously not
- belonging to the subtree.</li>
-</ul>
-<p>All operations that will change the number or order of declared departments for
-any of the participants are not supported.</p>
-
-<!--<h5>Supported organizational changes</h5>-->
-<p>However, the following changes are allowed:</p>
-<ul>
- <li>adding a new role, which previously was not contained in the predecessor
- model version, as a "Works For" or "Manager Of" role.</li>
- <li>completely removing a role from the model that previously was associated
- with a scoped organization via "Works For" or "Manager of".</li>
- <li>adding a new organization, which is not contained in the predecessor model
- version, as a "Part Of" of an existing scoped organization.
- Please note that if the added organization has suborganizations,
- "Works For" roles or "Manager Of" roles, these have to follow the same rules
- as for adding roles and organizations.
- This means that a new organizational subtree may only be added if all its parts
- previously were not part of the model.</li>
- <li>delete a complete tree of scoped participants, thus
- the root node and its entire subtree, like suborganizations and
- "Works For" roles or "Manager Of" roles. It is not allowed to remove only parts
- of a scoped organization.</li>
-</ul>
-<p>In case changes in the organizational structures, which are not allowed to be
-deployed in a succeeding model version, have been performed, a consistency error
-occurs, notifying that the organization tree
-is different from the tree in the model that was deployed earlier.
-The deployment fails.</p>
-<p class="image"><img src="images/deploy-valid-tree.png"><br>
-<strong>Figure:</strong> Consistency Error for Changed Participant Tree.</p>
-
-<h4 id="dupId">Duplicate Participant ID</h4>
-<p>IDs for participants have to be unique within all model participants
-like roles, organizations
-or conditional performer. In case you use the same ID for more than one
-participant, the deployment fails with the following error:</p>
-<p class="image"><img src="images/deploy-valid-id.png"><br>
-<strong>Figure:</strong> Consistency Error for Duplicate Participant ID.</p>
-<h4 id="adminRel">Administrator role has relationsship</h4>
-<p>The <strong>Administrator</strong> role is not allowed to have
-relationships to any organization. In case such a connection exist
-in the model, the deployment fails with the following consistency
-error:</p>
-<p class="image"><img src="images/deploy-valid-admin.png"><br>
-<strong>Figure:</strong> Consistency Error for unsupported Relationship of Administrator.</p>
-<h4 id="superorg">Multiple Superorganizations</h4>
-<p>Since release 5.2., it is not supported that a model participant has
-multiple superorganizations. Only one or zero relationships to other
-model participants are allowed, otherwise a consistency error occurs
-during model deployment and the deployment fails.</p>
-<p class="image"><img src="images/deploy-valid-mult-orgs.png"><br>
-<strong>Figure:</strong> Consistency Error for Multiple Superorganizations.</p>
-
-
-<script language="JavaScript" type="text/javascript">
-<!--
-writeFooter();
--->
-</script>
-</body>
-</html>
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-activities.htm b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-activities.htm
index a51cdf0..cb6db2e 100644
--- a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-activities.htm
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-activities.htm
@@ -11,11 +11,9 @@
<body>
<script language="JavaScript" type="text/javascript">
<!--
- writeNavigation("Working with Transitions","PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/toc.html",
- "mg-defdesk-3.htm","mg-defdesk-5.htm",
- "../../toc.html","Business Analyst Handbooks",
- "mg-preface.htm","The Modeling Guide",
- "mg-modeler-preface.html","The Process Workbench");
+ writeNavigation("Working with Sequence Flows","PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/toc.html",
+ "pep-process.htm","pep-con-sequence.htm",
+ "../../toc.html","Business Process Modeling Handbook");
-->
</script>
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-application.htm b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-application.htm
index c1a7d20..f717a0c 100644
--- a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-application.htm
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-application.htm
@@ -12,9 +12,8 @@
<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");
+ "pep-con-sequence.htm","pep-data.htm",
+ "../../toc.html","Business Process Modeling Handbook");
-->
</script>
@@ -22,9 +21,36 @@
<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>
+<p>This section will explain how to work with applications in the
+<strong>Business Process Modeling</strong> perspective.</p>
+<ul>
+ <li><a href="#cra">Creating Application</a></li>
+ <li><a href="#ra">Renaming Application</a></li>
+ <li><a href="#da">Deleting Application</a></li>
+ <li><a href="#ve">Viewing and Editing Application Properties</a>
+ <ul>
+ <li>Message Transformation Application</li>
+ <li>Camel Route Application</li>
+ <li>Web Service Application</li>
+ <li>UI Mashup</li>
+
+ </ul></li>
+</ul>
+
+<h2 id="cra">Creating Application</h2>
+
+<p>To create an application, right-click on the <strong>Application</strong> node in the
+<strong>My Process Models</strong> panel and select the type of the application you want to create.</p>
+<p class="image"><img src="images/cr-app.png"
+ alt=""> <br>
+<strong>Figure:</strong> Create Application</p>
+
+
+
+
+
+<!--
<h2>Creating Applications</h2>
<p>To create an application you can either:</p>
<ul>
@@ -89,7 +115,7 @@ application's pop-up menu in a diagram. In the <strong>Outline</strong> view, us
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>
+be part of the model.</p> -->
<script language="JavaScript" type="text/javascript">
<!--
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-con-sequence.htm b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-con-sequence.htm
index 473b9fa..62b6e3e 100644
--- a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-con-sequence.htm
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-con-sequence.htm
@@ -14,10 +14,8 @@
<script language="JavaScript" type="text/javascript">
<!--
writeNavigation("Specifying Applications","PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/toc.html",
- "mg-defdesk-4.htm","mg-defdesk-6.htm",
- "../../toc.html","Business Analyst Handbooks",
- "mg-preface.htm","The Modeling Guide",
- "mg-modeler-preface.html","The Process Workbench");
+ "pep-activities.htm","pep-application.htm",
+ "../../toc.html","Business Process Modeling Handbook");
-->
</script>
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-data-flow.htm b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-data-flow.htm
index b3eac3f..e4a9159 100644
--- a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-data-flow.htm
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-data-flow.htm
@@ -10,7 +10,9 @@
<body>
<script language="JavaScript">
<!--
- writeNavigation("Modeling the Organizational Structure","PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/toc.html", "mg-defdesk-7.htm","mg-defdesk-10.htm", "../../toc.html","Business Analyst Handbooks", "mg-preface.htm","The Modeling Guide", "mg-modeler-preface.html","The Process Workbench");
+ writeNavigation("Working with Gateways","PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/toc.html",
+ "pep-data.htm","pep-gateways.htm",
+ "../../toc.html","Business Process Modeling Handbook");
-->
</script>
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-data.htm b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-data.htm
index f5f8574..8363c5b 100644
--- a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-data.htm
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-data.htm
@@ -11,9 +11,9 @@
<body>
<script language="JavaScript" type="text/javascript">
<!--
- writeNavigation("Data Mappings","PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/toc.html",
- "mg-defdesk-6.htm","mg-defdesk-8.htm","../../toc.html","Business Analyst Handbooks",
- "mg-preface.htm","The Modeling Guide","mg-modeler-preface.html","The Process Workbench");
+ writeNavigation("Specifying Data Flow","PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/toc.html",
+ "pep-application.htm","pep-data-flow.htm",
+ "../../toc.html","Business Process Modeling Handbook");
-->
</script>
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
index 4a0a1fb..ac2a09f 100644
--- 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
@@ -12,12 +12,9 @@
<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");
+ writeNavigation("Swim Lanes Usage","PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/toc.html",
+ "pep-org-struct.htm","pep-pools-lanes.htm",
+ "../../toc.html","Business Process Modeling Handbook");
-->
</script>
<h1>Working with Events</h1>
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
index c585c0c..8c6a13a 100644
--- 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
@@ -11,10 +11,9 @@
<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");
+ writeNavigation("Modeling the Organizational Structure","PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/toc.html",
+ "pep-data-flow.htm","pep-org-struct.htm",
+ "../../toc.html","Business Process Modeling Handbook");
-->
</script>
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-org-struct.htm b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-org-struct.htm
index 6aa3350..45c7e8c 100644
--- a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-org-struct.htm
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-org-struct.htm
@@ -11,11 +11,9 @@
<body>
<script language="JavaScript" type="text/javascript">
<!--
- writeNavigation("Specifying Arbitrary Link Types","PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/toc.html",
- "mg-defdesk-8.htm","mg-defdesk-14.htm",
- "../../toc.html","Business Analyst Handbooks",
- "mg-preface.htm","The Modeling Guide",
- "mg-modeler-preface.html","The Process Workbench");
+ writeNavigation("Working with Events","PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/toc.html",
+ "pep-gateways.htm","pep-events.htm",
+ "../../toc.html","Business Process Modeling Handbook");
-->
</script>
<h1>Modeling the Organizational Structure</h1>
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-pools-lanes.htm b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-pools-lanes.htm
index f3d36b6..615712c 100644
--- a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-pools-lanes.htm
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-pools-lanes.htm
@@ -12,12 +12,9 @@
<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");
+ writeNavigation("Modeling Session Log","PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/toc.html",
+ "pep-events.htm","pep-session-log.htm",
+ "../../toc.html","Business Process Modeling Handbook");
-->
</script>
<h1>Swim Lanes Usage</h1>
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-process.htm b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-process.htm
index d92da5c..e25b226 100644
--- a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-process.htm
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-process.htm
@@ -12,10 +12,8 @@
<script language="JavaScript" type="text/javascript">
<!--
writeNavigation("Specifying Activities","PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/toc.html",
- "models/model-preface.html","mg-defdesk-4.htm",
- "../../toc.html","Business Analyst Handbooks",
- "mg-preface.htm","The Modeling Guide",
- "mg-modeler-preface.html","The Process Workbench");
+ "models/model-preface.html","pep-activities.htm",
+ "../../toc.html","Business Process Modeling Handbook");
-->
</script>
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-session-log.htm b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-session-log.htm
index 33323a8..b28a536 100644
--- a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-session-log.htm
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-session-log.htm
@@ -5,21 +5,22 @@
<meta http-equiv="Content-Style-Type" content="text/css">
<link rel="STYLESHEET" href="../../styles/carnot.css" charset="ISO-8859-1" type="text/css">
-<title>Working with Process Definitions</title>
+<title>Modeling Session Log</title>
<script language="JavaScript" src="../../styles/naviLine.js" type="text/javascript"></script>
</head>
<body>
<script language="JavaScript" type="text/javascript">
<!--
- writeNavigation("Specifying Activities","PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/toc.html",
- "models/model-preface.html","mg-defdesk-4.htm",
- "../../toc.html","Business Analyst Handbooks",
- "mg-preface.htm","The Modeling Guide",
- "mg-modeler-preface.html","The Process Workbench");
+ writeNavigation("","PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/toc.html",
+ "pep-pools-lanes.htm","",
+ "../../toc.html","Business Process Modeling Handbook");
-->
</script>
-<h1>Working with Process Definitions</h1>
+<h1>Modeling Session Log</h1>
+
+
+<!--
<p>The Business Process Modeling perspective visualizes the existing process definitions in the
<strong>My Process Models</strong> panel under model element. You can create, rename and delete process definitions.
Each process definition has its property panel wherein you can modify its properties.
@@ -168,7 +169,7 @@ A typical process definition contains swim lanes, activities and gateways, appli
<p>For more information, please refer to the chapter
<a href="PLUGINS_ROOT/org-eclipse.stardust.docs.dev/html/handbooks/modelling/mg-defdesk-3.htm">Working with Process Definition</a>
-
+ -->
<script language="JavaScript" type="text/javascript">