nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

Completing Transaction Only After Waiting State Finished

rallen1

Hello,

I was wondering if it is possible to have a transaction complete for a waiting state after the waiting state has finished.

For example, in the user guide regarding transactions:

http://www.activiti.org/userguide/#bpmnConcurrencyAndTransactions

There is a diagram describing the functionality:

[img]http://www.activiti.org/userguide/images/activiti.async.example.no.async.PNG[/img]

Using this example, is it possible for the

2nd TX‍

to exist after the next business day duration of time has occurred and the timer event has fired? A crude illustration of this:

[img]http://i.imgur.com/bXiQ1vG.png[/img]

If such a thing is not possible, is there a way in Activiti to rollback from

2nd TX‍

1st TX‍

?

Thank you for your time and any assistance is greatly appreciated.

Find more posts tagged with

Comments

martin_grofcik

Hi,

can you elaborate more the use case for it please?

Regards
Martin

rallen1

Hey Martin,

Thanks for getting back so quickly.

Although I used the the timer as an example of a waiting state, the use case will work with message catching and signal catching events. From a BPMN point of view, it would be something like:

[img]http://i.imgur.com/k2dnsXF.png?1[/img]

Task1 will task some asynchronous work to be performed by a separate process. The work could theoretically take minutes to days, so the workflow will wait on a message catching event that will be sent by the other process when it is complete.

In a catastrophic fail case where the other process mysteriously fails during its asynchronous work, we would like to be able to have the process send us a generic message and then roll back to right before AssignAsynchronousWork. This way AssignAsynchronousWork can be run again and then wait on the message once more.

In a normal case, when we have successfully received the message, then the transaction is complete.

I realize this could probably be done in the BPMN through something like this:

[img]http://i.imgur.com/PKYDatq.png?1[/img]

But the pattern I am describing would be used so frequently that doing this would pollute the BPMNs. There is also the issue that, in terms of my understanding, the transaction is set at the beginning of waiting stage, so that if Activiti rolls back, it will roll back such that it must receive AsynchronousWorkComplete again in order to progress – unless every task immediately after a message catching event is set to activiti:async="true". I would prefer to avoid that if possible.

This might all be for folly anyways as there appears to be no mechanism to fail or rollback a workflow through the RuntimeService.

Even though what I am asking for might not be possible, I appreciate you taking the time. Thanks.

martin_grofcik

Hi Rallen,

I realize this could probably be done in the BPMN through something like this:

Yes.

pollute the BPMNs

Use call activity or parse handler to add event gateway to async work.

Event-based gateway acts as wait state transaction is finished there.

Regards
Martin