Order of mappings not shown visually

[jpav]

In the future, we will likely support mappings where the order of mappings becomes important. Here are a couple of examples of possible scenarios where this may come into play:

1. A target element that needs to have the same value as a previous mapping, but where that previous mapping was a complex combination of multiple transformations that the user didn’t want to have to recreate every time that value is desired. Thus, the user would want either someway to save the first mapping transformation result in a variable (possibly the properties already supported? Our current Eclipse mapper allows for this via what we call variables.), or have some type of “copy” action available that would basically treat a previous mapping as a source for a later mapping.

2. Decision logic is involved in a target mapping that considers the results of previous mappings, again assuming considering just the source in the decision is too difficult due to the complexity of the transformations that created the previous target values.

So the concern is we should consider this likelihood in the UI design to hopefully avoid any jarring change to the user experience in the future when this support is realized.