The XML Import of a Keyboard screen type locks a specific property of the alphanumeric button control elements in the Editor.

• Related Articles

• Under specific circumstances it is possible to assign the same "screen type specific action" to different screen elements in the same screen in the Editor.

  Summary It may be possible to link the same screen specific action to different screen elements if the “screen type specific action” is used as a released property of an element in a symbol and this was added and configured first in the screen. ...

• Button as switch shows invalid state before a variable value is available

  Summary A button element configured as a switch displays an invalid state in the Service Engine before a variable value is available. This behavior has been modified. Description When a screen is opened in the Service Engine, a button element that is ...

• The automatic keyboard may not open in a specific screen type in the runtime.

  Summary The automatic keyboard may not open in the active directory user administration screen when clicking on the domain, username or password control elements in the runtime. DescriptionThe automatic keyboard may not open in the active directory ...

• Inserting a WPF element in a non-standard screen in the editor, may result in the color of screen specific control elements to be displayed incorrectly in the runtime.

  Summary When a WPF element is drawn in a non-standard screen in the runtime, the back color or font color of other screen specific control elements, like a combo-box in the alarm screen, may be incorrect. DescriptionWhen a WPF element is drawn in a ...

• Specific screen parameters may not be considered in the Runtime after XML Export/Import the screens in the Editor.

  Summary When XML export/importing screens in the Editor the parameters tap, double tap and manipulation may not be taken in the Runtime. DescriptionWhen XML export/importing screens in the Editor the parameters tap, double tap and manipulation may ...