... Please view this article for a scenario where _Task History_ is demonstrated: [Creating an Audit Trail in a Form].
|
|
| |
h3. Component: com.avoka.livecycle.taskHistory 1.0
|
...
h2. TaskHistory Service
Task History: 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.
|
|
| h3. Operation: taskHistory |
| h3. Operation Title: Set the Task History (taskHistory) |
| Set the Task History: Set values of a task history. |
| || Input Parameter || Type || Description ||
Editor || |
| Task ID | java.lang.String | 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 | java.lang.String | 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 | List<HistoryItem> | 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.| | |
| | |
|
|
h5.
{panel:borderStyle=solid} |
... For how to configure license information for this component service - Task History, please click on the following link:
[Avoka LiveCycle ES Component License Configuration]
Please send us any questions or comments on this documentation regarding Task History by clicking on the following link:
[Feedback|mailto:docfeedback@avoka.com?subject=DSC Documentation Feedback on Service: Task History]
{panel}
h3. Licence Configuration:
|| Parameter || Type || Description ||
| License Key | java.lang.String | The license key provided to you when you purchased a production license for this Solution Component. If blank this Solution Component will assume evaluation mode and allow 100 invocations or 6 hours up-time. |
| License Organisation | java.lang.String | The organization name you provided to Avoka for which you are licensing this Solution Component. | |
Task History DSC
