Tasks State Management

[jgilc]

Hello,
Searching in this group, for Task States, I found this answer from
Alex in (http://groups.google.com/group/tempo-dev/browse_thread/thread/
8553aa0cb0241882/5a10873f9198f64d?lnk=gst&q=State#5a10873f9198f64d):
<em>The high-level outcomes of a task are either "completed" or
"failed", and you can break down the outcomes into more specific
states (approved, duplicate, canceled, rejected, etc.). Your forms,
schemas and processes define the business aspects associated with the
task and you can use
multiple choices, e.g. radio buttons, and even more complex
combinatorial logic in your forms to drive the process. </em>

My question is: If the current Tempo API just have READY, CLAIMED,
COMPLETED, OBSOLETE; how can I achieve the above stated idea of
breaking outcomes into more specific states without transforming the
inner workings of Tempo?

Then looking at TMS in tempo confluence (http://www.intalio.org/
confluence/display/TEMPO/TMS) I read that many interfaces of
org.intalio.tempo.workflow.tms.server.TMSRequestProcessor cause task's
status changes. But others that deserves a change don't do anything
like "stop", "suspend/resume", etc. And there is the status "reserved"
and "skiped".
How many hard coded status are there currently? Where can I find more
information on this?
Thank you, Gil.

[Nicolas Modrzyk]

Hi Gil,

The different possible task states are all stored and explained here:

http://github.com/intalio/tempo/blob/master/tms-common/src/main/java/org/intalio/tempo/workflow/task/TaskState.java

As Alex said, the outcome of a task is mostly COMPLETED or FAILED.

The data related to states like approved, canceled, rejected would be contained in the output field of a task.

States found in this page:  (http://www.intalio.org/

confluence/display/TEMPO/TMS)  are specifically related to the Bpel4People specifications and are supported in a different branch of Tempo. (origin/b4p)

Thanks,

Nico

--

You received this message because you are subscribed to the Google Groups "tempo-dev" group.
To post to this group, send email to temp...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/tempo-dev?hl=en.

[jgilc]

Hello Nico,
about this
OBSOLETE: the task was asked to be skipped. TMP is stopped. You need
to act on your user process to react accordingly
Does it means that the current TMP process for the task is finished?
or that it is waiting for some callback? if so What callback?
about Bpel4People, I also want to understand what branch of tempo is
released in the community edition BPMS 6.x?
It would be neccessarily to get task output for each task if we want
to classify task by state at app presentation layer. About it, any one
can get an UI prototype that I uploaded today (19-11-2009)(based on
task clasified by PIPA, PATask and Notifications then subclasified by
states allowing actions according to the current task state) at
http://www.4shared.com/file/155338059/d96df9e0/openinfomanager01_191109.html
(It is not internationalized). It must work in ie 6+ and mozilla
firefox 3.5. It is just a mock up.
It must respond to events like View clicks (tree nodes). Task line
item click (must show actions and groupings) and double click (must
open task in a next tab panel by my desk). And attachment icon and
annotation icon click (must open a south panel showing a list of
attacments or an editor for annotations respectively). The free forms
would mainly respond to the menu item "Parte de ensamble y soldadura"
of Free Forms menu.
I would like to receive feedback about the utility of this layout for
a real colaborative user. What does it lacks?
I have many ideas about human-centric user interaction platform but I
don't know where is the appropiate space to discuss them and receive
feed back.
Thank you for your feedback.
Best Regards,
Gil.

[Nicolas Modrzyk]

On Thu, Nov 19, 2009 at 11:43 PM, jgilc <jgil1...@gmail.com> wrote:

Hello Nico,
about this
OBSOLETE: the task was asked to be skipped. TMP is stopped. You need
to act on your user process to react accordingly
Does it means that the current TMP process for the task is finished?

Yes.
 

or that it is waiting for some callback? if so What callback?

You can implement call back or change the way skip is handle at the task manager level. This is a process so you can edit it at will.
 

about Bpel4People, I also want to understand what branch of tempo is
released in the community edition BPMS 6.x?

The master branch. The tag may differ but the code is exactly the same.
 

It would be neccessarily to get task output for each task if we want
to classify task by state at app presentation layer. About it, any one

You can also add some metadata to the task model.
People went both ways, adding some metadata or storing data in the output/data field of the task.

can get an UI prototype that I uploaded today (19-11-2009)(based on
task clasified by PIPA, PATask and Notifications then subclasified by
states allowing actions according to  the current task state) at
http://www.4shared.com/file/155338059/d96df9e0/openinfomanager01_191109.html
 (It is not internationalized). It must work in ie 6+ and mozilla
firefox 3.5. It is just a mock up.
It must respond to events like View clicks (tree nodes). Task line
item click (must show actions and groupings) and double click (must
open task in a next tab panel by my desk). And attachment icon and
annotation icon click (must open a south panel showing a list of
attacments or an editor for annotations respectively). The free forms
would mainly respond to the menu item "Parte de ensamble y soldadura"
of Free Forms menu.
I would like to receive feedback about the utility of this layout for
a real colaborative user. What does it lacks?

It looks good, even in Spanish. The TO-DO list way of presenting the data is very sweet.
I think the best in this case, is to make this work and usable, so that we/you could have a live version that people could try out, and give comments on.
It's better to do only a few features first, and then iterate with new ones with and along user feedback.

Thank you

Nico