04-12-2018 01:58 PM
Took over some existing models that were used with Activiti 5.22 that made calls similar to this:
execution.getEngineServices().getRuntimeService().setVariables(
execution.getId(),
{'blah1': execution.getVariable('blah1'), 'blah2Key': 'blah2Val'});
getEngineServices is not part of DelegateExecution in Activiti 6, so not sure how to change so the results are identical to what we were doing in 5.22.
I'm guessing the following call would result in variables being set on a different scope:
execution.setVariables({'...': '...'});
04-20-2018 09:44 AM
execution.setVariables({'...': '...'}) should just work!
Also, did you try runtimeService.setVariables( execution.getId(), {});? The runtimeService bean should be available in the script context.
04-20-2018 11:30 AM
Thanks for the response.
I did get it to work by using Context:
org.activiti.engine.impl.context.Context.getProcessEngineConfiguration().getRuntimeService().setVariables(...);
I didn't realize runtimeService was directly available to the script, so removing Context.getProcessEngineConfiguration() works great. Much cleaner solution. Thank you.
Explore our Alfresco products with the links below. Use labels to filter content by product module.