Hi @jayv25585659 , IntelliJ cannot find com.adobe.acs because the wrong artifact is used in your pom.xml. The acs-aem-commons-all is only a content package (ZIP) and acs-aem-commons-bundle doesn’t exist for Cloud. You need to use the correct artifact acs-aem-commons-bundle-cloud. Update your depende...

Hi @gischellatte  If you're using a personal Adobe account, you won’t be able to access AEM or download the installer — because AEM is only available to enterprise (company) accounts.Here’s what you should do:Log out of your personal Adobe account.Log back in using your company email — choose “Compa...

Hi @gischellatte , Why the error happens:Your Adobe ID is not linked to an active Adobe Experience Cloud (AEM) product profile.It’s an access issue, not a browser/cache problem.What to do:Contact your company’s Adobe AdminAsk them to add your Adobe ID to the AEM product profile in adminconsole.adobe...

Hi @Divya_T13 , Yes, the "Replace" option in AEM works differently — it directly replaces the asset without going through the normal upload process, so your custom logic (like SlingPostProcessor) doesn’t get triggered.Since this is expected behavior, the best way to keep the previous metadata is to ...

Hi @Divya_T13 , In AEM 6.5, when you use the "Replace" option in the Assets UI, it does not trigger a Sling POST, which means SlingPostProcessor will not execute. This is expected behavior and not a bug.The "Replace" functionality uses a different servlet internally, bypassing the standard upload fl...

Hi @VivekSr5 , You're seeing this error because you're trying to edit a workflow that lives in the /libs folder — and in AEM as a Cloud Service, anything inside /libs is read-only. That means you can view it, but you can’t make changes to it.To fix this, you need to make a copy of the workflow and s...

Hi @Divya_T13 , In AEM 6.5, when an asset is re-uploaded (using the "Replace" option), its binary and metadata are immediately overwritten before the DAM Update Asset workflow is triggered. This means you cannot retrieve the previous metadata within the workflow because it's already lost by that poi...