Case Sensitivity in Mapping Templates

When you need attributes of mixed case, for example "pipe", "PIPE", "PiPe", to be treated as the same value, the Gateway provides the optional caseInsensitive parameter to interpret extracted data as either case insensitive, if set to "true" (default), or case sensitive, if set to "false".

The caseInsensitive attribute determines how string comparisons are handled during mapping operations. It affects the case sensitivity of:

• Attribute name

• Object ID node

• Class ID node

This parameter ensures that mappings can be configured to either ignore letter casing (case-insensitive) or enforce exact casing (case-sensitive) during processing.

Usage Rules

• caseInsensitive="true"

  All relevant string comparisons ignore case differences.

  For example, "Pipe" matches "pipe", "PIPE", "PiPe", and so on.

• By default, the value of caseInsensitive parameter is set to true in the mapping configuration, for example, when upgrading from previous versions, and as it’s optional then when it is missing caseInsensitive is assumed to be "true".

• caseInsensitive="false"

  All string comparisons require exact casing.

  For example, "Pipe" matches only "Pipe", not "pipe".

Example

<ObjectMappings caseInsensitive="false">
<Object>
<Conditions>
<Attribute name="TYPE" pattern="PIPE" />
</Conditions>

<ObjectID value="[TYPE]" />
<ClassID value="[Type]" />
</Object>
</ObjectMappings>

In the above example, mappings will map the ObjectID value from characteristics "TYPE" and classID value from characteristic "Type" of an object following strict casing when matching.

Note:

• Attribute name and value matching will respect exact casing when caseInsensitive="false". Hence, it affects not only <Conditions> statement matching, but also value-setting operations.

  For example, when case sensitivity is enabled, the following statements are not equivalent:

  • <ObjectID value="[EquipmentID]" />

  • <ObjectID value="[EquipmentId]" />