Chronologic Event List entry may be inaccurate when changing a user full name in the Runtime.

• Related Articles

• It may happen that the authorization signature text is not logged in the chronologic event list in the Runtime.

  Summary The Signature text may not be logged in the chronologic event list in the Runtime if the property "signature text editable" is disabled in the Editor. DescriptionThe Signature text may not be logged in the chronologic event list in the ...

• The audit trail entry in the Chronologic Event List for changing a recipe value contains the translated text rather than the keyword.

  Summary If the project is configured to use the variable identification for display in the runtime, and a value in a recipe of the Recipe Group Manager is changed, the Chronologic Event List contains the translated text of the identification instead ...

• Alarm Message and Chronologic Event lists visibility may not work correctly in the Runtime.

  Summary Alarm Message and Chronologic Event lists may be visible when the value of the variable linked to the visibility property is set to hide before opening the respective screens in the Runtime. DescriptionAlarm Message and Chronologic Event ...

• Under specific circumstances the 64 Bit runtime produces an unhandled exception after opening a chronologic event list screen.

  Summary The chronologic event list screen element may cause the 64 Bit runtime to sundenly close in a Windows Server 2012 R2 operating system. Description The chronologic event list screen element may cause the 64 Bit runtime to sundenly close in a ...

• It may happen that a control element is missing in the chronologic event list filter screen.

  Summary When creating a chronologic event list filter screen via the project wizard or by adding the default template the hour combo box is missing in the editor and runtime. Description When creating a chronologic event list filter screen via the ...