<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html>
<body link="#355491" alink="#4262a1" vlink="#355491" style="background: #e2e2e2; margin: 0; padding: 20px;">
<div>
<table cellpadding="0" bgcolor="#FFFFFF" border="0" cellspacing="0" style="border: 1px solid #dadada; margin-bottom: 30px; width: 100%; -moz-border-radius: 6px; -webkit-border-radius: 6px;">
<tbody>
<tr>
<td>
<table border="0" cellpadding="0" cellspacing="0" bgcolor="#FFFFFF" style="border: solid 2px #ccc; background: #dadada; width: 100%; -moz-border-radius: 6px; -webkit-border-radius: 6px;">
<tbody>
<tr>
<td bgcolor="#000000" valign="middle" height="58px" style="border-bottom: 1px solid #ccc; padding: 20px; -moz-border-radius-topleft: 3px; -moz-border-radius-topright: 3px; -webkit-border-top-right-radius: 5px; -webkit-border-top-left-radius: 5px;">
<h1 style="color: #333333; font: bold 22px Arial, Helvetica, sans-serif; margin: 0; display: block !important;">
<!-- To have a header image/logo replace the name below with your img tag -->
<!-- Email clients will render the images when the message is read so any image -->
<!-- must be made available on a public server, so that all recipients can load the image. -->
<a href="https://community.jboss.org/index.jspa" style="text-decoration: none; color: #E1E1E1">JBoss Community</a></h1>
</td>
</tr>
<tr>
<td bgcolor="#FFFFFF" style="font: normal 12px Arial, Helvetica, sans-serif; color:#333333; padding: 20px; -moz-border-radius-bottomleft: 4px; -moz-border-radius-bottomright: 4px; -webkit-border-bottom-right-radius: 5px; -webkit-border-bottom-left-radius: 5px;"><h3 style="margin: 10px 0 5px; font-size: 17px; font-weight: normal;">
Human Task Module RoadMap
</h3>
<span style="margin-bottom: 10px;">
modified by <a href="https://community.jboss.org/people/salaboy21">Mauricio Salatino</a> in <i>jBPM</i> - <a href="https://community.jboss.org/docs/DOC-18617">View the full document</a>
</span>
<hr style="margin: 20px 0; border: none; background-color: #dadada; height: 1px;">
<div class="jive-rendered-content"><p>I've being working with the Human Task module since I've started with my first steps in the jBPM community more than 3 years ago. Now it's time to take this component to the next level.</p><p>This wiki page describes the features and improvements that I will be tackling down on the next few months. If you have feedaback about this roadmap please leave a comment here or contact me.</p><p>Most of the changes and new features comes from people that is using jBPM or Drools and the Human Task module to handle Human Interactions, so feel free to drop a your suggestions or features that you would like to see in the short term.</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>I've divided the work into two different sides:</p><ul><li>External Improvements :<ul><li>Starting from the Local Task Service I will be focused in the following topics<ul><li><a class="" href="https://community.jboss.org/docs/DOC-18641">API improvements :Well defined interfaces and factories to interact with the human task functionality. Refactor towards CDI/WELD I will be adding here the proposed changes.</a></li><li>Documentation & Examples: Documentation about the exposed APIs and about the semantic of each method.</li></ul></li></ul><ul><ul><li>Transport improvements (probably using apache camel) and integration with different environments (Application Server, Servlet Containers)</li></ul></ul></li><li>Internal Refactorings<ul><li><a class="" href="https://community.jboss.org/docs/DOC-18641">Review Task, TaskData and I18N structures and queries</a></li><li>Admin Operations and Queries</li><li>Task Events and Queries</li><li>Refactoring for callbacks mechanisms (Task Parent)</li><li>Task Definition Deployment ( (deploy + new instance) instead of add)</li><li>Lifecycle hooks</li><li>Sub Tasks mechanisms </li></ul></li></ul><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>Notice that the External Changes will happen gradually and in parallel with the internal reviews.</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p><div class="toc" style="border: 1px dashed black; padding: 10px;"><ul><li>
<a class="jive-link-anchor-small" href="#Review_Task_TaskData_and_I18N_structures_and_queries">Review Task, TaskData and I18N structures and queries</a>
</li>
<li>
<a class="jive-link-anchor-small" href="#Admin_Operations_and_Queries_Improvements">Admin Operations and Queries Improvements</a>
</li>
<li>
<a class="jive-link-anchor-small" href="#Task_Events_and_Queries">Task Events and Queries</a>
</li>
<li>
<a class="jive-link-anchor-small" href="#Callbacks_Mechanisms_Review">Callbacks Mechanisms Review</a>
</li>
<li>
<a class="jive-link-anchor-small" href="#Task_Definition_Deployment_and_Instantiation_mechanisms">Task Definition Deployment and Instantiation mechanisms</a>
</li>
<li>
<a class="jive-link-anchor-small" href="#LifeCycle_Hooks">LifeCycle Hooks</a>
</li>
<li>
<a class="jive-link-anchor-small" href="#Sub_Tasks_and_Ad_Hoc_Sub_Tasks_Creation">Sub Tasks and Ad Hoc Sub Tasks Creation</a>
</li>
</ul></div></p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>I've added my personal priority, but feel free to leave a comment if you have another topics or if you feel that one of these bullets needs to be prioritized.</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>(10 is Top Priority and 1 Low)</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><h1 id="Review_Task_TaskData_and_I18N_structures_and_queries">Review Task, TaskData and I18N structures and queries</h1><p>A deep process of documentation and review of the core data structures that are being used by the module will be done. The main focus</p><p>of this revision is to improve these structures to be easily accessed and work in the best way possible. The queries associated to these entities</p><p>will be reviewed, extended and documented as necessary. Migration scripts should be provided for migrating the old structures to the new ones in case that new structures</p><p>modifies core fields.</p><p>A detailed documentation about these structures and the generated tables should be provided by this revision.</p><p>A categorization about the provided queries should also be included to identify missing bits.</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>A set of mock task structures and tests for the queries should be provided to guarrantee the expected results.</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p><span style="color: #ff0000;">Update: Based on revisions to the WS-HT specification and the current structures, I've started to belive that including the concept of </span></p><p><span style="color: #ff0000;">TaskDefinition will help us to create a simplier API, a simple deployment and instantiation mechanism and the relationship between the</span></p><p><span style="color: #ff0000;">different pieces of information that are kept. </span></p><p><span style="color: #ff0000;">This will help us to create simple queries on TaskInstances and more straight forward mechanisms. </span></p><p><span style="color: #ff0000;">All the Presentation, Assignment and delegation related fields can be extracted from the task itself and query only when an operation is executed.</span></p><p><span style="color: #ff0000;">For rendering the only information that matters is the one related with each particular task instance. We can avoid the need of querying for all the </span></p><p><span style="color: #ff0000;">other bits of information.</span></p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p><span style="color: #ff0000;"><span>Update 2: </span><a class="jive-link-external-small" href="https://community.jboss.org/docs/DOC-18641" target="_blank">https://community.jboss.org/wiki/HumanTaskAPIAndDataStructuresProposal</a></span></p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>Salaboy Priority: 9</p><h1 id="Admin_Operations_and_Queries_Improvements">Admin Operations and Queries Improvements</h1><p>All the administrative operations will be centralized in one place. Removing, archiving and querying finished tasks, and all the associated data.</p><p>These operations will include:</p><ul><li>Archive Finished Tasks</li><li>Delete Finished Tasks</li><li>Get all the finished tasks by Process instance</li><li>Get all the finished tasks by Process Definition</li><li>Etc.</li></ul><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>Salaboy Priority: 7</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><h1 id="Task_Events_and_Queries">Task Events and Queries</h1><p>Provide a mechanisms to record all the events derived by the Task interactions. </p><p>The WS-HT Specification defines 30 events that will be emited by the Human Task component depending on the different interactions against a human task instance.</p><p>A mechanism to record and query these events will be implemented.</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>Salaboy Priority: 7</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><h1 id="Callbacks_Mechanisms_Review">Callbacks Mechanisms Review</h1><p>The main focus of this review is to extend and abstract the current methods that are being used for registering callabacks from third party components that wants to</p><p>keep track of the tasks' lifecycle.</p><p>Having different strategies for setting up callbacks will decouple the responsability for this module to decide how to contact the interested components. Providing</p><p>an interface to implement these callbacks in an application dependant way will allow us to describe best practices depending on the third party application requirements.</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>Salaboy Priority: 6</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p><span style="color: #ff0000;"><span>Topic included here also: </span><a class="jive-link-external-small" href="https://community.jboss.org/docs/DOC-18641" target="_blank">https://community.jboss.org/wiki/HumanTaskAPIAndDataStructuresProposal</a></span></p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><h1 id="Task_Definition_Deployment_and_Instantiation_mechanisms">Task Definition Deployment and Instantiation mechanisms</h1><p>The WS-HT specification defines to phases to Deploy a task definition and then to create an instance for a specific task definition.</p><p>This feature will allow us to have global tasks definitions that can be instantiated multiple times once we get a definition deployed. This mechanism</p><p>will give us a fine grained control about who creates a task and how the interactions are done. </p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>Salaboy Priority: 4</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p><span style="color: #ff0000;"><span>Topic included here also: </span><a class="jive-link-external-small" href="https://community.jboss.org/docs/DOC-18641" target="_blank">https://community.jboss.org/wiki/HumanTaskAPIAndDataStructuresProposal</a></span></p><h1 id="LifeCycle_Hooks">LifeCycle Hooks</h1><p>A flexible mechanism to define and plug your own task lifecycles will be provided, increasing the flexibility of the Human Task module to fit more simpler and more complex scenarios.</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>Salaboy Priority: 4</p><h1 id="Sub_Tasks_and_Ad_Hoc_Sub_Tasks_Creation">Sub Tasks and Ad Hoc Sub Tasks Creation</h1><p>Having a good and flexible mechanisms for creating sub tasks is a very important feature to have and to show. It will allows us to have new tasks defined on the fly depending on</p><p>a parent User Task defined in our business processes.</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>Salaboy Priority: 6</p></div>
<div style="background-color: #f4f4f4; padding: 10px; margin-top: 20px;">
<p style="margin: 0;">Comment by <a href="https://community.jboss.org/docs/DOC-18617">going to Community</a></p>
<p style="margin: 0;">Create a new document in jBPM at <a href="https://community.jboss.org/choose-container!input.jspa?contentType=102&containerType=14&container=2034">Community</a></p>
</div></td>
</tr>
</tbody>
</table>
</td>
</tr>
</tbody>
</table>
</div>
</body>
</html>