On AEMaaCS, the fix is to undo the split and remove the extra dam index; then control behaviour via the query, not via multiple indexes. Steps to revert: Restore damAssetLucene-13-custom-1 In your repo, openui.apps/src/main/content/jcr_root/_oak_index/damAssetLucene-13-custom-1/.content.xml.​Paste b...

Hi @AishwaryaKa , The error comes from the Translation service failing to resolve a valid Translation Cloud Config/provider for the pages you’re adding. The NPE is thrown in TranslationCloudConfigUtilImpl, so the job setup in the Projects console fails, even though the language copy is created under...

Hi @EddieHuang , In AEM as a Cloud Service, the Touch UI RTE intentionally normalizes inline CSS (including colors) when it sanitizes HTML.#FF0000 and rgb(255,0,0) are treated as equivalent, and AEM converts to rgb(...) as part of its internal parsing/serialization.There is no supported config or ho...

Hi @Jerome_LeslyVi , A 504 on your custom POST servlet means AEM Publish is taking too long to respond; dispatcher just times out. Because it’s intermittent and only on prod, the problem is almost always resource contention or slow work in the servlet under real load/content. Focus on these 4 thing...

Hi @SheilaMc1 , Yes, AEM Assets (DAM) is platform‑agnostic and can integrate with Shopify (and similar systems) via APIs and custom development, even though there’s no native, out‑of‑the‑box Shopify connector today. How it’s usually done technically: AEM => Shopify product pages Store product/catalo...

Hi @KeerthanaHN , In AEM as a Cloud Service you can’t set manual priority between indexes. Oak always picks the index with the lowest cost that matches the query. Right now: You have two full‑text indexes covering dam assets: customindex-1-custom-1 (only /content/dam/targetfolder-1)damAssetLucene-1...

Hi @KeerthanaHN ,Solution A: single customized damAssetLucene + query‑side control This is usually the safest way in AEMaaCS.1. Customize damAssetLucene correctly In a Cloud environment on latest AEMaaCS, download the current damAssetLucene-* from /oak:index using CRX package manager.In your codeba...

Hi @tushaar_srivastava , Out‑of‑the‑box timeline is intentionally single‑resource only. AEM 6.5 does not support showing/acting on workflow steps for multiple assets in the timeline panel, so what you see (timeline only when 1 asset is selected) is expected product behavior. To get bulk approve / re...

Hi @HarrisSo ,Public embed IDs used in client‑side URLs (e.g. Launch property IDs or clientlib hashes) are not considered sensitive and are expected to be visible in the browser. However, any API client secret, access/refresh token, private key, or technical account credential is sensitive: if expos...

Hi @SreenivasBr, For IMS/OAuth login, the flow is: 1. AEM redirects the browser to Adobe IMS / your IdP.2. User authenticates there.3. Browser is redirected back to AEM with an authorization code.4. AEM exchanges that code with IMS for an access token + user profile, then creates an AEM login cookie...