Hi @jayv25585659 , The @SlingServletFilter annotation is part of Apache Sling, not AEM’s OSGi annotations. In AEM 6.5 / AEMaaCS, it often won’t be processed unless you also enable Sling annotation processing in your Maven build (via the Sling Maven SCR plugin or bnd). That’s why your filter works wi...

Hi @SatishNa , Workflows in Universal Editor–> Universal Editor itself does not have native workflow support yet.–> To enforce workflows, you configure AEM workflow launchers/policies on page activation in AEM. This way, when someone tries to publish from the Universal Editor, the action triggers yo...

Hi @chinmayis865517 , When you put a Dynamic Media video inside an Experience Fragment, extra wrapper markup and clientlibs get loaded, which slows down rendering. Make sure the Dynamic Media clientlibs are included only once (duplicate loads inside XF can cause delay). Check that the lazy loading c...

Hi @RadhaGa2 , You cannot start a workflow directly from the Content Fragment Editor in AEMaaCS. You can start a workflow for a Content Fragment, but you have to do it from the Assets console → Timeline → Start Workflow. Your custom workflow can include steps like review, approve, publish, or unpubl...

Hi @An___nie , Ingest metadata at source - Unlike photos, video tools (Premiere, After Effects, Media Encoder) don’t embed IPTC/XMP as cleanly. Encourage editors to set metadata in Adobe Premiere Pro (supports XMP), which AEM can read on ingest.AEM DAM Metadata Schemas - Configure custom metadata fo...

Hi @FabianaBa , Here are some short, practical tips for setting up AEM Assets 6.5 Managed Service Shared Links: Enable sharing in AEM Assets console - Admins must configure the Asset Link Sharing option in OSGi (Day CQ DAM Commons Link Externalizer).Externalizer setup - Make sure your publish domain...

Hi @Mahesh_Gunaje , Connected Assets is used when you want to share a central DAM across multiple AEM Sites instances. It avoids duplicating assets, ensures brand consistency, and saves storage. The trade-off is setup complexity and some performance dependency on the connection between instances. Dy...

Hi @alisa-dev , That warning means your custom service users are still using the old ACL-based permissions, but Adobe now requires principal-based access control (PBAC) for all system users in AEMaaCS and modern AEM 6.5 setups. In simple terms:- instead of granting permissions with classic ACLs, you...

Hi @PoovithaSelvaraj , In AEM MSM, the default rollout copies everything from the master to the live copies, which is why unwanted pages like sandbox content also get rolled out. To fix this, you need to create a custom rollout action that checks the replication (publish) status of each source page ...

Hi @datnguyenfiserv , In AEM as a Cloud Service (and newer AEM versions), anything under /etc/designs is deprecated and no longer accessible. That’s why your JS file returns 404.   The fix is to move your client library to /apps/<project>/clientlibs or /apps/<project>/frontend, and include it using ...