v4.8.8 release

v4.8.8 release had two new features, 9 improvements, and 30 bug fixes.

Significant new features

• Introduced a new AI Audit Widget that provides a snapshot of guardrail violations and AI performance indicators.
• Added Amazon Bedrock Guardrails features. This new feature has introduced a breaking change. See the "Breaking Changes" section below for more information.

Significant improvements

• Enhanced user permissions so that Site Categories are now only visible for sites to which a user has access to.
• Enhanced the SiteMapEntry lastmod field to support full timestamp formatting with both date and time.
• Added support for customizable report storage settings, allowing projects to specify where report CSVs are stored.
• Added support for Java 16+.
• Added the ability to export full URLs—including Permalink, Redirect (Permanent and Temporary), Alias, and CMS edit page URLs—from CMS search results and content reports.
• Introduced shared provider fields for Ask and Create clients, enabling admins to select from multiple AI models. This improvement has introduced a breaking change. See the "Breaking Changes" section below for more information.
• Moved Audience dropdown code into the existing Audience plugin.
• Created an API that enables projects to add custom UI in the top left, next to the item label, replacing the existing Audience dropdown. This improvement has introduced a breaking change. See the "Breaking Changes" section below for more information.
• Enhanced the BulkVectorIndexLog with additional details including run timestamps, item types to the failed-to-vectorize error messages, and the number of items that failed to vectorize.

Significant defects addressed

• Resolved an issue where video previews were missing when selecting shared videos for the Lead field in a new article.
• Resolved an issue where changes to a name made via a content form with a Global scope persisted, even after editing the form’s scope or deleting the form.
• Addressed an issue where opening multiple links simultaneously could display incorrect previews.
• Resolved an issue where the Archive button was visible and occasionally functional for users that did not have archive permissions in admin areas.
• Fixed an issue where escaped markup tags were shown in rich text field diffs when Track Changes were enabled.
• Resolved an issue where workflow options were missing when editing content revisions in draft or other non-published states.
• Brightspot now redirects to the published path’s original casing, rather than always lowercasing URLs.
• Resolved an issue where items filtered with @Where were not appearing in the Hierarchy view for reference fields.
• Fixed an issue where copying and pasting tables in the same RTE resulted in duplicate colspan and rowspan attributes.
• Resolved an issue preventing reports from being saved or accessed after importing Adobe Analytics report suites.
• Fixed an issue where attempting to publish a revision without a publish override would incorrectly reset the workflow, rather than publishing the revision as intended.
• Fixed an issue where the reset filters button on fullscreen search did not clear selected filters.
• Fixed an issue where the contents of the Dari HTML <style> element were incorrectly escaped.
• Resolved different issues while accessing Quick View for different users such as NPE errors and missing Quick View icons for certain users.
• Fixed an issue where P2E would fail if the data-state attribute was not the last entry in rich text element attributes.
• Removed an obsolete static database environment reference from TypePermission, replacing it with up-to-date usage of DatabaseEnvironment.getCurrent().
• Resolved an issue where enabling the debug profiler would display unintended sequence numbers at the top of HTML pages.
• Addressed issues with the GraphQL Reference Type Filter field so that selecting None now defaults to All Types, and choosing Content correctly includes all relevant content types.
• Resolved an issue where users having permissions for only a few statuses had only read-only access to content types.
• Fixed an issue where hierarchy view allowed selection of sections owned by other sites.
• Disabled the non-functional User Access widget in the platform, ensuring it will only be shown once the feature is fully implemented.
• Resolved issues with unnecessary spacing and padding in top-level widget messages and class notes.
• Fixed an issue where redirects were pointing to the last configured permalink rather than the canonical (first) permalink.
• Resolved an issue where creating a new Revision in environments with AI enabled could result in a NullPointerException.
• Fixed an issue where QueryRestriction parameters could cause ObjectIdResultPageto display a blank page.
• Addressed an issue where concurrent requests to GraphQL Content API (GCA) endpoints could fail with NoSuchElementException. This defect has introduced a breaking change. See the "Breaking Changes" section below for more information.
• Resolved an open redirect vulnerability on the CMS login page that allowed redirection to malicious external sites.
• Resolved an issue where Recent Activity Filters and Saved Search Filter (in the shelf) failed to filter content types for statuses other than Published.
• Updated the ValidateEncoding task plugin to support additional human-readable Unicode characters.
• Create with AI and Ask AI displays a clearer message when the AI Guardrails service is unavailable.

Breaking changes

• Added new API to AIChatProvider interface: #getModelNameInUse should return the model name that the provider is using. This is used to populate the model column in the audit widget. Additionally, Bedrock Chat Provider implementations of #handleResponse now take in the AiChatRequest as a param in order to record any error and have that information be properly saved on the the request.
• The AIChatClient#provider field has been deprecated and replaced with AIChatClient#providerOption. Existing provider info will be relocated to the new model automatically.
• The rendering of Overlay Provider selection is no longer provided by default. Instead, implementations of Overlay are expected to provide their own UI to discover and switch to overlays. Projects with their own custom implementation of Overlay should use this new API to render overlay selection in the title prefix are of the content page. Projects using the audience feature will still function.
• GraphQLJavaSchemaLoader#profiler was changed from protected to private. GCASchemaTypes#newInstance API signature changed.