Page History
...
The data mapping simulator is integrated in a tool that helps you debugging and providing insight into how a data mapping is executed by actually executing the data mapping editor. It can be used to debug your data mapping, and provides insight into how the runtime handles data mappings, without having to refer to . This makes development and maintenance faster since there is no need to test the data mapping though manually running and clicking through an application and referring to the runtime logging (although this remains possible). The simulator is fully integrated in the data mapping editor.
In fact, the simulator uses the runtime to:
...
Now it is time to run the mapping using the run button in the top of the editor. Four steps will come available after running the test:
# | Description | Example |
---|---|---|
1 | Link instances: shows which instances are mapped and which instances will be created. | Note that since person #1 does not meet the precondition, no instance is created nor mapped. |
2 | Instance management: shows which new instances are actually created. | |
3 | Link values: shows which values will be used in the next step | |
4 | Set values: sets the values. | |
5 | Clear values: shows which values are cleared. | Note that the |
name of Client #5 has been cleared because the value in the source module was unknown |
Expand | ||
---|---|---|
| ||
|
3. View the result of the data mapping
The result of the data mapping is the output: the profile after mapping. After instances have been created during the execution of a mapping, the instances will be shown in the panel on the right. Instances can be selected here to view the values of attributes and relations of this instance. It is also possible to compare this output profile with an expected profile. This would be the unit test of a data mapping (rule). Read more about unit testing a data mapping here.