Breaking Changes
There are no breaking changes in this release.
Assisted Service 12.8.59
We've fixed a bug in the histories written by the interaction log where outcomes were being recorded as "Task completed" rather than the value selected by the user.
Bookings 1.9.167
Similar to the previous release of Bookings, we've fixed another date format in the event manifest form.
Capita Paye.net Payment Field 10.1.26
This fix restores some backwards compatibility.
In version 10.1.12 (released in September 2022) we added support for payment reconciliation, which involved moving security keys to a configuration end point. If the keys weren't moved to the configuration end point, and instead were set directly in the form payment field (which is how things were set up prior to 10.1.12) the keys set in the field were incorrectly ignored. With this release, if you still have keys in the form field, they'll be used. We've also made sure that if you had multiple sets of keys, the correct one is used and not just the default.
Comms Template Manager 1.1.24
This release improves the fix in the previous version which increased the maximum amount of text you could have in a template. We found some situations where the new maximum length (25,000 characters) wasn't being picked up.
iCM4j Framework 25.17.975
This release includes:
- New subsite settings for the Document Section template which let you override the metadata titles output in the page source. See Document and Document Section for the updated documentation. For these settings to appear in the configuration the subsite extras form will need to be reimported to include the DOCUMENTSECTIONTITLEFORMAT field
- We've added a utility end point which can be used to convert image media definitions from the old fixed size thumbnail/image/large components to the standard variant approach. Note that variants replaced the older style components around 2016-2017 so this tool will be irrelevant to anyone who has started using the platform since then. We also don't recommend running this yourself, it's intended as a tool to be used by GOSS developers during an upgrade. All of which makes you wonder why I'm telling you about it in the release notes!
- There have been some minor CSS changes for form fields to make their styling more consistent when they are disabled
Share this page
