Hello @lone_Ranger - Verify if the child node has its own ACL (Access Control List) defined that could be overriding the inherited permissions from the parent node. If the child node has its own ACL and the "modify" permission is not inherited, you can explicitly grant the "modify" permission to the...

Hello @JakeCham -  Have you tried below approach :  If the parentNode.getNodes("par*") call is only returning a single node named "par" instead of all nodes starting with "par", it could be due to the implementation of the JCR repository you are using.  if (parentNode != null) { NodeIterator it = ...

Hello @sreenu539 -  I see the same has been reported here https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/java-lang-unsupportedoperationexception-in-junit-test-content/m-p/546188  Looks like these methods are not supported yet with the wcm.io mocking library & I see the iss...

Thankyou @kautuk_sahni for considering  !!

Hello @Akumar78 -  Workflow History: Purging workflows may remove the historical records of completed workflows, including information such as start time, end time, participants, and execution details. If your custom timeline view relies on this workflow history data, it may be affected.Workflow Arc...

Hello @RoujCh -  Refer to : https://helpx.adobe.com/experience-manager/kb/aem-forms-vulnerability-cve-2021-44228.html  https://community.adobe.com/t5/creative-cloud-services-discussions/log4j-vulnerability-and-adobe-cc/m-p/12847864   

Hello @satishpothabathula - Confirm that the CF definition allows for the inclusion of multiple instances of the field. In the Content Fragment Models console, check the field's definition to ensure the cq:isMultiple property is set to true.Make sure the data structure of the field in the multifield...

Hello @Nilesh_Mali  -  Though, we do have option to run the pipeline in Emergency Mode (AMS instances) thereby skipping the security and performance test steps. However, there is no option to skip code quality test while working with AEM as Cloud Service. Refer https://experienceleague.adobe.com/doc...

Hello @maddy_23 - You are correct! Storing sensitive credentials, such as access keys or secret IDs, in code or config files is generally not recommended because it exposes them to all developers and potential security risks. Recommended Approach : Storing credentials as environment variables is gen...

Hello @SDusane -  Please refer to below link :  https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/assets/admin/asset-reports.html?lang=en