Find out more about new features and improvements in the Fabasoft Cloud.
As an end user you can expect the following new features.
In the properties of a Teamroom, on the “Content Settings” tab, in the Storage Period of Expired Public Links field, you can specify the period of time after which entries from expired public links should be deleted. This allows you to clean up the list automatically. If no time period is specified, the entries are kept.
Alternatively, you can use the “Manage Public Links” context menu command for a Teamroom and manually delete the expired public links of the Teamroom using the “Delete Expired Public Links” button.
For performance reasons, the All Public Links Within This Teamroom field is no longer available. Instead, you can use the “Manage Public Links” context menu command and the “All Public Links” button to open a query-based list that allows you to search for objects with public links. Via the “Delete Public Links” context menu command, all public links of the selected objects can be deleted.
As an administrator you can expect the following new features.
Due to a restriction in Google Chrome and Microsoft Edge on how locally installed web browser extensions can be updated, we are forced to adjust the default behavior of the installation of web browser extensions.
As of the Fabasoft Cloud 2024 April Release, the Fabasoft Cloud Enterprise Client no longer installs the web browser extensions for Google Chrome and Microsoft Edge as a locally installed extension. Instead, the extension is registered so that it is automatically installed by the web browser via the respective store. From this point on, the Microsoft Edge Store extension (with the ID jdibaejnifcnoojmhgcbaohifohjamlg) is registered for Microsoft Edge and the Google Chrome Store extension (with the ID icjlkccflchmagmkfidekficomdnlcig) for Google Chrome. If there is already an existing configuration for the Fabasoft web browser extension that has been configured from a central location (e.g. company portal, software center, etc.), the Fabasoft Cloud Enterprise Client will not register it via the setup (as before). If you have restricted the web browser functionalities via policies, you must still add the corresponding exceptions for the Fabasoft Cloud Enterprise Client. This mainly concerns the web browser policies ExtensionInstallAllowList and NativeMessagingAllowlist (for NativeMessagingAllowlist, the exception for com.fabasoft.nmhostpu must be added).
However, if access to the respective store (Google Chrome or Microsoft Edge) is not permitted for a user on your systems, it is still possible to install the web browser extension as a local extension via a setup parameter. The setup parameter EXTLOCAL=1 can be used from the Fabasoft Cloud 2024 February Release. Example: msiexec /i <msipath> EXTLOCAL=1
In addition to installing the local extension, the configuration parameters override_update_url, ExtensionInstallAllowList and NativeMessagingAllowlist are automatically set so that the extension can be functionally installed and updated. A more detailed description of the respective configuration parameters can be found on the websites of the web browser manufacturers.
When does this change affect me?
Note: If the Fabasoft Cloud Enterprise Client Setup installs the local extension and therefore sets the configuration parameter override_update_url, the corresponding extension must not be installed via the store in the user profile of the web browser, otherwise the web browser extension will be marked as “broken”. The configuration parameter override_update_url is necessary for the web browser to update the locally installed extension.
If the Log E-Mail Dispatch Errors option is enabled in the SMTP settings (organization > “Advanced Settings” > “Define SMTP Settings”), a dispatch error is stored for e-mails that cannot be sent successfully in the background.
You can perform the following manual actions for e-mail dispatch errors: