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.

boundaryEvent: cancelActivity='false'

jcosano

Is working cancelActivity="false"?

Now, I think that I obtain same result with cancelActivity="false" or cancelActivity="true". And always works cancelling activity.

Or maybe I expect a different result, I hope that with cancelActivity="false", userTask associate with boundary, remains active.

pd.
I think that I'm asking so much…

Find more posts tagged with

Comments

tombaeyens

can you provide a unit test that shows the problem?

jcosano

Ok, I will do it!

jcosano

I start from BoundaryTimerEventTest

I put cancelActiviti="false" into process and junit change final assert expecting 2 tasks.

I think that is correct, if cancelActiviti=false I expect that there are 2 task… but now, only there is 1.

BoundaryTimerEventTestCancelFalse.zip

alemser

Hi,

Any news about this feature?

Regards,
Alessandro

jcosano

http://jira.codehaus.org/browse/ACT-284

No, this is not yet implemented.

jelies

This actually works with 5.5 version. Unit tests are working fine!

jbarrez

It works for simple cases, but (probably) not for the complex ones. That's the reason why it's still open, and why it isn't documented yet.