Behavior of process when has throw exceptions

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.

nandoztx

Is it correct to drop all process data (historic, runtime data), on exception occurrency, it's agreed with the BPM model?
If a process not have a userTask or boundaryEvent, the last commit have not exists, so when rolled back, the process would never have existed.

   Example:

startEvent->serviceTask1->serviceTask2->endEvent

   If has an exception in serviceTask2 is right wich all data must be rollback?

serviceTask1 has a webservice communication or RPC call.
A exception will throw in serviceTask2, so all data in serviceTask2 and serviceTask1will be rollback.
All business rule in serviceTask1 will not rolled back, cause its not a database transaction, but a external service.
When this process will rollback, any exception will be catched cause all process data has rolled back to last commit in userTask or boundaryEvent or not have a last commit if it's a new process (in this sample, no process historic or register will be persisted);

Thank's in advance.

frederikherema1

What you are describing is correct. When an exception occurs when executing a process, it's rolled back to the initial state it was in, prior to the API-call (or timer firing) that caused the process to "flow". In case of starting a process-instance, there is indeed NO process created when an exception occurs between process-start and the first wait-state or end-event.

So when you're using external non-transactional resources, you'll have to roll your own solution to overcome this. This is a generic (not activiti-specific) problem, communication with external services…