Mappings
For each context message one Mappings element must be present. A Mappings element has this sub element:
Element | Description |
---|---|
Mapping |
A Mapping element describes the source which must be used to fill a placeholder in the template. For the content of the Mapping element, see the example. |
Example:
<Mappings">
<Mapping>
<…>
</Mapping>
<Mapping>
<…>
</Mapping>
< /Mappings>
For each mappings element within a context message Mapping elements can be present. A Mapping element has this attribute:
Attribute | Description |
---|---|
type |
How to process the Source element to fill the Target placeholder:
|
A Template element has these sub elements:
Element | Description |
---|---|
Source |
Depending on the “type” attribute, the source is a field, a domain, a function or a hook.Within Source, you can use these placeholders:
|
Target | The placeholder as used in the Template |
Examples:
<Mapping type="field">
<Source>#table#.#key05#</Source>
<Target>ic_key05</Target>
< /Mapping>
<Mapping type="field">
<Source>#table#.#instance#</Source>
<Target>ic_instancename</Target>
< /Mapping>
<Mapping type="domain">
<Source>tcrefa</Source>
<Target>ic_trackingnumber</Target>
< /Mapping>
<Mapping type="function">
<Source>icm.get.screenid()</Source>
<Target>ic_screenid</Target>
< /Mapping>
<Mapping type="hook">
<Source>return(“ERPLN_” & icm.get.screenid())</Source>
<Target>ic_screenid</Target>
< /Mapping>