summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorVrishali Doke2012-09-13 05:48:12 (EDT)
committerStephan Born2012-09-13 05:48:12 (EDT)
commitbedacd473502e02f341345ee3314fa94acba9034 (patch)
tree62a8de2294bb1eb2c95f781367d96993cef9895b
parente38c44cec1f721c597e6fc5da5ec1255fb55c90d (diff)
downloadorg.eclipse.stardust.documentation-bedacd473502e02f341345ee3314fa94acba9034.zip
org.eclipse.stardust.documentation-bedacd473502e02f341345ee3314fa94acba9034.tar.gz
org.eclipse.stardust.documentation-bedacd473502e02f341345ee3314fa94acba9034.tar.bz2
CRNT-24955 - Added chapter for participants
git-svn-id: http://emeafrazerg/svn/ipp/product/trunk/stardust/documentation@59168 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/conditional-icon.pngbin0 -> 672 bytes
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/cre-cond-perf.pngbin0 -> 14973 bytes
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/create-org-org.pngbin0 -> 17655 bytes
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/create-org.pngbin0 -> 13991 bytes
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/create-role.pngbin0 -> 15851 bytes
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/del-cond-perf.pngbin0 -> 17272 bytes
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/del-confirm.pngbin0 -> 6466 bytes
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/del-role.pngbin0 -> 17004 bytes
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/leader.pngbin0 -> 8578 bytes
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/org-abc.pngbin0 -> 15540 bytes
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/org-del.pngbin0 -> 17233 bytes
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/org-icon.pngbin0 -> 782 bytes
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/org-rename.pngbin0 -> 17267 bytes
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/org-role.pngbin0 -> 16834 bytes
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/parti-icon.pngbin0 -> 813 bytes
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/rename-cond-perf.pngbin0 -> 16567 bytes
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/rename-role.pngbin0 -> 17271 bytes
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/role-icon.pngbin0 -> 830 bytes
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/role-prop.pngbin0 -> 11982 bytes
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/set-mgr.pngbin0 -> 18677 bytes
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-org-struct.htm696
22 files changed, 224 insertions, 474 deletions
diff --git a/org.eclipse.stardust.docs.analyst/analysttoc.xml b/org.eclipse.stardust.docs.analyst/analysttoc.xml
index ae3734c..9345bc9 100644
--- a/org.eclipse.stardust.docs.analyst/analysttoc.xml
+++ b/org.eclipse.stardust.docs.analyst/analysttoc.xml
@@ -15,7 +15,7 @@
</topic>
<topic href="html/handbooks/modelling_analyst/pep-perspective-overview.html" label="The Business Process Modeling Perspective">
- <topic href="html/handbooks/modelling_analyst/model-views/pep-panles.html" label="Panels">
+ <topic href="html/handbooks/modelling_analyst/model-views/pep-panels.html" label="Panels">
</topic>
<topic href="html/handbooks/modelling_analyst/model-views/pep-diagrams.html" label="The Process Diagram Canvas">
</topic>
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/conditional-icon.png b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/conditional-icon.png
new file mode 100644
index 0000000..db02685
--- /dev/null
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/conditional-icon.png
Binary files differ
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/cre-cond-perf.png b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/cre-cond-perf.png
new file mode 100644
index 0000000..bfa4129
--- /dev/null
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/cre-cond-perf.png
Binary files differ
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/create-org-org.png b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/create-org-org.png
new file mode 100644
index 0000000..85a874b
--- /dev/null
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/create-org-org.png
Binary files differ
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/create-org.png b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/create-org.png
new file mode 100644
index 0000000..a2780a8
--- /dev/null
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/create-org.png
Binary files differ
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/create-role.png b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/create-role.png
new file mode 100644
index 0000000..962a4f4
--- /dev/null
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/create-role.png
Binary files differ
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/del-cond-perf.png b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/del-cond-perf.png
new file mode 100644
index 0000000..aa9a855
--- /dev/null
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/del-cond-perf.png
Binary files differ
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/del-confirm.png b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/del-confirm.png
new file mode 100644
index 0000000..47187cb
--- /dev/null
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/del-confirm.png
Binary files differ
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/del-role.png b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/del-role.png
new file mode 100644
index 0000000..f86bc9e
--- /dev/null
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/del-role.png
Binary files differ
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/leader.png b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/leader.png
new file mode 100644
index 0000000..0457a37
--- /dev/null
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/leader.png
Binary files differ
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/org-abc.png b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/org-abc.png
new file mode 100644
index 0000000..7c924e9
--- /dev/null
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/org-abc.png
Binary files differ
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/org-del.png b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/org-del.png
new file mode 100644
index 0000000..ad73824
--- /dev/null
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/org-del.png
Binary files differ
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/org-icon.png b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/org-icon.png
new file mode 100644
index 0000000..02d6630
--- /dev/null
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/org-icon.png
Binary files differ
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/org-rename.png b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/org-rename.png
new file mode 100644
index 0000000..ddec313
--- /dev/null
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/org-rename.png
Binary files differ
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/org-role.png b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/org-role.png
new file mode 100644
index 0000000..0bf7674
--- /dev/null
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/org-role.png
Binary files differ
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/parti-icon.png b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/parti-icon.png
new file mode 100644
index 0000000..ead2bea
--- /dev/null
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/parti-icon.png
Binary files differ
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/rename-cond-perf.png b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/rename-cond-perf.png
new file mode 100644
index 0000000..a53ffc4
--- /dev/null
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/rename-cond-perf.png
Binary files differ
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/rename-role.png b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/rename-role.png
new file mode 100644
index 0000000..31fa849
--- /dev/null
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/rename-role.png
Binary files differ
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/role-icon.png b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/role-icon.png
new file mode 100644
index 0000000..6891446
--- /dev/null
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/role-icon.png
Binary files differ
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/role-prop.png b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/role-prop.png
new file mode 100644
index 0000000..e6a7c26
--- /dev/null
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/role-prop.png
Binary files differ
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/set-mgr.png b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/set-mgr.png
new file mode 100644
index 0000000..78a05a5
--- /dev/null
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/set-mgr.png
Binary files differ
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 5aa58ec..f12f6e1 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
@@ -25,7 +25,7 @@ instance. Being assigned one or more activity instances, a user can perform thes
activities by completing the work items in his worklist.</p>
<p>Hence, there is a distinction between</p>
<ul>
- <li>roles and organizations, which are visible both in the modeling as well as
+ <li>roles and organizations, which are visible both at the time of modeling as well as
in the runtime environment,</li>
<li>users who are visible only in the runtime environment and</li>
<li>modelers who are visible only in the modeling environment.</li>
@@ -35,496 +35,246 @@ Individual human performers are created and assigned to these roles only in the
<a href="PLUGINS_ROOT/org.eclipse.stardust.docs.enduser/html/handbooks/execution-clients/carnot-clients.html">
@productname@ Portal</a>, the
<a href="PLUGINS_ROOT/org.eclipse.stardust.docs.enduser/html/handbooks/swing-portal/swing-portal.html">
-@productname@ Swing Portal</a>, console administration tools or via embedding application.</p>
-<p>The following sections describe the usage of participants in
-the Process workbench:</p>
+@productname@ Swing Portal</a>, console administration tools or via embedding application.
+The following sections describes the usage of participants in Business Process Modeling:</p>
<ul>
- <li><a href="#rep">Representation in the Process Workbench</a></li>
+ <li><a href="#rep">Representation in the Business Process Modeling Perspective</a></li>
<li><a href="#org">Organizations</a></li>
<li><a href="#role">Roles</a></li>
<li><a href="#condPerformers">Conditional Performers</a></li>
<li><a href="#associate">Establishing Associations between Organizational Elements</a></li>
</ul>
-<h3>Participant IDs</h3>
-<p>Please note that IDs containing hyphens, blanks or dots and IDs starting with
-digits are not supported.</p>
-<p>IDs for participants have to be unique within all model participants like roles, organizations
-or conditional performer. When trying to add a duplicate ID, this is indicated in
-the participant properties page:</p>
-<p class="image"><img src="images/error-duplicate-id-prop.png" alt=""> <br>
-<strong>Figure:</strong> Duplicate ID indicated in Properties Page.</p>
-<p>The <strong>Problems View</strong> also shows the following error entry:</p>
-<p class="image"><img src="images/error-duplicate-id-org.png" alt=""> <br>
-<strong>Figure:</strong> Duplicate ID indicated in Problems View.</p>
-
-<h2 id="rep">Representation in the Process Workbench</h2>
-<p>In the <strong>Process Workbench</strong>, a participant may be represented,
-depending on the type of resource, by one of the symbols:</p>
+
+<h2>Representation in the Business Process Modeling Perspective</h2>
<ul>
- <li><img class="noborder" src="images/role-icon.png" alt=""> - Role</li>
- <li><img class="noborder" src="images/cond-perf-icon.png" alt=""> - Conditional Performer</li>
- <li><img class="noborder" src="images/organization-icon.png" alt=""> - Organization</li>
+ <li>Participants Node - <img src ="images/parti-icon.png"></li>
+ <li>Organization - <img src="images/org-icon.png"></li>
+ <li>Role - <img src="images/role-icon.png"></li>
+ <li>Conditional Performer - <img src="images/conditional-icon.png"></li>
+
</ul>
-<p>Participants are represented in the Outline view as in the following
-figure:</p>
-<p class="image"><img src="images/participants-outline.png" alt=""> <br>
-<strong>Figure:</strong> Representations of Participants in the Outline View</p>
-<p>In diagram, participants are represented as displayed in the following
-figure:</p>
-<p class="image"><img src="images/participants-diagram.png" alt=""> <br>
-<strong>Figure:</strong> Participants represented in a Diagram.</p>
-
-<h2 id="org">Organizations</h2>
+<h2>Organization</h2>
<p>An organization element represents a group of resources. For example, a department or any organizational unit.
-This section describes which properties are provided and how to work with organization elements in the modeler.</p>
-<h3>Creating and Deleting Organizations</h3>
-<p>To create an organization you can either:</p>
-<ul>
- <li>Select <strong>Participants</strong> in the diagram <a
- href="model-views/views-diagrams.html#toolbarPalette">toolbar palette</a> and from the
- pop-up menu <strong>Organization</strong>. Then move the cursor to the diagram canvas
- to place the organization symbol there. The organization is created by subsequently
- clicking on the canvas.</li>
- <li>In the <strong>Participants</strong> section of the <a
- href="model-views/views-outline.html">Outline view</a> area, select <strong>New
- &gt; New Organization</strong> from the pop-up menu. The created organization will appear in
- the tree view.</li>
- <li>Or in the <strong>Outline</strong> view, select the model and from its pop-up
- menu <strong>New Participant &gt; New Organization</strong>.</li>
-</ul>
-<p>When deleting organizations, you must make a distinction between deleting an
-organization from the model information or only deleting a symbol from a diagram. To do
-the first - delete an organization from the model - you proceed as follows:</p>
-<ul>
- <li>Having selected the symbol of the organization in the <strong>Participants</strong>
- tree of the <strong>Outline</strong> view, choose the option <strong>Delete</strong>
- in the pop-up menu of this organization.</li>
- <li>Having selected the symbol of the organization in a diagram, choose the
- option <strong>Delete </strong> in the pop-up menu of this organization.</li>
-</ul>
-<p>The option <strong>Delete Symbol</strong> in the pop-up menu called from within
-the diagram canvas will only remove the organization symbol from the diagram.</p>
-<h3>General Properties</h3>
-<p>The <strong>General</strong> properties entry contains:</p>
-<ul>
- <li>ID - please note that the ID has to be unique within all model participants. IDs containing
- hyphens, blanks or dots and IDs starting with digits are not supported.</li>
- <li>Name</li>
- <li>Internationalization</li>
-</ul>
-<h3 id="binding">Department Binding</h3>
-<p>It is possible for organizations to add a department scope which is
-evaluated at runtime. This department scope is described as a data path
- to process data which returns a scope key to identify a department representing
- this scope.</p>
-<p>In the <strong>Department Binding</strong> section you can determine
-that the organization is allowed to support departments by enabling the checkbox
-<strong>Organization supports departments.</strong>.</p>
-<p class="image"><img src="images/mg-org-prop-binding.png" alt="Runtime Binding">
-<br>
-<strong>Figure:</strong> Department Binding</p>
-<p>Once the checkbox is enabled, a new field opens, where you can enter
-data for the department OID. It is possible to select one of the following
-two data types:</p>
-<ul>
- <li>a primitive data of type <tt>String</tt> without access path.
- <p class="image"><img src="images/mg-org-prop-depart-2.png" alt=""></p></li>
- <li>a structured data and an access path evaluating to String.
- <p class="note"><strong>Note</strong><br>
- the data path should be an element (type String) of the structured data and not be using
- methods as dereferentiation path.</p>
- <p class="image"><img src="images/mg-org-prop-depart-1.png" alt=""></p></li>
-</ul>
-<h3 id="contrOrg">Controlling Parameters for Organizations</h3>
-<p>The following controlling parameter is provided for organizations:</p>
-<ul>
- <li><strong>Cost Center</strong></li>
-</ul>
-<p class="image"><img src="images/org-controlling.png"
-alt="Organization Controlling Parameter"><br>
-<strong>Figure:</strong> Organization Controlling Parameter</p>
-<h3 id="task">Task Assignment</h3>
-<p>In the properties dialog of the organization you can choose how the task assignment
-is performed:</p>
-<ul>
- <li>Select <strong>Task Assignment</strong> in the properties dialog.</li>
- <li>Choose the mode for task assigment. You have the choice of <tt>Choose
- Assignment</tt> or <tt>Assign Automatically</tt>.</li>
-</ul>
-<p class="image"><img src="images/mg-task-assignment-org.png" alt="Task Assignment">
-<br>
-<strong>Figure:</strong> Task Assignment of an Organization</p>
-<h3>Simulation</h3>
-<p>In this section you can specify simulation configurations, as described detailed in the chapter
- <a href="PLUGINS_ROOT/org.eclipse.stardust.docs.simulation/html/simulation/simulation-configurations.html">
- Simulation Configurations</a>
-of the
- <a href="PLUGINS_ROOT/org.eclipse.stardust.docs.simulation/html/simulation/toc.html">
- @productname@ Developer Simulation Guide</a>.)</p>
-<h3>Effort Planning</h3>
-<p>In this section you can set the organization complexity for project effort calculation:</p>
-<p class="image"><img src="images/organization-prop-effort.png" alt=""> <br>
-<strong>Figure:</strong> Effort Planning Property of an Organization</p>
-<p>Please refer to the chapter <a href="process-effort-calculation.html">Project Effort Calculation</a> for
-detailed information on this functionality.</p>
-<h2 id="role">Roles</h2>
-
-<p>A role denotes the responsibility assigned to the participants. Following
-sections provide information on how to work with roles.</p>
-
-
-<h3>Creating and Deleting Roles</h3>
-<p>To create a role you can either:</p>
-<ul>
- <li>Select <strong>Participants</strong> in the diagram <a
- href="model-views/views-diagrams.html#toolbarPalette">toolbar palette</a> and from the
- pop-up menu <strong>Role</strong>. Then move the cursor to the diagram canvas to place
- the role symbol there. The role is created by subsequently clicking on the canvas.</li>
- <li>In the <strong>Participants</strong> section of the <a
- href="model-views/views-outline.html">Outline view</a> area, select <strong>New
- &gt; New Role</strong> from the pop-up menu. The created role will appear in the tree view.</li>
- <li>Or in the <strong>Outline</strong> view, select the model and from its pop-up
- menu <strong>New Participant &gt; New Role</strong>.</li>
-</ul>
-<p>When deleting roles you must make a distinction between deleting a role from the
-model information or only deleting a symbol from a diagram. To do the first - delete a
-role from the model - you proceed as follows:</p>
-<ul>
- <li>Having selected the symbol of the role in the <strong>Participants</strong>
- tree of the Outline view, choose the option <strong>Delete </strong> in the pop-up
- menu of this role.</li>
- <li>Having selected the symbol of the role in a diagram, choose the option <strong>Delete
- </strong> in the pop-up menu of this role.</li>
-</ul>
-<p>The option <strong>Delete Symbol </strong> in the pop-up menu called from within
-the diagram canvas will only remove the role symbol from the diagram.</p>
-<h3>General Properties</h3>
-<p>The <strong>General</strong> properties entry contains:</p>
-<ul>
- <li>ID - please note that the ID has to be unique within all model participants. IDs containing
- hyphens, blanks or dots and IDs starting with digits are not supported.</li>
- <li>Name</li>
- <li>Internationalization</li>
- <li>Cardinality</li>
-</ul>
-<h4 id="cardinality">Cardinality</h4>
-<p>You can define the cardinality of roles in the properties dialog. Type in the
-maximum users that can be assigned to this role in the <strong>Cardinality</strong> entry
-field.</p>
-<p class="image"><img src="images/mg-role-cardinality.png" alt="Cardinality"> <br>
-<strong>Figure:</strong> Setting the Cardinality<br /></p>
-<h3 id="contrRole">Controlling Parameters for Roles</h3>
-<p>The following controlling parameters are provided for roles:</p>
-<ul>
- <li><strong>Working Weeks Per Year:</strong> number of working weeks per year.</li>
- <li><strong>Actual Cost Per Minute:</strong> actual cost per minute.</li>
- <li><strong>Target (System) Worktime Per Day:</strong> target system worktime
- per day in minutes.</li>
- <li><strong>Target Worktime Per Week:</strong> target worktime per week in
- hours.</li>
- <li><strong>Target Queue Depth:</strong></li>
-</ul>
-<p class="image"><img src="images/role-controlling.png"
- alt="Controlling Parameters for Roles"> <br>
-<strong>Figure:</strong> Controlling Parameters for Roles</p>
-<h3>Task Assignment</h3>
-<p>In the properties dialog of the role you can choose how the task assignment is
-performed:</p>
+This section describes which properties are provided and how to work with organization elements.</p>
<ul>
- <li>Select <strong>Task Assignment</strong> in the properties dialog.</li>
- <li>Choose the mode for task assigment. You have the choice of <tt>Choose
- Assignment</tt> or <tt>Assign Automatically</tt>.</li>
-</ul>
-<p class="image"><img src="images/mg-task-assignment.png" alt="Task Assignment">
-<br>
-<strong>Figure:</strong> Task Assignment of a Role</p>
-
-<h3>Simulation</h3>
-<p>In this section you can specify simulation configurations, as described detailed in the chapter
- <a href="PLUGINS_ROOT/org.eclipse.stardust.docs.simulation/html/simulation/simulation-configurations.html">
- Simulation Configurations</a>
-of the
- <a href="PLUGINS_ROOT/org.eclipse.stardust.docs.simulation/html/simulation/toc.html">
- Developer Simulation Guide</a>.)</p>
-<h3>Effort Planning</h3>
-<p>In this section you can set the role complexity for project effort calculation:</p>
-<p class="image"><img src="images/role-prop-effort.png" alt=""> <br>
-<strong>Figure:</strong> Effort Planning Property of a Role</p>
-<p>Please refer to the chapter <a href="process-effort-calculation.html">Project Effort Calculation</a> for
-detailed information on this functionality.</p>
-<h2 id="condPerformers">Conditional Performers</h2>
-<p>The conditional performer is evaluated at runtime and it determines the identity of the actual performer.
-The following sections help you to work with conditional performers.</p>
-<h3>Creating and Deleting Conditional Performers</h3>
-<p>To create a conditional performer you can either:</p>
-<ul>
- <li>Select <strong>Participants</strong> in the diagram <a
- href="model-views/views-diagrams.html#toolbarPalette">toolbar palette</a> and from the
- pop-up menu <strong>Conditional Performer</strong>. Then move the cursor to the
- diagram canvas to place the symbol for the conditional performer there. The
- conditional performer is created by subsequently clicking on the canvas.</li>
- <li>In the Participants section of the <a
- href="model-views/views-outline.html">Outline view</a> area, select <strong>New
- &gt; New Conditional Performer </strong>from the pop-up menu. The created conditional performer
- will appear in the tree view.</li>
- <li>Or in the Outline view, select the model and from its pop-up menu <strong>New
- Participant &gt; New Conditional Performer.</strong></li>
-</ul>
-<p>As described in the chapter <a href="mg-basics-9.htm">Participants and Users</a>,
-the <a href="PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/handbooks/others/glossary.html#oid">OID</a> or respectively
-<a href="PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/handbooks/others/glossary.html#id">ID</a>
-of the performer assigned dynamically at runtime is passed to
-the @productname@ resource.</p>
-
-<h3>Runtime Binding</h3>
-<p>Among the conditional performer's properties, there is also the distinction
-between an individual user of the runtime environment and a performer defined in the
-modeling environment (corresponding to a role or organization) used as a conditional
-performer. This distinction has to be made in the same properties dialog. Click <strong>Runtime
-Binding</strong> to define the performer as a user, organization/role or user group and choose the
-data and optional data path to provide the performer's identity.</p>
-<p>In the <strong>Kind</strong> drop-down list, define the performer as one
-of the following:</p>
-<ul>
- <li>User</li>
- <li>Organization/Role</li>
- <li>User Group</li>
- <li>Organization/Role or User Group</li>
-</ul>
-<p class="image"><img
- src="images/mg-performer-props.png" alt=""><br>
-<strong>Figure:</strong> Specifying a Conditional Performer</p>
-<h4>Oid/Id</h4>
-<p>In the <strong>OID/Id</strong> section, choose the data and data path providing
-the performer identity.</p>
-<p class="image"><img src="images/mg-org-cond-perf-oid.png"
- alt="Conditional Performer Properties"><br>
-<strong>Figure:</strong> Conditional Performer</p>
-
-<p class="note"><strong>Note</strong><br>In case the data is of type <strong>Long</strong>, the value is used to identify the
-OID of the performer, as thus it refers to a user. If the data is of type <strong>String</strong>,
-the value is used to identify the Id of the performer, as this has to be a role in that case.</p>
-<h4>User Realm</h4>
-<p>If the conditional performer is defined as a user, an additional field appears to
-fill in the users
-<a href="PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/handbooks/concepts/admin-concepts/ag-multipartition.htm#realm">
-realm</a> data.</p>
-<p class="image"><img src="images/mg-performer-props-realm.png" alt=""><br>
-<strong>Figure:</strong> Specifying a Conditional Performer as User</p>
-<h4>Using the Last Activity Performer data</h4>
-<p>The <strong>Last Activity Performer</strong> data usage determines that the
-performer is used as a computed value. The algorithm for a specific process
-instance is as follows:</p>
-<ol>
- <li>Select all <tt>COMPLETED</tt> activity instances belonging
- to the specific process instance, ordered descending by the last modification time.</li>
- <li>Traverse the result and select the first interactive activity instance.</li>
- <li>Return the user of that activity.</li>
-</ol>
-<p class="note"><strong>Note</strong><br>
-Please note that in case the activity is the first activity in the work flow,
-there would be no <strong>Last Activity Performer</strong>.
-If an activity other than the first one is unable to retrieve
-the last activity performer due to the transaction isolation level <tt>COMMITMENT</tt>,
-set in the database, enable the <strong>Fork on traversal</strong> flag in the
-transition between the current and the last activities.
-Please refer to the section <a href="mg-basics-13.htm#activityThread">Activity Thread</a> of the
-chapter <a href="mg-basics-13.htm">Runtime Behavior</a> for detailed
-information on the <strong>Fork on Traversal</strong>
-functionality.</p>
-<h3>Simulation</h3>
-<p>In this section you can specify simulation configurations, as described detailed in the chapter
- <a href="PLUGINS_ROOT/org.eclipse.stardust.docs.simulation/html/simulation/simulation-configurations.html">
- Simulation Configurations</a>
-of the
- <a href="PLUGINS_ROOT/org.eclipse.stardust.docs.simulation/html/simulation/toc.html">
- Developer Simulation Guide</a>.</p>
-<h3>Effort Planning</h3>
-<p>In this section you can set the performer complexity for project effort calculation:</p>
-<p class="image"><img src="images/performer-prop-effort.png" alt=""> <br>
-<strong>Figure:</strong> Effort Planning Property of a Conditional Performer</p>
-<p>Please refer to the chapter <a href="process-effort-calculation.html">Project Effort Calculation</a> for
-detailed information on this functionality.</p>
-<h3>Deleting Conditional Performers</h3>
-<p>When deleting conditional performers, you must make a distinction between deleting
-a conditional performer from the model information or only deleting a symbol from a
-diagram. To do the first - delete a conditional performer from the model - you proceed as
-follows:</p>
-<ul>
- <li>Having selected the symbol of the conditional performer in the <strong>Participants</strong>
- tree of the <a href="model-views/views-outline.html">Outline view</a>, choose the
- option <strong>Delete </strong> in the pop-up menu of this conditional performer.</li>
- <li>Having selected the symbol of the conditional performer in a diagram,
- choose the option <strong>Delete</strong> in the pop-up menu of this
- conditional performer.</li>
+ <li>Creating Organization</li>
+ <li>Renaming Organization</li>
+ <li>Deleting Organization</li>
+
+ <li>Creating Role</li>
+ <li>Viewing and Editing Organization Properties</li>
</ul>
-<p>The option <strong>Delete Symbol </strong> in the pop-up menu called from within
-the diagram canvas will only remove the symbol for the conditional performer from the
-diagram.</p>
-<h2 id="associate">Establishing Associations between Organizational Elements</h2>
-<p>Organizations are groups of human resources. Consequently, they may contain
-individual roles or subordinate organizations. Like process definitions, organizational
-hierarchies can be modeled in the @productname@ Workbench with the help of diagrams.</p>
-<p>To model your organizations, use either diagrams bound to a process definition or
-model diagrams. A prerequisite for establishing relationships between an organization and
-its members is the existence of these elements: an organization and all its members (roles
-or smaller organizational units). Proceed as follows:</p>
+
+<h3>Creating Organization</h3>
+<p>To create organization, right-click <strong>Participants</strong> node in the <strong>My Process Models</strong> panel
+ and click <strong>Create Organization</strong>.</p>
+
+ <p class="image"><img src="images/create-org.png"
+alt=""><br>
+<strong>Figure:</strong> Create Organization</p>
+
+<h3>Renaming Organization</h3>
+<p>To rename the organization, right-click on the <strong>Organization</strong> node in the <strong>My Process Models</strong> panel
+and click <strong>Rename</strong>.
+Specify the new name for organization.</p>
+<p class="image"><img src="images/org-rename.png"
+alt=""><br>
+<strong>Figure:</strong> Rename Organization</p>
+
+<h3>Deleting Organization</h3>
+<p>To delete organization, right-click on the <strong>Organization</strong> node in the <strong>My Process Models</strong> panel
+and click <strong>Delete</strong>.</p>
+
+<p class="image"><img src="images/org-del.png"
+alt=""><br>
+<strong>Figure:</strong> Delete Organization</p>
+<p>Click <strong>Yes</strong> in the <strong>Confirm</strong> dialog box. The organization gets deleted.</p>
+<p class="image"><img src="images/del-confirm.png"
+alt=""><br>
+<strong>Figure:</strong> Delete Organization - Confirmation</p>
+<h3>Creating Role</h3>
+
+<p>To create a role under organization, right-click on the <strong>Organization</strong> node in
+the <strong>My Process Models</strong> panel
+and click <strong>Create Role</strong>.</p>
+
+
+<p class="image"><img src="images/org-role.png"
+alt=""><br>
+<strong>Figure:</strong> Organization - Create Role</p>
+<h3 id="set">Set as Manager</h3>
+<p>The role created under organization can be set as manager or team lead. Right-click on the role
+created under organization node and click <strong>Set as Manager</strong>.</p>
+
+<p class="image"><img src="images/set-mgr.png"
+alt=""><br>
+<strong>Figure:</strong> Role - Set as Manager</p>
+<p>Note that at a time you can set only one role under organization as a team lead.</p>
+<h3>Creating Organization under Organization</h3>
+<p>To create organization under organization, right-click on the <strong>Organization</strong> node in
+the <strong>My Process Models</strong> panel
+and click <strong>Create Organization</strong>.</p>
+
+
+<p class="image"><img src="images/create-org-org.png"
+alt=""><br>
+<strong>Figure:</strong> Organization - Create Organization</p>
+
+
+<p>Not yet implemented.</p>
+
+<h3>Viewing and Editing Organization Properties</h3>
+<p>To view organization properties, click the <strong>Organization</strong> node in
+the <strong>My Process Models</strong> panel. The organization properties get displayed.
+
+<p class="image"><img src="images/org-abc.png"
+alt=""><br>
+<strong>Figure:</strong> Organization Properties</p>
+<p>Following properties are displayed:</p>
+
<ul>
- <li>Place the organization symbol and the symbol representing a member of this
- organization (e.g. a role or another organization) in a diagram.</li>
- <li>Right-click the symbol representing a member.</li>
- <li>Select <strong>Connect</strong> in the context menu.</li>
- <li>Click the organization the member is going to belong to.</li>
+
+ <li>Organization Name</li>
+ <li>Description</li>
+ <li>Public Visibility - By default, this check box is selected. It indicates that the element is
+ visible and available for reference from any other model.</li>
+ <li>Department - It is possible for organizations to add a department scope which is evaluated at runtime.
+ This department scope is described as a data path to process data which returns a
+ scope key to identify a department representing this scope.
+ <ul>
+ <li>Supports Departments - You can select this check box to determine whether the organization
+ is allowed to support departments. When you select this check box, the <strong>Data</strong>
+ and <strong>Data Path</strong> fields are enabled.
+ </li>
+ <li>Data - The drop-down list displays the data that you need to select for department.
+ You can select one of the following two data types:
+ <ul>
+ <li>a primitive data of type string without access path</li>
+ <li>a structured data and an access path evaluating to String</li>
+ </ul>
+
+ </li>
+ <li>Data Path - Specify the data path for the selected structured data</li></ul></li>
+ <li>Team Lead - Click the Team Lead tab to specify the role that can act as a team lead.
+ There can only be one team leader per organization. You can also define the team leader, using the
+ <strong>Set as Manager</strong> option.
+ <ul>
+ <li>Leader - By default, None is selected. You need to select the role from the drop-down list. </li>
+ <p class="image"><img src="images/leader.png" alt=""><br>
+ </ul>
+ </li>
+ <li>Activity Assignment - You have the choice for activity assignment.
+ The <strong>Choose Assignment</strong> option is selected by default. If you select <strong>Assign Automatically</strong>
+ option, then the Assembly Line mode gets activated. For more information, please refer to the chapter
+ <a href="PLUGINS_ROOT/org.eclipse.stardust.docs.enduser/html/handbooks/execution-clients/pp_renovated/pp-launch-panels.html">Launch Panels</a>
+ of the <a href="PLUGINS_ROOT/org.eclipse.stardust.docs.enduser/html/toc.html">Enduser Handbook</a>.
+ </li>
+ <li>Controlling - </li>
+ <li></li>
+
</ul>
-<p class="image"><img src="images/mg-connect-organizations.png" alt=""> <br>
-<strong>Figure:</strong> Making an Organization Part of Another</p>
-<p>To add further members to the organization, repeat these operations for each
-member. An example of an organizational hierarchy diagram is shown below.</p>
-<p class="image"><img src="images/organizational-diagram.png" alt=""> <br>
-<strong>Figure:</strong> A Sample Organizational Diagram</p>
-<h3>Restrictions on Associations</h3>
-<p>The following sections describes the restrictions on associations between organizational elements.</p>
-<h4>Only one relationship to other participants supported</h4>
-<p>Please note that a model participant can only have one relationship like
-<strong>Work For</strong> or <strong>Manager of</strong> to other
-participants. Otherwise the model validation fails and the
-following error message appears in the <strong>Problems</strong>
-view:</p>
-<p class="image"><img src="images/work-for-error-problem-view.png" alt="Problems View"> <br>
-<strong>Figure:</strong> Error indicated in Problems View</p>
-<h4>Only one relationship to other organizations supported</h4>
-<p>An organization should not be part of more than one other organization. Otherwise
-the model validation fails and the
-following error message appears in the <strong>Problems</strong>
-view:</p>
-<p class="image"><img src="images/part-of-error-problem-view.png" alt="Problems View"> <br>
-<strong>Figure:</strong> Error indicated in Problems View</p>
-<h4>Administrator Role cannot be connected</h4>
-<p>Since @productname@ version 5.2. and later, it is not possible
-to connect the <strong>Administrator</strong> role to any
-organization. In case models with @productname@ versions older than 5.2 contain
-such a connection, an error message in the <strong>Problems</strong> view
-indicates this in the following way:</p>
-<p class="image"><img src="images/admin-error-problem-view.png" alt="Problems View"> <br>
-<strong>Figure:</strong> Administrator Assignment Error in Problems View</p>
-<h3 id="scope">Behavior of Scoped Organizations</h3>
-
-<p>Infinilty Platform supoports scoping of roles, orgnizations and departments.
-The following sections describes what happens when the organizations are scoped.</p>
+<h2>Creating Roles</h2>
+<p>You can create roles in two ways:</p>
<ul>
- <li><a href="#implicit">Implicitly Scoped Roles</a></li>
- <li><a href="#hierScop">Organizational Hierarchies and Target Departments</a></li>
- <li><a href="#matrix">Matrix Organizations</a></li>
- <li><a href="#deploy">Deployment Restrictions</a></li>
+ <li>Creating roles under Organization node</li>
+ <li>Creating roles under Participants node</li>
+
</ul>
-<h4 id="implicit">Implicitly Scoped Roles</h4>
-<p>Roles are implicitly scoped via the next scoped Organization above.</p>
-<p>When a User is assigned to an (implicitly) scoped Role, the Role
-and the departments for all organizations, the Role has a "Works For" or "Is Manager Of"
-relationship, have to be specified.</p>
-<h4 id="hierScop">Organizational Hierarchies and Target Departments</h4>
-<p>All Organizations and Roles underneath a scoped Organization inherit
-the target departments of this Organization, as long as the suborganization does not define
-a new target department. Hence, for every participant the relevant target department is the scope of the
-next scoped Organization upwards the organizational hierarchy.</p>
-<h4 id="matrix">Matrix Organizations</h4>
-<p>@productname@ only allows pure tree structures for
-organizational hierarchies. Neither Roles nor Organizations may be assigned
-to more than one Organization. Matrix structures can be mapped by disjoint
-organizational structures with possibly different scopes (e.g. branch vs. project),
-whereby users might be assigned to Roles in both structures.</p>
-
-<h4>Matrix Organization - Example</h4>
-<p>
-@productname@ supports the matrix organization structure at runtime. While modelling, you cannot model
-the matrix structure completely.
-The matrix organization structure can be achieved at runtime using the process portals. You need to create
-departments in the Administration perspective to make a complete matrix structure.</p>
-<p>The following diagram displays the sample structure created at the modeler level.
-In the organization structure diagram, we have four organizations - M1 Project Orga, M2 Project Leader Orga, M1 Test Orga and M1 Development Orga.
-Each of these organizations have roles defined. The <b>M1 Project Manager</b> is the manager of <b>M1 Project Organization</b>.
-The <b>M3 Project Member</b> works for <b>M2 Project Leaders Organization</b>.
-These two organizations - the <b>M1 Project Organization</b> and <b>M2 Project Leaders organizations</b> are connected. The <b>M2 Test Engineer Organization</b>
-works for <b>M1 Test organization</b> and <b>M1 Test Manager</b> is the manager of the <b>M1 Test Organization</b>.
-
-We cannot connect one role to multiple organizations directly. That's why we need to create departments and assign users to roles.
-To achieve the same scenario, three red arrows are used to indicate that you need to create department <b>Project A</b> in the <b>M1 Test organization</b> and department
-<b>Project A and Project B</b> in the <b>M2 Leaders Organization</b>.</p>
-
-<p class="image"><img src="images/SamsaModel_MatrixOrgaStructure.png" alt="Sample Matrix Model">
-<br>
-<strong>Figure:</strong> Sample Model for Matrix Organization</p>
-<h4 id="deploy">Deployment Restrictions</h4>
-<p>Note that restrictions exist for deploying a model
-with changes in the department association for existing roles or organizations,
-to a succeeding model version.
-Please refer to the section
-<a href="mg-deploy-model.html#structure">Changes in the organizational structure</a>
-of the
-<a href="mg-deploy-model.html#consistency">Consistency Checks</a>
-part in the chapter
-<a href="mg-deploy-model.html">Deploying a Workflow Model</a>
-for detailed information on which changes are supported and which will lead to
-a consistency error.</p>
-<h3 id="teamLeader">The Team Leader Role</h3>
-<p>A role can be assigned as team leader to an organization. Please refer to the
-section <a href="mg-basics-9.htm#teams">Teams</a> of the chapter
-<a href="mg-basics-9.htm">Participants and Users</a> for
-a detailed description on the definition of a team.</p>
-<p>There can only be one
-team leader per organization. In case no team leader is associated to an organization
-yet, you are offered the following two types of connection:</p>
+<h3>Creating Roles under Participants Node</h3>
+<p>To create role, right-click on <strong>Participants</strong> node and click <strong>Create Role</strong>.</p>
+
+<p class="image"><img src="images/create-role.png"
+alt=""><br>
+<strong>Figure:</strong> Create Role</p>
+<h4>Renaming Role</h4>
+<p>To rename role, right-click on role and click <strong>Rename Role</strong>.</p>
+
+<p class="image"><img src="images/rename-role.png"
+alt=""><br>
+<strong>Figure:</strong> Rename Role</p>
+
+<h4>Deleting Role</h4>
+<p>To delete role, right-click on role and click <strong>Delete Role</strong>.</p>
+
+<p class="image"><img src="images/del-role.png"
+alt=""><br>
+<strong>Figure:</strong> Delete Role</p>
+
+<h3>Viewing Role Properties</h3>
+<p>To view role properties, click on role of which you want to view the properties.</p>
+
+<p class="image"><img src="images/role-prop.png"
+alt=""><br>
+<strong>Figure:</strong> Role Properties</p>
<ul>
- <li>Works For</li>
- <li>Manager Of</li>
+ <li>Role Name - Specify role name.</li>
+ <li>Description - Specify role description.</li>
+ <li>Public Visibility - </li>
+ <li>Activity Assignment -You have the choice for activity assignment.
+ The <strong>Choose Assignment</strong> option is selected by default. If you select <strong>Assign Automatically</strong>
+ option, then the Assembly Line mode gets activated. For more information, please refer to the chapter
+ <a href="PLUGINS_ROOT/org.eclipse.stardust.docs.enduser/html/handbooks/execution-clients/pp_renovated/pp-launch-panels.html">Launch Panels</a>
+ of the <a href="PLUGINS_ROOT/org.eclipse.stardust.docs.enduser/html/toc.html">Enduser Handbook</a>></li>
+ <li>Controlling
+ <ul>
+ <li>Controlling Weeks per Year</li>
+ <li>Target Worktime per Day</li>
+ <li>Target Worktime per Week</li>
+ <li>Target Queue Depth</li>
+ <li>Actual Cost per Minute</li>
+ </ul>
+ </li>
</ul>
-<p>The <strong>Works For</strong> connection is a simple assignment of a role to an
-organization, whereas the <strong>Manager Of</strong> connection defines the role to be the
-organizations team leader.</p>
-<p class="image"><img src="images/mg-connect-teamleader.png"
- alt="Team Leader Connection"> <br>
-<strong>Figure:</strong> Connecting a Role as Team Leader</p>
-<p>The connect transition between a team leader and an organization is displayed as a
-dashed line.</p>
-<p class="image"><img src="images/mg-teamleader-transition.png"
- alt="Team Leader Connection"> <br>
-<strong>Figure:</strong> Connect Transition between Team Leader and Organization</p>
-<p>In the
-<a href="PLUGINS_ROOT/org.eclipse.stardust.docs.enduser/html/handbooks/execution-clients/bcc_renovated/business-control-center.html">
-Business Control Center Perspective</a> of the
-<a href="PLUGINS_ROOT/org.eclipse.stardust.docs.enduser/html/handbooks/execution-clients/carnot-clients.html">
-@productname@ Portal</a>,
-the team leader has an overview over the activities
-of all users belonging to the same organization the team leader belongs to.</p>
-<h4>Invalid Teamlead connection</h4>
-<p>In case an organization has an invalid teamlead connection, e.g. it
-has a teamlead connection, but the team leader is not set in the model file,
-an error indicates this in the <strong>Problems View</strong>.</p>
-<p class="image"><img src="images/teamlead-error.png"
- alt="Team Leader Connection Error"> <br>
-<strong>Figure:</strong> Connection Error displayed in the Problems View.</p>
-<p>You have the option to use the provided <strong>Quick Fix</strong>
-functionality for quickly fixing this error. Right-click the error entry and
-choose the <strong>Quick Fix</strong> option in the drop-down menu.</p>
-<p class="image"><img src="images/teamlead-error-quick-fix-1.png"
- alt="Team Leader Connection Error"> <br>
-<strong>Figure:</strong> Select Quick Fix to fix the Error.</p>
-<p>The <strong>Quick Fix</strong> dialog opens, where you can fix the
-teamlead connection for the organization.</p>
-<p class="image"><img src="images/teamlead-error-quick-fix-2.png"
- alt="Quick Fix Dialog"> <br>
-<strong>Figure:</strong> Quick Fix Dialog</p>
-<h2>Assigning Processes Restricted by Role and Organization</h2>
-<p>In case you want the admin user to view all the processses in the model whereas the other user/role
-should start only a specific process. For example, you have a model which contains four
-processes P1, P2, P3 and P4. The process P1 and P2 display the data whereas P3 and P4 update of data.
-The model has two participants that are Admin and Teller.</p>
-<p>Suppose you want the Admin user to start all the four processes and the Teller user to start only two processes
-that are P1 and P2.</p>
-<p>To achieve this, define an organization A and make the roles Admin and Teller Works for organization A. Then
-assign the manual start trigger of P1 and P2 process to organization and manual start trigger of P3 and
-P4 to Admin role.</p>
+
+<h2>Conditional Performer</h2>
+<p>The conditional performer is evaluated at runtime and it determines the identity of the actual performer.
+The following sections help you to work with conditional performers.</p>
+
+<h3>Creating Conditional Performer</h3>
+
+<p>To create conditional performer, right-click <strong>Participants</strong> node
+and click <strong>Conditional Performer</strong>.</p>
+
+
+<p class="image"><img src="images/cre-cond-perf.png"
+alt=""><br>
+<strong>Figure:</strong> Create Conditional Performer</p>
+
+<h3>Renaming Conditional Performer</h3>
+
+<p>To create conditional performer, right-click on conditional performer
+in <strong>Participants</strong> node
+and click <strong>Rename</strong>.</p>
+
+
+<p class="image"><img src="images/rename-cond-perf.png"
+alt=""><br>
+<strong>Figure:</strong> Rename Conditional Performer</p>
+
+<h3>Deleting Conditional Performer</h3>
+<p>To delete conditional performer, right-click on conditional performer
+in <strong>Participants</strong> node
+and click <strong>Delete</strong>.</p>
+
+
+<p class="image"><img src="images/del-cond-perf.png"
+alt=""><br>
+<strong>Figure:</strong> Delete Conditional Performer</p>
+
+<h3>Viewing Conditional Performer Properties</h3>
+
+
+
+
+
+
+
+
+
+
+
+
<script language="JavaScript" type="text/javascript">
<!--