Hi @baw_gov , I am not sure what do you mean assets on the reports. You are expecting assets like images/pdf in report ? But if you want asset path or any other metadata as part of report, it can be configured.  

Hi @Ravi_Joshi , AEMaaCS provides OOTB Graphql API support for Content Fragments. https://experienceleague.adobe.com/docs/experience-manager-cloud-service/assets/admin/graphql-api-content-fragments.html?lang=en  Recently it is also enabled in AEM 6.5 SP 10.

Hi @Alex86 , extraClientlibs properties won't work during page creation. Please check the urls differences. 1. During page creationhttp://localhost:4502/mnt/overlay/wcm/core/content/sites/createpagewizard.html/content/wknd  /libs/wcm/core/content/sites/createpagewizard/jcr:content/head/clientlibs re...

Hi @imalakaamir , Please paste the actual error details. You have to scroll up a bit of your build logs to get it.

Hi @NitinL , Could you please check once in vanilla instance. If this issue still exists please raise this concern to support team. And I believe this issue is not only applicable to Content Fragment component required fields but for all the Component fields wherever required property is used.

Hi @jonasy18481676 , Please have an eye on this. I have raised this concern in github. https://github.com/AdobeDocs/experience-manager-65.en/issues/274 

Hi @jonasy18481676 , Instead of title KEY in body, Please try with jcr:title. It works. Postman  AEM  

Hi @uniqvaibhav , Could you please raise this in aem forms forum to get an expert advise https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager-forms/bd-p/experience-manager-forms-qanda

Please check the logs to find out if there is any issue.

Hi @derek20 , Publisher would be accessed via dispatcher, so you need to allow asset api json in dispatcher filters configuration. For eg. like below # Allow http api assets JSON /0101 { /type "allow" /extension "json" /path "/api/assets/<<project-name>>/<<cf-folder-name>>/*" }