Publishing UI - Part 2

1. Preview Publication Table of Contents

When content is selected for publishing and the user advances to the Review page, the selected items are displayed alongside a preview of the table of contents for each resulting Publication in the Portal. This enables users to understand the impact of their publishing choices before any updates are applied, giving them the opportunity to refine their selections or proceed with confidence.

For Collections published that have multiple Publication Filters, the Review page presents a separate preview for each resulting Publication. Users can review how each Publication’s table of contents will appear in the Portal prior to publishing, ensuring that the output aligns with their expectations.

Note: The functionality will be released in a separate patch to the 4.19.0 release and will include more detailed release notes.

2. Publishing UI – Filtering Selections

When partially publishing a Collection, users can now refine their selection using enhanced filters. In addition to filtering by document name or folder name, users can filter content by attributes such as change type, last published date, and other relevant metadata. These expanded filtering options are particularly beneficial for Collections with a high volume of documents and files, helping ensure that the appropriate content is accurately identified and selected for publishing.

Note: The functionality will be released in a separate patch to the 4.19.0 release and will include more detailed release notes.

Projects - The next phase of Editorial Projects

1. Editorial Projects in Primary Navigation

In the 4.19 release, Editorial Projects has been elevated from a table of contents accordion item to a dedicated primary navigation item, now named Projects. This change reflects the growing role of project-based workflows in the CCMS and addresses usability challenges that came with its previous placement.

What's changed?

• Renamed: ‘Editorial Projects’ has been renamed to "Projects" in the CCMS.
• Promoted to primary navigation: Projects is now accessible as a primary navigation item, replacing its previous location as a TOC accordion.
• Search: Editors can now search for both projects and amendments directly within the Projects view.

• Empty state handling: Collections with no projects will display an appropriate empty state within the Projects view.

What's unchanged?

All existing amendment creation and merge workflows remain the same. Projects and amendments created prior to this release are fully accessible within the new ‘Projects’ view. No data migration or editor action is required.

2. Archive Projects

Editors can now archive amendments and editorial projects directly within the CCMS, replacing the previous process of raising a development support ticket. Archived amendments are accessible from the ‘Archive’ tab within ‘Projects’, providing a separation from active work.

What's new?

• Archive an amendment: Editors can archive individual amendments from within a project.
• Archive a project: Editors can archive an entire project’s folder
• Retrieve archived items: Archived amendments and projects can be restored by editors without development involvement.
  • Retrieving a project restores all its child amendments.
  • Retrieving an amendment restores that amendment and its parent project.
• Archived items are read-only: Content within archived amendments cannot be edited.
• Clear visual distinction: Archived amendments and projects are clearly separated from active ones in the Projects view.

 What's unchanged

Amendment creation, merging, and document editing workflows are unaffected. Permanent deletion and bulk archiving are not supported as a part of this feature.

3. Refine Component Search Results by its Parent’s Metadata Values

The CCMS search experience has been enhanced to allow editors to refine search results by the metadata values of its parent items. This release also introduces the ability to refine search results by metadata text fields, a capability previously unavailable in refine results.

What's new

• Filter by metadata text fields: Users can now refine search results using metadata text values.
• Grouped metadata types: Configured metadata values are displayed in a single categorized view, grouped by Components, Documents, and Folders.
• Cross-level component filtering: Component search results can now be refined by the metadata of their parent documents and folders, not just the component itself. Combined selections apply as cumulative filters. A component must satisfy all selected criteria to appear in results.

What's unchanged

Existing search behavior, document-to-component linking, and search architecture are unaffected

Video Webinar

Resolved Bugs