Screen layout
-
Task Details
Assignee:
Candidates:
Name:
Description:
Process:
Duedate:
Priority:
Comments
John wrote: bla bla bla
Joe replied: bla bla bla
John repied: bla bla bla
Joe replied: Absolutely right!
Becky wrote: blabla
Cindy wrote: Hi
John replied: By
People
Person | Role |
|---|---|
John Doe | Requester |
Joe Smoe | Boss of requester |
Bart | Alternative candidate for this task |
Lisa | Alternative candidate for this task |
Homer | Alternative candidate for this task |
Marge | Alternative candidate for this task |
Add Person
Variables
Variable | Value | Type |
|---|---|---|
Current salary | 2 cts | Money |
Pay raise requested | 25 cts | Money |
Report | click here | Versioned Word Document |
Report | click here | PDF Document |
Add Variable
View Execution Variables
Subtasks
-
Use cases
-
View and optionally update the task details
View the comments and add a new comment
View and optionally update the task variables
View and navigate to the subtasks
View logs on the task
Ad hoc approvals: A versioned document should be a resource/variable type
Human Interaction Management (see below)
-
Notes
-
Depending on the user's permissions, this page is read-only or read-write. Also group tasks should be read only and only have the take (or take & perform) actions available.
View execution variables could navigate to the execution details page that has all the process variables displayed. Or it could use AJAX to add the process execution variables to this page.
-
Human Interaction Management
-
In HIM, the idea is that work is being done ad hoc, in contrast to an automated business process, where the steps and control flow is predefined. Any user can start a 'story', which would translate to a task in our application.
Then, it should be possible to associate a number of people, documents, urls, and other entprise content to the task. Privileges of people to resources also should be controllable. The owner can involve people with this task, define a role for that collaboration and define priviliges.
As tasks get created, completed and delegated by all participants, those activities could end up being displayd as a process graph.
Some important requirements:
It should be easy to link people to a task
It should be easy to link various types of resources to a task
It should be easy to manage privileges of people to resources
-
Comments
-
Tom: Please add your name and comment below like this
Comments