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

• Related Articles

• It may happen that some standard recipes screen specific functions are not logged in the chronologic event list in the runtime.

  Summary Although the actions are executed correctly, the "new recipe"/"delete recipe"/"read recipe" standard recipes screen specific functions are not logged in the chronologic event list when executed from a client runtime. DescriptionAlthough the ...

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

  Summary When changing a user full name in the Runtime the Chronologic Event List text may show the original user full name also in the new (“to”) field instead of the new full Name. DescriptionWhen changing a user full name in the Runtime the ...

• 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 ...

• 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 ...