Avoka
Avoka Tools for Adobe LiveCycle
Overview
LiveCycle ES Components
LiveCycle ES Add-ons
Shopping Cart
License Agreement
Contact Avoka

Component: Task History

ComponentView
Append task history information into a repeating XML element. Task ID is used to determine the user who completed the action, and the route chosen. The repeat element must be a repeating element inside a form or XML variable. Specify a relative element or attribute name under the repeat element.


Operations

Icon Name About Link
NoIcon

Set the Task History

Set values of a task history.

Why use it
  • You wish to generate Audit Log for each step of Human Centric Process. This component will record time stamp, user details and a custom note for each step that gets completed.
  • You may need a form processing Audit Log within the form itself for record keeping or archival purpose.
Properties




Input Parameters

Task History Settings

Inputs - The task history settings.

Task ID - In the situation where a history item needs to output information about the user who completed the task; this input parameter cannot be blank. Such is the case when a History Item a typed: Login (the login of the user who completed a task), 'First Last' (first & last name of the user who completed a task), 'Last First' "Last', 'First' or 'Route Chosen'.

Repeat Element * - A repeat element variable expression is intended to point to an element which is to be repeatedly appended to, each time a Task History task gets executed. This means that this XPath expression must point to an element inside (not the root node) of an XML variable. For example an XML-typed variable called 'xmlEl' might have a Repeat Element Expression of '/process_data/xmlEl/rootName/repeatingElement'. Each time this task gets executed another instance of 'repeatingElement' gets added under 'rootName'.

History Items * - This parameter encapsulates a list of history items, each of which is to be added underneath one instance of the repeating element. \\ \\ That is, each time this task gets executed every sub-element in the History Items list gets added under 'repeatingElement' in our example. For instance a history item with sub-element name 'UserName' will be added under 'repeatingElement' in our XML tree. \\ \\ Each history item has a type assigned to it, which can either be a date/timestamp, a user's name that completed a user task, or an XPath type. If the type is XPath then the XPath expression must be supplied as well.

LCES JNDI Datasource - This component uses the LCES datasource to lookup the most recent UserTask. If left blank, the default (java:/IDP_DS) is used.



 

DOWNLOADS
0
LiveCycle ES Components Installer
File size: 28.4 MB

LiveCycle ES Components only
File size: 18.6 MB

Ver: 8.0.20090422

0

DOCUMENTATION
0
Business Process Techniques and Patterns
0
LiveCycle ES Components
0
Release Notes
0