Legacy platform

Overview of an identifier screen

An identifier screen is a special type of screen that has multiple variants of its User Interface (UI), and each variant corresponds to a unique identifier.

An example for identifier screens is Address Display screens. These screens behave in the same manner but have different address formats based on the locale.

The UI to be displayed is determined by the application at runtime, based on certain data or conditions that return the unique identifier to be used. For example, Identifier Query and Identifier ID. Identifier screens are used when the UI, which includes the widgets shown and their layout, vary significantly but the underlying behavior or APIs called from the screen remain same.

Consider the Customer Pickup screen. The address information is displayed based on the Identifier Query property. For example, if the Identifier Query is Address:PersonInfo.Country, the data is present on Address namespace on PersonInfo element which in turn contains the Country attribute that is used to determine the address format to be displayed. The Identifier Query can be changed while defining the binding or mapping for the screen. However, you must ensure that the data is present in the <namespace>:<element>:<attribute> format. In the same Customer Pickup screen, the information in the Products, Previously Picked, Canceled Products tabs are displayed based on the Identifier ID property, which cannot be changed. For example, the Identifier ID for the Previously Picked screen can be PreviouslyPickedLine.

Note: When you add a new identifier widget, you must use the Identifier Query property. You can use the Identifier ID property as well. However, if you use Identifier ID, it takes precedence over Identifier Query.