Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

A task defines a step in the process diagram. Tasks can be defined as user tasks or module tasks to execute automated steps in a workflow. Every task has a list of actions to complete the step in a workflow.

For a task you You can configure the following properties for a task:

Name (Not visible on diagram)
Name of the task. Name information are is not visible to users and is used to identify for identifying the task.

Caption
Caption The caption of the task. Captions are shown to to users and can be localized when needed. A caption may contain the data templates expressions to replace data from data model.

Role
Name of role to assign task. Tasks are may share same roles if assign to same users.

Prework
Script to be executed before task assigned to role. Please refer Type
Type of the task. A task can be Normal or Module.

Is Start Point?
Specifies the task if it is the start point of workflow or not.

Is Case Handler?
When you click this option, the task-related form is used in the case.

Instructions
Enter the descriptions for the task. The explanations will appear in the notification/reminder e-mails, under the form title and in the tasks falling on the job lists.

Role
The role to which the task will be sent is selected.

Allow Forwarding?
Click to permit users else to assign.

Is Hidden?
Click to hide the relevant task from users with reading permission. This feature can be used in starting tasks.

Delayed Execution
Check this field to process the task in delayed context. By default, Emakin executes task steps in a synchronized context until the task is assigned to a user or the workflow is completed. If you check this field, the workflow engine temporarily stops execution at the task and commits the current state to the database. The remaining execution is performed in another transaction. In some cases, you may need to use this field to ensure saving the current state and perform the remaining operations in another error-checking context.

Prework
The script which is executed before the task is assigned to the role. Please refer to the Task Prework Script section for more details.

Postwork
Script to be The script which is executed after the task is completed. Please refer refer to the Task Postwork Script section for more details.

Options
List of task options. Task options are provides quick access to following task properties:

If property enabled related icon is highlighted. Task properties are not limited to options icons, please use context menu to access more advanced properties.

Notification

Configures the notification to be send at task when assigned to users. By default this notification is disabled.

First Reminder

After task is assigned, configures the reminder notification if task still is not completed. By default 30 minutes is set.

Repeating Reminder

After task is assigned or first reminder is sent, configures the repeating notification until task is complete. By default this notification is disabled.

Please use this property with caution, sending too much messages degrades the importance of notifications.

Deadline

 

Watchers

...

Condition to Initiate
XPath expression to evaluate task allowed to initiate. XPath expression is evaluated from the active case profile.

Delayed Execution
Check this field to process the task in a delayed context. By default, Emakin executes task steps in a synchronized context until the task is assigned to a user or the workflow is completed. If you check this field, the workflow engine temporarily stops execution at the task and commits the current state to the database. The remaining execution is performed in another transaction. In some cases, you may need to use this field to ensure saving the current state and perform the remaining operations in another error-checking context.

Variables

List of the overridden Pool variables in a task scope. Please refer to the pool page for more information.

Forms

This feature can be used to set the form to default, enabled, hidden or disabled status for each task. The forms feature becomes available after determining an element in the form design part. You can decide section status for every process step.

  • The default state inherits the rules from to form. Example; formatting and conditional rules. 
  • Enabled state permits entering new information or changing the information in the section.
  • Hidden state hides section when related task run.
  • Disabled state shows a related section in the form, but it doesn't permit adding new information or changing existing information in the section.