Appendix I: Dynamic Field Mapping Limitations

In some screens, the position of a field may vary. It is therefore necessary to map some fields in such a way, that even if they appear in a different position, they will still be recognized and mapped. This is possible by defining the label near the field (the label must be to the left of the field) and identifying the field according to this label. This mapping type is called "Single Dynamic" as the mapping position changes dynamically according to the leading label. Refer to Map Fields section for further details as to how to map application fields according to their leading label.

Following are some limitations:

There is no specific identifier on the host screen which distinguishes between protected fields and static text which cannot change in runtime. This implies the following limitations:

  • If a field does not have a distinctive label exactly to its left, it cannot be defined as a dynamic field.

  • This feature is disabled for applications that are defined with a right to left language (a new dynamic field mapping can't be created).

  • This feature is disabled, when working with a character based host (VT).

  • Static and Dynamic field mappings should not be set to match the same fields.

Specific use cases

  • When the protected field is blank, any text to the right of the field is matched as the protected field area.


  • When a label and field are separated by a single white space, the protected field won't be matched, unless the "field search area" and "label search area" do not overlap.


  • When arbitrary text in a protected field, matches the label search criteria it is wrongly matched as a field label, and the text to the right of it may be wrongly marked as a protected field.


  • When the text of the protected field starts with white spaces or separator characters, such as a dot or colon this text won't be considered as part of the field.


  • If two white spaces or separator characters appear as a sequence inside a protected field, they will be considered as a field boundary. For example, a row part containing the text "Hello, world" will be identified as a protected field with the text "Hello" only. In addition, when a leading label is defined as a part of a protected field's actual label and the actual label contains two or more separator characters (after the given leading label), the rest of the actual label might be falsely marked as the protected field. Note that these limitations are data-dependent, they may only surface when specific data is sent from the host and therefore may not be identified during desgin time but only in runtime.