Workflow Task Generation
Workflow Tasks may be generated by the User manually or automatically from activity events:
- A single Workflow Task when a policy activity generates one or more business errors (errors configured from ValidateExpressions rule).
- A single Workflow Task for a specific business error generated from a policy activity (errors configured from ValidateExpressions rule).
- A single Workflow Task for a specific activity requirement.
- A Workflow Task may be generate when a Policy or Policy Client requirement is generated from a policy activity.
- A Workflow Task may be manually added by a User to a Policy or Client.
- A Workflow Task may be generated as a Policy or Policy Client requirement is manually added by a User.
Workflow Task Generation Types
Automated Types
The Workflow Tasks generated from activity events (business errors and requirements) are defined with an automatic generation method. These tasks are created during cycle, Data Intake (DI) and AsFile processing. Once a Workflow Task is generated from an event within the activity, that same task will not be duplicated upon subsequent activity processing attempts either initiated by a User or cycle. When a Workflow Task is generated by an activity due to a business error, it is associated to the activity. When a Workflow Task is generated by a Requirement, it is associated to the Requirement.
Manual Types
Aside from Workflow Tasks generated from activity processing, Users may add Workflow Tasks to Policies and Clients. These tasks are defined with a manual generation method. This Workflow Task must then be manually handled throughout its life cycle. A manually added Workflow Task is associated to the Policy or Client dependent on the context where manual addition took place. Typical use of this Workflow Task type may be to pass responsibility for fulfillment of a requested policy or client change.