Conditions to a map

Use the Map by Condition feature to define rules that govern how mappings (links) are established between fields in a pipeline.

A condition consists of one or more expressions that can

• Check for the existence of a field in the pipeline
• Check for the value of a field
• Compare a field to another field

At run time, the application runs all conditional mappings and assigns a value to the target field only when the condition is true. Otherwise, the application ignores the mapping. In scenarios where the fields are mandatory and the conditions are not satisfied, you might observe flow service runtime failure issues.

You can map multiple source fields to the same target field if the mappings to the target have conditions. In some scenarios, where you have mapped multiple source fields to a single target field, at most, only one of the conditions you define can be true at run time. If more than one condition to the same target field evaluates to true, then the result is not definite because the order in which the conditions are run is not guaranteed.

You can define conditions for a map using the Condition Editor page. The Condition Editor page can be accessed by selecting the map and clicking the Map by Condition icon on the Pipeline page or by double-clicking the map.

The Condition Editor page function is similar to that of the Expression Editor page. For more information about the Condition Editor screen description, see Expression Editor.