Task Management

When a workflow requires a user to be involved, that interaction is often called a task or assignment. Assignment Management is critical to process optimization both from a user perspective (letting users know what they need to do) as well as a management and oversight perspective (knowing where bottlenecks are, where time is spent).

‘Decisions’ includes a comprehensive Assignment Management system that manages assignments not only to users/groups but also assignments to ‘other systems’ (where we are expecting another system to respond or to produce some data).

Task Lists

Task Lists

Users can be involved in the process with tasks assigned for them to work on. These tasks can be communicated actively (like through email), can be listed on the ‘Decisions’ web or mobile user app, and can be embedded in external portals (like SharePoint) or custom applications using the API.

The way the tasks are presented is totally customizable (what data, sublists, etc.) using the Report Designer in the ‘Decisions’ Studio.

On Assigning …

On Assigning …

Tasks can be assigned to a user, to a group (like ‘Coding Supervisors’), or contextually to a role in the system (like the manager for the finance department or the head nurse on the 3 East Wing).

Tasks can be re-assigned either on a task by task basis or can be delegated to other individuals who have the right to ‘act as’ a person. Because of this, there is no need to adjust the process when a certain person calls in sick or goes on vacation.

Response by Form, Email or ________

Response by Form, Email or ________

While tasks can be worked directly in the forms produced by the graphical form designer or using any other web technology, they can also be configured to be managed with a direct email response. A user gets an email, hits reply and provides an answer, or clicks a link right in the email. Emails sent back to the system will complete the workflow interaction.

Guest Users

Users without credentials in the system can also be assigned tasks to interact with. While they cannot log in, they can be informed of their task via email or other mechanisms and would be allowed to interact with the system using both forms and email responses.

Deadlines, SLA’s and Escalations

Tasks can set expectations when they will be completed. Multiple levels (like warn, escalate, expire) can be set on any task. In addition to recording if the task was not completed when it was expected to be, functionality can be triggered to do things like notify a user or even re-assign a task.

These task level SLA’s (how long payroll has to set up new employee) help support overall workflow SLA’s (how long should employee onboarding take).