-
1. Re: When is the process state saved
salaboy21 Oct 19, 2011 10:31 AM (in response to whabelitz)Hi Whabelitz,
A safe point is basically a point where is safe to store the process status. You can think about safe points as every time that the process engine is delegating an activity to an external entity. This external entities can be Users or Systems (asynchronous systems). So, every time a safe point is hit (User task or asynchronous call to an external system) the engine can store the current status, and that status can be recovered later.
Cheers
-
2. Re: When is the process state saved
whabelitz Oct 19, 2011 10:47 AM (in response to salaboy21)So asynchronous work items and user tasks are the only options for a safe point? What is with waiting for signal or timers? And when is the status SUSPENDED set for a process?
-
3. Re: When is the process state saved
salaboy21 Oct 19, 2011 11:04 AM (in response to whabelitz)1 of 1 people found this helpfulWaiting for signal and timers are the same situation.. you delegate to an external entity the execution thread, that means that the process can persist the current status until the timers due or the external events comes.
SUSPENDED is not related with that at all.
Cheers
-
4. Re: When is the process state saved
whabelitz Oct 19, 2011 11:28 AM (in response to salaboy21)Ok. Now I know when a process is at a safe point. But when is the process status set to SUSPENDED?
-
5. Re: When is the process state saved
salaboy21 Oct 19, 2011 11:32 AM (in response to whabelitz)I don't have the code infront of me right now, but that suspended means, that the business process instance was suspended at business level. I'm don't remember if there is an API to change that status now..
-
6. Re: When is the process state saved
pmancham Jan 13, 2012 7:32 PM (in response to salaboy21)I created a workitem to call a web-service. I added the workitem to a workflow and I would like the process state saved immediately after the work item is executed. (So, that if I had to load the workflow after a server crash, the workflow will start from a point where it does not have to make same web-service call again - if it already called that webserivce before server crash)
What should I have in my WorkItemHandler.executeWorkItem() method in order to achieve this?