is it possible to suspend and resume process instance in jBPM6? How?

[rsmagdum]

Hi,

is it possible to suspend running process at any time at any node?
and also can we resume it?
if yes, from where we can do it?

[salaboy21]

You can do that from the KIE Workbench at the moment. It is a planned feature for the next release but it is not there yet.

Regards

[rsmagdum]

Hi Mauricio,

1) from where we can suspend/resume process instance in kie-workbench?
I am seeing just abort and signal in actions tab of running process instance.

2) And When next version will be released?

Thanks,
Rahul

[salaboy21]

Hi Rahul,

1) Abort and signal are not suspend and resume.

What are you trying to achieve with suspend and resume? Because maybe it can be implemented in a different way.

2) we are aiming to short release cycles so expect more news in a couple of months

[rsmagdum]

Hi Mauricio,

My use case is, while deploying any new/modified BPMN to jBPM, there should not be any running process instance.

To achieve this

-I can wait for all running processes to finish. But while doing so I need some provision by which engine will complete all running process instances but it will not trigger any new process instance. is this provision available with jBPM?

-Or we can suspend all running process instances, perform deploy of new/modified BPMN, and resume all process instances. So next time whenever that particular process will be triggered it will use new BPMN.

-is there any other better way to achieve my use case?

Thanks,
Rahul

[salaboy21]

I don't really understand your use case. You state: "My use case is, while deploying any new/modified BPMN to jBPM, there should not be any running process instance."

Why is that? Why is that so important?

for the first point you can code that on top of jBPM as a business restriction that you have.. that's not a common thing (or generic enough) to be included in jBPM.

Regarding your second, there is no need for such mechanism in jBPM, because it handle different runtime environments, if you start the new version of the process (which needs to be in a new version of the project) it will start the new process definition and leave the older ones in a different runtime environment until they finish.

Third Point: yes.. the way that it is actually working in the KIE-WB is the way to go IMO.

HTH