Created on 2021-01-19 07:52:11; Last updated on 2022-01-28 05:00:24
The following properties are available :
This file is the definition of the visual mapping. You normally edit it via the mapping tree editor.
This file is the xslt transformation that will be applied on the internal xml representation of your incoming message to transform it into the outgoing message. It is generated from the mapping definition file.
You can only edit this file via the mapping definition file. If you directly want to write an advanced xslt transformation, you have to use an xslt transformation instead of a visual transformation.
Xslt files that will be included in the generated xslt. It allows you to define some custom xslt functions, and use them in the mapping. The uploaded file must contain all of your functions. It must looks like :
<?xml version="1.0" encoding="UTF-8"?>
<xsl:function name="bfn:xml-parse" >
Allows you to use special transformation modes. The available modes are :
Normal : transformation reads content and metadata of the incoming message, and its result will affect content and metadata of the outgoing message.
Metadata only for outgoing message : only the metadata of the outgoing message will be updated. The content of the outgoing message will be the same as the input. This mode can be used in special situations where the transformation must only generate some additional metadata.
Metadata only for incoming message : only the metadata of the incoming message will be used, not its content. This mode can be used in special situations where the transformation only operated on the metadata of the incoming message. A dummy message in will be used instead of the incoming content.
Metadata only : the transformation only operates on the metadata of the incoming message, and can only update metadata of the outgoing message. Content will not be updated by the transform.
Note: If you want to extract some information from the input message and then save the extracted information in a user defined metadata, you must select the correct "Transformation mode" depending on your case.
Below is an example to show what will happen for the output message when the input message is processed by a channel whose "Message In" is of type "XML" and the "Message Out" is of type "Not Defined".
In this case the transformation will extract the status of the message from the input message and save it in a user defined metadata.
Status field from the "Message In" in the transformation is mapped to "MessageStatus" user defined metadata in the "Message Out". Moreover, the "Transformation mode" is "Normal".
Now when the message will be processed by this channel it will be empty, as shown below:
Empty Output Message
To fix this issue, you will need to change the "Transformation mode" to be "Metadata only for outgoing message (does not change content)." to make sure that the output message is not empty.
Now when the message will be processed by this channel it will be generated properly, as shown below: