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

• Related Articles

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

• Visibility doesn't work for “Chronological Event List Filter” MDI Element

  Description In the screen of type "Chronological Event List Filter" the link to a variable for visibility does not work correctly. In the Service Engine, when a time filter is clicked, the visibility setting no longer works as configured. This error ...

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

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

• [MSI Interface] Deleting an Alarm Event Group prevents sending of Exception Messages

  Summary In the Werum MSI Interface, deleting an alarm/event group leads to an error under certain conditions. This has been fixed. Description In the MSI configuration an alarm/event group is used to define an exception message. Later, a group is ...