v4.8.0-rc.2024.8.21 release

v4.8.0-rc.2024.8.21 release has six bug fixes, eight improvements, and four new features.

Significant new features

• Added an API client to retrieve analytics from Adobe Analytics.
• Added a task for processing analytics ingested from Adobe Analytics.
• Added reporting for analytics ingested from Adobe Analytics.
• Deployed infrastructure for directly integrating with Azure Blog Storage.

Significant improvements

• Improved the form of the ping command used to determine if a database is available.
• When configuring a content report using a content query, the list Display Fields now includes an extra identifier if several fields have the same name. If previously the editor saw the field Description twice in the Display Fields list, now the editor sees Description (description) and Description (cms.seo.description).
• Updated the class ContentEditPage so that its methods return more compact URLs. Previously the methods returned unnecessarily long URLs with many query parameters set to false.
• Improved field filtering in GCA editorial schemas.
• Added a message to the content edit form clearly indicating that using AI Chat to develop an asset incurs charges from the AI provider.
• Added a warning message to the Report widget that appears when an incorrect configuration prevents Brightspot from running the report.
• Added a copy control content_copy in the Ask AI widget so editors can copy the response from the AI provider.
• Localized prompts now appear in the various AI widgets.

Significant defects addressed

• Corrected an issue preventing proper population of lists of objects. For example, when creating a role, the list of content types included entries other than content types.
• Corrected an issue inserting incorrect links in the search panel's grid view for integrated searches. For example, when searching on Getty Images, clicking on an image in grid view did not open the corresponding image in the content edit form.
• Corrected an issue preventing population of The Shelf's source list when the asset in the content edit form did not include a typeId in its URL.
• Corrected an issue throwing NullPointerException errors when generating a content report. Specifically, if a content report was incorrectly configured and then subsequently correctly configured, running the correct configuration threw this error.
• Corrected an issue incorrectly including a reply button in an actionable notification for conversations. Specifically, in the Conversation widget editors cannot reply to a reply, but a Reply button was appearing in notifications triggered by a reply.
• Corrected an issue preventing publication of assets when Pinecone was configured as the vector database provider for Ask AI.