@Zendark  - See if below article is helpful:https://levelup.gitconnected.com/aem-conditionally-show-or-hide-fields-in-touchui-dialogs-with-coral-3-ie-aem-6-3-bfd48c261012

@sharaj  - Do you have any variation/variations for this Content Fragment. I am not sure if we can copy the variation, try if any variation exists and if we are able to copy it.

@Sammy_Kumar - Checkout this documentation : https://helpx.adobe.com/experience-manager/using/configure-touchui-rte.html

@RahulSi13  - Link for sourceedit plugin addition : https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/how-to-add-sourceedit-to-touchui-dialog/m-p/264857 Link for Custom plugin: https://www.bounteous.com/insights/2022/01/06/custom-rich-text-editor-plugins-adobe-experience-mana...

@ShikhaSharma  - I think the extra clientlibs are being loaded from your template or having some dependency due to which it is pulling the depenedent clientlibs. Try checking your dependencies and the defined clientlibs at template level.

@BenDu3 - I would recommend going through the SPP Portal and cover each topic listed there and you checkout the below udemy course which i found online:https://www.udemy.com/course/aem-forms-backend-developer-exam-prep-ad0-e127/?utm_source=adwords&utm_medium=udemyads&utm_campaign=Search_DSA_GammaCat...

@s1101v  - Can you please mention the use case that, like you want to access the templates/CF or anything specific inside the /conf folder. You could give permissions to users to specific template or CF Model from User Management.

@Tarun_Kumar_ReddyGo  - I can just see the warnings but not the errors. Also could you please check if crx-quickstart exists in same directory and try re-run the Jar to launch AEM in 4502.

Use Query Parameters ProperlyEnsure that the query parameter is correctly appended to the URL using ? for the first parameter and & for subsequent ones. For your variation parameter, it should follow the proper query string format. Example: bashhttp://localhost:4502/graphql/execute.json/wknd/Emplo...

@RahulSi13  - Please check if you are using the correct template where policies are defined. Also the Style System props are seen at the root of the component. But as per the screenshot i think you are looking for it further down.