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.

Skip a call activity

himanshu_mps

Hi,

I have a workflow in which I have multiple subprocesses (using call activity). When a particular subprocess (call activity) is executing, the user should be able to cancel/skip that call activity and should be able to execute the next subprocess in order. Is there any way this can be acheived ?

Thanks,
Himanshu

Find more posts tagged with

Comments

frederikherema1

Add a catching boundary-event to the call-activity/subprocess, a message-boundary event for example - with cancelActivity="false". Make the outgoing flow go to the next call-activity… Make your UI send a message to the execution to "cancel" the execution of the ongoing call-activity. That should work

himanshu_mps

Hi,

I am able to attach the message boundary event. But I don't see any method in the runtime service to actually send a cancel message to the particular process. Could you please provide a code snippet so that it is clear ?

Also, shouldn't be cancelActivity set to "true" in this case ?

frederikherema1

Yes, it should indeed be set to "true", the value of the cancelActivity attribute.

Messaging an executions can be done using the runtimeService:

<br> /**<br>&nbsp;&nbsp; * Notifies the process engine that a message event with name 'messageName'<br>&nbsp;&nbsp; * has been received and has been correlated to an execution with id<br>&nbsp;&nbsp; * 'executionId'.<br>&nbsp;&nbsp; * <br>&nbsp;&nbsp; * The waiting execution is notified synchronously.<br>&nbsp;&nbsp; * <br>&nbsp;&nbsp; * @param messageName<br>&nbsp;&nbsp; *&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the name of the message event<br>&nbsp;&nbsp; * @param executionId<br>&nbsp;&nbsp; *&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the id of the execution to deliver the message to<br>&nbsp;&nbsp; * @throws ActivitiObjectNotFoundException<br>&nbsp;&nbsp; *&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; if no such execution exists.<br>&nbsp;&nbsp; * @throws ActivitiException<br>&nbsp;&nbsp; *&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; if the execution has not subscribed to the signal<br>&nbsp;&nbsp; */<br>&nbsp; void messageEventReceived(String messageName, String executionId);<br>

The right execution to message can be found using an ExecutionQuery, filtering by processInstanceId and message-event subscription.