Standardised Site iCM4j 8.0.511

Released 24/02/2023

Breaking Changes

There are no breaking changes in this release.

Assisted Service 11.7.43

We've fixed the alignment of the buttons in the assisting banner.

Case Management 1.34.1305

An End Point, goss.CaseManagement.v1.core.user.getGroupsAndMembers, was missing from the build which meant users weren't being displayed when reassigning cases. This bug was present in the previous 1.34.1224 and 1.34.125 releases.

We've also improved how Case Management integrates with the Data Retention Manager. In addition to the normal DRM functionality, the following applies to Case Management history data:

• When creating schedules for cases, pick the caseManagement End Point from the "Retention end point" drop-down in advanced settings
• Only data from closed cases is deleted
• The retention period is calculated from the date the case was closed
• The terminated process instance is also deleted when the retention period is reached (the DRM normally only deletes history records)
• Solr records are updated when case data is deleted
• If you don't specify a labelc, all history records for a case, excluding "labela": "Case Management - caseType", "labelc": "reporting" are deleted
• A "labela": "Case Management - caseType", "labelc": "audit" record is written

Chill Theme 14.11.72

We've standardised the markup in the iCM.NET and iCM4j frameworks for menu links in the footer by adding new classes. 

The new markup is:

<ol class="utilitymenu--footer">
    <li class="utilitymenu__item">
        <a class="utilitymenu__link" href="https://gosshosted.com/themes">Themes</a> </li>
    <li class="utilitymenu__item">
        <span class="utilitymenu__text">Developer articles</span> </li>
</ol>

Command Theme 13.6.59

The styling for bullet points in the theme meant they were hidden, so we've restored them by sorting out the padding.

Data Retention Manager 1.2.37

Custom End Points weren't appearing in the scheduling form's drop-down list, which meant you weren't able to pick product specific versions when creating schedules.

Similarly, we've restored some functionality that lets you pick an End Point to calculate the deletion date, rather than setting a fixed schedule. This is used in Bookings to delete data a set period of time after an event has taken place.

We've also changed the default behaviour for the types of histories that get deleted. Previously, if you didn't enter a "labelc" value when creating a schedule, the tool would delete histories with "labelc" values of null, "notes", and "attachments". "email" has been added to that list.

iCM4j Framework 23.16.779

To fix the padding in the cookie banner and body of the cookie dialog, a new class and modifier, a-body--cookie has been added.