Case tasks configuration
In the context of the project, there are settings for a bpmn processes. This configuration is possible in two places:
- A caseTaskBehaviour bean
- ACaseTaskAttributesMappingRegistrar class which can be added to any module and configured. From here configuration falls into caseTaskBehaviour during the system boot.
Configuration types:
attributesMappingByWorkflow - Attributes which are to be passed through the case task to the bpmn process.
Type:Â Map<String, Map<String, String>>
Sample:
<property name="attributesMappingByWorkflow">
   <map>
       <entry key="activiti$perform">
           <map>
               <entry key="icaseTask:performers" value="wfperf:performers"/>
               <entry key="icaseTask:controller" value="wfperf:controller"/>
               <entry key="wfperf:enableControl" value="wfperf:enableControl"/>
               <entry key="wfperf:performerPermission" value="wfperf:performerPermission"/>
               <entry key="wfperf:controllerPermission" value="wfperf:controllerPermission"/>
           </map>
       </entry>
   </map>
</property>
The first level at this configuration is an ID bpmn of the process.
Further is the list of PROPERTY_OF_CASE_TASK->PROPERTY_OF_BPMN_PROCESS pairs.
workflowTransmittedVariables – Attributes which are to be transferred from  one process to another.
This particular functional operates in the conditions when within one transaction the task ends from which one need to send the parameters and the new task starts into which the parameters should go.
Type: Map<String, List<String>>
Sample:
<property name="workflowTransmittedVariables">
   <map>
       <entry key="activiti$case-perform">
           <list>
               <value>optionalPerformers</value>
               <value>excludedPerformers</value>
           </list>
       </entry>
   </map>
</property>
The first level in the given configuration is an ID bpmn of the process in which variables should be transferred.
Next is the list of transmitted attributes.