Hi @SaverioHe, There is a hotfix package released by Adobe, and it is available under Software Distribution: https://experience.adobe.com/#/downloads/content/software-distribution/en/aem.html?package=%2Fcontent%2Fsoftware-distribution%2Fen%2Fdetails.html%2Fcontent%2Fdam%2Faem%2Fpublic%2Fadobe%2Fpack...

Hi @Srikanth23696837zrx0, Relying on events, event handlers etc will not work. Mainly because all of them are triggered after specific node/resource is removed - so it is too late to read any information. This is actually what you already observed on your own. You can try solution that base on WCMCo...

Hi @RajeshGa8, Sling Data Fetcher is part of Apache Sling GraphQL Core, which is not part of AEM out of the box. You need to make sure that Apache Sling GraphQL Core bundle is installed and active on your instance (manually or via package). Without it, registering custom fetcher will not be possible...

Hi @agyawa, I do not think using granite:rendercondition is the way to go. Main reason is that granite:rendercondition is designed to conditionally hide GUI elements, not necessarily content paths. It also might not be possible to use it against content paths. I am not sure what exactly is your case...

Hi @agyawa, This might not be possible. Or in other words, what you can see could be expected result. Please check official documentation about built in users/groups. Even if you set a 'deny-everyone' on a node, the administrators can still access the node Link to documentation: https://experience...

Hi @Magicr, I have checked it on fresh AEM 6.5 with SP24 instance, and it is working fine for me. I am getting a screen that allows me to edit a selected workflow model. Could you please check following aspects: After clicking Edit button, could you confirm if there is a correct extension for url op...

Hi @UserSD, Have you tried to use OOTB User Synchronization mechanism? Here is a link to documentation that describes, how it works, what are the limitations, and how it can be configured. https://experienceleague.adobe.com/en/docs/experience-manager-65/content/security/sync#

Hi @Magicr, If you are using AEM 6.5 you can consider to use below tool from ACS Commons, so you may not need to implement anything custom. https://adobe-consulting-services.github.io/acs-aem-commons/features/package-garbage-collector/index.html However if the implementation is still the key, you ca...

Hi @GopiTh, Classic UI is not available in AEMaaCS. You can still find it in AEM SDK, so local version of AEMaaCS, but this is only due to fact AEM SDK is not fully reflecting AEMaaCS. There is no way to enable Classic UI on AEMaaCS. Here is documentation that clearly indicates which features are de...

Hi @jooca, According to Adobe documentation AEM 6.5 LTS you have to use apis classifier in your pom every time you are including 6.6.0 uber-jar dependency in your project pom files. It is because unlike in AEM 6.5, in LTS all public apis are now part of uber-jar-6.6.0-apis.jar not uber-jar-6.6.0.jar...