Log in to create and rate content, and to follow, bookmark, and share content with other members. Not a member? Join Now!

AnsweredAssumed Answered

'Key' Task

Question asked by burn83 on Dec 9, 2012
Latest reply on Dec 11, 2012 by burn83

Like • Show 0 Likes0
Comment • 5

Hello!!! i'm a new user of this workflow engine!!

I'm very pleased to join in this community!!

In my use case…i would like to say if in activiti workflow it's possible to set some task in order to trasform them in "key" task..

id est:
start -> task1 -> "task2=Key" -> task3 -> task4=Key -> end.

If, in this process, the user cannot reach task4 and he is stopped in task3,and he must logout for any reasons, at the moment of a new login, he must restart to task2, because he doesn't reach the next "key" task!!

Thanks in advance.

No one else has this question

Outcomes

5 Replies

jbarrez Dec 10, 2012 9:43 AM
Mark Correct
Correct Answer
That would be a pretty complex thing to do. I'm afraid BPMN 2.0 doesn't have such semantics out of the box.
I would start by looking into transactions (BPMN semantics, not technical!) and compensation handlers … but it'll be pretty tricky I think.
Like • Show 0 Likes0
Actions
dognose Dec 10, 2012 11:32 AM
Mark Correct
Correct Answer
I would do the following:

- Mark KeyTasks in a certain way. (By using a certain PriorityScope or sth).
- Mark Non-KeyTasks also.
- Add a SignalCatchingEvent to every Non-KeyTask leading back to the Key-Task. (Call it "AbortSignal_task3" or sth.)
- When user logs out (or session expires?) Send the "AbortSignal" to all active Non-KeyTasks of the current user.
(Here the priority comes into play: You can simple query for all active Tasks with priority 3 for example)

However this will just make the flow return to the keytask. Values the user entered in a prior exectuion will remain visible.
If you need to have those cleared, you can add a service task doing this.
Like • Show 0 Likes0
Actions
burn83 Dec 10, 2012 11:06 PM
Mark Correct
Correct Answer
I would do the following:

- Mark KeyTasks in a certain way. (By using a certain PriorityScope or sth).
- Mark Non-KeyTasks also.
- Add a SignalCatchingEvent to every Non-KeyTask leading back to the Key-Task. (Call it "AbortSignal_task3" or sth.)
- When user logs out (or session expires?) Send the "AbortSignal" to all active Non-KeyTasks of the current user.
(Here the priority comes into play: You can simple query for all active Tasks with priority 3 for example)

However this will just make the flow return to the keytask. Values the user entered in a prior exectuion will remain visible.
If you need to have those cleared, you can add a service task doing this.

sorry…what's "sth"!?
Like • Show 0 Likes0
Actions
dognose Dec 11, 2012 11:49 AM
Mark Correct
Correct Answer
sth. = something. ;)
Like • Show 0 Likes0
Actions
burn83 Dec 11, 2012 9:46 PM
Mark Correct
Correct Answer
.. :) thx!
Like • Show 0 Likes0
Actions

'Key' Task

Outcomes

Related Content

Recommended Content