incubator-hise-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From r.@apache.org
Subject svn commit: r983563 [3/3] - in /incubator/hise/site: author/src/documentation/content/xdocs/ publish/
Date Mon, 09 Aug 2010 09:07:59 GMT
Modified: incubator/hise/site/publish/index.html
URL: http://svn.apache.org/viewvc/incubator/hise/site/publish/index.html?rev=983563&r1=983562&r2=983563&view=diff
==============================================================================
--- incubator/hise/site/publish/index.html (original)
+++ incubator/hise/site/publish/index.html Mon Aug  9 09:07:58 2010
@@ -168,6 +168,38 @@ if (VERSION > 3) {
       </p>
       
 <p>
+          Following features are currently supported in our latest internal release:
+      </p>
+          
+<ul>
+              
+<li>Task lifecycle handling</li>
+              
+<li>Deadlines</li>
+              
+<li>Escalations</li>
+              
+<li>Delegations</li>
+              
+<li>Comments</li>
+              
+<li>Task history in comments</li>
+              
+<li>Renderings</li>
+              
+<li>Attachments</li>
+              
+<li>Task filtering using queries</li>
+              
+<li>Notifications</li>
+          
+</ul>
+      
+<p>
+          For more details, please refer to <a href="user-guide.xhtml">User Guide</a>. 
+      </p>
+      
+<p>
         HISE reads Human Tasks definitions provided in XML format and distributes 
         issues initiated by External Systems to various Task Operators. 
         Basic scenario for HISE usage is described on following sequence diagram. 
@@ -179,11 +211,7 @@ if (VERSION > 3) {
       </p>
       
 <p>
-        Distribution contains WAR J2EE application and claimsHandling Task example. 
-      </p>
-      
-<p>
-        More informations is available in User Guide. 
+        HISE contains two distributions: J2EE WAR and ServiceMix 4 OSGi. Both of them contain claimsHandling Task example. 
       </p>
   
 </div>

Modified: incubator/hise/site/publish/road-map.html
URL: http://svn.apache.org/viewvc/incubator/hise/site/publish/road-map.html?rev=983563&r1=983562&r2=983563&view=diff
==============================================================================
--- incubator/hise/site/publish/road-map.html (original)
+++ incubator/hise/site/publish/road-map.html Mon Aug  9 09:07:58 2010
@@ -161,16 +161,51 @@ if (VERSION > 3) {
 }
         </script>
 <h1>Road Map</h1>
+      
+<p>Planned goals for version 1.0.0:</p>
 
 <ul>
  
-<li>Currently, there's only POJO based possibility for connecting with HISE services. The goal is to add Web Services based distributions. Those will include WAR and JBI distribution.</li>
+<li>Implement remaining WS-Human-Task spec. It will include work queues.</li>
  
-<li>Second thing is to implement remaining WS-Human-Task spec. It will include adding scheduler, implementing time notifications and adding tasks escalations.</li>
+<li>Resolve remaining Jira issues. Those are mostly small improvements.</li>
+
+</ul>
+      
+<p>Accomplished goals for 0.3.0:</p>
+
+<ul>
+ 
+<li>Web Services based distributions. WAR and ServiceMix 4 OSGi distributions.</li>
+ 
+<li>Implemented substantial part of WS-Human-Task spec. It includes:
+          <ul>
+              
+<li>Task lifecycle handling</li>
+              
+<li>Deadlines</li>
+              
+<li>Escalations</li>
+              
+<li>Delegations</li>
+              
+<li>Comments</li>
+              
+<li>Task history in comments</li>
+              
+<li>Renderings</li>
+              
+<li>Attachments</li>
+              
+<li>Task filtering using queries</li>
+              
+<li>Notifications</li>
+          
+</ul>
  
-<li>Third thing is to migrate Hibernate JPA to OpenJPA for licensing reasons.</li>
+</li>
  
-<li>Future plans (after 1.0 release) include OSGi bundle distribution to increase wide adoption of HISE. </li>
+<li>Migrated Hibernate JPA to OpenJPA for licensing reasons.</li>
 
 </ul>
   

Modified: incubator/hise/site/publish/user-guide.xhtml
URL: http://svn.apache.org/viewvc/incubator/hise/site/publish/user-guide.xhtml?rev=983563&r1=983562&r2=983563&view=diff
==============================================================================
--- incubator/hise/site/publish/user-guide.xhtml (original)
+++ incubator/hise/site/publish/user-guide.xhtml Mon Aug  9 09:07:58 2010
@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="UTF-8"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Apache HISE User Guide</title><meta name="generator" content="DocBook XSL Stylesheets V1.75.2" /></head><body><div class="book" title="Apache HISE User Guide"><div class="titlepage"><div><div><h1 class="title"><a id="id3503732"></a>Apache HISE User Guide</h1></div><div><p class="releaseinfo">0.2.0-SNAPSHOT</p></div></div><hr /></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="index"><a href="#id3503796">Index</a></span></dt><dt><span class="chapter"><a href="#id3503830">1. Quick Introduction into WAR distibution</a></span></dt><dt><span class="chapter"><a href="#id3503960">2. Intoduction into OSGi distribution</a></span></dt><dt><span class="chapter"><a href="#id3503980">3. Claims Handling Example</a></span></dt></dl></div><div class="index" title="Index"><div class="titlepage"><div><div><h2 class="title"><a id="id3503796"></a>
 Index</h2></div></div></div><div class="index"></div></div><div class="chapter" title="Chapter 1. Quick Introduction into WAR distibution"><div class="titlepage"><div><div><h2 class="title"><a id="id3503830"></a>Chapter 1. Quick Introduction into WAR distibution</h2></div></div></div><p>
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Apache HISE User Guide</title><meta name="generator" content="DocBook XSL Stylesheets V1.75.2" /></head><body><div class="book" title="Apache HISE User Guide"><div class="titlepage"><div><div><h1 class="title"><a id="id3790367"></a>Apache HISE User Guide</h1></div><div><p class="releaseinfo">0.3.0</p></div></div><hr /></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="index"><a href="#id3790419">Index</a></span></dt><dt><span class="chapter"><a href="#id3790455">1. Quick Introduction into WAR distibution</a></span></dt><dt><span class="chapter"><a href="#id3790617">2. Intoduction into OSGi distribution</a></span></dt><dt><span class="chapter"><a href="#id3790639">3. Claims Handling Example</a></span></dt><dt><span class="chapter"><a href="#id3790706">4. Concepts</a></span></dt><dd><dl><dt><span class="sect1"><a href="#taskInstan
 ceData">Task instance data</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id3790762">Presentation parameters</a></span></dt><dt><span class="sect2"><a href="#id3790775">Context Data</a></span></dt><dt><span class="sect2"><a href="#id3790809">Operational data</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id3790818">Generic Human Role</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id3790871">Task initiator</a></span></dt><dt><span class="sect2"><a href="#id3790883">Task stakeholders</a></span></dt><dt><span class="sect2"><a href="#id3790901">Potential owners</a></span></dt><dt><span class="sect2"><a href="#id3790918">Actual owner</a></span></dt><dt><span class="sect2"><a href="#id3790931">Buisness administrators</a></span></dt><dt><span class="sect2"><a href="#id3790947">Excluded owners</a></span></dt><dt><span class="sect2"><a href="#id3790960">Recipients</a></span></dt><dt><span class="sect2"><a href="#id3790976">Potential delegatees</a></spa
 n></dt></dl></dd><dt><span class="sect1"><a href="#id3790990">Logical People Group</a></span></dt></dl></dd><dt><span class="chapter"><a href="#task_properties">5. Task properties</a></span></dt><dd><dl><dt><span class="sect1"><a href="#id3791019">Task Properties</a></span></dt></dl></dd><dt><span class="chapter"><a href="#task_features">6. Task features</a></span></dt><dd><dl><dt><span class="sect1"><a href="#states">Task finite state machine</a></span></dt><dt><span class="sect1"><a href="#id3791142">Deadline</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id3791211">Escalations</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id3791357">Delegation</a></span></dt><dt><span class="sect1"><a href="#comments">Comments</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id3791415">Comments added by user</a></span></dt><dt><span class="sect2"><a href="#id3791448">Task history in comments</a></span></dt></dl></dd><dt><span class="sect1"><a href="#renderin
 g">Rendering</a></span></dt><dt><span class="sect1"><a href="#attachments">Attachments</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id3791642">addAttachment</a></span></dt><dt><span class="sect2"><a href="#id3791668">deleteAttachment</a></span></dt><dt><span class="sect2"><a href="#id3791676">getAttachmentInfos</a></span></dt><dt><span class="sect2"><a href="#id3791698">getAttachments</a></span></dt></dl></dd><dt><span class="sect1"><a href="#filtering">Task filtering</a></span></dt><dt><span class="sect1"><a href="#presentationElements">Presentation elements</a></span></dt><dt><span class="sect1"><a href="#presentationElements">Presentation elements</a></span></dt></dl></dd><dt><span class="chapter"><a href="#taskOperations">7. Task operations</a></span></dt><dd><dl><dt><span class="sect1"><a href="#id3792011">Participant operations</a></span></dt><dt><span class="sect1"><a href="#id3792881">Administrative Operations</a></span></dt><dt><span class="sect1"><a hre
 f="#simpleQuery">Simple Query operations</a></span></dt></dl></dd><dt><span class="chapter"><a href="#id3793103">8. Notifications</a></span></dt><dd><dl><dt><span class="sect1"><a href="#id3793108"></a></span></dt><dd><dl><dt><span class="sect2"><a href="#id3793141">Notification properties</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#examples">9. Examples</a></span></dt><dd><dl><dt><span class="sect1"><a href="#taskInfoExample">Task info example</a></span></dt></dl></dd></dl></div><div class="list-of-figures"><p><b>List of Figures</b></p><dl><dt>6.1. <a href="#id3791134">State transitions</a></dt></dl></div><div class="list-of-tables"><p><b>List of Tables</b></p><dl><dt>7.1. <a href="#id3792043">Participant operations</a></dt><dt>7.2. <a href="#id3792888">Administrative Operations</a></dt><dt>7.3. <a href="#id3793013">Simple Query operations</a></dt></dl></div><div class="index" title="Index"><div class="titlepage"><div><div><h2 class="title"><a id=
 "id3790419"></a>Index</h2></div></div></div><div class="index"></div></div><div class="chapter" title="Chapter 1. Quick Introduction into WAR distibution"><div class="titlepage"><div><div><h2 class="title"><a id="id3790455"></a>Chapter 1. Quick Introduction into WAR distibution</h2></div></div></div><p>
       In order to have something running, you need to do following steps:
       </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>Download HISE distribution</p></li><li class="listitem"><p>Then you need to unzip HISE WAR contents into your application server directory (like Apache Tomcat). Name it hise.</p></li><li class="listitem"><p>
             Copy example files from examples/claims-approval/* into WEB-INF/classes directory.
@@ -19,9 +19,9 @@
             </pre><p>
             addUsers.sql looks like this:
             </p><pre class="programlisting">
-              insert into ORG_ENTITY (name, type, userpassword) values ('user1', 'USER', 'pass1');
-              insert into ORG_ENTITY (name, type, userpassword) values ('group1', 'GROUP', null);
-              insert into USER_GROUPS (USERGROUPS_NAME, ORGENTITY_NAME) values ('user1', 'group1');
+                insert into HISE_ENTITY (name, type, userpassword) values ('user1', 'USER', 'pass1');
+                insert into HISE_ENTITY (name, type, userpassword) values ('group1', 'GROUP', null);
+                insert into HISE_USER_GROUPS (USERGROUPS_NAME, ORGENTITY_NAME) values ('user1', 'group1');
             </pre><p>
             This defines Organizational Entities and specifies associations between users and groups.
           </p></li><li class="listitem"><p>
@@ -38,15 +38,15 @@
               Additionally, when WS Addressing reply-to field is specified in approve request, 
               HISE will send reply on task completion to a specified address. 
            </p></li></ul></div><p>
-    </p></div><div class="chapter" title="Chapter 2. Intoduction into OSGi distribution"><div class="titlepage"><div><div><h2 class="title"><a id="id3503960"></a>Chapter 2. Intoduction into OSGi distribution</h2></div></div></div><p>
-      HISE OSGi distribution works out of box under Apach ServiceMix 4. 
+    </p></div><div class="chapter" title="Chapter 2. Intoduction into OSGi distribution"><div class="titlepage"><div><div><h2 class="title"><a id="id3790617"></a>Chapter 2. Intoduction into OSGi distribution</h2></div></div></div><p>
+      HISE OSGi distribution works out of box under Apache ServiceMix 4. 
       It contains bundles directory with required dependencies. 
-      In order to run it, you need to put those artifacts into SMX4/deploy directory. 
+      In order to run it, you need to type in ServiceMix console: <code class="code">features:install hise-h2-test-example-osgi</code> 
       Next, you can point your browser to http://localhost:8181/cxf address 
       and see deployed Web Services.
     </p><p>
-      This distribution was tested under apache-servicemix-4.1.0-psc-01-00RC1 (FUSE). 
-    </p></div><div class="chapter" title="Chapter 3. Claims Handling Example"><div class="titlepage"><div><div><h2 class="title"><a id="id3503980"></a>Chapter 3. Claims Handling Example</h2></div></div></div><p>
+      This distribution was tested under apache-servicemix-4.2.0-fuse-01-00. 
+    </p></div><div class="chapter" title="Chapter 3. Claims Handling Example"><div class="titlepage"><div><div><h2 class="title"><a id="id3790639"></a>Chapter 3. Claims Handling Example</h2></div></div></div><p>
       HISE distribution contains claimsHandling example, which defines a single 
       Human Interaction with one potential owner (Task Operator).
     </p><p>
@@ -97,4 +97,891 @@
       </p><div class="mediaobject" align="center"><img src="claimsHandling.png" align="middle" /></div><p>
       
       Detailed information on endpoint addresses is defined in claimsHandling-hise-dd.xml file.
-    </p></div></div></body></html>
+    </p></div><div class="chapter" title="Chapter 4. Concepts"><div class="titlepage"><div><div><h2 class="title"><a id="id3790706"></a>Chapter 4. Concepts</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="#taskInstanceData">Task instance data</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id3790762">Presentation parameters</a></span></dt><dt><span class="sect2"><a href="#id3790775">Context Data</a></span></dt><dt><span class="sect2"><a href="#id3790809">Operational data</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id3790818">Generic Human Role</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id3790871">Task initiator</a></span></dt><dt><span class="sect2"><a href="#id3790883">Task stakeholders</a></span></dt><dt><span class="sect2"><a href="#id3790901">Potential owners</a></span></dt><dt><span class="sect2"><a href="#id3790918">Actual owner</a></span></dt><dt><span class="se
 ct2"><a href="#id3790931">Buisness administrators</a></span></dt><dt><span class="sect2"><a href="#id3790947">Excluded owners</a></span></dt><dt><span class="sect2"><a href="#id3790960">Recipients</a></span></dt><dt><span class="sect2"><a href="#id3790976">Potential delegatees</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id3790990">Logical People Group</a></span></dt></dl></div><p>
+Human tasks, or briefly tasks enable the integration of human beings in service-
+oriented applications.
+Human tasks are services “implemented” by people. They allow the integration of
+humans in service-oriented applications. A human task has two interfaces. One
+interface exposes the service offered by the task, like a translation service or an
+approval service. The second interface allows people to deal with tasks, for example
+to query for human tasks waiting for them, and to work on these tasks.
+A human task has people assigned to it. These assignments define who should be
+allowed to play a certain role on that task. Human tasks may also specify how task
+metadata should be rendered on different devices or applications making them
+portable and interoperable with different types of software. Human tasks can be
+defined to react on timeouts, triggering an apropriate escalation action.
+This also holds true for notifications. Notifications are a special type of human task
+that allows the sending of information about noteworthy business events to people.
+Notifications are always oneway, i.e., they are delivered in a fire-and-forget manner:
+The sender pushes out notifications to people without waiting for these people to
+acknowledge their receipt.
+
+</p><div class="sect1" title="Task instance data"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="taskInstanceData"></a>Task instance data</h2></div></div></div>
+	Task instance data falls into three categories:
+	<div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>Presentation data – The data is derived from the task
+				definition or the notification definition such as the name, subject
+				or description.</p></li><li class="listitem"><p> Context data - A set of dynamic properties, such as priority,
+				task state, time stamps and values for all generic human roles.
+			</p></li><li class="listitem"><p> Operational data – The data includes the input message, output
+				message, attachments and comments.</p></li></ul></div><div class="sect2" title="Presentation parameters"><div class="titlepage"><div><div><h3 class="title"><a id="id3790762"></a>Presentation parameters</h3></div></div></div>
+		The presentation data is used, for example, when displaying a task or
+		a notification in the task list client. The presentation data has been
+		prepared for display such as by substituting variables. See
+		<a class="link" href="#presentationElements" title="Presentation elements">Presentation Elements</a>
+		for more details.
+	</div><div class="sect2" title="Context Data"><div class="titlepage"><div><div><h3 class="title"><a id="id3790775"></a>Context Data</h3></div></div></div>
+		The task context includes a lot of things, for example:
+		<div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>task state</p></li><li class="listitem"><p>priority</p></li><li class="listitem"><p> Values for all generic human roles, i.e. potential owners,
+					actual owner and business administrators</p></li><li class="listitem"><p>Time stamps such as start time, completion time</p></li><li class="listitem"><p>Skipable indicator</p></li><li class="listitem"><p>task history language and indicator</p></li></ul></div>
+		For whole list of information go to
+		<a class="link" href="#taskInfoExample" title="Task info example">task info example</a></div><div class="sect2" title="Operational data"><div class="titlepage"><div><div><h3 class="title"><a id="id3790809"></a>Operational data</h3></div></div></div><p>The operational data of a task consists of its input data and
+			output data or fault data. Operational data is accessed using the
+			XQuery extension functions and programming interface.</p></div></div><div class="sect1" title="Generic Human Role"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="id3790818"></a>Generic Human Role</h2></div></div></div><p>Generic human roles define what a person or group of people
+      resulting from a people query can do with tasks and notifications. The
+      aplication distinguish fallowing generic human roles: 
+	</p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><a class="link" href="#taskInitiator">Task initiator</a></li><li class="listitem"><a class="link" href="#taskStakeholders">Task stakeholders</a></li><li class="listitem"><a class="link" href="#potentialOwners">Potential owners</a></li><li class="listitem"><a class="link" href="#actualOner">Actual owner</a></li><li class="listitem"><a class="link" href="#businessAdministrators">Business
+            administrators</a></li><li class="listitem"><a class="link" href="#excludedOwners">Excluded owners </a></li><li class="listitem"><a class="link" href="#recipients">Recipients</a></li><li class="listitem"><a class="link" href="#potentialDelegatees">Potential delegatees</a></li></ul></div><p> </p><div class="sect2" title="Task initiator"><div class="titlepage"><div><div><h3 class="title"><a id="id3790871"></a><p><a id="taskInitiator"></a>Task initiator</p></h3></div></div></div><p>Task initiator is the
+      person who creates the task instance. Depending on how the task has been
+      instantiated the task initiator may or may not be defined. If task
+      initiator is defined it is exactly one person.</p></div><div class="sect2" title="Task stakeholders"><div class="titlepage"><div><div><h3 class="title"><a id="id3790883"></a><p><a id="taskStakeholders"></a>Task stakeholders</p></h3></div></div></div><p>Task stakeholders are
+      the people ultimately responsible for the oversight and outcome of the
+      task instance. A task stakeholder can influence the progress of a task,
+      for example, by adding ad-hoc attachments, forwarding the task, or
+      simply observing the state changes of the task. It is also allowed to
+      perform administrative actions on the task instance and associated
+      notifications, such as resolving missed deadlines. Compliant
+      implementations MUST ensure that at least one person is associated with
+      this role at runtime.</p></div><div class="sect2" title="Potential owners"><div class="titlepage"><div><div><h3 class="title"><a id="id3790901"></a><p><a id="potentialOwners"></a>Potential owners</p></h3></div></div></div><p>Potential owners of a
+      task are persons who receive the task so that they can claim and
+      complete it. A potential owner becomes the actual owner of a task by
+      explicitly claiming it. Before the task has been claimed, potential
+      owners can influence the progress of the task, for example by changing
+      the priority of the task, adding ad-hoc attachments or comments. All
+      excluded owners are implicitly removed from the set of potential
+      owners.</p></div><div class="sect2" title="Actual owner"><div class="titlepage"><div><div><h3 class="title"><a id="id3790918"></a><p><a id="actualOner"></a>Actual owner</p></h3></div></div></div><p>Actual owneris the person
+      actually performing the task. A task has exactly one actual owner. When
+      task is performed, the actual owner can execute actions, such as
+      revoking the claim, forwarding the task, suspending and resuming the
+      task execution or changing the priority of the task.</p></div><div class="sect2" title="Buisness administrators"><div class="titlepage"><div><div><h3 class="title"><a id="id3790931"></a><p><a id="businessAdministrators"></a>Buisness administrators</p></h3></div></div></div><p>Buisness administrators are the people
+      who can play the same role as task stakeholders but at task type level.
+      Therefore, business administrators can perform the exact same operations
+      as task stakeholders. Business administrators may also observe the
+      progress of notifications. Compliant implementations MUST ensure that at
+      runtime at least one person is associated with this role.</p></div><div class="sect2" title="Excluded owners"><div class="titlepage"><div><div><h3 class="title"><a id="id3790947"></a><p><a id="excludedOwners"></a>Excluded owners</p></h3></div></div></div><p><a id="excludedOwners"></a>Excluded owners may not
+      become an actual or potential owner and thus they may not reserve or
+      start the task. They can only doing statistic or information
+      operations.</p></div><div class="sect2" title="Recipients"><div class="titlepage"><div><div><h3 class="title"><a id="id3790960"></a><p><a id="recipients"></a>Recipients</p></h3></div></div></div><p>Recipients are persons who
+      receive the notification, such as happens when a deadline is missed or
+      when a milestone is reached. This role is similar to the roles potential
+      owners and actual owner but has different repercussions because a
+      notification recipient does not have to perform any action and hence it
+      is more of informational nature than participation. A notification has
+      one or more recipients.</p></div><div class="sect2" title="Potential delegatees"><div class="titlepage"><div><div><h3 class="title"><a id="id3790976"></a><p><a id="potentialDelegatees"></a>Potential delegatees</p></h3></div></div></div><p>Potential delegatees
+      are persons or group peopels who can be delegate to perform the task.
+      Potential delegatees are indication durning creation task by the task
+      initiator. </p></div></div><div class="sect1" title="Logical People Group"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="id3790990"></a>Logical People Group</h2></div></div></div><p>A logical people groups is an element that could represents one person, a set of people, or one or many unresolved group of people. It is global element enclosed in a human interactions definition document. Multiple human tasks in the same document can utilize the same logical people group definition. 
+    </p><pre class="programlisting">
+	   
+		&lt;htd:logicalPeopleGroups&gt;
+    
+    		    &lt;htd:logicalPeopleGroup name="regionEmployees"&gt;
+            		&lt;htd:documentation xml:lang="en-US"&gt;Employee group.&lt;/htd:documentation&gt;
+            		&lt;htd:parameter name="region" type="xsd:string"/&gt;
+        	    &lt;/htd:logicalPeopleGroup&gt;
+
+    		&lt;/htd:logicalPeopleGroups&gt;
+	   
+    </pre></div></div><div class="chapter" title="Chapter 5. Task properties"><div class="titlepage"><div><div><h2 class="title"><a id="task_properties"></a>Chapter 5. Task properties</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="#id3791019">Task Properties</a></span></dt></dl></div><div class="sect1" title="Task Properties"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="id3791019"></a>Task Properties</h2></div></div></div><p>The fallowing basic attributs are defined for tasks:
+
+	</p><div class="sect2" title="name"><div class="titlepage"><div><div><h3 class="title"><a id="id3791027"></a><p><a id="task_name"></a>name</p></h3></div></div></div><p>This attribute is mandatory. It is used to specity the name of the task. 
+		The name, combined with namespace create a unique identifier the task definition.
+	     </p></div><p>
+	</p><div class="sect2" title="priority"><div class="titlepage"><div><div><h3 class="title"><a id="id3791041"></a><p><a id="task_priority"></a>priority</p></h3></div></div></div><p>This element is used to specify the priority of the task. It is an
+		optional element which value is an integer expression. If not present, the priority of the 			task is set to 0 what is the highest priority. Larger numbers identify lower priorites.
+             </p></div><p>
+	</p><div class="sect2" title="autoActivate"><div class="titlepage"><div><div><h3 class="title"><a id="id3791056"></a>autoActivate</h3></div></div></div><p>This element allows enable automatic activation task (if it is possible) immediately after
+		 it is creation. It is binary type and optional. If not present the default value is false 
+             </p></div><p>
+	</p><div class="sect2" title="isSkipable"><div class="titlepage"><div><div><h3 class="title"><a id="id3791066"></a>isSkipable</h3></div></div></div><p>This element is used to determines whether a task can actuall be skipped at runtime. 
+		It is binary type and optional. If not present the default value is true. 
+             </p></div><p>
+	</p><div class="sect2" title="peopleAssignments"><div class="titlepage"><div><div><h3 class="title"><a id="id3791076"></a><p><a id="task_peopleAssignments"></a>peopleAssignments</p></h3></div></div></div><p> It is used to assign people and group of people to different generic human role. 
+		This element is mandatory and is defined by "Using Literals" 
+		or "Logical people groups".
+	     </p><pre class="programlisting">
+	   	
+	      &lt;htd:peopleAssignments&gt;
+            	&lt;htd:potentialOwners&gt;
+                  &lt;htd:from&gt;
+                    &lt;htd:literal&gt;
+                        &lt;htd:organizationalEntity&gt;
+                            &lt;htd:users&gt;
+                                &lt;htd:user&gt;user1&lt;/htd:user&gt;
+                            &lt;/htd:users&gt;
+                        &lt;/htd:organizationalEntity&gt;
+                    &lt;/htd:literal&gt;
+                  &lt;/htd:from&gt;
+                &lt;/htd:potentialOwners&gt;	
+
+		&lt;htd:businessAdministrators&gt;
+		         ...		
+		&lt;/htd:businessAdministrators&gt;
+	      &lt;htd:peopleAssignments&gt;
+
+	...
+
+	      &lt;htd:potentialOwners&gt;
+ 		 &lt;htd:from logicalPeopleGroup="regionalClerks"&gt;
+    		    &lt;htd:argument name="region"&gt;
+       			htd:getInput("part1")/region
+    		    &lt;/htd:argument&gt;
+  		 &lt;/htd:from&gt;
+	      &lt;/htd:potentialOwners&gt;
+		
+	     </pre></div><p>
+	</p></div></div><div class="chapter" title="Chapter 6. Task features"><div class="titlepage"><div><div><h2 class="title"><a id="task_features"></a>Chapter 6. Task features</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="#states">Task finite state machine</a></span></dt><dt><span class="sect1"><a href="#id3791142">Deadline</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id3791211">Escalations</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id3791357">Delegation</a></span></dt><dt><span class="sect1"><a href="#comments">Comments</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id3791415">Comments added by user</a></span></dt><dt><span class="sect2"><a href="#id3791448">Task history in comments</a></span></dt></dl></dd><dt><span class="sect1"><a href="#rendering">Rendering</a></span></dt><dt><span class="sect1"><a href="#attachments">Attachments</a></span></dt><dd><dl><dt><span c
 lass="sect2"><a href="#id3791642">addAttachment</a></span></dt><dt><span class="sect2"><a href="#id3791668">deleteAttachment</a></span></dt><dt><span class="sect2"><a href="#id3791676">getAttachmentInfos</a></span></dt><dt><span class="sect2"><a href="#id3791698">getAttachments</a></span></dt></dl></dd><dt><span class="sect1"><a href="#filtering">Task filtering</a></span></dt><dt><span class="sect1"><a href="#presentationElements">Presentation elements</a></span></dt><dt><span class="sect1"><a href="#presentationElements">Presentation elements</a></span></dt></dl></div><div class="sect1" title="Task finite state machine"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="states"></a>Task finite state machine</h2></div></div></div>
+Human tasks can have a number of different states and substates. The state diagram
+for human tasks below shows the different states and the transitions between them.
+Go to <a class="link" href="#taskOperations" title="Chapter 7. Task operations">task Operations</a> to see more details about functions from the graph.
+
+    <div class="figure"><a id="id3791134"></a><p class="title"><b>Figure 6.1. State transitions</b></p><div class="figure-contents"><div><img src="states.png" alt="State transitions" /></div></div></div><br class="figure-break" /></div><div class="sect1" title="Deadline"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="id3791142"></a>Deadline</h2></div></div></div><p>Hise implements a deadline mechanism. Deadlines are defined inside task definitions and contains some <a class="link" href="#escalations">escalation</a> action. There are two types of deadlines:
+
+	  </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p><span class="emphasis"><em>Start deadline</em></span> : Specifies the time until the task must start. It is defined as either the period of time or the point in time until the task must reach state inProgress. The time starts to be measured
+from the time at which the task enters the state Created. If the task does not
+reach state InProgress by the deadline an escalation action or a set of
+escalation actions is performed. Once the task is started, the deadline becomes
+obsolete and are removed.</p></li><li class="listitem"><p><span class="emphasis"><em>Comletion deadline</em></span> : Specifies the due time of the task. It is defined as either the period of time until the task gets due or the point in time when the task gets due. The time starts to be measured from the time at which the task enters the state Created. If the task does not reach one of the final states (Completed, Failed, Error, Exited, Obsolete) by the deadline an escalation action or a set of escalation actions is performed.</p></li></ul></div><p>
+	</p><p>A task may have multiple start deadlines and completion deadlines associated with it. When the task reaches a final state (Completed, Failed, Error, Exited, Obsolete) all deadlines are deleted.
+	</p><p>
+	</p>
+	  Simple example ot the deadline implementation:
+	<p>
+	</p><pre class="programlisting">
+	   
+		&lt;htd:deadlines&gt;
+	    	  
+		    &lt;htd:startDeadline&gt;
+    		        &lt;htd:documentation xml:lang="xsd:language"&gt;
+      			    Text
+    		        &lt;/htd:documentation&gt;
+    		
+			( &lt;htd:for expressionLanguage="anyURI"&gt;
+        		      duration-expression
+			  &lt;/htd:for&gt;
+			| &lt;htd:until expressionLanguage="anyURI"&gt;
+			      deadline-expression
+ 			  &lt;/htd:until&gt;
+			)
+    		
+			&lt;htd:escalation name="NCName"&gt;
+      				...
+			&lt;/htd:escalation&gt;
+  
+		    &lt;/htd:startDeadline&gt;
+  
+		    &lt;htd:completionDeadline&gt;
+			 ...
+		    &lt;/htd:completionDeadline&gt;
+
+	      	&lt;/htd:deadlines&gt;
+	   
+	</pre><p>
+	</p><div class="sect2" title="Escalations"><div class="titlepage"><div><div><h3 class="title"><a id="id3791211"></a>Escalations</h3></div></div></div><p>Escalations is a definition of actions to be executed if a task's status is not reached within a certain time. An escalation must specify exactly one escalation action ( notification or reassignment). In one deadline could be defined many escalations. 
+		</p><pre class="programlisting">
+	  	 
+			&lt;htd:escalation name="NCName"&gt;
+      				...
+			&lt;/htd:escalation&gt;
+		
+		</pre><p>
+The escalatino definition may contain:
+	       </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><a class="link" href="#condition">condition</a></li><li class="listitem"><a class="link" href="#notification">notification</a></li><li class="listitem"><a class="link" href="#notification">localNotification</a></li><li class="listitem"><a class="link" href="#reassignment">reassignment</a></li><li class="listitem"><a class="link" href="#toParts">toParts element</a></li></ul></div><p>	
+	   </p><div class="sect3" title="Condition"><div class="titlepage"><div><div><h4 class="title"><a id="id3791262"></a><p><a id="condition"></a>Condition</p></h4></div></div></div><p>Condition is a element that allows (if evaluates to true) perform escalation. If the condition is not fulfilled during the cause deadline, the escalation is removed along with the deadline. Condition is an optional element.
+
+		</p><pre class="programlisting">
+	  	 
+			&lt;htd:condition expressionLanguage="anyURI"&gt;
+  				boolean-expression
+			&lt;/htd:condition&gt;
+		
+		</pre><p>
+	   </p></div><div class="sect3" title="Notifications"><div class="titlepage"><div><div><h4 class="title"><a id="id3791280"></a><p><a id="notification"></a>Notifications</p></h4></div></div></div><p>Notifications are used to inform people about the status of the task. Notifications are explained in more detail in section “Notifications”. Notification can be either referred to, or defined inline. A notifications imported from a different namespace can be added by a localNotification element. A inlined notification is defined by a notification element. Notifications used in escalations may use the same type of input data as the surrounding task, or different type of data. If the same type of data is used then the input message of the task is passed to the notification implicitly.
+If not, then the toPart elements are used to assign appropriate data to the notification.
+
+		</p><pre class="programlisting">
+	  	 
+			&lt;!-- notification specified by reference --&gt;
+			&lt;htd:localNotification reference="QName"&gt;
+  			  &lt;htd:priority expressionLanguage="anyURI"&gt;
+    			  	integer-expression
+  			  &lt;/htd:priority&gt;
+
+  			  &lt;htd:peopleAssignments&gt;
+    			      &lt;htd:recipients&gt;
+      				...
+   			      &lt;/htd:recipients&gt;
+ 			  &lt;/htd:peopleAssignments&gt;
+			&lt;/htd:localNotification&gt;
+            
+            		...
+            
+			&lt;!-- notification specified inline --&gt;
+			&lt;htd:notification name="NCName"&gt;
+  				...
+			&lt;/htd:notification&gt;
+		
+		</pre><p>
+	   </p></div><div class="sect3" title="ToParts"><div class="titlepage"><div><div><h4 class="title"><a id="id3791314"></a><p><a id="toParts"></a>ToParts</p></h4></div></div></div><p>ToParts is a element used when notifications in escalations use different type of data then input date. Then the toPart elements are used to assign appropriate data to the notification. If any of the toParts fails, the escalation action will not be performed and the execution of the task is not affected.
+
+		</p><pre class="programlisting">
+	  	 
+			&lt;htd:toParts&gt;
+  			    &lt;htd:toPart part="NCName" expressionLanguage="anyURI"&gt;
+    				expression
+  			    &lt;/htd:toPart&gt;
+   				...
+			&lt;/htd:toParts&gt;
+		
+		</pre><p>
+	   </p></div><div class="sect3" title="Reassignments"><div class="titlepage"><div><div><h4 class="title"><a id="id3791334"></a><p><a id="reassignment"></a>Reassignments</p></h4></div></div></div><p>Reassignments are used to replace the potential owners of a task when an escalation is triggered. The reassignment element is used to specify reassignment. If present, the element must specify potential owners. In the case where several reassignment escalations are triggered, the first
+reassignment (lexical order) will be considered for execution. The task is set to state
+Ready after reassignment.
+
+		</p><pre class="programlisting">
+	  	 
+			&lt;htd:reassignment&gt;
+  			    &lt;htd:potentialOwners&gt;
+     				...
+  			    &lt;/htd:potentialOwners&gt;
+			&lt;/htd:reassignment&gt;
+		
+		</pre><p>
+	   </p></div></div></div><div class="sect1" title="Delegation"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="id3791357"></a>Delegation</h2></div></div></div><p>Delegation element is used to specify constraints concerning delegation of the task. Attribute potentialDelegatees defines to whom the task may be delegated. The fallowing values are allowded:
+
+	</p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">
+             anybody - It is allowed to delegate the task to anybody
+          </li><li class="listitem">
+             potentialOwners - It is allowed to delegate the task to potential owners previously selected.
+          </li><li class="listitem">
+             nobody - It is not allowed to delegate the task.
+          </li><li class="listitem">
+             other - It is allowed to delegate the task to other people or group of people.
+          </li></ul></div><p>
+	</p><p>
+	The delegation element is optional. If this element is not present the task is allowed 
+	to be delegated to anybody.
+	</p><p>
+	Simple example:
+	</p><pre class="programlisting">
+	  
+	   &lt;htd:delegation potentialDelegatees="other"&gt;
+ 		&lt;htd:from&gt;
+                    &lt;htd:literal&gt;
+                        &lt;htd:organizationalEntity&gt;
+                            &lt;htd:groups&gt;
+                                &lt;htd:group&gt;group4&lt;/htd:group&gt;
+                            &lt;/htd:groups&gt;
+                            &lt;htd:users&gt;
+                                &lt;htd:user&gt;user2&lt;/htd:user&gt;
+                            &lt;/htd:users&gt;
+                        &lt;/htd:organizationalEntity&gt;
+                    &lt;/htd:literal&gt;
+                &lt;/htd:from&gt;
+            &lt;/htd:delegation&gt;
+	  
+	</pre></div><div class="sect1" title="Comments"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="comments"></a>Comments</h2></div></div></div><p> There are two features connecting with comments. Users can add
+		comments to task and also view all task comments. The second feature
+		is additional, it is not in specyfication - history of the task could
+		be write as comments. This section describes this two features</p><div class="sect2" title="Comments added by user"><div class="titlepage"><div><div><h3 class="title"><a id="id3791415"></a>Comments added by user</h3></div></div></div><p>User can add and view added comments. There is not oporunity to
+			delete comment, thus comments are persistent. Comment consist:</p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>date and time</p></li><li class="listitem"><p>user name</p></li><li class="listitem"><p> comment</p></li></ul></div><p>
+			The
+			<code class="code">comment</code>
+			is assumed to be text.
+		</p><p>
+			The
+			<code class="code"> user name</code>
+			is set on value using during authorization.
+		</p></div><div class="sect2" title="Task history in comments"><div class="titlepage"><div><div><h3 class="title"><a id="id3791448"></a>Task history in comments</h3></div></div></div><p>It is a lile bit more complex. History of task consist
+			information about state change and actual owner change. For every
+			event comment is created. It consists every information like ordinary
+			comment. Content of the comment describe situation that caused the
+			comment creation. Default this feature is off.</p><p>
+			Usually
+			<code class="code"> user name</code>
+			is set on value using during authorization. The first exception is
+			request
+			<code class="code">approve</code>
+			, then users name is set on value of field
+			<code class="code">initiator</code>
+			from request. The second exception is connected with deadLines.
+			Sometimes as a result of cross deadline may be initialize change
+			actual owner or change task state. Then the field
+			<code class="code">attachedBy</code>
+			has value
+			<code class="code">Deadline crossed</code>
+		</p><p> Task history suppor internalization. User can choose language
+			of comments that describe task history. Default language is english.
+			If you want to change it, have to specified language for every task.
+		</p><p>Example of settings active task history comments in polish
+			language....</p><pre class="programlisting">
+			
+			&lt;htd:task name="exampleName"&gt;
+				..........
+				
+			&lt;htd:savingTaskHistory lang="PL"&gt;
+          			&lt;htd:active&gt;true&lt;/htd:active&gt;
+          		&lt;/htd:savingTaskHistory&gt; 
+				
+				..........
+			&lt;/htd:task&gt;
+			
+		</pre><p>and in english</p><pre class="programlisting">
+			
+			&lt;htd:task name="exampleName"&gt;
+				..........
+				
+			&lt;htd:savingTaskHistory&gt;
+          			&lt;htd:active&gt;true&lt;/htd:active&gt;
+          		&lt;/htd:savingTaskHistory&gt; 
+				
+				..........
+			&lt;/htd:task&gt;
+			
+		</pre></div></div><div class="sect1" title="Rendering"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="rendering"></a>Rendering</h2></div></div></div><p>It is assumed that a single task instance can be rendered by different task list clients
+so the task engine does not depend on a single dedicated task list client. Similarly it
+is assumed that one task list client can present tasks from several task engines in
+one homogenous list and can handle the tasks in a consistent manner.
+</p><p>There is not oportunity to set one rendering for every task, each of task should have own definition of rendering </p><p>The definition of rendering must contain type(name), and content. Connten is assumed to be XQuery or string.</p><p>Example of definition rendering:</p><pre class="programlisting">
+			
+			&lt;htd:task name="exampleName"&gt;
+				..........
+				
+		                &lt;htd:rendering type="exampleType"&gt;
+                &lt;expression&gt;
+                    &lt;![CDATA[
+                   
+                        declare namespace htd="http://www.example.org/example"; 
+                                      
+                        &lt;example name="anyname" xmlns:cla="http://www.insurance.example.com/claims"&gt;
+                            &lt;param name="type" value="{htd:getInput("ClaimApprovalRequest")/cla:cust/cla:firstname/text()}"/&gt;
+                        &lt;/example&gt;
+            
+                    
+                    &lt;/expression&gt;
+                &lt;/htd:rendering&gt;
+				..........
+			&lt;/htd:task&gt;
+			
+			</pre><p>There are two functions connected with rendering:</p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>get rendering type</p></li><li class="listitem"><p>get rendering</p></li></ul></div><div class="sect3" title="Get rendering type"><div class="titlepage"><div><div><h4 class="title"><a id="id3791560"></a>Get rendering type</h4></div></div></div>
+Returns list every types of rendering associated with task.
+</div><div class="sect3" title="Get Rendering"><div class="titlepage"><div><div><h4 class="title"><a id="id3791566"></a>Get Rendering</h4></div></div></div>
+Return information abuut rendering with given type. If rendering definition consist XQuery, evaluation is returned.
+</div></div><div class="sect1" title="Attachments"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="attachments"></a>Attachments</h2></div></div></div><p>
+				Arbitrary additional data may be attached to a task. This additional
+				data is referred to as task ad-hoc attachments. An ad-hoc attachment
+				is specified by its name, its content. The
+				<code class="code">name</code>
+				element is used to specify attachment name. Several attachments may
+				have the same name and can then be retrieved as a collection.
+			</p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3>
+				The
+				<code class="code">accesType</code>
+				is assumed to be inline. Thus this proprty MUST contains the string
+				constant
+				<code class="code">inline</code>
+				.
+			</div><p> The attachment can be any valid XML. Moreover the 
+				attachment data is assumed to be of that type and if it is not, the
+				attachment is set on empty.</p><p>
+				The
+				<code class="code">attachedAt</code>
+				element indicates when the attachment is added.
+			</p><p>
+				The
+				<code class="code">attachedBy</code>
+				element indicates who added the attachment. It will be name of user
+				that invoke the opeartion.
+			</p><p> There are four operations to manage attachments:</p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>addAttachment</p></li><li class="listitem"><p>deleteAttachments</p></li><li class="listitem"><p>getAttachemntInfos</p></li><li class="listitem"><p>getAttchments</p></li></ul></div><div class="sect2" title="addAttachment"><div class="titlepage"><div><div><h3 class="title"><a id="id3791642"></a>addAttachment</h3></div></div></div><p>Example of appriopriate message to create attachment</p><pre class="programlisting">
+				
+ 				   	&lt;soapenv:Header /&gt;
+   					&lt;soapenv:Body&gt;
+     					 &lt;xsd:addAttachment&gt;
+        				 &lt;xsd:identifier&gt;54&lt;/xsd:identifier&gt;
+         				 &lt;xsd:name&gt;attachment1&lt;/xsd:name&gt;
+        				 &lt;xsd:accessType&gt;xsd:any&lt;/xsd:accessType&gt;
+         				 &lt;xsd:attachment&gt;&lt;abc&gt;&lt;a&gt;test&lt;/a&gt;&lt;/abc&gt;&lt;/xsd:attachment&gt;
+      					 &lt;/xsd:addAttachment&gt;
+   					&lt;/soapenv:Body&gt;
+				
+			</pre><p>
+					Properties
+					<code class="code">attachedBy</code>
+					and
+					<code class="code">attachedAt</code>
+					are set by system.
+				</p></div><div class="sect2" title="deleteAttachment"><div class="titlepage"><div><div><h3 class="title"><a id="id3791668"></a>deleteAttachment</h3></div></div></div><p> This operation delete all task attachments that has the same
+					name as specified in request.</p></div><div class="sect2" title="getAttachmentInfos"><div class="titlepage"><div><div><h3 class="title"><a id="id3791676"></a>getAttachmentInfos</h3></div></div></div><p> Returns attachment information for all attachments associated
+					with the task:</p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>attached name</p></li><li class="listitem"><p>attached by</p></li><li class="listitem"><p>attached at</p></li><li class="listitem"><p>access type</p></li></ul></div></div><div class="sect2" title="getAttachments"><div class="titlepage"><div><div><h3 class="title"><a id="id3791698"></a>getAttachments</h3></div></div></div><p>Get all attachments of the task with given name. For every
+					attachment is returned attachmentInfo and value of attachement</p></div></div><div class="sect1" title="Task filtering"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="filtering"></a>Task filtering</h2></div></div></div><p>Simple query operations allow to retrieve task data. 
+		There are two similary operations and diffirence beetwen then is only in returned data.
+		User can specify a few features that describe Task he is finding:
+	</p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>generic human role</p></li><li class="listitem"><p>status list</p></li><li class="listitem"><p>createdOn - it specified date of creating task. I must be use with following operators
+				equals ( "= "), not equals
+				( "&lt;&gt; "), less than ( "&lt; "),
+				greater than ( "&gt; "), less
+				than or equals ( "&lt;= "),
+				and greater than or
+				equals ( "&gt;= ") <a class="link" href="#simpleQueryExample">see example</a>
+				</p></li><li class="listitem"><p>where clause - is logically ANDed with the rest condition, it 
+					may only reference one Task column
+					with operators as described above.<a class="link" href="#simpleQueryExample">see example</a></p></li><li class="listitem"><p>maxTask - If maxTasks is specified, then the number of task abstracts returned for this
+					query will not exceed this limit. </p></li></ul></div><p>
+
+	</p><p><a id="simpleQueryExample"></a>
+			</p><pre class="programlisting">
+				&lt;xsd:genericHumanRole&gt;ACTUALOWNER&lt;/xsd:genericHumanRole&gt;
+				&lt;xsd:status&gt;READY&lt;/xsd:status&gt;
+				&lt;xsd:status&gt;OBSOLETE&lt;/xsd:status&gt;        
+				&lt;xsd:createdOnClause&gt;&lt;![CDATA[&lt;&gt;02-08-2010 17:16]]&gt;&lt;/xsd:createdOnClause&gt;
+				&lt;xsd:whereClause&gt;&lt;![CDATA[priority&lt;=5]]&gt;&lt;/xsd:whereClause&gt;
+				 &lt;xsd:maxTasks&gt;30&lt;/xsd:maxTasks&gt;
+			
+			</pre><p>
+	</p><p>
+	</p></div><div class="sect1" title="Presentation elements"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="presentationElements"></a>Presentation elements</h2></div></div></div><p>Information about tasks or notification should be available in a human-readable way to allow users deadlining with their tasks and notofications via a user inerface.
+For example, a user queries for his
+tasks, getting a list of tasks he should work on, displaying a short description of
+each task. Upon selection of one of the tasks, more complete information about the
+task is displayed by the user interface.
+</p><p>Definition of presemttiom consist:</p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p><code class="code">name</code> - some kind of task title </p></li><li class="listitem"><p><code class="code">presentation parameters</code> -  this element specifies parameters used in two others presentation parameters: 
+<code class="code">subject</code> and <code class="code">description</code>. This attribute is optional and see
+<a class="link" href="#presentationExample">example</a> for details</p></li><li class="listitem"><p>
+<code class="code">subject</code> - brief task/notification description 
+</p></li><li class="listitem"><p>
+<code class="code">description</code> - long description of the task
+</p></li></ul></div><p>Example of the definition od presentation</p><a id="presentationExample"></a><pre class="programlisting">
+	
+           &lt;htd:presentationElements&gt;
+                
+               &lt;htd:name xml:lang="en-US"&gt; Approve Claim&lt;/htd:name&gt;
+                
+               &lt;htd:presentationParameters&gt;
+                    
+                   &lt;htd:presentationParameter name="firstname" type="xsd:string"&gt;
+declare namespace cla="http://www.insurance.example.com/claims";
+declare namespace htd="http://www.example.org/WS-HT";
+xs:string(htd:getInput("ClaimApprovalRequest")/cla:cust/cla:firstname)
+&lt;/htd:presentationParameter&gt;
+                    
+                   &lt;htd:presentationParameter name="lastname" type="xsd:string"&gt;
+declare namespace cla="http://www.insurance.example.com/claims";
+declare namespace htd="http://www.example.org/WS-HT";
+xs:string(htd:getInput("ClaimApprovalRequest")/cla:cust/cla:lastname)
+&lt;/htd:presentationParameter&gt;
+                    
+                   &lt;htd:presentationParameter name="euroAmount" type="xsd:double"&gt;
+declare namespace cla="http://www.insurance.example.com/claims";
+declare namespace htd="http://www.example.org/WS-HT";
+xs:double(htd:getInput("ClaimApprovalRequest")/cla:amount)
+&lt;/htd:presentationParameter&gt;
+                        
+               &lt;/htd:presentationParameters&gt;
+                
+&lt;htd:subject xml:lang="en-US"&gt; Approve the insurance claim for PLN {$euroAmount} on behalf of {$firstname} {$lastname}&lt;/htd:subject&gt;
+
+               &lt;htd:description xml:lang="en-US" contentType="text/plain"&gt; Approve this claim following corporate guideline #4711.0815/7 for {$firstname} {$lastname}&lt;/htd:description&gt;
+
+            &lt;/htd:presentationElements&gt;
+
+</pre></div><div class="sect1" title="Presentation elements"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="presentationElements"></a>Presentation elements</h2></div></div></div><p>Information about tasks or notification should be available in a human-readable way to allow users deadlining with their tasks and notofications via a user inerface.
+For example, a user queries for his
+tasks, getting a list of tasks he should work on, displaying a short description of
+each task. Upon selection of one of the tasks, more complete information about the
+task is displayed by the user interface.
+</p><p>Definition of presemttiom consist:</p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p><code class="code">name</code> - some kind of task title </p></li><li class="listitem"><p><code class="code">presentation parameters</code> -  this element specifies parameters used in two others presentation parameters: 
+<code class="code">subject</code> and <code class="code">description</code>. This attribute is optional and see
+<a class="link" href="#presentationExample">example</a> for details</p></li><li class="listitem"><p>
+<code class="code">subject</code> - brief task/notification description 
+</p></li><li class="listitem"><p>
+<code class="code">description</code> - long description of the task
+</p></li></ul></div><p>Example of the definition od presentation</p><a id="presentationExample"></a><pre class="programlisting">
+	
+           &lt;htd:presentationElements&gt;
+                
+               &lt;htd:name xml:lang="en-US"&gt; Approve Claim&lt;/htd:name&gt;
+                
+               &lt;htd:presentationParameters&gt;
+                    
+                   &lt;htd:presentationParameter name="firstname" type="xsd:string"&gt;
+declare namespace cla="http://www.insurance.example.com/claims";
+declare namespace htd="http://www.example.org/WS-HT";
+xs:string(htd:getInput("ClaimApprovalRequest")/cla:cust/cla:firstname)
+&lt;/htd:presentationParameter&gt;
+                    
+                   &lt;htd:presentationParameter name="lastname" type="xsd:string"&gt;
+declare namespace cla="http://www.insurance.example.com/claims";
+declare namespace htd="http://www.example.org/WS-HT";
+xs:string(htd:getInput("ClaimApprovalRequest")/cla:cust/cla:lastname)
+&lt;/htd:presentationParameter&gt;
+                    
+                   &lt;htd:presentationParameter name="euroAmount" type="xsd:double"&gt;
+declare namespace cla="http://www.insurance.example.com/claims";
+declare namespace htd="http://www.example.org/WS-HT";
+xs:double(htd:getInput("ClaimApprovalRequest")/cla:amount)
+&lt;/htd:presentationParameter&gt;
+                        
+               &lt;/htd:presentationParameters&gt;
+                
+&lt;htd:subject xml:lang="en-US"&gt; Approve the insurance claim for PLN {$euroAmount} on behalf of {$firstname} {$lastname}&lt;/htd:subject&gt;
+
+               &lt;htd:description xml:lang="en-US" contentType="text/plain"&gt; Approve this claim following corporate guideline #4711.0815/7 for {$firstname} {$lastname}&lt;/htd:description&gt;
+
+            &lt;/htd:presentationElements&gt;
+
+</pre></div></div><div class="chapter" title="Chapter 7. Task operations"><div class="titlepage"><div><div><h2 class="title"><a id="taskOperations"></a>Chapter 7. Task operations</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="#id3792011">Participant operations</a></span></dt><dt><span class="sect1"><a href="#id3792881">Administrative Operations</a></span></dt><dt><span class="sect1"><a href="#simpleQuery">Simple Query operations</a></span></dt></dl></div><p>A number of applications are involved in the life cycle of a task. These comprise:</p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>The task list client, i.e. a client capable of displaying information about the task under consideration</p></li><li class="listitem"><p>The requesting application, i.e. any partner that has initiated the task</p></li><li class="listitem"><p>The supporting application, i.e. an appl
 ication launched by the task list client
+        to support processing of the task. </p></li></ul></div><p>The task infrastructure provides access to a given task. It is important to
+ understand that what is meant by task list client is the software that presents a UI
+ to one authenticated user, irrespective of whether this UI is rendered by software
+ running on server hardware (such as in a portals environment) or client software
+ (such as a client program running on a users workstation or PC).</p><p>This chapter describe all operations that can be use to interaction with task or to manipulate task.
+ If it wass possible, operations related to the same subject were collected in one sections </p><div class="sect1" title="Participant operations"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="id3792011"></a>Participant operations</h2></div></div></div><p>Operations are executed by end users, i.e. actual or potential owners. The identity of
+the user is implicitly passed when invoking any of the operations listed in the table
+below. The participant operations listed below only apply to tasks unless explicitly
+noted otherwise. The authorization entity indicates people of which roles are
+authorized to perform the operation. Stakeholders of the task are not mentioned
+explicitly. They have the same authorization rights as business administrators.
+  </p><div class="sect1" title="Operations"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="id3792039"></a>Operations</h2></div></div></div><div class="table"><a id="id3792043"></a><p class="title"><b>Table 7.1. Participant operations</b></p><div class="table-contents"><table summary="Participant operations" border="1"><colgroup><col /><col /><col /><col /></colgroup><thead><tr><th>Operation name</th><th>Desription</th><th>Parameters</th><th>Authorization</th></tr></thead><tbody><tr><td>
+						<div class="literallayout"><p><br />
+							addAttachment<br />
+							<a class="link" href="#attachments" title="Attachments">details</a><br />
+						</p></div>
+					</td><td>Add attachment to a task.</td><td>
+						In
+						<div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">task identifier</li><li class="listitem">attachment name</li><li class="listitem">access type</li><li class="listitem">attachment</li></ul></div>
+						Out
+						<div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">void</li></ul></div>
+					</td><td>Actual Owner, Business Administrator</td></tr><tr><td>
+						getAttachmentInfos
+						<a class="link" href="#attachments" title="Attachments">details</a>
+					</td><td>Get attachemnt information for all attachments associated
+						with the task</td><td>
+						In
+						<div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">task identifier</li></ul></div>
+						Out
+						<div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">list of attachment data</li></ul></div>
+					</td><td>Potetnial Owners, Actual Owner, Business Administrator
+					</td></tr><tr><td>
+						getAttachments
+						<a class="link" href="#attachments" title="Attachments">details</a>
+					</td><td>Get all attachments of a task with given name</td><td>
+						In
+						<div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">task identifier</li><li class="listitem">attachment name</li></ul></div>
+						Out
+						<div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">list of attachments</li></ul></div>
+					</td><td>Potetnial Owners, Actual Owner, Business Administrator
+					</td></tr><tr><td>
+						deleteAttachments
+						<a class="link" href="#attachments" title="Attachments">details</a>
+					</td><td>Delete attachments with the specified name from the task(if
+						multiple attachemnets with that name exist , all are deleted)
+					</td><td>
+						In
+						<div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">task identifier</li><li class="listitem">attachment name</li></ul></div>
+						Out
+						<div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">void</li></ul></div>
+					</td><td>Potetnial Owners, Actual Owner, Business Administrator
+					</td></tr><tr><td>
+						addComment
+						<a class="link" href="#comments" title="Comments">details</a>
+					</td><td>Add comment to a task</td><td>
+						In
+						<div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">task identifier</li><li class="listitem">plain text</li></ul></div>
+						Out
+						<div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">void</li></ul></div>
+					</td><td>Potetnial Owners, Actual Owner, Business Administrator
+					</td></tr><tr><td>
+						getComments
+						<a class="link" href="#comments" title="Comments">details</a>
+					</td><td>Get all comments of a task</td><td>
+						In
+						<div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">task indentifier</li></ul></div>
+						Out
+						<div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">list of comments</li></ul></div>
+					</td><td>Potetnial Owners, Actual Owner, Business Administrator
+					</td></tr><tr><td>
+						geRendering
+						<a class="link" href="#rendering" title="Rendering">details</a>
+					</td><td>Returns the rendering specified by the type parameter.
+					</td><td>
+						In
+						<div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">task identifier</li><li class="listitem">rendering type</li></ul></div>
+						Out
+						<div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">any type</li></ul></div>
+					</td><td>any</td></tr><tr><td>
+						getRenderingTypes
+						<a class="link" href="#rendering" title="Rendering">details</a>
+					</td><td>Returns the rendering types available for the task.</td><td>
+						In
+						<div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">task identifier</li></ul></div>
+						Out
+						<div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">list of QNames</li></ul></div>
+					</td><td>name</td></tr><tr><td>claim</td><td>Claim responsibility for a task, i.e. set the task to status
+						Reserved</td><td>
+						In
+						<div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">task identifier</li></ul></div>
+						out
+						<div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">void</li></ul></div>
+					</td><td>Potetnial Owners, Actual Owner, Business Administrator
+					</td></tr><tr><td>start</td><td>Start the execution of the task, i.e. set the task to status
+						InProgress.</td><td>
+						In
+						<div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">task identifier</li></ul></div>
+						Out
+						<div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">void</li></ul></div>
+					</td><td>Actual Owner, Potential Owners(only i state Ready)</td></tr><tr><td>stop</td><td> Cancel/stop the processing of the task. The task returns to
+						the Reserved state.</td><td>
+						In
+						<div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">task identifier</li></ul></div>
+						out
+						<div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">void</li></ul></div>
+					</td><td>Actual Owner, Business Administrators</td></tr><tr><td>release</td><td>Release the task, i.e. set the task back to status Ready.
+					</td><td>
+						In
+						<div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">task identifier</li></ul></div>
+						Out
+						<div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">void</li></ul></div>
+					</td><td>Actual Owner, Business Administrators</td></tr><tr><td>suspend</td><td>Suspend the task</td><td>
+						in
+						<div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">task identifier</li></ul></div>
+						Out
+						<div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">void</li></ul></div>
+					</td><td>Potential Owners(only in state Ready), Actual Owner,
+						Business Administrator</td></tr><tr><td>suspendUntil</td><td>Suspend the task for a given period of time or until a fixed
+						point in time. The caller has to specify either a period of time
+						or a fixed point in time</td><td>
+						in
+						<div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">task identifier</li><li class="listitem">time period</li><li class="listitem">point of time</li></ul></div>
+						Out
+						<div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">void</li></ul></div>
+					</td><td>Potential Owners(only in state Ready), Actual Owner,
+						Business Administrator</td></tr><tr><td>resume</td><td>Resume a suspended task.</td><td>
+						in
+						<div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">task identifier</li></ul></div>
+						Out
+						<div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">void</li></ul></div>
+					</td><td>Potential Owners(only in state Ready), Actual Owner,
+						Business Administrator</td></tr><tr><td>complete</td><td>Execution of the task finished successfully.</td><td>
+						in
+						<div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">task identifier</li><li class="listitem">output data of task</li></ul></div>
+						Out
+						<div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">void</li></ul></div>
+					</td><td>Actual Owner</td></tr><tr><td>remove</td><td>Applies to notification only. Used by notification
+						recipients to remove the notification permanently from their task
+						list client. It will not be returned on any subsequent retrieval
+						operation invoked by the same user</td><td>
+						in
+						<div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">task identifier</li></ul></div>
+						Out
+						<div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">void</li></ul></div>
+					</td><td>Notification Recipient</td></tr><tr><td>fail</td><td>ActualOwner completes the execution of the task raising a
+						fault.</td><td>
+						in
+						<div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">task identifier</li><li class="listitem">fault name</li><li class="listitem">fault data</li></ul></div>
+						Out
+						<div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">void</li></ul></div>
+					</td><td>Actual Owner</td></tr><tr><td>set Priority</td><td>Change the priority of the task. The caller has to specify
+						the integer value of the new priority</td><td>
+						in
+						<div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">task identifier</li><li class="listitem">priority</li></ul></div>
+						Out
+						<div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">void</li></ul></div>
+					</td><td> Actual Owner, Business Administrator</td></tr><tr><td>skip</td><td>Skip the task. Enable only if task is skipable</td><td>
+						in
+						<div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">task identifier</li></ul></div>
+						Out
+						<div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">void</li></ul></div>
+					</td><td> Actual Owner, Business Administrator,Task initiator</td></tr><tr><td>forward</td><td>Forward active task to another person or a set of people
+					</td><td>
+						in
+						<div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">task identifier</li><li class="listitem">organizational entity</li></ul></div>
+						Out
+						<div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">void</li></ul></div>
+					</td><td> Actual Owner, Business Administrator, Potential Owners(only
+						in READY state)</td></tr><tr><td>delegate</td><td>Assign the task to one user and set the task to state
+						Reserved. If the recipient was not a potential owner then this
+						person is added to the set of potential owners.</td><td>
+						in
+						<div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">task identifier</li><li class="listitem">priority</li></ul></div>
+						Out
+						<div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">void</li></ul></div>
+					</td><td> Actual Owner, Business Administrator</td></tr><tr><td>getTaskInfo</td><td>Applies to both tasks and notifications. Returns info about
+						the task.</td><td>
+						in
+						<div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">task identifier</li></ul></div>
+						Out
+						<div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">task</li></ul></div>
+					</td><td> Any</td></tr><tr><td>getTaskDescription</td><td>Applies to both tasks and notifications. Returns the
+						presentation description in the specified mime type.</td><td>
+						in
+						<div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">task identifier</li><li class="listitem">content type – optional, default is text/plain
+							</li></ul></div>
+						Out
+						<div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">String</li></ul></div>
+					</td><td> any</td></tr><tr><td>setOutput</td><td>Set the data for the part of the task's output message.
+					</td><td>
+						in
+						<div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">task identifier</li><li class="listitem">part name (optional for single part messages )y
+							</li><li class="listitem">output data of task</li></ul></div>
+						Out
+						<div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">void</li></ul></div>
+					</td><td>Actual Owner</td></tr><tr><td>deleteOutput</td><td>Deletes the output data of the task.</td><td>
+						in
+						<div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">task identifier</li></ul></div>
+						Out
+						<div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">void</li></ul></div>
+					</td><td>Actual Owner</td></tr><tr><td>setFault</td><td>Set the fault data of the task.</td><td>
+						in
+						<div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">task identifier</li><li class="listitem">fault name</li><li class="listitem">fault data of task</li></ul></div>
+						Out
+						<div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">void</li></ul></div>
+					</td><td>Actual Owner</td></tr><tr><td>delete Fault</td><td>Deletes the fault name and fault data of the task.</td><td>
+						in
+						<div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">task identifier</li></ul></div>
+						Out
+						<div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">void</li></ul></div>
+					</td><td>Actual Owner</td></tr><tr><td>getInput</td><td>Get the data for the part of the task's input message.
+					</td><td>
+						in
+						<div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">task identifier</li><li class="listitem">part name (optional for single part messages)
+							</li></ul></div>
+						Out
+						<div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">any type</li></ul></div>
+					</td><td>Potentail Owners, Actual owner, Business Administrator
+					</td></tr><tr><td>getOutput</td><td>Get the data for the part of the task's output message.e
+					</td><td>
+						in
+						<div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">task identifier</li><li class="listitem">part name (optional for single part messages)
+							</li></ul></div>
+						Out
+						<div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">any type</li></ul></div>
+					</td><td>Business Administrator, Actual Owner</td></tr><tr><td>getFault</td><td>Get fault data of the task</td><td>
+						in
+						<div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">task identifier</li></ul></div>
+						Out
+						<div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">fault name</li><li class="listitem">fault data</li></ul></div>
+					</td><td>sd</td></tr></tbody></table></div></div><br class="table-break" /></div></div><div class="sect1" title="Administrative Operations"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="id3792881"></a>Administrative Operations</h2></div></div></div><p>Collection of operations that can be performed only by business
+	administrators. These operations support task management.</p><div class="table"><a id="id3792888"></a><p class="title"><b>Table 7.2. Administrative Operations</b></p><div class="table-contents"><table summary="Administrative Operations" border="1"><colgroup><col /><col /><col /><col /></colgroup><thead><tr><th>Operation name</th><th>Desription</th><th>Parameters</th><th>Authorization</th></tr></thead><tbody><tr><td><div class="literallayout"><p>activate</p></div></td><td>Activates the task. Lets move from state CREATE to READY 
+			or RESERVED. Type of transition depends on the number of Potential owners. 
+			If there is only one then is set state RESERVED and the Potential owners 
+			becomes Actual owner.
+		</td><td>
+          		In
+				<div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">task identifier</li></ul></div>
+				Out
+				<div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">void</li></ul></div>
+			</td><td>Business Administrator</td></tr><tr><td>nominate</td><td>Nominate organization entity to process the task. When one person is 
+			nominated then task status changes to RESERVE and the person becomes Actual Owner. if 
+			nominated more persons or group of people then task status changes to REDY. Each nominated 
+			organization entity should be added to Potential owners. This operation can be performed 
+			when the task is in the state CREATED 
+		</td><td>
+          		In
+          		<div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">task identifier</li><li class="listitem">organizational entity</li></ul></div>
+          		Out
+          		<div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">void</li></ul></div>
+          	</td><td>Business Administrator</td></tr><tr><td>setGenericHumanRole</td><td>Sets the organization entity on exactly one Generic Human Role. 
+			All other membership to   some Generic Human Role are removed
+		</td><td>
+          		In
+          		<div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">task identifier</li><li class="listitem">generic human role</li><li class="listitem">organizational entity</li></ul></div>
+          		Out
+          		<div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">void</li></ul></div>
+          	</td><td>Business Administrator</td></tr></tbody></table></div></div><br class="table-break" /></div><div class="sect1" title="Simple Query operations"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="simpleQuery"></a>Simple Query operations</h2></div></div></div><p>
+		Simple query operations allow to retrieve task data. To see deatails
+		go to
+		<a class="link" href="#filtering" title="Task filtering">filtering</a>
+	</p><div class="table"><a id="id3793013"></a><p class="title"><b>Table 7.3. Simple Query operations</b></p><div class="table-contents"><table summary="Simple Query operations" border="1"><colgroup><col /><col /><col /><col /></colgroup><thead><tr><th>Operation name</th><th>Desription</th><th>Parameters</th><th>Authorization</th></tr></thead><tbody><tr><td>getMyTaskAbtracts</td><td>Retrieve the task abstracts. This operation is used to
+						obtain the data required to display a task list.</td><td>
+						In
+						<div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">generic human rule</li><li class="listitem">status list</li><li class="listitem">where clause</li><li class="listitem">createdOn clause</li><li class="listitem">maxTasks</li></ul></div>
+						Out
+						<div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">list of tasks abstracts</li></ul></div>
+					</td><td>any</td></tr><tr><td>getMyTasks</td><td>Retrieve the task abstracts. This operation is used to
+						obtain the data required to display a task list.</td><td>
+						In
+						<div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">generic human rule</li><li class="listitem">status list</li><li class="listitem">where clause</li><li class="listitem">createdOn clause</li><li class="listitem">maxTasks</li></ul></div>
+						Out
+						<div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">list of tasks</li></ul></div>
+					</td><td>any</td></tr></tbody></table></div></div><br class="table-break" /></div></div><div class="chapter" title="Chapter 8. Notifications"><div class="titlepage"><div><div><h2 class="title"><a id="id3793103"></a>Chapter 8. Notifications</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="#id3793108"></a></span></dt><dd><dl><dt><span class="sect2"><a href="#id3793141">Notification properties</a></span></dt></dl></dd></dl></div><div class="sect1"><div class="titlepage"></div><p>Notification are used to notify a person or a group of people of diffrent business event or actions on the tasks. Inter alia are used in escalation action to notify a user that  a task is overdue or a task has not been started yet. 
+    </p><p>Notifications are simple human interactions that do not block the progress of the
+caller, that is the caller does not wait for the notification to be completed. The notification appears on the task list of all notification recipients. Notifications may have multiple recipients and business administators. The generic human roles task initiator, task stakeholders, potential
+owners, actual owner and excluded owners play no role. Notifications do not have ad-hoc attachments, comments or deadlines.
+    </p><p>Definition of notifications</p><pre class="programlisting">
+	 
+	&lt;htd:notification name="NCName"&gt;
+
+  	  &lt;htd:interface portType="QName" operation="NCName"/&gt;
+    	  &lt;htd:priority expressionLanguage="anyURI"&gt;
+    	       integer-expression
+    	  &lt;/htd:priority&gt;
+  
+	  &lt;htd:peopleAssignments&gt;
+    	     &lt;htd:recipients&gt;
+      		...
+    	     &lt;/htd:recipients&gt;
+             &lt;htd:businessAdministrators&gt;
+      		...
+    	     &lt;/htd:businessAdministrators&gt;
+  	  &lt;/htd:peopleAssignments&gt;
+  
+	  &lt;htd:presentationElements&gt;
+    		...
+  	  &lt;/htd:presentationElements&gt;
+  
+	  &lt;htd:renderings&gt;
+    		...
+          &lt;/htd:renderings&gt;
+	&lt;/htd:notification&gt;
+	 
+    </pre><div class="sect2" title="Notification properties"><div class="titlepage"><div><div><h3 class="title"><a id="id3793141"></a>Notification properties</h3></div></div></div><p>Notification properties are a subset of task properties and task features. Functionality of these elements is identical to their counterparts defined for the task. If you want to know their definitions read in chapter Task properties and Task features. </p><p>The following attributes and elements are defined for notifications:
+	</p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><a class="link" href="#task_name">name</a></li><li class="listitem"><a class="link" href="#task_priority">priority</a></li><li class="listitem"><a class="link" href="#task_peopleAssignments">peopleAssignments</a></li><li class="listitem"><a class="link" href="#presentationElements" title="Presentation elements">presentationElements</a></li><li class="listitem"><a class="link" href="#rendering" title="Rendering">rendering</a></li></ul></div><p>
+	</p></div></div></div><div class="chapter" title="Chapter 9. Examples"><div class="titlepage"><div><div><h2 class="title"><a id="examples"></a>Chapter 9. Examples</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="#taskInfoExample">Task info example</a></span></dt></dl></div><div class="sect1" title="Task info example"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="taskInfoExample"></a>Task info example</h2></div></div></div><p> This is response for request getTaskInfo</p><pre class="programlisting">
+&lt;soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"&gt;
+   &lt;soap:Body&gt;
+      &lt;getTaskInfoResponse xmlns="http://www.example.org/WS-HT/api/xsd" xmlns:ns2="http://www.example.org/WS-HT" xmlns:ns3="http://www.example.org/WS-HT/api"&gt;
+         &lt;task&gt;
+            &lt;ns3:id&gt;3477&lt;/ns3:id&gt;
+            &lt;ns3:taskType&gt;TASK&lt;/ns3:taskType&gt;
+            &lt;ns3:name xmlns:ns4="http://www.insurance.example.com/claims"&gt;ns4:Task1&lt;/ns3:name&gt;
+            &lt;ns3:status&gt;IN_PROGRESS&lt;/ns3:status&gt;
+            &lt;ns3:priority&gt;0&lt;/ns3:priority&gt;
+            &lt;ns3:taskStakeholders&gt;
+               &lt;ns2:users&gt;
+                  &lt;ns2:user&gt;user3&lt;/ns2:user&gt;
+               &lt;/ns2:users&gt;
+            &lt;/ns3:taskStakeholders&gt;
+            &lt;ns3:potentialOwners&gt;
+               &lt;ns2:users&gt;
+                  &lt;ns2:user&gt;user1&lt;/ns2:user&gt;
+               &lt;/ns2:users&gt;
+            &lt;/ns3:potentialOwners&gt;
+            &lt;ns3:businessAdministrators&gt;
+               &lt;ns2:users&gt;
+                  &lt;ns2:user&gt;user1&lt;/ns2:user&gt;
+                  &lt;ns2:user&gt;user2&lt;/ns2:user&gt;
+               &lt;/ns2:users&gt;
+            &lt;/ns3:businessAdministrators&gt;
+            &lt;ns3:actualOwner&gt;user1&lt;/ns3:actualOwner&gt;
+            &lt;ns3:createdOn&gt;2010-08-05T16:15:09.253+02:00&lt;/ns3:createdOn&gt;
+            &lt;ns3:createdBy&gt;soapui&lt;/ns3:createdBy&gt;
+            &lt;ns3:activationTime&gt;2010-08-05T16:15:09.253+02:00&lt;/ns3:activationTime&gt;
+            &lt;ns3:isSkipable&gt;true&lt;/ns3:isSkipable&gt;
+            &lt;ns3:presentationName&gt;Approve Claim&lt;/ns3:presentationName&gt;
+            &lt;ns3:presentationSubject&gt;Approve the insurance claim for PLN 1234 on behalf of EdmundZorn&lt;/ns3:presentationSubject&gt;
+            &lt;ns3:renderingMethodExists&gt;false&lt;/ns3:renderingMethodExists&gt;
+         &lt;/task&gt;
+      &lt;/getTaskInfoResponse&gt;
+   &lt;/soap:Body&gt;
+&lt;/soap:Envelope&gt;
+
+</pre></div></div></div></body></html>



Mime
View raw message