These are the paths which I've found from where its getting picked.- /libs/dam/cfm/admin/clientlibs/v2/adminpage/core.js- /libs/dam/cfm/admin/clientlibs/v2/adminpage/page.jsBut rather than overlaying, I've added custom script for this requirement, which is working as expected.

Hi @somen-sarkar, I have went through the thread which you mentioned. Its hiding for specific users. But in my case I've to hide based on authoring. Attaching screenshot for better understanding, here if a required field is not authored by default rest of options are disabled. So I want to implement...

I've implemented a new option for publish to preview, but I'm unable to find where to disable the option if required fields in my content fragment are not authored.Can anyone help me with the path in libs where Quick Publish and Manage Publication options are disabled if required fields are not auth...

Hi @Anilkumar9 After fetching the fragment data, you need to adapt to content fragment and iterate over the content elements like below. private HashMap<String, Object> myObj = new HashMap<>();ContentFragment fragment = fragmentResource.adaptTo(ContentFragment.class);if (Objects.requireNonNull(fragm...

@jayv25585659 Please refer this - https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/can-i-delete-policies-found-in-the-layout-containers/td-p/369385 Thanks!

@Sandeep_k_Singh Please refer this - http://www.sgaemsolutions.com/2019/01/showhide-tabs-and-fields-based-on-drop.html. Make sure you create in same structure as described.

@kautuk_sahni -- I didn't find any solution for this, as a workaround I have created new CFM, it's not showing as outdated, although I compared all the properties for the old and new remains same.

@Jagadeesh_Prakash yeah you are correct, its not showing as CFM is outdated in vanilla instance. But I wonder how my project code is affecting the CFM.

@Jagadeesh_Prakash yeah it seems strange, as replication time is also showing correctly.And as you suggested, I have verified my CFM and there are no warnings or indications.

Yeah content fragment is created at the correct place. I'm able to fetch the fields as well. My only query is whenever I'm publishing the page, content fragment model is showing as outdated, even though I publish the content fragment just now and when I publish my page, it again shows as content fra...