Idea Delivered

Thanks for posting the idea. We have, indeed got few requests from different customers to support customization in Data Pipeline.

We have implemented such support in Sites 10.1. Data Pipeline now supports custom resolvers.

And this implementation has been backported as a hotfix to Sites 10. Please contact CS for the hotfix.

Enhanced Granularity and Customization in Data Pipeline Control for Components

We require the ability to control publishing at the component level. This would allow editors to manage which content can be published or unpublished.


For example, if a component includes a "Publish Embargo Date" or "Unpublish Embargo Date" within its metadata, a custom resolver should prevent the publishing or unpublishing of the component based on that date.


This feature is particularly important when editors need to control specific announcements that must be available on the site for a designated period.


Currently, publishing can be controlled at the folder level or through schema settings. However, this option would provide significant benefits for scenarios that cannot be addressed through these means.

In earlier versions of Tridion (when datapublishing was not enabled), it was possible to implement this check and prevent publishing or unpublishing at the component level through a custom resolver.