CSSCurrent en:Version 7.4.0: Unterschied zwischen den Versionen

Aus Cryptshare Documentation
Wechseln zu:Navigation, Suche
Keine Bearbeitungszusammenfassung
Keine Bearbeitungszusammenfassung
Zeile 12: Zeile 12:
* Obsolete log files and service definitions will be removed with this update, that were only relevant to earlier versions of Cryptshare and are no longer required.
* Obsolete log files and service definitions will be removed with this update, that were only relevant to earlier versions of Cryptshare and are no longer required.
* The installed OWA package version displays the build number.
* The installed OWA package version displays the build number.
* If the notification of all recipients fails during a transfer, the Cryptshare Server skips the notification of the sender about a ‘successful notification of the recipients’. Starting with this version, the sender's notification is now also saved as failed. This affects the display in the transfer log and responses from the SOAP and REST API. This is to avoid the false impression that the sender has been informed about the transfer.


=== REST-API ===
=== REST-API ===
Zeile 19: Zeile 20:
== Bug Fixes ==
== Bug Fixes ==
* Fixed an issue causing application logs to appear in host system syslogs (`/var/log/messages` or `/var/log/syslog`).
* Fixed an issue causing application logs to appear in host system syslogs (`/var/log/messages` or `/var/log/syslog`).
* Fixed an issue where the sender’s <code>notificationFailed</code> was not updated (set to <code>true</code>) when all recipient notifications failed due to an invalid mail server, and each recipient had <code>notificationFailed=true</code>
* Fixed an issue where boolean properties in the Transfer-Polling API response defaulted to <code>false</code> when not included. They now return <code>null</code> unless specified via the '''Fields''' parameter.
* Fixed an issue where boolean properties in the Transfer-Polling API response defaulted to <code>false</code> when not included. They now return <code>null</code> unless specified via the '''Fields''' parameter.
* Fixed an issue where the  Transfers in the "Processing" state that exceeded their <code>expiration_date</code> were incorrectly returned as active in the API response before the cleanup task ran. They are now correctly returned with the state <code>DELETED_BY_EXPIRATION</code>
* Fixed an issue where the  Transfers in the "Processing" state that exceeded their <code>expiration_date</code> were incorrectly returned as active in the API response before the cleanup task ran. They are now correctly returned with the state <code>DELETED_BY_EXPIRATION</code>
* Fixed an issue where under specific circumstances the "Save changes" button in the policy administration was not responsible.
* Fixed an issue where under specific circumstances the "Save changes" button in the policy administration was not responsible.
* Fixed an issue that prevented transfers created by QUICK from being polled via the Rest Api.
* Fixed an issue that prevented transfers created by QUICK from being polled via the Rest Api.

Version vom 1. Juli 2025, 08:18 Uhr

eRelease Date: TBD

Important Update Notes

Language Packages

Due to structural changes in the language packages, all supported server language packages will be updated automatically, customized language packages will be removed during the update process (a backup is done before). If more language packages are needed, it is required to download and install them again.

In case your language packages have been modified, the attached delta-file Datei:Delta english lp 7.3.0 to 7.4.0.txt can help you to locate the changes in this update and re-apply the modifications. The structure of this file is explained in Language Pack Changes.

New features

Improvements

  • Obsolete log files and service definitions will be removed with this update, that were only relevant to earlier versions of Cryptshare and are no longer required.
  • The installed OWA package version displays the build number.
  • If the notification of all recipients fails during a transfer, the Cryptshare Server skips the notification of the sender about a ‘successful notification of the recipients’. Starting with this version, the sender's notification is now also saved as failed. This affects the display in the transfer log and responses from the SOAP and REST API. This is to avoid the false impression that the sender has been informed about the transfer.

REST-API

Enhanced Transfer Polling: Sender Details now available

The sender’s name and phone number are now saved in the database and can be retrieved via the Sender/Recipient Transfer polling API.

Bug Fixes

  • Fixed an issue causing application logs to appear in host system syslogs (`/var/log/messages` or `/var/log/syslog`).
  • Fixed an issue where boolean properties in the Transfer-Polling API response defaulted to false when not included. They now return null unless specified via the Fields parameter.
  • Fixed an issue where the Transfers in the "Processing" state that exceeded their expiration_date were incorrectly returned as active in the API response before the cleanup task ran. They are now correctly returned with the state DELETED_BY_EXPIRATION
  • Fixed an issue where under specific circumstances the "Save changes" button in the policy administration was not responsible.
  • Fixed an issue that prevented transfers created by QUICK from being polled via the Rest Api.