Release Notes
We added External Reference Codes for Categories and Tags and their associated API’s, improving their portability for data migration scenarios.
Highlights:
Users can now perform CRUD operations using a Tag’s ERC through its headless API (Keyword)
Users can now perform CRUD operations using a Category’s ERC through its headless API (TaxonomyCategory)
We added External Reference Codes for references in widget configurations in Content Management applications. This helps promote data integrity when pages and their widgets are migrated across environments.
Highlights:
References within the following page widgets now use ERC’s instead of internal ID’s:
We added several API endpoints for Documents & Media to improve programmatic management of these entities.
Highlights:
Users can now add, delete, and retrieve document types via headless API (DocumentDataDefinitionType)
Users can now add, delete, and retrieve document metadata sets via headless API (DocumentMetadataSet)
It is now possible to subscribe to documents and folders, allowing users to receive notifications when they are updated.
Highlights:
Users can now subscribe to documents and folders through the “Subscribe” action and through the Subscribe icon in the Info Panel
If a user subscribes to a folder, all documents and subfolders within it will be automatically subscribed to as well
During the publishing process, users can both define and manage permissions, as well as schedule publication dates for their web content. When creating content for the first time, users will have the opportunity to conveniently review and manage permissions. Furthermore, when editing previously created content, users can also adjust permissions directly from the editor view. Additionally, users can easily select the desired publication date for their content during the publishing process.
Users can select and reorder categories for a blog’s friendly URL, so they can preview the order of the categories in the friendly URL and determine how the categories will be presented in the friendly URL along with the title.
Users are able to set different values for the asset types separators in the friendly URLs. Also, they are able to reset to default value, so for those asset types that they have clicked on this option, the separator will be the value defined by default for those specific asset types.
This release expands the support of the Timeline History feature to Blogs, Wiki pages, Bookmarks, Forms, Knowledge base, Message boards, and Categories. The feature enhances the publication toolbar with tools to detect and manage collaboration conflicts.
A timeline icon shows recent modifications in the same asset, which may have been done in production or parallel Publications.
The user can view, discard, or move these changes directly from the toolbar.
Warning icons appear to make users aware of current conflicts in the Publication.
Key benefits:
Enhanced context for content editors and managers for a streamlined collaboration.
New capabilities to detect conflicts before publishing time, while users may have more time to decide how to resolve conflicts without the go-live pressure.
This set of improvements aims to simplify the manual work users must do to resolve conflicts when publishing a publication. Now, instead of raising a conflict to be resolved manually by the user, the system will try to overwrite conflicting changes in production with the modifications done in the publication, meaning that the Modification and Modification deletion conflict types won’t be presented for the user anymore.
In the case of a Deletion modification conflict, the system won’t resolve it automatically, but now it makes it easier to keep the modifications made in the publication. In the Conflicting changes screen, we added a button with the option to "Restore in Production" for conflicts in which the asset was deleted from production and is now in the Recycle bin.
Key benefits:
Reduce the amount of manual work by automatically solving most of the conflicts.
Improve user satisfaction and reliability on publications by ensuring that assets supported by Recycle Bin can be quickly restored, avoiding requiring the user to discard needed changes.