AnsweredAssumed Answered

Force Process to Persist

Question asked by flavio.donze on Apr 25, 2013
Latest reply on Apr 29, 2013 by trademak

Is there a simple way or workaround to force a process to persist?

As discused in, I have a process which only consists of a few service tasks.
The deadlock problem was solved as I changed the process to run asynchronous.

I have one important use case though, where I need the process to run synchronous (return from the service call after the process is done).

I need the process to be persistent since I'm reading the data during the process (create a XML for history purpose).

Here ( I read:
"you either have to include a (non-functional) waitstate for this e.g. with a timeout on it of 1 second, or wait for the 'async' functionality ( to be implemented."

I tried the following:
<receiveTask id="persist" name="persist"/>
<boundaryEvent id="persistTimer" cancelActivity="true" attachedToRef="persist">
<sequenceFlow id="persistTimerToCommit" sourceRef="persistTimer" targetRef="commit"/>

But the service returns immediately and the process runs in the background.

I also had a working "hack" with the receive task, which was signaled after the process was started.

Is there an option to force the process to persist, without hacking?
Or is there an official workaround?

greets and thanks ahead