Enable Preview for referenced content in AEM as Cloud Service

[#1]

Request for Feature Enhancement (RFE) Summary:	Enable Preview for referenced content in AEM as Cloud Service
Use-case:	Currently, Preview service is limited in the sense that referenced content associated with the page does not automatically get pushed to Preview and there is no option to Push to Preview for Assets, Tags, etc.
Current/Experienced Behavior:	Currently, Preview service is limited in the sense that referenced content associated with the page does not automatically get pushed to Preview and author has to use Add content option to include Referenced assets, tags, etc. The only option to do this in Bulk is to use a Workflow but that does not allow author to selectively distribute content.
Improved/Expected Behavior:	Page and all referenced content associated with the page should automatically get pushed to Preview or at least author should get an option to select the references and decide whether to push those.
Environment Details (AEM version/service pack, any other specifics if applicable):	AEM as Cloud Service Latest release
Customer-name/Organization name:	Abbott
Screenshot (if applicable):	Preview option missing for Assets.
Code package (if applicable):

[#2]

@rampai 

Basically the assets and tags used in the page you are publish to preview gets published as well to preview - this is what I observe.

But, I agree that I miss also the option to publish-to-preview the tags and the assets separately and, to have the preview columns also there to see the current status.

As workaround for publish just assets and tags to publish you can use the "+Add Content" button in the publish dialog of the sites. Here, you have also DAM and tag paths available.

Just a node on the include children option: this does work for /content/dam but not for tags - so be careful here

BR

[#3]

@rampai 

Thanks for proposing this idea

This has been reported to the engineering under the internal reference SITES-20526. The product team will triage this request to verify feasibility based on the prioritization model. This post will be updated according to the Jira request status.