v4.8.3 release

v4.8.3 had two new features, nine improvements, and 17 bug fixes.

Significant new features

• Introduced footnotes to Ask AI answers. Now, when Ask AI responds to a prompt, it will also cite exactly where it got the information from in the footnotes. Clicking these sources will take you directly to the original source.
• A user with a role that has the Publish permission, but does not have the Workflow permission, now sees the Publish button on the content edit page of an asset.
  

Significant improvements

• Made Ask AI conversations easier to follow and understand by introducing a way to save forked chat request data. This lets users save different versions or paths of their conversations, so they can explore different ideas without losing track of a conversation.
• While using Create with AI, users now have the ability to use AI on Pre-Publish Actions fields. This feature allows editors to make quick, last-minute changes to content using AI before publishing. Brightspot flags any AI-altered content as being AI-generated.
• Made saved searches clearer by improving the Contains AI label.
• Ask AI now offers collapsible references in the Ask AI window.
• Added an Introspection entry field to the GCA to give programmatic access to the type system. This improvment introduced a breaking change. See "Breaking changes" below for more information.
• Users are now able to specify where AI prompt suggestions appear at the content type level and at the field level.
  
  • Prompt setup moved: AI prompts are now configured in Sites & settings under AI.
  • Site-wide prompts: Users can create prompts that appear on all pages.
  • Prompt selection/creation: Users can pick existing prompts or make new ones.
  • Content type prompts: Users can add prompts specific to content types.
  • Content type field prompts: Users can add prompts to all fields on a content type.
  • Field-specific prompts: Users can add prompts to individual fields.
  • Prompt hierarchy: Site-wide, then content type, then field-level prompts are shown.
  • No duplicate site-wide prompts: Site-wide prompts do not repeat on specific pages.
  • Embedded content prompts: Linked content shows both site-wide and main page prompts.
• Deprecated DAM PageServlets related to Collections.
• Deprecated RichTextToolbarItem.CUSTOM.
• If content has not been published in more than two days, Brightspot will now generate an empty sitemap instead of no sitemap at all, which resulted in a 404 error.
  

Significant defects addressed

• Fixed an issue when creating a table inside of a table that caused table icons to overlap.
• Fixed an issue preventing changes to data that was relocated from one module type to another to persist after the first save action. Now, changes persist after the first save action after data is relocated from one module type to another.
• Fixed an issue that caused a page to get stuck in an infinite loop when saving a content template.
• Resolved an issue by increasing the Lingotek connector locale limit from 300 to 1000.
• Fixed an issue where live blog posts remain locked in the CMS after a user publishes them.
• Corrected an issue that saw a WIP message displayed on the content edit page after moving a revision between workflow states or after saving a revision while it was in a workflow state.
• Resolved an issue causing an error when loading a content edit page after a populated field in a data model changed from a single embedded record field to a list of the same record type.
• Fixed an issue of Rich Text Editor toolbar drop-down menus flickering while re-sizing the browser window.
• Fixed an issue in which the images that are dragged from The Shelf were appearing in the wrong order.
• Fixed an issue where Styleguide was not displaying certain errors.
• Fixed an issue in which schema description is not removed from GraphQL Schema Definition Language (SDL) when a certain setting was applied.
• Resolved an issue that caused errors in logs when reloader was triggered.
• Resolved an issue of not being able to edit inline rich text elements when wrapped in a block rich text element with fields.
• Fixed an issue where pasting links surrounded by <u> tags into a rich-text editor field was removing the link.
• Resolved an issue related to a site health alert pointing to a condition which no longer existed.
• Fixed an issue causing editorial content types to not be properly represented in the GraphQL schema upon schema generation.
• Resolved an issue where large GraphQL endpoints, due to the length of time it took for them to load, were making other endpoints temporarily unavailable.
• Fixed an issue that was confusing the view system reflection APIs when searching for the list of properties of a view model. This fix introduced a breaking change. See "Breaking changes" below for more information.
  

Breaking changes

• As a result of adding an Introspection entry field, a breaking change was introduced: The GCA field Get > Record > View > Response has an argument named request that has been split into a secondary argument named typed. request used to have a dynamic type name, but now has a more generic and static type name of ViewRequestInput and has a different shape in that it only accepts generic headers/parameters via name/value pairs. All of the ViewModel type specific parameters have been moved to the sibling argument typed that now has the dynamic type name since it holds the type specific arguments.
• As a result of fixing an issue caused by a getModel method on ViewModel, the viewModel#getModel instance method has been removed, and there is now a new static ViewModel#getModel(Object) method.