App Suite Middleware
API - HTTP-API
SCR-1586
Summary: New Parameter 'user' for Action 'resolve' in Module 'chronos'
The resolve
action in module chronos
of the HTTP API is extended by the new optional parameter user
, through which the identifier of the calendar user can be specified.
If an event is found, it'll be returned under the perspective of this user, i.e. having an appropriate parent folder identifier assigned. The current session user still needs to have appropriate access rights for the resolved event, though.
See the documentation for further details.
Configuration
SCR-1584
Summary: New Property 'com.openexchange.calendar.includeCreatorInFreeBusy'
To control whether the entity that originally created a conflicting event is included in free/busy results, even if event details cannot be accessed by the requesting user, the lean configuration property com.openexchange.calendar.includeCreatorInFreeBusy
is introduced. Possible values are:
never
- Never expose the created by information in foreign events of free/busy results.resources-only
- Include the created by information in foreign events of free/busy results of resource attendees, only.always
- Always expose the created by information in foreign events of free/busy results.
It defaults to always
for backwards compatibility, is reloadable, and can be defined through the config-cascade.
Although there has already been a similar switch for App Suite UI io.ox/calendar//freeBusyStrict
to show/hide these details from foreign events, this middleware property controls the exposure of the "created by" information at API level, so should be used in favor of the UI setting.
[8.40.56]
3rd Party Libraries/License Change
SCR-1577
Summary: Updated OSGi target platform bundles
Updated the following OSGi target platform bundles
org.eclipse.osgi.util_3.7.300.v20231104-1118.jar
updated toorg.eclipse.osgi.util_3.7.400.v20250516-0916.jar
org.eclipse.osgi_3.20.0.v20240509-1421.jar
updated toorg.eclipse.osgi_3.23.100.v20250514-1759.jar
Configuration
SCR-1576
Summary: New properties to control number of tombstone records
In order to control how many tombstone records are persisted per calendar account, the following new lean configuration properties are introduced, each applicable for the corresponding calendar provider and defaulting to a value of 2500
unless overridden:
com.openexchange.calendar.ical.maxEventTombstones = 2500
com.openexchange.calendar.google.maxEventTombstones = 2500
A value of -1
disables the limit. Both properties are reloadable and config-cascade aware.
See the property documentation for further details.