Content Population

The Content Population filter is used to insert information into a message. The filter can replace the body of the message with a static body and the values of given fields with static (literal) values or message property values.

If the Body Template File property is supplied, the message body is replaced with the data in the file. Following the replacement, the message is parsed using the Definition File and each field in the message (listed in the Field Mappings field) has its value replaced with the respective value. The values can reference message properties.

A common use of this filter is to create acknowledgment messages containing information from the original message.

If you are parsing the incoming message or the body template, you must have a definition defined.

Configuration Properties

Property	Description
Maximum Concurrency	The maximum level of concurrency for this filter. A setting of `0` (zero) means unlimited. Limiting the level of concurrency limits memory usage. Refer to Maximum Concurrency for details.
Definition	Identifies the message definition describing the layout of the output message. This is only required if you are inserting values into the body of the message. If a body template file is specified, then this definition must match the message structure of the data in that file.
Body Template File	An optional file that replaces the entire message body. Any field replacements occur after the body has been replaced. If the message body is replaced, the existing message body is placed into the temporary message property `$InputMessageBody`. This message property is only available within this filter.
Field Mappings	This property is only available if a definition file has been specified in the Definition configuration property. Fields listed in this mapping have their values replaced by the constant values or message property values specified in the Value column. Message properties are denoted with a `$` prefix in name of the message property; for example, `$MessageType`. To create field mappings: Select the Browse button to display the Field Mappings dialog: In the Field column, use the Browse button to select the desired field path (entering the name of field path directly into the column is not recommended). The Value column holds the actual string to be inserted into the outgoing message: To enter a literal value, enter a string directly into the column. To enter a message property, select it from the drop-down list, or enter it manually. When selecting a message property from the drop-down list, the names of the message properties are displayed without the prefix `$`. However, when manually entering a message property, you must prefix the message property name with `$` to denote the use of a message property. Repeat steps 2 to 3 until you have added all the field mappings you require. Select the OK button to save the field mappings.