WorkFlow Element

Workflow tasks can be generated from activity processing when an error is generated by the activity. The Workflow feature must be "turned on" through a system property.

The configuration will generate a workflow task when the activity generates an error and with existence of one of two definitions.

  • Configuration within the <Transaction> element. This is described in more detail below.

  • Configuration on specifically defined errors in ValidateExpressions attached business rule. See ValidateExpressions attached business rule for more detail.

WorkFlow Element: Elements and Attributes

Element

Attribute

Parent Element

Description

<WorkflowTask>

  

<Transaction>

Optional:

This element identifies the workflow task that is generated when a business error is generated from ValidateExpressions attached business rule.

Note: This is a transaction level generation of a single workflow task when one or more business errors are generated by the ValidateExpressions attached business rule. Alternatively, ValidateExpressions attached business rule can generate an individual workflow task for any individual business error in the rule without the configuration of this element in the transaction.

Values:

literal workflow task name
 

CREATEONUSEREXECUTION

<WorkflowTask>

Optional:

The attribute indicates when the Workflow Task is generated. 

Values:

  • No

    • default

    • Workflow Tasks are generated only through batch cycles, Data Intake processes, and the AsFile post insert process.

  • Yes

    • Any execution attempt to process the activity including user-initiated attempts on the OIPA UI can generate Workflow Tasks.

XML Schema

<Transaction>
 ...
    <WorkflowTask CREATEONUSEREXECUTION="[No | Yes]">[workflow task name]</WorkflowTask>
...
</Transaction>

XML Example

<Transaction>
...
    <WorkflowTask>Premium activity errors</WorkflowTask>
...
</Transaction>