This template is made up of a subflow file as shown in the following figure. It is merely a starter file
for use as a container for all your inbound mappers. The template demonstrates the inclusion of the two
inbound mapper templates. The data source properties of the mappers are promoted. To use the template, copy
the file into your implementation project and rename it to InboundMapperContainer.subflow. If possible,
include it in the same broker schema as the mappers that it will contain. The container provides an easy way
for you to group all your inbound mappers into a single flow for inclusion in your physical transmission
wrapper flows. Figure 1. InboundMapperContainer.subflow
