AnsweredAssumed Answered

How to ignore old workflow definitions parsing errors

Question asked by dadumancic on Jan 30, 2014
Latest reply on Feb 10, 2014 by dadumancic
Hi,

we have upgraded Alfresco from 4.2.b to 4.2.e. Our Activiti process had to be changed as old process definition had errors with new version of Alfresco. One of them:
<blockcode>
Caused by: org.activiti.engine.ActivitiException: Errors while parsing:
Exclusive Gateway 'exclusivegateway8' has outgoing sequence flow 'flow38ignore' which is the default flow but has a condition too. |
</blockcode>
We have corrected the process and it works fine for new instances.
The problem we have is that any query to history will throw exception, as the Alfresco cannot load old workflow definitions. For example, if user opens 'My completed tasks' it will throw an error.
Can this be ignored/fixed?
I have found that Activiti has a property for enabling/disabling safe BPMN parsing: http://www.activiti.org/userguide/#advanced.safe.bpmn.xml
Is this applicable to Alfresco?

With regards,
Davorin

Outcomes