-
1. Re: Persisting Correlation Keys Data in the table after the Process Instance has completed.
swiderski.maciej May 12, 2015 12:46 PM (in response to kiranhk)it has to be removed to allow reuse the same correlation key to cover cases like reopening ticket or work on canceled orders etc.
There was recently added support to include correlation key (flatten representation) into process instance log and will be released with next (6.3.0) version of jBPM.
HTH
-
2. Re: Persisting Correlation Keys Data in the table after the Process Instance has completed.
kiranhk May 13, 2015 1:56 PM (in response to swiderski.maciej)Thanks for the info Maciej.
What if i don't want that to happen, is there a config setting/property which will change this behavior. I don't have a scenario where i would want to reopen with the same Correlation Key.
thanks.
-
3. Re: Persisting Correlation Keys Data in the table after the Process Instance has completed.
swiderski.maciej May 14, 2015 2:12 AM (in response to kiranhk)you would have to replace default JPAPersistenceContextManager and its Factory to override remove method to skip correlation keys removal.
Alternatively you can change the named query GetCorrelationKeysByProcessInstanceId inside jbpmorm.xml to make sure it won't return the correlation key information. If you'd like to follow this approach then you need to make a copy of default JBPMorm.xml file and modify that query, next use that modified orm file inside persistence.xml instead of the default one.
HTH
-
4. Re: Persisting Correlation Keys Data in the table after the Process Instance has completed.
kiranhk May 14, 2015 12:53 PM (in response to swiderski.maciej)Thanks for the info. Appreciate it.