Mapping is a property of BPMN elements such as user tasks, service tasks and script tasks. It describes how data should be passed between a process and models such as forms, connectors, and scripts in a process. The data can be passed to variables within those models, such as form variables and script variables or other values in the model such as form fields, connector inputs and outputs and decision table inputs and outputs. Mapping this data is split between input mappings and output mappings:
- Input mapping sets how and which data is sent from process variables to another model within the process.
- Output mapping sets how and which data is sent from models within the process back to process variables.
There are five options for setting the Mapping behavior:
Any mapping configured in a process is stored in the Extensions Editor using the ID of the BPMN element. If not sending any variables then the ID of the element will not appear in the mappings section. The following is an example of explicitly mapping variables:
"mappings": {
"Task_1f1wpht": {
"inputs": {
"flavor": {
"type": "variable",
"value": "choice"
},
"price": {
"type": "value",
"value": "${lookUp.price}"
},
"Limit": {
"type": "value",
"value": 200
}
}
}
},
}