topic Re: No process variables if exception is thrown? in Alfresco Archive

No process variables if exception is thrown?

clstokes — Wed, 30 Oct 2013 18:39:26 GMT

If an exception is thrown from a service (or script) task, then none of the process variables added during that process are available after it completes. Is this expected?<?xml version="1.0" encoding="UTF-8" ?><definitions id="definitions" targetNamespace="http://activiti.org/bp

Re: No process variables if exception is thrown?

martin_grofcik — Thu, 31 Oct 2013 06:44:58 GMT

I would expect that 2 script tasks are executed in one transaction. I do not know what you want to achieve. But you can run tasks with async='true'.

http://www.activiti.org/userguide/#bpmnConcurrencyAndTransactions

Re: No process variables if exception is thrown?

clstokes — Fri, 01 Nov 2013 00:46:38 GMT

I want to be able to retrieve process variables from a process if it failed. Do I need to be doing something specifically with transactions?

What's the best way via the HistoryService (or another service) to determine if a process has failed?

Re: No process variables if exception is thrown?

martin_grofcik — Fri, 01 Nov 2013 07:35:17 GMT

What's the best way via the HistoryService (or another service) to determine if a process has failed?

I would say to use error boundary event. Error boundary event allows you to specify what to do after the error. And you can search easily for processes which has failed.
http://www.activiti.org/userguide/#bpmnBoundaryErrorEvent

I want to be able to retrieve process variables from a process if it failed.

HistoryService, RuntimeService?

Re: No process variables if exception is thrown?

clstokes — Sat, 02 Nov 2013 20:08:34 GMT

Is there a particular field or query I can do for failed processes? Or do I need to set my own process variable and query for that?

Re: No process variables if exception is thrown?

trademak — Tue, 05 Nov 2013 13:15:21 GMT

When you have a default service and script task and one of these fail, the transaction is rolled back and the process instance isn't even created and the startProcessInstance call gets back an exception. If you don't want this behavior then you can make a task async and then the transaction is only rolled back to the previous async task. Because then the job mechanism is used, this will be retried 3 times by default and then the job will be in a failed state. Now you can query on these jobs using the JobQuery with the method withException. This will give back all jobs with an exception.

Best regards,