We develop practical software solutions for state-of-the-art service desks.Read here which customer suggestions and innovations we have recently implemented.
The following new features are included in the version update from 17.07.2024
The messages in the IBI-aws Client have been visually revamped and now feature a modern design. The new skin is available in the latest version of the IBI-aws SkinDesigner as a base for your custom skin.
As of this version, you can conveniently store the message file on an Azure Blob Storage.
You can find further information at Microsoft Azure Blob
From this version onwards, we are focusing exclusively on 64-bit operating systems.
Support for “Incoming Webhooks” will end on October 1, 2024. With Teams Workflows, you can continue sending IBI-aws messages to Teams channels as usual beyond this date.
Among other things, there are the following new features since the version update of 31.10.2023:
Create and edit messages, even if the IBI-aws Admin is already being used by another person.
The IBI-aws Admin can now serve several clients in the same instance.
Messages can now also be sent to Microsoft Teams channels.
A content type can be used to categorize and visually distinguish messages.
On May 16, 2022, the latest IBI-aws update was released – including highly exciting new features:
To make the communication between IBI-aws Admin and IBI-aws Clients even more secure, the message file can now be encrypted using a certificate.
In addition to the previously supported directory services, Microsoft Azure Active Directory is now also supported. This means that addressing can also be performed via users and computers of an Azure Active Directory.
On January 24, 2022, the latest IBI-aws update was released – including highly exciting new features:
Address messages based on registry entries even more precisely from now on.
Improve the overview by archiving messages.
The proxy settings have been integrated into the IBl-aws Admin for simplicity.
The maximum length of the message reason can be specified per message group.
Further, technical information about this and previous updates can be found in the documentation.