You can use a submap to use the same mapping transformation in multiple message maps.
You use submaps to define a set of mapping functions that you can reuse in multiple message maps.
A submap transform references another map. It calls or invokes a map from a separate file, which can be stored in a library, an application, an integration service, or an Integration project.
A submap can contain components of the message body only, such as global elements and global types. A submap does not contain Properties, message headers, or the Local Environment tree. The elements or types that define the input and outputs of a submap must be defined as globals in an XML or DFDL message model. You cannot use user-defined elements as a submap input or output unless it is defined using a global type in an XML or DFDL schema. You cannot use a JSON data element defined from a JSON schema, or REST API swagger document, as a submap input or output.
For more information, see Creating a submap.
You edit a submap transform in the Graphical Data Mapping editor.
The Graphical Data Mapping editor saves submaps as .map files.
For more information, see Graphical Data Mapping editor.
To configure the inputs and the output to a submap transform, you connect one or more inputs, and a single output.
You must have message models for any messages that you want to include in a mapping. You can select the message model from your existing message models in your application, integration service, or library when you create a message map. The mapping facility supports message models that are provided in DFDL schema and XML schema files, REST API swagger 2.0 documents, JSON schema draft 4, or MRM message sets.
If your message model includes wildcards (xsd:any), you can use a Cast function to redefine these data elements to a global type or element from any message schema in your application. For more information, see Casting elements in a message map. You can also define dynamically a wildcard by adding user-defined elements.
For more information, see Transforms (Mapping operations).
A submap can be referenced from other message maps.
When you construct your transformation map, you create a submap to group part of the message transformation. The submap must be in a project visible to the main map that they are called from.
To create a submap, you define a Submap transform between the input object and the output object in your message map. The submap can then be used to enable reuse of common transformations for sections of, or the whole of, the message.
You can also refactor existing transform logic into a submap from a local transform, by using the context menu action.
For more information, see Calling a submap.
You can use a submap to reuse common data transformations.
You can reuse submaps in other solutions, and in other products that support graphical data maps.