Version 1.24
Announcement
From IBI-aws MobileClient version 1.13, Windows 10 Mobile will no longer be supported. Sorry for the inconvenience. Please refer to the Microsoft End of support for the operating system mentioned.
Published on 25th March 2020
Admin
new
- Command line interface
- Message overview: "Message" can be displayed as column
- Application Pool: Applications can be copied
- Messages can be exported as templates
- New property "External ID" introduced for messages
- ID of the pool entries can be copied
- Event logging: From now on, events are always logged to the Windows Event Log
- Message dialog: Pressing the shift key while clicking on "Save" opens the publish dialog afterwards
modified
- Various usability improvements implemented
- Message overview: The category "Active" now also displays messages whose early warning is already active
- E-mail dispatch dialog: The dispatch details are displayed when checking a message
fixed
- FTP: "Restart Clients" failed and WebClient was updated too often
- Lists: Selection may not have been correct with active filter
- List in "Create message from template" was unsorted
- E-mail address and groups referenced in templates could be deleted
Client
new
- A displayed early warning is now sufficient for status updates or resolve messages to be displayed
- Event logging: From now on, events are always logged to the Windows Event Viewer
- Unlimited number of additional message data sources possible
modified
- Improved reliability of start parameter /FixTray under Windows 10
- Support for long file paths improved
- Local caching of message files improved
- Messages are closed more quickly after the end time
- Start process accelerated
fixed
- URLs that were too long were not displayed correctly
- Tray icon was not always reset correctly if no active messages were available
- Fixed application window focus behavior
WebClient
new
- Expired and completed messages will continue to be displayed for 7 days unless the message file is rewritten
modified
- Change of the CSS classes for better individualization
- Consider the setting upcomingMessageDisplayOffset also for messages with early warnings