Configuration
On this page you can find more information about the configuration of the tasks feature in the Ometa Business Connector Framework. This article describes the following subjects:
Configuring Tasks
This section will show you how to configure tasks. We configure these tasks on a master data level. We can use these task definitions on lifecycle states.
The configuration window of tasks can be opened by clicking on the Tasks button in the ribbon of the Case Management window.
There are two tabs in this window. The first one, 'Task Definitions', is used to create tasks. The next one, 'Task Templates', is used to create templates.
Task Definitions
The task definitions part of the window looks like this:
A task definition contains the configuration of a task. The following fields are configured on a task definition:
| Field | Description | |
|---|---|---|
| Name | Contains the name of the task definition. | |
| Description | Contains the description of the task. This explains what should be done by the assignee. | |
| Owner | Indicates who the owner of the task is. In most cases a team leader. | |
| Assigned To | Indicates who the assignees of the task are. These are the users or roles responsible for executing the task. | |
| Expected Duration | Indicates how long a task should take. | |
| Type | Contains the type of the task (Human or System). | |
| End Actions | These are actions or methods that should run when the task is closed successfully. | |
| Enable Creation Mailing | Indicates whether a Mail should be sent to notify the assignee when the task is created or reassigned. | |
| Send Completion Mail | Indicates whether a Mail should be sent when the task is completed. | |
| Mail Method Settings | Contains the settings of the mail method. The employees / roles assigned to the role will be dynamically set in the 'To' context field. If one or more email addresses are set here they will also receive the mail by default, case properties can be used. |
There are two types of task definitions. 'System' and 'Human'.
System Task Definitions
A system task definition is a task which runs automatically, without human interaction. A system task definition has the following extra configuration field:
| Field | Description |
|---|---|
| Method Settings | Contains the settings of the method that this task should run. |
Human Task Definitions
A human task definition is a task which needs human interaction in order to run successfully. A human task definition has the following extra configuration fields:
| Field | Description |
|---|---|
| Url | Contains the URL where the assignee can find more information related to the task. |
End Actions
End Actions are methods that need to run after a task is closed. These actions will only be triggered when the task is closed successfully. To add an end action, you just need to click on the add-button near the end actions label. Select the object, profile and method in the drop down and the end action is configured.
Task Templates
A task template is used for creating a flow of task definitions. This is useful for when a task should wait on the completion of another task.
You can drag a task definition from the toolbox to the canvas of the template. You are able to connect the task definitions together to create a sequence or flow. In the image above, the Create Employee in AD task will not be generated until the Approve Employee task is closed succesfully.