Routing Between Mapper Subflows

The PrepareRouting node determines the type of SWIFT message that is being mapped and creates a list of label names for the RouteToNextMapper subflow to call. It also allows the user to configure custom pre and post body mapper subflows to be called when a specific message type is being processed. This is done by creating entries in the value table. The Category column defaults to SWIFT_MT_MAPPERS_IN but can be overridden by the user by adding a CONFIG='<value>' to the PARAM field of the channel table entry. The Key column for the value table entry will be 'PRE_BODY_MAPPER' or 'POST_BODY_MAPPER'. The Value column contains the label name of the subflow that should be run when this message type is processed by the inbound mapper.

If the customer wants a special pre or post body mapper they can prefix the message type to the Key column to identify a different mapper to call. For example, if the customer had a special message flow that they wanted to call for SWIFT 103 messages after the main body mapper was called they could use a Key of '103_ POST_BODY_MAPPER'.

The PrepareRouting node always sets the last label in its list to 'MTToISFMapperRouteBackLabel' so that control will be passed back to the FINToISFCommonMapper flow for cleanup and return to the calling subflow.