Data Input Mapping
The Data Input Mapping allows you to define the data transformation for Data Input Associations connected to the selected shape with her inner data input.
Context
First of all, you got the context part (See the picture below).
The context is defined by all connected data object and data input.
A diagram like that will give you the following context:
Each element listed in the context can be edited, deleted or you can access to their details information. You can also create new context element.
Mapping
When you have your context filled with the wanted elements, you can now do your data transformation using the mapping field (see the picture below).
In the left column we have the internal data inputs which need to be mapped to one element of your context. Those inputs could be read only when they are provided by an operation bound on a task. If not, you can create new ones and manage them as you please. In the right column you have the mapping expression, each inner data inputs have its own.
Default mapping
When you don’t specify any mappings, the tool does some default mapping depending on the type of the task, the inputs that are linked by data associations and the name of those inputs. The default mapping is equal to null when there are no matched inputs. As soon as user enter a value on one of the mapping, the default mapping on the other inputs doesn’t apply anymore, they will be equal to null by default.
The default mapping value is displayed at the bottom of the row of the value of the mapping or if a Literal Expression was selected, it will appear as placeholder on the value.
How to use this functionality ?
For example, lets say that we want to do a one to one mapping.
-
Navigate in the right column for each inner data inputs and select the "Literal Expression" logic.
-
Then in each literal expression, just write the name of the element from your current context you wanna assign to the inner data input.
-
(Optional) If you want you can use the FEEL language to add some transformation to your data.
-
Then your mapping is done, congratulations !
-
If you want to clear the mapping you can use the button "Clear" at the end. This will clear all the input mapping! If you want to just clear one of them, click on the expression and use the clear functionality of the logic.
Multi instance mapping
When your task, call activity, sub-process has the MI parallel loop or MI sequential loop (cf. Multi instance Loop Details) attribute enabled, you will have an additional section in your data input mapping modal.
The "Collection to iterate" dropdown allows you to choose an element from your context with a data type which is a collection. The iterator name field is used to create a new variable with a given name, with a data type which is an instance of the collection selected. This variable will be available in the auto-completion of every mapping expression.
For example if I have in my context a data input called "Names" which is a collection of string and I create an iterator variable called "Iterator" which gonna have the string type. Then I will be able to use the iterator in my mapping expression.
We still can also use the FEEL language function with it if we want to transform the data.
