You are viewing the documentation for Blueriq 15. Documentation for other versions is available in our documentation directory.
Before you upgrade make sure to read the General Upgrade instructions as well as the Upgrade instructions for previous versions.
The changes are color coded. Orange elements have been changed, Green elements have been added and Red elements have been removed compared to the 15.x release.
Table of contents
DCM 2.0: process outbox table
This only applies to DCM 2.0 installations
The column processid
is added to the process_outbox
table. The upgrade scripts can be found in the dbscripts/features.dcm2/upgrades.15-11 folder of the process-sql-store.
DCM 2.0: Case Creation simplified
We've simplified case creation, the Case Engine is now responsible for making sure the case is in a usable state after with only one message event. See DCM Create Case updates for the changes that need to be performed.
SDK changes
Case creation simplified
com.aquima.interactions.process.impl.TriggeredMessageEvent now implements com.aquima.interactions.process.IMessageEvent:
- TriggeredMessageEvent.getMessageEvent()
+ public String TriggeredMessageEvent.getName()
+ public IValue TriggeredMessageEvent. getField(String name)
+ public Map<String, IValue> getFields()
com.aquima.interactions.process.wrapper.ReadonlyProcessEngine:
- public void closeCase(IUserData userData, GUID caseId)
- public void notifyEvent(IUserData user, String messageEventName, IMessageEvent eventData)
IProcessEngine interface segregation
The IProcessEngine interface has been split to multiple smaller specific interfaces. Currently the DCM 1 IProcessEngine implements those segregated interfaces to ensure backwards compatibility. We do however use the smaller, more specific interfaces, in certain methods or constructors already. An overview of the changed interfaces can be found here.
The changed usages of those more specific interfaces are:
com.aquima.interactions.process.
IAuthorizationAlgorithmEvaluationContext:
- IProcessEngine getProcessEngine();
+ IProcessData getProcessData();
com.aquima.interactions.process.IPriorityAlgorithmEvaluationContext
:
- IProcessEngine getProcessEngine();
+ IProcessData getProcessData();
com.aquima.interactions.process.IProcessEngineManager
:
- IProcessEngine getProcessEngine(String projectName, Version projectVersion, ModuleID moduleId, IProcessExtensionFactory processExtensionFactory, ITraceEngine traceEngine)
- IInitializationReport getReport(String projectName, Version projectVersion, ModuleID projectId, IProcessExtensionFactory processExtensionFactory, ITraceEngine traceEngine)
- boolean resetCache(String moduleName)
- boolean resetCache();
+ IInitializationReport getReport(String projectName, Version projectVersion, ModuleID projectId, IProcessExtensionFactory processExtensionFactory, ITraceEngine traceEngine)
+ void resetCache(ApplicationID id)
+ void resetCache();
com.aquima.interactions.process.IRoutingAlgorithmEvaluationContext
:
- IProcessEngine getProcessEngine();
+ IProcessData getProcessData();
com.aquima.interactions.process.impl.nodes.NodeFactory
constructor changed from: public NodeFactory(ProcessDefinition process, IProcessEngine engine, IExpressionParser parser)
To: public NodeFactory(ProcessDefinition process, IProcessEngineDefinitions processEngineDefinitions, IExpressionParser parser)
com.aquima.interactions.process.impl.IntermediateMessageEventMappingDefinition
constructor changed from: public IntermediateMessageEventMappingDefinition(IProcessEngine processEngine, IIntermediateMessageEventMappingDS datasource)
To: public IntermediateMessageEventMappingDefinition(IProcessEngineDefinitions processEngineDefinitions, IIntermediateMessageEventMappingDS datasource)
Known issues
For an overview of known issue please refer to: Known issues.
1 Comment
Frans Vink
For dcm 2.0 installations, a database update of the process-store-sql and a update of the maintenance-app config-file is also necessary