Brightspot Releases

v4.2.6 release

Release date: March 4, 2020

Significant new features

  • Brightspot has a new integration with Amazon Textract for automated text extraction from PDF documents and image files saved as JPG and PNG. With the extracted metadata, the documents are more easily accessible using Brightspot search. Amazon Textract is enabled as a plugin. Filed under: Amazon Textract
  • Brightspot now generates a log of actions taken by Brightspot users, including successful and unsuccessful account logins, changes to an account, changes to content types, and permission changes. For each event, when the event occurred, where the event occurred, the source, the outcome, and the identity of the users associated with the event are captured. Filed under: logs

Significant improvements

  • Dashboards are available to view and edit directly under Admin on the navigation menu. Filed under: dashboard
  • Filters in the Community Moderation widget now persist. When you set a filter, the setting is still applied when you log out and log back into Brightspot. Filed under: community
  • You can now add a title to the Resources widget. Filed under: Resources widget
  • If you need to publish a large taxonomy set and have the tags prepared in a CSV file, you can now upload that file to Brightspot using the Upload widget. Brightspot automatically creates the tags and applies them to the site on which you are currently working. The CSV file must contain the Display Name, Internal Name, Description, SEO Title, SEO Description, SEO Keywords, and URL in plain text. If the file contains any duplicate tags, Brightspot updates the existing tags. Filed under: tag
  • If an error occurs during bulk upload, you now have the opportunity to fix the error without uploading all the files again. Filed under: bulk upload
  • When configuring a Brightcove account in Brightspot, you can now add an internal name. Filed under: Brightcove
  • Certain areas of Brightspot are designed to be used only by developers who are aware of the implications of making any changes to avoid catastrophic errors to the site. For access to these developer areas, Brightspot users must now be assigned to a role that has developer permissions enabled. Filed under: user
  • When you open or close the lead in an item, Brightspot remembers that selection and the lead is opened or closed in all content types. Filed under: lead
  • The bulleted list and numbered list icons in the rich-text editor now serve as toggles for applying and removing bullets and numbers from items in a list. If the cursor is on an item in a bulleted list, click the bulleted list icon to remove the bullet or click the numbered list icon to change the bullet to a number. If the cursor is on an item in a numbered list, click the numbered list icon to remove the number or click the bulleted list icon to change the number to a bullet. If the cursor is positioned before the first letter of an item in a list, click the backspace key to remove the number or bullet. Filed under: rich-text editor
  • To improve accessibility, you can now use the tab key and the return (or enter) key on the keyboard to navigate to and then select various elements on the Brightspot user interface. Click the tab key while on a page to access fields from left to right then down the page. Filed under: accessibility
  • In Digital Asset Management, the Download and Share options have been moved to the Tools Menu. Filed under: Digital Asset Management
  • In Assignment Desk, the Create Assignment option has been moved to the Tools Menu. By default, the Assignment Desk Dashboard now displays 50 assignments, instead of 10. Filed under: Assignment Desk
  • In the CMS search, selections for common filters can now persist across content types until you click Reset. The Enable Sticky Search Filters option must be marked in the Global site settings on the navigation menu under Admin > Sites & Settings. In the search panel, the common filters are displayed above the filters specific for the content type. Filed under: CMS search
  • There are now two options for restoring archived content: restore it to either draft status or live status. When restoring content to draft, the content is then sent through the workflow before publishing and reactivating the URL. Filed under: restore, archive
  • User settings were stored locally, requiring the settings to be configured on different devices. The user settings are now stored with the user account so the settings are available on all devices. Filed under: user profile
  • In the Upload widget, if you click outside the pop-up window or close it, a confirmation message will appear to verify the action. The confirmation is designed to prevent you from inadvertently closing the window and having to start the upload process again. Filed under: upload
  • To facilitate running simple queries, the predicate input field in the GraphQL Schema for the Content Management API is now optional instead of required. The query limit has been increased from 10 to 200. Filed under: API, GraphQL
  • To improve the experience for mobile users, the Preview pane is automatically off by default. For other devices, there is a new Closed by Default option under Sites & Settings > Preview to turn off preview by default for the entire site. Filed under: preview
  • The current options to increase contrast and change black inputs have been combined into one option called High Contrast Mode. Filed under: article
  • When uploading files, after choosing files to upload, the names of the each file is now displayed if the file is not an image. For an image, a thumbnail of the image is displayed. Filed under: bulk upload

Significant defects addressed

  • In CMS search, not all actions were available for all results for some content types that were not published. All actions are now available as expected. Filed under: CMS search
  • In an article with multiple authors, when authors were moved using drag-and-drop, they could no longer be edited. The authors can now be edited as expected. Filed under: author, article
  • Email notifications for messages posted to Slack were displaying the incorrect requestor information. The correct name of the requestor is now displayed. Filed under: Slack notification
  • In the rich-text editor, when pasting cells from Excel into a table, the contents of the first cell failed to paste. The complete content is now pasted as expected. Filed under: rich-text editor
  • Attempting to import content from Brightspot into Adobe InDesign using the Brightspot InDesign plugin failed. The content from Brightspot now imports into the InDesign template and the data is written to the corresponding Brightspot object as expected. Filed under: Adobe InDesign
  • In the rich-text editor, when the HTML view was enabled, all the other toolbar actions were hidden, including the option to toggle out of HTML mode. All actions now appear in HTML view as expected. Filed under: rich-text editor
  • In an article, selecting Mobile in the Preview pane adjusted the content but not the size of the pane. Both the pane and the content now adjust as expected. Filed under: preview

Breaking changes

  • An API messaging signature changed.

    • Before: DeliveryOption#messageFromHtml(MessageContext messageContext, org.jsoup.nodes.Document document)
    • After: DeliveryOption#messageFromHtml(MessageContext messageContext, String html)
  • This release removes the SearchCarousel page servlet. Projects can materialize to maintain support.
  • Integrating AWS Textract mandated the following changes:

    • Refactors DAM document data extraction logic to take asynchronous service calls.
    • Refactors DocumentDataExtractor to be an embedded record.
    • Deprecates Cloud Convert API site settings (they can be set in the data extraction settings).
    • The DAM plugin must now set the default or order of document extractor services in Global settings.
  • A refactor requires reindexing all instances of Dashboard, since Dashboard#name is now an @Indexed field. Also, Dashboards are now Global.
  • This change removes the hard-coded default groups (Landscape, Portrait, Square) that were previously being used in the focus dropdown. Projects will need to add their desired group to every image size in styleguide/_imageSizes.config.json. For example:
    "80xauto": {
      "previewWidth": 80,
      "previewHeight": 80,
      "maximumWidth": 200,
      "maximumHeight": 200,
      "srcsetDescriptors": ["2x", "3x"],
      "group" : "Foo"
    "fullwidthMedia": {
      "width": 1920,
      "height": 482,
      "maximumHeight": 482,
      "srcsetDescriptors": ["2x", "3x"],
      "group" : "Bar"

  • In this case, the focus dropdown will now show options for setting focus points for All Sizes, Foo, and Bar. Any image sizes that do not have a group specified will fallback to the focus points for All Sizes.
  • In order for projects to maintain parity, they will have to go into styleguide/_imageSizes.config.json and add Landscape, Portrait, and Square (case insensitive) to the appropriate image sizes. This will allow the existing focus points to be edited and modified.
Previous Topic
v4.2.7.1 release
Next Topic
v4.2.5 release
Was this topic helpful?
Thanks for your feedback.
Our robust, flexible Design System provides hundreds of pre-built components you can use to build the presentation layer of your dreams.

Asset types
Module types
Page types
Brightspot is packaged with content types that get you up and running in a matter of days, including assets, modules and landing pages.

Content types
Landing pages
Everything you need to know when creating, managing, and administering content within Brightspot CMS.

Admin configurations
A guide for installing, supporting, extending, modifying and administering code on the Brightspot platform.

Field types
Content modeling
Rich-text elements
A guide to configuring Brightspot's library of integrations, including pre-built options and developer-configured extensions.

Google Analytics
Apple News