|author||Vrishali Doke||2012-04-02 03:06:22 -0400|
|committer||Stephan Born||2012-06-15 10:38:22 -0400|
CRNT-23425 - Added details for delegation to any participant
git-svn-id: http://emeafrazerg/svn/ipp/product/trunk/stardust/documentation@55154 8100b5e0-4d52-466c-ae9c-bdeccbdeaf6b
1 files changed, 11 insertions, 6 deletions
diff --git a/org.eclipse.stardust.docs.enduser/html/handbooks/execution-clients/detail-views/case-details-view.html b/org.eclipse.stardust.docs.enduser/html/handbooks/execution-clients/detail-views/case-details-view.html
index 9f39331..bcd7895 100644
@@ -134,7 +134,7 @@ To attach a process instance to a case:
<p class="image"><img src="images/tool-corres.png"alt=""><br>
<p>A new Correspondence tab opens, where you can edit correspondence content.
-For more information, please refer to the chapter<a href="context-portal-correspondence.html">Creating Correspondence
+For more information, please refer to the chapter <a href="context-portal-correspondence.html">Creating Correspondence
@@ -155,7 +155,7 @@ For more information, please refer to the chapter<a href="context-portal-corresp
<li>Click the <img src="images/tickmark.png">icon. The new case name gets displayed. </li>
<h3>Delegating a Case</h3>
-<p>Every case has an owner. The existing case owner and administrator can modify this field.
+<p>Every case has an owner. The existing case owner and administrator can modify this field. Note that the case should not be in terminated state.
For more information on case owner, please refer to the
<span class="hideReference"><strong>Owner of a Case</strong> of chapter
@@ -169,8 +169,13 @@ of the <a href="PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/handbooks/concep
Using the <strong>Delegate Case Ownership</strong> option, you can change the owner.
<p>Note that there are no restrictions to whom the case owner can delegate the case. The case owner can delegate
-the case to any participant defined in any active model. Such as: any @productname@ Portal user, role,
-(can be implicitly scoped role), organization, (can be scoped organization) and department. Note that the case should not be in terminated state.</p>
+the case to any participant regardless of current performer defined in any active model. Such as, delegation to
+any @productname@ Portal user, role (can be implicitly scoped role),
+organization (can be scoped organization), and department. The Pick from List and Pick from Tree options
+include all participants regardless of
+current performer and all the departments in the hierarchy. Departments (both implicitly and explicitly scoped)
+are ordered alphabetically by the prepended parent organization name.
<p>To modify the case owner:</p>
@@ -180,7 +185,7 @@ the case to any participant defined in any active model. Such as: any @productna
<strong>Figure:</strong> Delegate Case Ownership</p>
- <li>If you want to delegate the case to role or organization, then in the <strong>Delegate Case Ownership</strong> dialog box,
+ <li>If you want to delegate the case to role or organization and its departments, then in the <strong>Delegate Case Ownership</strong> dialog box,
click the link <strong>Pick from Tree</strong>.
The Participant Tree gets displayed.
@@ -444,7 +449,7 @@ for detailed information.</p>
<p>If the process instance to be detached is the last active process instance but at least one case member still exists, the
-state of the case process instance changes to completed. Following warning message is displayed.</p>
+state of the case process instance changes to complete. Following warning message is displayed.</p>
<p class="image"><img src="images/detach-pi-complete.png"