New features 4.1.x

This section explains the various new features introduced with release 4.1.x of Sitecore Content Hub™.

New feature Description
New media delivery service to replace satellites
What? The new media delivery service with CDN to replace satellites.
How? The delivery network has been separated from the application to create an independent service with Cloudflare's CDN layer on top while keeping all current functionalities.
Why? Along with the microservices already created (content delivery service, media processing service, identity service, and consumption tracker service) and our journey towards SaaS (software as a service); we need to create a media delivery service decoupled from Content Hub to replace the current delivery network and satellite infrastructure.
In addition to the benefits of decoupled services (more reliability, faster recovery time, reduced resource consumption and costs, etc.), Cloudflare enables us to achieve higher performance data delivery with high reliability and flexibility, also at lower costs than our current delivery infrastructure.
Support for animated gifs
What? The ability to ingest and visualize animated GIFs in Content Hub.
How? Extension of media processing with a new flow for GIFs and introducing a new GIF previewer to visualize GIFs in asset details page (no inline preview from search, only from the details page in 4.1).
Why? There was no support for animated GIF files in Content Hub. Supporting GIFs was requested by customers and contribute to the overall Sitecore Digital Asset Management (DAM)™ strategy of supporting the broadest range of media files possible.
Pluggable previews
What? The ability for superusers to configure a viewer for currently non-supported file formats.
How? A new setting was introduced to map input formats or renditions to a viewer. The mapped viewer can either be an internal viewer provided out-of-the-box or an external viewer that requires configuration via an external component within the same setting.
Why? Visual previews are essential in Sitecore DAM to identify assets quickly, navigate through them, and minimize the number of file downloads that could be required otherwise. Since files come in various formats, which are sometimes proprietary, we have implemented a generic solution for end-users to configure their own viewers according to their needs in terms of file visualization.
Bulk download of public collections
What? Ability for users, with whom a collection has been shared, to download all assets from that collection at once.
How? A new bulk download operation was introduced on the public collections page, which enables users to create a ZIP package with all assets from the public collection in one click.
Why? The previous implementation only provided a single download for assets within a public collection, resulting in a repetitive and time-consuming process to download multiple assets. This new capability solves that issue.
Bulk download of Chili/print publications
What? The ability for end-users to select multiple publications and a quality/output format to create one download package.
How? We have introduced a new download order operation and a new download order page for publications.
Why The Chili integration previously only provided a single download for publications, resulting in a repetitive and time-consuming process to download multiple publications.
Custom CDN support
What? The ability for customers to use their own CDN.
How? We have introduced a new setting for superusers to configure their own content provider.
Why? This additional capability enables public links to render using the customer's content provider when displaying URLs or URL placements through Sitecore XP or SFMC connectors.
Reference content
What? The ability to create relations between content items, which allow you to combine the building blocks and produce the final content faster.
How? We have implemented the ability to link multiple content items to each other through a reference field.
Why? Dividing the content into smaller pieces and identifying the variables per channel or audience allows you to gain time while producing the content for specific needs. This feature also reduces duplication because you only create content once and reference it everywhere needed.
Shared scripts
What? The ability to share and reuse script code.
How? A shared script is referenced by another script and exposes a simple method.
Why? We have implemented shared scripts, which allow you to share and reuse script code.
Script telemetry
What? Understanding which scripts are being executed.
How? The Scripts page includes quick display boxes to help you understand the script telemetry. The display boxes show the following details:
  • Most run scripts: listing the top two most run scripts.
  • Longest running scripts: listing the top two longest-running scripts.
Why? Developers need insight into what caused scripts to run, how long they took, and what entities they impacted.
Fluent SDK
What? The fluent SDK is a wrapper that builds on top of the existing SDKs.
How? The fluent SDK allows users to manage Azure resources like create, update, or delete. The fluent API reduces the complexity of classes and their objects by chaining methods.
Why? The fluent SDK is a wrapper that builds on top of the existing SDKs and allows you to perform certain operations in a fluent manner.

Can we improve this article ? Provide feedback