CRNT-25977 - Added Activities chapter

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

16 files changed, 154 insertions, 237 deletions

diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/act-fly-connect.png b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/act-fly-connect.png
new file mode 100644
index 0000000..9f15bbb
--- a/dev/null
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/act-fly-connect.png
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/act-fly-del.png b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/act-fly-del.png
new file mode 100644
index 0000000..cc65956
--- a/dev/null
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/act-fly-del.png
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/act-fly-event.png b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/act-fly-event.png
new file mode 100644
index 0000000..4e79dd7
--- a/dev/null
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/act-fly-event.png
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/act-fly-gateway.png b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/act-fly-gateway.png
new file mode 100644
index 0000000..47d1fbf
--- a/dev/null
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/act-fly-gateway.png
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/act-fly-man.png b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/act-fly-man.png
new file mode 100644
index 0000000..0f83adc
--- a/dev/null
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/act-fly-man.png
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/act-fly-menu.png b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/act-fly-menu.png
new file mode 100644
index 0000000..08cbef4
--- a/dev/null
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/act-fly-menu.png
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/act-fly-newact.png b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/act-fly-newact.png
new file mode 100644
index 0000000..bcc7d91
--- a/dev/null
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/act-fly-newact.png
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/act-fly-sub.png b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/act-fly-sub.png
new file mode 100644
index 0000000..b3fc418
--- a/dev/null
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/act-fly-sub.png
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/act-gen-app.png b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/act-gen-app.png
new file mode 100644
index 0000000..b72ac0c
--- a/dev/null
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/act-gen-app.png
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/act-gen-prop.png b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/act-gen-prop.png
new file mode 100644
index 0000000..6b693fc
--- a/dev/null
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/act-gen-prop.png
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/app-act.png b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/app-act.png
new file mode 100644
index 0000000..0797bfd
--- a/dev/null
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/app-act.png
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/manual-act.png b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/manual-act.png
new file mode 100644
index 0000000..18ceb66
--- a/dev/null
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/manual-act.png
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/subpro-act.png b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/subpro-act.png
new file mode 100644
index 0000000..1223adf
--- a/dev/null
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/subpro-act.png
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 5b9dba4..ac239c1 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
@@ -20,17 +20,33 @@
 </script>
 
 <h1>Specifying Activities</h1>
+<p>When you create a new activity in the @productname@'s Business Process Modeling perspective, 
+by default, it creates a manual activity. You can create following type of activities in Business
+ Process Modeling perspective.</p>
+ <ul>
+ 	<li>Manual Activity - This <img src="images/manual-act.png"> icon represents the manual activity. </li>
+ 	<li>Application Activity - This  <img src="images/subpro-act.png"> icon represents the application activity.</li>
+ 	<li>Subprocess Activity - This  <img src="images/app-act.png"> icon represents the subprocess activity.</li>
+ 
+ </ul>
+ <p>For more information, please refer to the chapter <a href="PLUGINS_ROOT/org.eclipse.stardust.docs.dev/
+ html/handbooks/concepts/workflow-basics/mg-basics-5.htm">Activities</a> 
+  of the <a href="PLUGINS_ROOT/org.eclipse.stardust.docs.dev/
+ html/handbooks/concepts/key-concepts.html">Concepts handbook</a>.</p>
+ 
+<p>You can perform following operations on activities:</p> 
 <ul>
 	<li><a href="#add">Adding Activities</a></li>
+	<li><a href="#renam">Renaming Activities</a></li>
 	<li><a href="#del">Deleting Activities</a></li>
-	<li><a href="#fly">Activity Flyout Menu</a></li>
+	<li><a href="#fly">Using Activity Flyout Menu</a></li>
 	<li><a href="#mod">Viewing and Modifying Activity Properties</a></li>
 	
 </ul>
 
 <h2 id="add">Adding Activities</h2>
 <p>
-To add activities, you can either:
+You can add activity using four different ways:
 </p>
 <ul>
 	<li>In the toolbar, click <strong>Create Activity</strong> icon and drop it to swim lanes</li>
@@ -49,6 +65,36 @@ To add activities, you can either:
 
 </ul>
 
+<p>OR</p>
+<ul>
+
+	<li>Drag an application from the <strong>Applications</strong> node in the <strong>My Process Models</strong> panel 
+	and drop it in the swim lane.
+	The application activity gets created.</li>
+</ul>
+
+<p>OR</p>
+<ul>
+	<li>Drag a process definition from the model node in the <strong>My Process Models</strong> panel 
+	and drop it in the swim lane. 
+	The subprocess activity gets created.</li>
+</ul>
+
+
+
+
+
+<p>By default, manual activity gets created.</p>
+<h2 id="renam">Renaming Activities</h2>
+
+<p>To rename activities, perform the following steps:</p>
+
+<ol>
+	<li>Double-click activity name in the swim lanes</li>
+	<li>Specify the new name</li>
+
+</ol>
+
 <h2 id="del">Deleting Activities</h2>
 <p>To delete activities, perform the following steps:</p>
 
@@ -60,249 +106,119 @@ To add activities, you can either:
 	<p class="image"><img src="images/del-act.png" alt=""> <br>
 <strong>Figure:</strong> Delete Activity - Flyout Menu</p>
 
-
 </ol>
 
-
-
-
-<!-- 
-<p>As explained in the chapter <a href="mg-basics-5.htm">Activities</a> a series of
-activities connected with one another by transitions constitutes the core of the process.
+<h2 id="fly">Using Activity Flyout Menu</h2>
+<p>The activity flyout menu is displayed when you hover the mouse in the proximity of the activity.
 </p>
-<p>An activity is represented in the <strong>Process Workbench</strong> in two
-different ways. In the <strong>Outline</strong> view it is represented by a small gear
-pictogram. In diagrams you will see an activity depicted as a box possibly with transition
-symbols.</p>
-<p>&nbsp;</p>
-<p class="image"><img src="images/mg-defdesk-17.png" alt=""> <br>
-<strong>Figure:</strong> A Representation of an Activity</p>
-<h2>Creating and Deleting Activities</h2>
-<p>To create an activity you can either:</p>
-<ul>
-    <li>In the diagram toolbar palette select <strong>Activites</strong> under <strong>Items</strong>
-    and click on the canvas to place the activity symbol there. The created activity will
-    also appear in the tree view under the process definition symbol in the <strong>Outline</strong>
-    view.</li>
-</ul>
-<p class="image"><img src="images/mg-create-activity.png" alt=""> <br>
-<strong>Figure:</strong> Creation of an Activity</p>
-<ul>
-    <li>In the <strong>Outline</strong> view select the process definition to which
-    you want to add an activity. From its pop-up menu choose <strong>New Activity</strong>.
-    The created activity will appear in the tree view under the process definition symbol.
-    Subsequently, you can drag the activity symbol to the diagram canvas to create an
-    activity symbol there.</li>
-</ul>
-<p>When deleting activities you must make a distinction between deleting an activity
-from the model information or only deleting a symbol from a diagram. To do the first -
-delete an activity from model - you proceed as follows:</p>
-<ul>
-    <li>Having selected the symbol of the activity in the <strong>Outline</strong>
-    view, choose the option <strong>Delete </strong> in the pop-up menu of this process
-    definition.</li>
-    <li>Having selected the symbol of the activity in a process definition diagram,
-    choose the option <strong>Delete</strong> in the pop-up menu of this activity.</li>
-</ul>
-<p>The option <strong>Delete Symbol </strong> in the pop-up menu called from within
-the diagram canvas will only remove the activity symbol from the diagram.</p>
-<h2>Modifying Activity Properties</h2>
-<p>The properties of an activity are accessible in its properties dialog. To open
-this dialog, right-click the activity symbol - in the <strong>Outline</strong> view or
-diagram - and select the option <strong>Properties</strong>. Double-clicking on the
-activity symbol will open this dialog as well.</p>
-<p>Activity characteristics are bundled into the following categories, each
-represented in an own tabbed pane:</p>
-<ul>
-    <li><a href="#general">General</a></li>
-    <li><a href="#display">Display</a></li>
-    <li><a href="#controlFlow">Control Flow</a></li>
-    <li><a href="#in">In Data Mappings</a></li>
-    <li><a href="#out">Out Data Mappings</a></li>
-    <li><a href="#controlling">Controlling</a></li>
-    <li><a href="#simulation">Simulation</a></li>
-    <li><a href="#effort">Effort Planning</a></li>
-</ul>
 
-<h3 id="general">General</h3>
-<p>Next to a name, an ID and a description, general properties of an activity
-comprise the following checkbox options:</p>
-<ul>
-    <li><strong>Auto Id Generation</strong><br><br>
-    Overwrites the option for automatic Id generation set in <a
-        href="mg-preferences.html">@productname@ Preferences</a>.<br><br></li>
-    <li><strong>Allows Abort by Participant</strong><br><br>
-    Determines whether the assigned participant may abort instances of this 
-	activity in the @productname@ Portal.<br>
-	Note that only the activity itself is aborted, not the root process hierarchy. 
-	The process instances will continue as if this activity had been completed.<br>
-	This option affects the Process Portal activity operations only. It does not 
-	influence the @productname@ API usage.<br><br></li>
-    <li><strong>Hibernate Initially</strong> (Hibernate On Creation)<br><br>
-    Determines whether the activity instance should directly change its state to
-    hibernated after creation - thus ending the synchronous flow here.<br><br></li>
-    <li><strong>Supports relocation</strong><br><br>
-    Determines if relocation is supported for this activity and it can
-    be used as starting point for the relocation. This checkbox is enabled for 
-    manual activities and application activities only. For
-    details on relocation, refer to chapter 
-    <a href="PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/handbooks/concepts/executing-workflow/concept-relocation.html">Relocation of Activities</a>
-    in the <a href="PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/handbooks/concepts/key-concepts.html">Concepts</a> 
-    section of the 
-    <a href="PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/handbooks/handbooks.htm">
-    Developer Handbooks</a>.<br><br></li>
-    <li><strong>Is relocation target</strong><br><br>Determines if the activity
-    is allowed as target point of a relocation. For
-    details on relocation, refer to chapter 
-    <a href="PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/handbooks/concepts/executing-workflow/concept-relocation.html">Relocation of Activities</a>
-    in the <a href="PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/handbooks/concepts/key-concepts.html">Concepts</a> 
-    section of the 
-    <a href="PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/handbooks/handbooks.htm">
-    Developer Handbooks</a>.</li>
-</ul>
-<p class="image"><img src="images/mg-defdesk-18.png" alt="General Activity Properties">
-<br>
-<strong>Figure:</strong> General Activity Properties</p>
-<p>Please note that IDs containing
-         hyphens, blanks or dots and IDs starting with digits are not supported.</p>
-<h3 id="display">Display</h3>
-<p>For this property a checkbox is provided to mark activities as auxiliary
-from a business perspective. This option is disabled by default, except for the route activities.
-Auxiliary activities marked as <strong>Is Auxiliary Activity</strong>
-will be treated equivalent to route activities in the process history.</p>
-<p class="image"><img src="images/activity-props-display.png"
-    alt="Display Option"> <br>
-<strong>Figure:</strong> Is Auxiliary Activity Option</p>
-<p>For route activities, this option 
-is set to <strong>Is Auxiliary Activity</strong> per default.</p>
-<h3 id="controlFlow">Control Flow</h3>
-<p>Control flow options define the split, join and loop behavior around the
-activity.</p>
-<p class="image"><img src="images/mg-defdesk-19.png" alt="Control Flow Options">
-<br>
-<strong>Figure:</strong> Control Flow Options</p>
-<p><strong>Join</strong> behavior specifies the runtime behavior in case of multiple transitions from
-the predecessor activity leading to the chosen activity. The following options are
-offered:</p>
-<ul>
-    <li>All incoming transitions are required to be processed for the execution of
-    the activity (join with the <strong>AND</strong> option).</li>
-    <li>If one incoming transition is processed the chosen activity is instantiated
-    (join with the<strong> XOR</strong> option). If multiple incoming transitions are
-    processed at runtime the chosen activity is instantiated multiple times.</li>
-</ul>
-<p><strong>Split</strong> behavior specifies how multiple transitions to the following activities are
-to be executed:</p>
-<ul>
-    <li>all (split with the <strong>AND</strong> option)</li>
-    <li>or one of them (split with <strong>XOR</strong> option).</li>
-</ul>
-<p>See also <a href="mg-basics-6.htm">Control Flow</a> for basic informations.</p>
+	<p class="image"><img src="images/act-fly-menu.png" alt=""> <br>
+<strong>Figure:</strong> Activity - Flyout Menu</p>
+<p>Following menu options are available in the activity flyout menu.</p>
+
+<table>
+	<tr>
+		<th>Menu Icon</th>
+		<th>Menu Option</th>
+		<th>Description</th>	
+	</tr>
+	<tr>
+		<td><img src="images/act-fly-del.png" alt=""></td>
+		<td>Delete</td>
+		<td>Deletes the activity.</td>
+	</tr>
+	<tr>
+		<td><img src="images/act-fly-man.png" alt=""></td>
+		<td>Subprocess</td>
+		<td>Changes the activity type to subprocess. Click the Subprocess icon to change the activity type to Subprocess.</td>
+	</tr>
+	<tr>
+		<td><img src="images/act-fly-sub.png" alt="">
+		</td>
+		<td>Application</td>
+		<td>Changes the activity type to application. Click the Application icon to change the activity type to Application.</td>
+	</tr>
+	<tr>
+		<td><img src="images/act-fly-connect.png" alt="">
+		</td>
+		<td>Sequence Flow</td>
+		<td>Starts a connection from the activity. Click the Sequence Flow icon and connect it to another activity.</td>
+	</tr>
+	<tr>
+		<td>
+		<img src="images/act-fly-newact.png" alt=""></td>
+		<td>New Activity</td>
+		<td>Adds a new manual activity connected from the existing activity. Click the new activity icon and drop it on the swim lane.</td>
+	</tr>
+	<tr>
+		<td>
+		<img src="images/act-fly-gateway.png" alt="">
+		</td>
+		<td>New Gateway</td>
+		<td>Adds a new gateway connection to the activity. Click the new gateway connection and drop it between the activities.</td>
+	</tr>
+	<tr>
+		<td><img src="images/act-fly-event.png" alt="">
+		</td>
+		<td>New End Event</td>
+		<td>Adds a new end event to the activity. Click the new end event icon and drop it on the swim lane.</td>
+	</tr>
+	
+</table>
 
-<p><strong>Loop </strong>behavior specifies how an activity is repeated 
-until the loop condition is fulfilled. During the runtime execution of loop activity   
-the specific part of the workflow is repeated.  
-<p> When an activity enters the loop, one or more instances of the activity are created and performed.
-On termination of the activity instance, the loop condition is evaluated and based on the result 
- a new activity instance is created. This is repeated until the loop gets terminated and then
-the subsequent activity is performed, if any.</p>
-<p> None indicates that the activity is performed exactly once regardless of the evaluation of the condition.
-The following loop conditions can be applied when the activity needs to be performed more than once. </p>
+<h2 id="mod">Viewing and Modifying Properties of an Activity</h2>
+<h3>General Properties</h3>
 
-<ul>
-	<li> While - indicates that the condition is evaluated before the creation of an activity
-	instance. If the condition evaluation result is TRUE, an activity instance is created and performed.
-	If FALSE, the workflow continues and the next activity is performed. Using "while" loop it 
-	is possible that no activity instance is created.</li>
-	<li> Repeat - indicates that the condition is evaluated at the completion of the activity instance.
-	If the condition evaluation result is TRUE, the loop ends and the next activity is performed.
-	If FALSE, a new instance of the activity is created and repeated.</li>
+<p>To view and modify the properties of an activity, perform the following steps:</p>
 
+<ol>
+	<li>Select the activity in the swim lane. 
+	The properties window is displayed at the top right corner of the swim lane. </li>
+<p class="image"><img src="images/act-gen-prop.png" alt=""> <br>
+<strong>Figure:</strong> Activity - General Properties</p>
+
+	<li>Specify the properties:
+	<ul>
+		<li>UUID - A unique identifier ID gets generated as an identifier for client server communication</li>
+		<li>ID - Default ID of the activity</li>
+		<li>Name - Specify name of the activity</li>
+		<li>Description - Specify the description</li>
+		<li>Allow Abort by Participant - Determines whether the assigned participant may abort instances of 
+		this activity in the Infinity Process Platform Portal.
+		Note that only the activity itself is aborted, not the root process hierarchy. 
+		The process instances will continue as if this activity had been completed.
+		This option affects the Process Portal activity operations only. 
+		It does not influence the Infinity Process Platform API usage.
+		<li>Hibernate Initially (Hibernate On Creation) -
+		Determines whether the activity instance should directly change its state to 
+		hibernated after creation - thus ending the synchronous flow here.</li>
+		<li>Supports relocation -Determines if relocation is supported for this 
+		activity and it can be used as starting point for the relocation. 
+		This check box is enabled for manual activities and application activities only.</li>
+		<li>Is relocation target -Determines if the activity is allowed as 
+		target point of a relocation. For details on relocation, 
+		refer to chapter <a href=""> Relocation of Activities</a> in the Concepts section of the Developer Handbooks.
+		</li>
+		<li>Application - By default, this option is selected. When you select this option, the activity icon 
+		changes to application icon.
+		The adjacent drop-down list displays list of applications
+		defined in all the models displayed under the <strong>Models</strong> node.</li>
+		<p class="image"><img src="images/act-gen-app.png" alt=""> <br>
+<strong>Figure:</strong> Activity - General Properties - Application</p>
+		<li>Suprocess - If you select the option, the activity acts as a subprocess and 
+		the activity icon 
+		changes to subprocess icon with a plus sign in the center-bottom of the activity. 
+		The adjacent drop-down list displays all the processes defined in all the models
+		displayed under the <strong>Models</strong> node.
+		<ul>
+			<li>Share Data with Current Process - TO DO. Clarification from Marc and Kyle. Told Caroline to
+			ask them.</li>
+		</ul>
 </ul>
-<p> The syntax language for the loop condition parameter is carnotEL. Currently, the single line format 
-is supported. The following figure explains the While loop condition.</p>
-<p>&nbsp</p>
-<p class ="image"><img src = "images/while-loop.png" alt="">
-<br>
-<strong>Figure:</strong>While Loop Condition</p>
-
-<p> More elaborate cycles in the model should be modeled
-explicitly by cycles in the activity/transition graph. See figure below.</p>
-<p class="image"><a href="images/mg-defdesk-trans-cycle_orgSize.png" target="_blank">
-<img src="images/mg-defdesk-trans-cycle.png" alt=""></a> <br>
-<strong>Figure:</strong> Transition in a Cycle</p>
-<p>In this example transition conditions influence the process flow. Please refer to
-<a href="mg-defdesk-5.htm#transitionConditions">Specifying Transition Conditions</a>.</p>
 
-<h3 id="in">In Data Mappings</h3>
-<p>The activity properties dialog allows you to add and remove data mappings
-belonging to this activity. The In data mapping maps workflow data to the input of the
-activity. Refer to <a href="mg-defdesk-7.htm">Specifying Data</a> for more information on
-mapping data to applications via an activity.</p>
-
-<h3 id="out">Out Data Mappings</h3>
-<p>The activity properties dialog allows you to add and remove data mappings
-belonging to this activity. The Out data mapping maps workflow data to the output of the
-activity. Refer to <a href="mg-defdesk-7.htm">Specifying Data</a> for more information on
-mapping data to applications via an activity.</p>
+</ol>
 
-<h3 id="controlling">Controlling Properties</h3>
-<p>The @productname@ Analyst Edition provides activities with the following controlling
-properties:</p>
-<ul>
-    <li>Measure</li>
-    <li>Target Measure Quantity</li>
-    <li>Difficulty</li>
-    <li>Target Processing Time</li>
-    <li>Target Execution Time</li>
-    <li>Target Idle Time</li>
-    <li>Target Waiting Time</li>
-    <li>Target Queue Depth</li>
-    <li>Target Cost Per Execution</li>
-    <li>Target Cost Per Second</li>
-    <li>Resource Performance Calculation</li>
-</ul>
-<br />
-<p class="image"><img src="images/mg-act-controlling.png" alt=""> <br>
-<strong>Figure:</strong> Controlling Properties</p>
-<h4 id="resource">Resource Performance Calculation</h4>
-<p>This property has the default
-value <tt>include</tt> for interactive activities and <tt>not include</tt> for 
-non-interactive activities. It is used in the Business Control Center view 
-<a href="PLUGINS_ROOT/org.eclipse.stardust.docs.enduser/html/handbooks/execution-clients/bcc_renovated/views/bcc-views-resource.html">
-Resource Performance</a> view,
-where all activities having this controlling property set to <tt>include</tt> are
-included into the calculation.</p>
-<h3 id="simulation">Simulation</h3>
-<p>In this section you can specify simulation configurations, as described detailed in
-the chapter <a
-    href="PLUGINS_ROOT/org.eclipse.stardust.docs.simulation/html/simulation/simulation-configurations.html">
-Simulation Configurations</a> of the <a
-    href="PLUGINS_ROOT/org.eclipse.stardust.docs.simulation/html/simulation/toc.html"> 
-Developer Simulation Guide</a>.)</p>
-<h3 id="effort">Effort Planning</h3>
-<p>In this section you can specify the subprocess refinement required.</p>
-<p class="image"><img src="images/activitiy-prop-effort.png"
-    alt="Effort Planning Prop"> <br>
-<strong>Figure:</strong> Setting the Subprocess Refinement Required.</p>
-<p>Pease refer to the chapter <a href="process-effort-calculation.html">Project
-Effort Calculation</a> for detailed information on Project Effort calculations.</p>
 
-<h2 id="subprocess">Subprocess Activities</h2>
-<p>To define an activity as a subprocess:</p>
-<ul>
-    <li>Right-click the symbol in the diagram canvas and choose <strong>Subprocess</strong>.</li>
-    <li>Select the process you want to define as subprocess.</li>
-</ul>
-<p class="image"><img src="images/mg-select-subprocess.png"
-    alt="Setting the Implementation to Subprocess"> <br>
-<strong>Figure:</strong> Setting the Implementation to Subprocess</p>
-<p>For details on configuring subprocess activities, refer to chapter
-<a href="PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/handbooks/modelling/mg-subprocesses.html">
-Configuring Subprocess Activities</a>
-of the 
-<a href="PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/handbooks/handbooks.htm">
-Developer Handbooks</a>.</p> -->
 <script language="JavaScript" type="text/javascript">
 <!-- 
 writeFooter(); 
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 db5af56..4aaea8d 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
@@ -155,7 +155,8 @@ Also, when you hover the mouser over the symbol its outline changes to red color
     alt="Mouse Hover - Flyout Menu" /> <br>
 <strong>Figure:</strong> Mouse Hover - Flyout Menu</p>
 <h4>Double-clicking Symbol</h4>
-<p>To rename the activity or subprocess activity and application, double-click on its symbol name in the swim lane.
+<p>To rename the activity or subprocess activity and application, double-click on its 
+symbol name in the swim lane and specify new name.
 </p>
   <p class="image"><img src="images/doubl-clik.png"
     alt="Double-click on Activity Symbol" /> <br>
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 eaa2504..ac76e70 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
@@ -75,7 +75,7 @@ A typical process definition contains swim lanes, activities and gateways, appli
 <h2 id="prop">Modifying Properties of a Process Definition</h2>
 <h3>General Properties</h3>
 
-<p>To view the properties of a process definition, perform the following steps:</p>
+<p>To view and modify the properties of a process definition, perform the following steps:</p>
 
 <ol>
 	<li>Select the process definition under the model node. The properties window is displayed at the top right corner 
@@ -166,7 +166,7 @@ A typical process definition contains swim lanes, activities and gateways, appli
 
 </ol>
 <p>For more information, please refer to the chapter 
-<a href="PLUGINS_ROOT/org-eclipse.stardust.docs.dev/html/handbooks/modelling/mg-defdesk-3.htm">Working with Process Definition</a>
+<a href="PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/handbooks/modelling/mg-defdesk-3.htm">Working with Process Definition</a>