New UI proposal
0 views
Skip to first unread message
jgilc
Nov 13, 2009, 8:55:15 AM11/13/09
to tempo-dev
Hi, I am interested in using intalio tempo
human-centric capabilities and specifically extend its ui and behavior
to allow a better human interaction (like task delegation, list
presentation and sorting, and changing some task metadata like
priority, etc).
By now we are developing the user ui prototype (it is the easiest
part :D ) with extjs. Something like a mix of the "google gears tasks
example and "adobe air tasks example" (nothing offline, just ui
prototypes). Please see the picture in the file
newtempolookandfeel.png
UI Description:
Content of left pannels:
View Panel: TreeView (Tasks{All,New,Saved,Assigned
(Claimed),Delegated,Completed},Notifications,Processes)
Task Actions Panel: List of Actions
(Task:{Execute,Claim,Revoke,Delegate,Cancel Delegation,Show
Attachments,Set Priority, Annotate, Clear Complete}, Notifications:
{Open,Dismiss}, Processes:{Init} )
Task Grouping Panel: List of Actions (Tasks:{No Group, Due Date,
Priority, State, Creation Date}, Notifications:{No Group,Priority,
Creation Date}, Processes:{Category?}
Double clicking an item in the GridPanel will trigger the default
action for each type of object (Task: Execute, Notification: Open,
Process: Init).
Clicking and item just selects it and updates the Action list Panel
and the grouping list Panel (by the way the entire list of action for
a task will depend upon the state of the task selected, so with
notification (well let's see how to check when it is read)).
Lists will be sortable thanks to extjs GridPanel capabilities.
Delegation action will show up a form ... which will trigger a
delegation process(initially will be very simple, cancel delegation
have to do with task deadline and acceptance by the delegatee).
Line item task with attachments will show some icon and when clicked,
the ui will show in a south panel all attachments for easy download.
Task execution will follow the stablished way through invoking orbeon
forms in a floating dialog, although I would preffer to have closable
tabs.
A New Task is all incoming tasks (role assign).
A Saved Task is a task that we are currently working on but it is not
completed.
A Delegated Task is a task that we delegated and are waiting for
Acceptance or needs supervision at Completion.
An Assigned Task is mainly this, the boss or the process itself
assigned me the task (now it is claimed to me).
A Completed task is well ... Completed. (It could be checked to show
no more in the list, may be a rule could get rid of them from the list
based on a period of time).
Notifications and Processes you already know what are ;) .
The menu bar is intended for stand alone Forms (Somebody ask for
include links in task list in another post) and also for Reports,
(Dash boards, etc... anything that could be embeded in a tab page).
I will be glad if as members of tempo-dev you give me your advice
based on bpm and tempo development experience.
I also want to know if somebody like this ui, and also its extjs front-
end implementation, and are pleased to colaborate in its development.
We have already done a first prototype as the file shows, by the end
of next week we will have the major part of the ui look and feel and
response behaviour (just prototype) offline from tempo, and stand
alone web site app.
Please, if any body want to reply by mail send it here jgilc at desoft
dot lt dot cu , not to gmail account.
Thank you in advance,
Best Regards,
Gil.
PD: A well thought Task Delegation Model
http://khaled.gaaloul.free.fr/?cat=9
http://portal.acm.org/citation.cfm?id=1556176.1556195&coll=&dl=GUIDE&type=series&idx=SERIES10714∂=series&WantType=Proceedings&title=AICPS&CFID=42992554&CFTOKEN=58121140
human-centric capabilities and specifically extend its ui and behavior
to allow a better human interaction (like task delegation, list
presentation and sorting, and changing some task metadata like
priority, etc).
By now we are developing the user ui prototype (it is the easiest
part :D ) with extjs. Something like a mix of the "google gears tasks
example and "adobe air tasks example" (nothing offline, just ui
prototypes). Please see the picture in the file
newtempolookandfeel.png
UI Description:
Content of left pannels:
View Panel: TreeView (Tasks{All,New,Saved,Assigned
(Claimed),Delegated,Completed},Notifications,Processes)
Task Actions Panel: List of Actions
(Task:{Execute,Claim,Revoke,Delegate,Cancel Delegation,Show
Attachments,Set Priority, Annotate, Clear Complete}, Notifications:
{Open,Dismiss}, Processes:{Init} )
Task Grouping Panel: List of Actions (Tasks:{No Group, Due Date,
Priority, State, Creation Date}, Notifications:{No Group,Priority,
Creation Date}, Processes:{Category?}
Double clicking an item in the GridPanel will trigger the default
action for each type of object (Task: Execute, Notification: Open,
Process: Init).
Clicking and item just selects it and updates the Action list Panel
and the grouping list Panel (by the way the entire list of action for
a task will depend upon the state of the task selected, so with
notification (well let's see how to check when it is read)).
Lists will be sortable thanks to extjs GridPanel capabilities.
Delegation action will show up a form ... which will trigger a
delegation process(initially will be very simple, cancel delegation
have to do with task deadline and acceptance by the delegatee).
Line item task with attachments will show some icon and when clicked,
the ui will show in a south panel all attachments for easy download.
Task execution will follow the stablished way through invoking orbeon
forms in a floating dialog, although I would preffer to have closable
tabs.
A New Task is all incoming tasks (role assign).
A Saved Task is a task that we are currently working on but it is not
completed.
A Delegated Task is a task that we delegated and are waiting for
Acceptance or needs supervision at Completion.
An Assigned Task is mainly this, the boss or the process itself
assigned me the task (now it is claimed to me).
A Completed task is well ... Completed. (It could be checked to show
no more in the list, may be a rule could get rid of them from the list
based on a period of time).
Notifications and Processes you already know what are ;) .
The menu bar is intended for stand alone Forms (Somebody ask for
include links in task list in another post) and also for Reports,
(Dash boards, etc... anything that could be embeded in a tab page).
I will be glad if as members of tempo-dev you give me your advice
based on bpm and tempo development experience.
I also want to know if somebody like this ui, and also its extjs front-
end implementation, and are pleased to colaborate in its development.
We have already done a first prototype as the file shows, by the end
of next week we will have the major part of the ui look and feel and
response behaviour (just prototype) offline from tempo, and stand
alone web site app.
Please, if any body want to reply by mail send it here jgilc at desoft
dot lt dot cu , not to gmail account.
Thank you in advance,
Best Regards,
Gil.
PD: A well thought Task Delegation Model
http://khaled.gaaloul.free.fr/?cat=9
http://portal.acm.org/citation.cfm?id=1556176.1556195&coll=&dl=GUIDE&type=series&idx=SERIES10714∂=series&WantType=Proceedings&title=AICPS&CFID=42992554&CFTOKEN=58121140
Nicolas Modrzyk
Nov 14, 2009, 7:47:11 PM11/14/09
to temp...@googlegroups.com
Hello Gil,
I think the screenshot was missing from your previous mail.
In any case, right now, everything you are trying to achieve is supported by the Tempo code.
The only two minor current limitations I can see are:
- grouping is supported at the code level, but not at the Web Service level, so we may have to write a quick method to return the tasks in groups. Since the underlying persistence properly supports group by, this should be a fairly easy new method to implement. (getTasksGroupBy(..))
- Delegation is totally supported, but while the original owner of the task is kept in the Task Lifecycle, I am not sure we are persisting it at all, so it may not be available at the Tempo API level.
That's it. Attachments, Execution, Saving.. and all the other actions can be accessed through the Tempo API.
Let us know if you need some more indications.
Regards,
Nico
I think the screenshot was missing from your previous mail.
In any case, right now, everything you are trying to achieve is supported by the Tempo code.
The only two minor current limitations I can see are:
- grouping is supported at the code level, but not at the Web Service level, so we may have to write a quick method to return the tasks in groups. Since the underlying persistence properly supports group by, this should be a fairly easy new method to implement. (getTasksGroupBy(..))
- Delegation is totally supported, but while the original owner of the task is kept in the Task Lifecycle, I am not sure we are persisting it at all, so it may not be available at the Tempo API level.
That's it. Attachments, Execution, Saving.. and all the other actions can be accessed through the Tempo API.
Let us know if you need some more indications.
Regards,
Nico
jgilc
Nov 16, 2009, 9:46:35 AM11/16/09
to tempo-dev
Hello Nico,
Thank you for your reply, the screenshot was uploaded as a file. I can
see it in the list when we open tempo-dev group. the link is
http://tempo-dev.googlegroups.com/web/newtempolookandfeel.png?gda=GOXviEkAAACZMZ7f_-szcIjLcWeBj1zsy-bC3PgjYD-OIcDARZsB4z4PDflgLlWG3EwRWL8xDyfa4bZDq9fZORtBwZjSHGJkhAioEG5q2hncZWbpWmJ7IQ
If there is a way to upload files along messages reply, please tell me
because this google group ui doesn't show me any field for attachments
along the message body.
I already upload another file "uiproposalrefinement.png" and the link
is
http://tempo-dev.googlegroups.com/web/uiproposalrefinement.png?gda=9VbSo0oAAACZMZ7f_-szcIjLcWeBj1zsJrXAxuMVS0ELL-Bhq2oJkf40dAsQFeqfBs7g86JVYsqMkmga4hT1yfV-LcR9eqfb_e3Wg0GnqfdKOwDqUih1tA&gsc=5DHRWQsAAAA_Fq8QqE6lFbW8s5KkWTm2
We plan to use extjs grid grouping and sorting capabilities, just
client side not server side behaviour.
The idea behind delegation is: When a user choose to delegate a task,
a new task is created for the delegatee asking him to accept or reject
the task. The delegated task will show up now in the Delegated list
until accepted or rejected.
If rejected it will show up again in the Assigned list (claimed) of
the former user. If accepted, it will be just delegated using current
tempo api (?) and will disappear from first user list and show up
claimed in the second user list.
If the delegation is without choice then the delegation process will
pass the task directly to the second user.
There might be more modes like supervised delegation, etc. But we want
to keep it simple at first.
Task Execution is easy for now, because it is the same functionality
through orbeon component. Something like the Entry Form of the liferay
portlet but an IFRAME in a next tab. We already test this an it works
fine, I mean new web page in an IFRAME inside a next to Task Desk Tab.
New tasks are just READY.
Assigned tasks are CLAIMED but the user is not working on it yet.
There are some questions:
How to know when a task is CLAIMED and an user Saved it but it is not
COMPLETED? this is for Saved Tasks entry.
I would like to know if somebody is interested in this ui model and
likes to contribute?
Best Regards,
Gil.
Reply all
Reply to author
Forward
0 new messages