Hi @DennisAtDept  Please check if helps https://medium.com/@arunpatidar26/cq-iscontainer-property-in-aem-94e5318e04fa 

Hi @Mahesh_Gunaje  I think it is expected since the url is not relative(path + anchor). you can go with two fields in order to support MSM path conversion.

Hi @Nitesh-Chavan  Please check https://sourcedcode.com/blog/aem/checking-run-mode-from-sightly-htl-in-aem  

Hi @ButhpurKiran  You can use Firefly APIs to generate images  https://developer.adobe.com/firefly-services/docs/firefly-api/guides/api/image_generation/V3_Async/    You need to create your own clientlibs to call APIs

Hi @KARTHIKAV1  I don't think so if there are other configuration, try to restart MSM Bundle or if trying in local try to restart felix console or AEM 

Hi @veerareddyc1015  You can apply only one policy to one component within a structure. To restrict the components, you may need another template.

Hi @veerareddyc1015  Maybe you can try using Style System, if style change is for a component. https://experienceleague.adobe.com/en/docs/experience-manager-65/content/sites/authoring/siteandpage/style-system    However the better solution is to inject additional project specific CSS from context-aw...

Hi @Mahesh_Gunaje  Once the extension request is approved, the extension immediately becomes active in the AEM as a Cloud Service Author services.

Hi @ManjulaKumar  try http://localhost:4502/editor.html/libs/settings/workflow/models/scheduled_tree_activation.infinity.json 

Hi @Mahesh_Gunaje  I believe you can use Jenkins or any other CI/CD tool to automate manual process/commands. Adobe provide the postman collection to get token and other thing you can convert those to API calls in your pipeline.