Using the Avoka Task History DSC

Scenario

As a form is assigned to multiple users, it is often necessary to keep an audit trail of who has "touched" the form, when, and what their comments where. To complicate matters, a user task, embedded inside of a loop may be performed many times. Each time it gets executed by someone there is new knowledge or experience being gained about that case. This knowledge needs to be shared amongst the users of the workflow so that they can percieve and understand the progression of the case.

Although LC Workflow automatically stores information in the database about each step that is performed, it is often more useful to embed this information directly into the form, in an "audit trail" or "history" table, where anyone who opens the form can see its history.

The Task History DSC

The Task History DSC is able to record the knowledge and experience gained in multiple executions of a task, in a clean, consistent manner. This enables workflow users to view and learn from the task's previous execution history.

To obtain an evaluation copy of the Task History DSC, go to the Avoka Website: http://www.avoka.com and follow the links.
The Task History DSC, once installed, will appear as a new service with two operations in your LiveCycle WorkBench.

The Process

The user-tasks for both Employee and Manager are connected in a loop. If the manager is happy that the issue is resolved s/he ticks a checkbox in the form. At the split this is read and used to either route the case onwards, or back to the Employee, to reapply. After each user task certain fields of the form are read by the Task History step "Record Experience" and used to keep a "running record" of the case.

It is this running record that is useful to keep track of progress, and communicate ideas between people. Such an approach can make a workflow experience more collaborative in nature, as opposed to being strictly regimented. The task History DSC makes maintaining and adding to this continuous record - simpler.

The Form