CRNT-25178 - Added Cross model documentationv1.0.0.20130206-1300

git-svn-id: http://emeafrazerg/svn/ipp/product/trunk/stardust/documentation@62335 8100b5e0-4d52-466c-ae9c-bdeccbdeaf6b

19 files changed, 143 insertions, 138 deletions

diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/add-pro-param.png b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/add-pro-param.png
index a3b3e2a..3cfadc2 100644
--- a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/add-pro-param.png
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/add-pro-param.png
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/circular.png b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/circular.png
new file mode 100644
index 0000000..2d9a21b
--- a/dev/null
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/circular.png
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/data-flow-pi.png b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/data-flow-pi.png
new file mode 100644
index 0000000..5bca3e4
--- a/dev/null
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/data-flow-pi.png
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/data-path.png b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/data-path.png
index 7c23329..8b88058 100644
--- a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/data-path.png
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/data-path.png
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/pi-context.png b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/pi-context.png
new file mode 100644
index 0000000..8c960d0
--- a/dev/null
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/pi-context.png
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/ref-app-activity.png b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/ref-app-activity.png
new file mode 100644
index 0000000..c97dca1
--- a/dev/null
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/ref-app-activity.png
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/ref-app.png b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/ref-app.png
new file mode 100644
index 0000000..496dec5
--- a/dev/null
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/ref-app.png
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/ref-data.png b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/ref-data.png
new file mode 100644
index 0000000..dc56a53
--- a/dev/null
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/ref-data.png
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/ref-lane.png b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/ref-lane.png
new file mode 100644
index 0000000..54b8488
--- a/dev/null
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/ref-lane.png
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/ref-parti.png b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/ref-parti.png
new file mode 100644
index 0000000..085d961
--- a/dev/null
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/ref-parti.png
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/ref-pro.png b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/ref-pro.png
new file mode 100644
index 0000000..a04651b
--- a/dev/null
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/ref-pro.png
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/ref-struct.png b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/ref-struct.png
new file mode 100644
index 0000000..38dfb9a
--- a/dev/null
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/ref-struct.png
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 a81199b..1b3fd45 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
@@ -327,7 +327,7 @@ nor selected. The message names themselves are not filtered. The top level tree
 
 
 <h3 id="cam">Camel Route Application</h3>
-<p>Following properties of the comel route application need to be specified:</p>
+<p>Following properties of the camel route application need to be specified:</p>
 
 
 <h4>Route Definitions</h4>
@@ -414,6 +414,20 @@ nor selected. The message names themselves are not filtered. The top level tree
     Body.</li>
 </ul>
 
+<h2>Working with Referenced Application</h2>
+
+
+<p>If the <strong>Public Visibility</strong> check box is selected of the application, then it can 
+be referenced in the consumer model. To reference the application, drag and drop the application from the
+provider model to the consumer model.</p>
+
+<p class="image"><img src="images/ref-app.png">
+<br> <strong>Figure:</strong> Drag and Drop the Application to Consumer Model</p>
+
+<p>Based on the application type, it gets converted to appropriate task types.</p>
+<p class="image"><img src="images/ref-app-activity.png">
+<br> <strong>Figure:</strong> Referenced Application converted to Script Task</p>
+
 
 <script language="JavaScript" type="text/javascript">
 <!-- 
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 baf8be5..e0203d0 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
@@ -33,8 +33,11 @@ is indicated by arrows:
 <ul>
 	<li>One input data mapping</li>
 	<li>One output data mapping</li>
-	<li>A pair of the two </li>
+	<li>A pair of the two, per data </li>
 </ul>
+<p>In case multiple data mappings exist between one data and one activity, only the first data mapping
+will be displayed.</p>
+
 
 <h2>Creating Data Flow Connection</h2>
 <p>You can create data flow connections using two different ways: </p>
@@ -78,8 +81,8 @@ is indicated by arrows:
 			<li>Input - Select this check box to specify in data flow. If the input data flow is created while connecting
 			activity with data then this check box is selected by default.</li>
 			<li>Output - Select this check box to specify out data flow.</li>
-			<li>Input Data Path - Specify the input data path.</li>
-			<li>Output Data Path - Specify the output data path.</li>
+			<li>Input Data Path - Enabled when <strong>Input</strong> check box is selected. Specify the input data path.</li>
+			<li>Output Data Path - Enabled when <strong>Output</strong> check box is selected. Specify the output data path.</li>
 			<li>Output Access Point - The <strong>Default</strong> option is selected by default. It also contains 
 			the option <strong>Activity Instance</strong>.			
 			</li>
@@ -88,80 +91,38 @@ is indicated by arrows:
 	</li>	 
 </ol>
 
+<h2>Data Mappings in Process Interface Context</h2>
 
+<p>The Process Interface Context is needed when one model is referring to another model through exposed process interface. 
+Suppose the referred subprocess has IN parameters defined and it returns the result. Then, in this case. the called process 
+should know the IN and OUT parameters. So if the referred process has exposed the parameters 
+then you need to provide the data mappings in the process interface context.
+</p>
+<p>
+Note that the data type specified in the formal parameters should match with the data type 
+specified in the consumer model. For example, you have defined structure data type 
+in the provider model. To access the same structured data in the consumer model, 
+you need to drag and drop the structured data and reference through the data mappings.
+</p>
+<p>To specify the process interface context, perform the following steps:
+</p>
 
+<ol>
+	<li>Create the data flow between the referred subprocess and the data</li>
+	<li>Click the data flow connection</li>
+	<p class="image"><img SRC="images/data-flow-pi.png">
+<br><strong>Figure:</strong> Data Flow - Referred Elements</p>
+ 	<li>Specify the data path in the <strong>Input Data Path</strong> text box.</li>
+ 	<li>In the <strong>Input Access Point</strong> drop-down list, from the <strong>processInterface</strong> option
+ 	select the specified parameter. If <strong>Input</strong> check box is selected, then only this field is enabled.</li>
+ 	<p class="image"><img SRC="images/pi-context.png">
+<br><strong>Figure:</strong> Input Access Point - Process Interface Context</p>
+ 	
+	<li>Similarly, you can specify Output Access Point if the <strong>Output</strong> check box is selected.</li>
 
+</ol>
 
 
-<!-- 
-<h2>
-  Data Mapping Connection</h2>
-<P  >
-After data mappings are created they render automatically in the <strong>Process Workbench</strong> as connections between the activity symbol and the data symbol. There is at most one data mapping connection between an activity and a data, summarizing all existing data mappings for them. The data mapping direction is indicated by arrows: </P>
-<UL>
-<LI  >
-If there is an In data mapping to the activity the connection is labeled with an arrow to the activity.</LI>
-<LI  >
-If there is an Outdata mapping to the data the connection is labelled with an arrow to the data.</LI>
-<LI  >
-If there are data mappings for both directions, both arrows are drawn.</LI>
-</UL>
-<p class="image"><IMG SRC="images/mg-defdesk-29.png">
-<br><strong>Figure:</strong> An In Data Mapping Connection</p>
-<P  >
-There is a shortcut to create a first data mapping between an activity and a data: in the diagram containing the activity and the data element you can map the data as the activity's input/output. To do this, proceed as follows:</P>
-<ul>
-	<li>Right-click the data.</li>
-	<li>Select <strong>Connect</strong> in the context menu.</li>
-	<li>Click the activity.</li>
-</ul>
-<p class="image"><img SRC="images/mg-connect-data-mapping.png">
-<br><strong>Figure:</strong> Create a In Data Mapping</p>
-<p>An In data mapping is created, visualized by a data mapping connection.</p>
-<p>If you have created at least one link type with source type <strong>Data</strong> and 
-target type <strong>Activity</strong>, you have the choice to select
-between these custom link types and the standard data mapping connection type. Please refer to chapter
-	<a href="mg-defdesk-14.htm">Specifying Arbitrary Link Types</a> for information on custom 
-	link types.</p>
-<p class="image"><img SRC="images/mg-connect-data-mapping-select.png">
-<br><strong>Figure:</strong> Select the Link Type for Data Mapping</p>
-<P  >To create an Out data mapping, this works the other way around:</p>
-<ul>
-	<li>Right-click the activity first.</li>
-	<li>Select <strong>Connect</strong> in the context menu.</li>
-	<li>Click the data.</li>
-</ul>
-<p class="image"><img SRC="images/mg-connect-out-data-mapping.png">
-<br><strong>Figure:</strong> Create an Out Data Mapping</p>
-<p>In case of process interface context, please refer to the section 
-<span class="showReference">
-<a href="PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/handbooks/modelling/mg-defdesk-8.htm#PI">Data Mappings in Process Interface Context
-</a>
-</span><span class="hideReference">
-<strong>Data Mappings in Process Interface Context</strong></span>
- of the chapter 
-<span class="showReference">
-<a href="PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/handbooks/modelling/mg-defdesk-8.htm">
-Data Mappings</a></span><span class="hideReference">
-<strong>Data Mappings</strong></span>
- in the 
-<span class="showReference">
-<a href="PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/handbooks/handbooks.htm">Developers Handbook</a>.</p> 
-</span><span class="hideReference">
-<strong>Developers Handbook</strong> of the <strong>@productname@ Documentation</strong>.</span>
-<h2>
-  Deleting Data Mappings</h2>
-
-<p>A data mapping can be deleted by</p>
-<UL>
-<li> selecting it in the diagram view and choosing <strong>Delete</strong> from the pop-up menu.
-To delete only the symbol, choose <strong>Delete Symbol </strong>or </li>
-<li>
-by selecting it in the data mapping properties pane of the activity's properties dialog and pressing the <strong>Delete</strong> button.
-</li>
-
-</UL> -->
-
 <script language="JavaScript">
 <!-- 
 writeFooter(); 
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 3cd3dbf..03a2611 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
@@ -217,9 +217,15 @@ To delete the comment, select the comment and click the <strong>Delete</strong>
 <p class="image"><img src="images/data-comment.png" alt=""> <br>
 <strong>Figure:</strong> Data - Comment</p>
 
+<h2>Working with Referenced Data</h2>
 
+<p>If the <strong>Public Visibility</strong> check box is selected of the data, then it can 
+be referenced in the consumer model. To reference the data, drag and drop the data from the
+provider model to the consumer model.</p>
+<p class="image"><img src="images/ref-data.png" alt=""> <br>
+<strong>Figure:</strong> Drag and Drop the Data to Consumer Model</p>
 
-
+<p>The data gets referred in the consumer model.</p>
 
 
 
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-modeler-compatibility.html b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-modeler-compatibility.html
index c4e1d96..0c839a1 100644
--- a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-modeler-compatibility.html
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-modeler-compatibility.html
@@ -101,6 +101,8 @@ When imported, only those models are displayed properly in the Business Process
 	<li>One output data mapping</li>

 	<li>A pair of the two </li>

 </ul>

+<p>In case multiple data mappings exist between one data and one activity, only the first data mapping

+will be displayed.</p>

 <h3 id="conf">Conditional Sequence Flow</h3>

 <p>The web-based modeler supports setting conditional sequence flow only from gateways to activities.

 However, if you import a model created in Eclipse and it has conditional sequence flow from activity to activity.

@@ -361,60 +363,7 @@ can only edit General Properties of these elements. </p>
 	

 </table>

 

-<!-- 

 

-<h2>Content</h2>

-<ul>

-    <li><a href="mg-preferences.html">Setting @productname@ Preferences</a></li>

-    <li class="expand" onclick="openClose(this, 'persp')">

-    <a href="mg-modeler-views.html">The Analyst Perspective</a>

-    <li class="noicon" id="persp" style="display: none;">

-    <ul>

-    	<li><a href="model-views/views-outline.html">Outline view</a></li>

-        <li><a href="model-views/views-diagrams.html">Working with Diagrams</a></li>

-        <li><a href="model-views/views-cheat.html">Cheat Sheet View</a></li>

-        <li><a href="model-views/views-repository.html">@productnameonly@ Process Model Repository</a></li>

-        <li><a href="model-views/views-bookmark.html">@productnameonly@ Process Model Bookmarks</a></li>

-        <li><a href="model-views/views-traversal.html">@productnameonly@ Process Model Traversal</a></li>

-        <li><a href="model-views/views-simplify.html">Simplifying the Modeler View</a></li>

-    </ul></li>

-    <li class="expand" onclick="openClose(this, 'model')">

-    <a href="models/model-preface.html">Working with Models</a></li>

-    <li class="noicon" id="model" style="display: none;">

-    <ul>

-        <li><a href="models/model-upgrade.html">Model Upgrade</a></li>

-        <li><a href="models/model-handling.html">Creating and Deleting Models</a></li>

-        <li><a href="models/model-props.html">Model Properties</a></li>

-        <li><a href="models/model-validation.html">Workflow Model Validation</a></li>

-        <li><a href="models/model-import.html">Importing and Exporting Models</a>

-        <li><a href="models/model-element-refs.html">Element References</a></li>

-        <li><a href="models/model-clean.html">Cleaning Up Models</a></li>

-    </ul></li>

-    <li><a href="mg-defdesk-3.htm">Working with Process Definitions</a></li>

-    <li><a href="mg-defdesk-4.htm">Specifying Activities</a></li>

-    <li><a href="mg-defdesk-5.htm">Working with Transitions</a></li>

-    <li><a href="mg-defdesk-6.htm">Specifying Applications</a></li>

-    <li><a href="mg-defdesk-7.htm">Specifying Data</a></li>

-    <li><a href="mg-defdesk-8.htm">Specifying Data Mappings</a></li>

-    <li><a href="mg-defdesk-10.htm">Modeling the Organizational

-    Structure</a></li>

-    <li><a href="mg-defdesk-14.htm">Specifying Arbitrary Link Types</a></li>

-    <li><a href="mg-defdesk-15.htm">Using Annotations</a></li>

-    <li><a href="mg-pools-lanes.htm">Pools and Lanes Usage</a></li>

-    <li><a href="mg-copy-paste-elements.html">Copying and Pasting

-    Modeled Elements</a></li>

-    <li><a href="property-page-authorization.html">Property Page

-    Authorization</a></li>

-    <li><a href="process-effort-calculation.html">Project Effort

-    Calculation</a></li>

-    <li><a href="pattern-support.html">Modeling Pattern Support</a></li>

-    <li><a href="mg-defdesk-16.htm">Retrieving Diagrams from Model

-    Information</a></li>

-    <li><a href="mg-modelreport.htm">Process Model Report</a></li>

-	<li><a href="mg-deploy-model.html">Deploying a Workflow Model</a></li>

-    <li><a href="mg-defdesk-18.htm">Debugging Process Definitions</a></li>

-    <li><a href="mg-internationalization.html">Native Language Support</a></li>

-</ul> -->

 <script language="JavaScript" type="text/javascript">

 <!-- 

 writeFooter(); 

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 2bdb6bf..39bf353 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
@@ -17,10 +17,10 @@
  -->
 </script>
 <h1>Modeling the Organizational Structure</h1>
-<p>Interactive Activities are assigned to participants - roles or organizations.
+<p>Swim lanes are assigned to participants - roles or organizations.
 Users assigned to these roles or organizations perform the work represented by an activity
-instance. Being assigned one or more activity instances, a user can perform these
-activities by completing the work items in his worklist.</p>
+instance. Being assigned one or more swim lanes, a user can perform the
+activities associated with those swim lanes by completing the work items in his worklist.</p>
 <p>Hence, there is a distinction between</p>
 <ul>
     <li>roles and organizations, which are visible both at the time of modeling as well as
@@ -44,6 +44,7 @@ The following sections describe the usage of participants in Business Process Mo
     <li><a href="#org">Organizations</a></li>
     <li><a href="#role">Roles</a></li>
     <li><a href="#condPerformers">Conditional Performers</a></li>
+    <li><a href="#reforg">Working with Referenced Participants</a></li>
     
 </ul>
 
@@ -378,6 +379,22 @@ alt=""><br>
 alt=""><br>
 <strong>Figure:</strong> Conditional Performer - Comments</p>
 
+<h2 id="reforg">Working with Referenced Participants</h2>
+<p>You can reference the participants from the provider model in the consumer model. To reference the participant, perform the following steps: </p>
+<ol>
+	<li>Select the lane of the process of the consumer model. The properties page of the lane gets displayed.</li>
+	<li>From the <strong>Participants</strong> drop-down list, select the participant of the provider model</li>
+	<p class="image"><img src="images/ref-parti.png" 
+	alt=""><br>
+	<strong>Figure:</strong> Swim Lane - Participants - Provider Model</p>
+	<li>The participant of the provider model gets referred for lane of the consumer model.</li>
+	
+	
+	<p class="image"><img src="images/ref-lane.png" 
+	alt=""><br>
+	<strong>Figure:</strong> Participant Referenced for Swim Lane</p>
+</ol>
+
 	
 <script language="JavaScript" type="text/javascript">
 <!-- 
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 f20e3fc..5779ffd 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
@@ -30,7 +30,7 @@ A typical process definition contains swim lanes, activities and gateways, appli
 	<li><a href="#rename">Renaming a Process Definition</a></li>
 	<li><a href="#del">Deleting a Process Definition</a></li>
 	<li><a href="#prop">Modifying Properties of a Process Definition</a></li>
-	
+	<li><a href="#ref">Working with Referenced Process</a></li>
 </ul>
 <h2 id="create">Creating a Process Definition</h2>
 <p>Perform the following steps to create a new process definition.</p>
@@ -157,7 +157,7 @@ When you select the Provides Process Interface, the following options are displa
 
 	<li>Web Service - If you select this check box then the process interface is invokable remotely via web service endpoint.</li>
 	<li>Rest Service - If you select this check box then the process interface is invokable remotely via rest endpoint.</li>
-	<li>Add Parameters -Click the <strong>Add</strong> icon to specify the process interface parameters. 
+	<li>Add Parameters -Click the <strong>Add</strong><img src="images/add-element.png"> icon to specify the process interface parameters. 
 	Formal parameters can be defined only for the data from the current model.</li>
 	
 	<p class="image"><img src="images/add-pro-param.png" alt=""> <br>
@@ -174,7 +174,7 @@ When you select the Provides Process Interface, the following options are displa
 	<li>Data Type - Select data from the drop-down list. You can select following data types:
 		<ul>
 			<li>Primitive -If you select this option, you need to specify <strong>Primitive Type</strong> of the data. </li>
-			<li>Data Structure - If you select this option, you need to specify <strong>Data Structure</strong> of the data.</li>
+			<li>Structured Data - If you select this option, you need to specify <strong>Structured Type</strong> of the data.</li>
 			<li>Document - If you select this option, you need to specify <strong>Document Type</strong> of the data.</li>
 		
 		</ul>
@@ -184,9 +184,8 @@ When you select the Provides Process Interface, the following options are displa
 
 </ul>
 <h4 id="ip">Implements Process Interface</h4>
-<p>A model that wants to provide an alternate implementation of its process definition should opt for 
-Implements Process Interface option. It provides an implementation 
-for a process interface defined in a provider model file.
+<p>This option is supported only for imported models from Eclipse-based modeler to Web-based modeler. If
+ the imported model has this relationship then it is maintained in the Web-based modeler.
 </p>
 
 <h3>Data Path</h3>
@@ -202,7 +201,7 @@ Perform the following steps to modify the Data Path properties:</p>
 	<p class="image"><img src="images/data-path-icon.png" alt=""> <br>
 <strong>Figure:</strong> Process Properties - Data Path Icon</p></li>
 
-	<li>Click the <strong>Add</strong> icon to specify the data path properties.
+	<li>Click the <strong>Add</strong><img src="images/add-element.png"> icon to specify the data path properties.
 	
 	
 	<p class="image"><img src="images/data-path.png" alt=""> <br>
@@ -222,6 +221,8 @@ Perform the following steps to modify the Data Path properties:</p>
    </span><span class="hideReference">
    <strong>Modeling Handbook</strong> in the <strong>@productname@ Documentation</strong>.</span>
 	</li>
+	<li>Data - Select data from the drop-down list. It displays data elements from the current model only.</li>
+	<li>Path - Specify data path, if applicable.</li>
 </ol>
 
 <h3>Display</h3>
@@ -271,14 +272,56 @@ Perform the following steps to modify the Data Path properties:</p>
 	<li>Click the <strong>Comments</strong> icon displayed at top-right corner of the swim lane
 		<p class="image"><img src="images/proc-com-icon.png" alt=""> <br>
 <strong>Figure:</strong> Process Properties -Comments Icon</p></li>
-<li>Specfiy the comment in the text box and click <strong>Submit</strong></li>
+<li>Specify the comment in the text box and click <strong>Submit</strong></li>
 <p class="image"><img src="images/proc-comm.png" alt=""> <br>
 <strong>Figure:</strong> Process Properties -Comments</p>
 </ol>
 <p> To delete the comment, select the comment and click the <strong>Delete</strong> icon. 
 The user, who has submitted the comment, can delete that comment.</p>
 
+<h2 id="ref">Working with Referenced Process</h2>
+<p>The referenced process definition becomes the subprocess in the referencing model. 
+If the <strong>Provides Process Interface</strong> option is set for the process in the referenced model 
+then only it can be referenced in another model.
+</p>
+
+	<p>Drag and drop the process from the referenced model.</p>
+	
+	<p class="image"><img src="images/ref-pro.png" alt=""> <br>
+	<strong>Figure:</strong> Drag Referenced Process Definition</p>
+<p>
+If the selected subprocess is a referenced process from a provider model then the following execution types are available:
+<ul>
+	<li>Synchronous / Separate Data</li>
+	<li>Asynchronous / Separate Data</li>
+	<li>Synchronous / Shared Data</li>
+</ul>
+<p>By default, Synchronous / Separate Data is selected. Note that in these cases invocation at 
+runtime is always done via the process interface.
+If the selected subprocess is a process from the same model 
+then the subprocess will be invoked directly at runtime as no process interface exists.
+</p>
+<p>A model using model elements from another model cannot be referenced by the other model.
+Thus, circular references are not allowed between models. An error is displayed if you try to establish such
+a relationship between models.
+</p>
+
 
+<p class="image"><img src="images/circular.png" alt=""> <br>
+	<strong>Figure:</strong> Circular Reference Error</p>
+
+<p>For more information, please refer to the chapter
+<span class="showReference">
+<a href="PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/handbooks/concepts/multi-model/using-elements.html">Using Elements from Other Process Models
+</a> 
+   </span><span class="hideReference">
+   <strong>Using Elements from Other Process Models</strong></span>
+   of the 
+   <span class="showReference">
+<a href="PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/handbooks/concepts/multi-model/multi-model.html">Multi-model Audit Trail Setups
+</a>.
+   </span><span class="hideReference">
+   <strong>Multi-model Audit Trail Setups</strong> in the <strong>@productname@ Documentation</strong>.</span>
 
 
 <script language="JavaScript" type="text/javascript">
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-struct-type.htm b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-struct-type.htm
index 11f5375..736856a 100644
--- a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-struct-type.htm
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-struct-type.htm
@@ -184,6 +184,21 @@ node in the <strong>My Process Models</strong> panel.</p>
 	<strong>Figure:</strong> Imported Type Declaration</p>

 <p>The imported type declaration is represented using this <img src="images/imp-type-icon.png"> icon.</p>

 

+<h2 id="ref">Working with Referenced Structured Type</h2>

+<p>If the Public Visibility property is selected for the structured type in the referenced model then you 

+can refer the structured type in the another model. Note that the structured types 

+from the referenced model are read only. You cannot edit the referenced structured types. 

+To refer the structure data:

+</p>

+

+	<p>Drag and drop the structured type to referencing process from the <strong>Structured Type</strong> node 

+	of the referenced model.</p>

+	

+	<p class="image"><img src="images/ref-struct.png" alt=""> <br>

+	<strong>Figure:</strong> Drag Referenced Structured Type</p>

+	

+

+