This content has been marked as final. Show 5 replies
For Scenario 1:
The process will be terminated because when you catch the TaskCreated event, it will execute all the operation in sequence within the same branch. It doesn't create a separate branch when you draw a route from the TaskCreated event to your script operation.
My suggestion is to create a separate process an use the "Start Point" option when you add the TaskCreated event. This way you'll ensure that you have a separate branch when you catch the event and won't interrupt the main process.
I'm still looking at scenario 2. I'll come back to it later when I have a few minutes.
Now for Scenario 2:
I think you were on the right track with adding a filter. I implemented your logic and I'm getting the same results as you, where all the tasks are being forwarded.
The reason is that for every instance of that task (Task B ), it creates an event listener that listens for an event of type TaskForward. So all tasks instances are basically listening at that point. When you forward you item a TaskForward event is sent and all tasks are catching it. That's why you need to add a filer on the event catcher to make sure you only forward the right one.
What I did is added a filter where I make sure only the items from a particular step and from a particular process are being forwarded. My filter has the two following elements:
/MapContent/ProcessInstanceID = /process_data/@id
/MapContent/StepName = "Name of user operation"
That filtered the task that I forwarded properly.
I hope this helps.
Jasmin - Thanks so much for the quick reply. I'll give them a try and see if I can get it to work.
I've been playing with events lately and was trying to
"nut out" the semantics of Events being attached to tasks. For an explanation of why you are experiencing Scenario 1 have a look at slide 19 of the BPMN tutorial (http://www.bpmn.org/Documents/OMG%20BPMN%20Tutorial.pdf).
Hope that helps.
I'm trying to generate a Deadline when a Task is Claimed form a Group Queue.
I've got a TaskClaimed event listener that catches the claim event from the group queue, but I'm stumped on how to then set the Deadline Time for the task when the user has claimed it.
Girish very kindly send me a process that pokes the Deadline Date directly into the ES MySQL table - which does update the Deadline date as show for the task - however A) The Deadline never fires and B) I know poking data into the ES tabels is bad practice.
I've found a 'TaskDeadlineTimer' event that looks like it should do the job but can't figure out how to set it up to set the Deadline for thee specific Process / Task that has been claimed.
Does any one have an example of configuring the 'TaskDeadlineTimer' ?