BeginOutboundMapper

The BeginOutboundMapper subflow, which is shown in the following figure, has the following main responsibilities:

• Provide a facility to name the mapper. This is done by means of a label node, where the label name property is promoted so that it can be set at a higher level in the main output mapper flow. The mapper name specified here must exactly match the name of a mapper configured in the configuration database.
• Trap any errors that occur during the mapping process and forward the details directly to the EndOutboundMapper subflow. Mapping errors need to be caught here because, if not, they would be caught by the generic error flow and the transaction would be rolled back.
• Provide the details of each transaction, batch, or both, in the physical transmission being mapped.
• For single transactions, parse the ISF representation of each transaction. Store the transaction ISF and other details in the environment, where they are accessible to the format-specific output mapper component.