Adobe Experience Manager

So, I have a scenario, We’ve more than 5000+ pdf and XDP to convert.we’re running on AEM on prem LTS.  Has anyone here done something similar? As this is going to be a lot of configurations, implementations and then migration. I need some guidance on how to achieve it. I am closely following documentation and seems like it should be easier process after the right configuration. Configure the Automated Forms Conversion service (AFCS) | Adobe Experience Manager I appreciate the help or any more documentation, if we have it. I have search on AEM forums but, didn’t find anything yet. 

 Request for Feature Enhancement (RFE) Summary: Provide configuration in AEM as a Cloud Service to control or disable the default video preview rendition (cq5dam.preview.mp4) generated by the standard Asset Compute processing pipeline. Today, cq5dam.preview.mp4 is created automatically for all supported video assets as part of the default Asset Compute processing profile and cannot be turned off by customers. We need a supported way to: Disable this preview rendition entirely (per program/folder), or Constrain it by file size/duration/resolution, or Mark individual assets/folders as “do not generate preview MP4”. The main driver is to reduce time-to-publish for large live content where downstream workflows depend on the original master, not on an internal preview proxy. Use-case: Customers ingest very large, high‑resolution video masters (e.g. 1 to 15 GB 4K MOV files) into AEMaaCS Assets in near real time during live events (e.g. sports, automotive races, conc

Hi There, We have a requirement where several custom dropdown fields have been added to the metadata schema of our assets (DITA files). During the translation process, AEM currently picks up the dropdown key value (the stored value) instead of the display label. This key is then sent for translation and applied to the translated language copy. As a result, the translated copy fails to load the corresponding dropdown option correctly in its properties. Additionally, all dropdown labels and options remain in English after translation. We would like to explore whether there is an OOTB approach in AEM to automatically localize or translate these dropdown labels across language copies. Thanks,Ravi Joshi

Default checked state is not appearing for coral checkboxes"granite/ui/components/coral/foundation/form/checkbox"but it's working fine for granite foundation one. i.e. granite/ui/components/foundation/form/checkbox. I've tried many ways (e.g. checked (string) property setting as true, defaultChecked / uncheckedValue etc.) but nothing is working. One thing noticed that, "checked" property has type  ' booleanel ' while in JCR, only boolean is available;not the expression lang type. So,is it causing any issue?  Any pointers on this will be really helpful.

Hello,We have an AEM integration in place with Adobe Target. We're encountering a replication error when publishing pages that contain activities. Saving the activities works fine—there are no errors, and the activities are successfully synced to the Target workspace. However, when we attempt to publish the page, we receive an error related to Goal Metrics.Please note that we don't require any tracking.Has anyone experienced this issue before? If so, what was the resolution? Any insights or guidance would be greatly appreciated.  Error.log:2025-09-08 20:08:36 - ERROR - test_and_target : Error replicating /content/campaigns/project/experience/test-experience - com.day.cq.analytics.testandtarget.TestandtargetException : com.adobe.tsdk.common.TSDKException: Unable to parse goalsandsettings from json.metricsJson:{"goals":{"metrics":[{"title":"MY PRIMARY GOAL","postGoalSuccessAction":"","type":"engagement","worth":"","engagementType":"pageViews","metricLocalId":10}]}} @davidj

Hi All, I am using adaptive form core component in aem as a cloud. After create a new theme, i am creating a core component adaptive form buts its not visible and not available to select only the default theme Canvas is available. Can some the correct way to create theme for core component adaptive form and how to use it while creating the form, so use that on localhost aem server.

In my dispatcher_httpderror log, I keep getting the following messages. Fri Oct 10 23:59:24.646793 2025 [managed_rewrite_maps:debug] [pid 123] [cm-p123-e123-aem-publish-123] Managed rewrite maps check in progressFri Oct 10 23:59:24.650947 2025 [managed_rewrite_maps:debug] [pid123] [cm-p123-e123-aem-publish-123] No managed rewrite maps configuredFri Oct 10 23:59:24.655150 2025 [managed_rewrite_maps:debug] [pid123] [cm-p123-e123-aem-publish-123] Managed rewrite maps check DONEFri Oct 10 23:59:24.659466 2025 [managed_rewrite_maps:debug] [pid123] [cm-p123-e123-aem-publish-123] Waiting for 30 seconds for next managed rewrite maps check I am not using any Apache RewriteMap directive on my setup.These errors pollute my log and have no value, how can I get rid of them?And I want to keep the debug level, so that I can see the REAL errors 

trying to execute "aio login" and result is:Visit this url to log in: https://aio-login.adobeioruntime.net/api/v1/web/default/applogin?id=********&port=*****&redirect_uri=https%3A%2F%2Faio-login.adobeioruntime.net%2Fapi%2Fv1%2Fweb%2Fdefault%2Fapplogin%2Flogin-success - Waiting for browser loginnode:events:497 throw er; // Unhandled 'error' event ^ Error: spawn undefined\System32\WindowsPowerShell\v1.0\powershell ENOENT at ChildProcess._handle.onexit (node:internal/child_process:285:19) at onErrorNT (node:internal/child_process:483:16) at process.processTicksAndRejections (node:internal/process/task_queues:90:21) Emitted 'error' event on ChildProcess instance at: at ChildProcess._handle.onexit (node:internal/child_process:291:12) at onErrorNT (node:internal/child_process:483:16) at process.processTicksAndRejections (node:internal/process/task_queues:90:21) { errno: -4058, code: 'ENOENT', syscall: 'spawn undefined\\System32\\WindowsPower

Hi AEM Community, I'm working on migration project , migrating from classic UI to touch UI. we have one button on siteadmin navigation bar called "start workflow" when clicked content tree dialog will open first where user where dialog will open with selected page(s) will show along next and cancel button if user selects next button then workflow model screen will load where model will be prepopulated. To achieve same in touch UI I have create a button at /apps/wcm/core/content/sites/jcr:content/actions/secondary/wokflow-button and below is xml<?xml version="1.0" encoding="UTF-8"?><jcr:root xmlns:sling="http://sling.apache.org/jcr/sling/1.0" xmlns:granite="http://www.adobe.com/jcr/granite/1.0" xmlns:cq="http://www.day.com/jcr/cq/1.0" xmlns:jcr="http://www.jcp.org/jcr/1.0" xmlns:nt="http://www.jcp.org/jcr/nt/1.0"jcr:primaryType="cq:Page"><jcr:content jcr:primaryType="nt:unstructured"><actions jcr:primaryType="nt:unstructured"><secondary jcr:primaryTy

Hi Team, We are receiving CPU spike issues recently, so to troubleshoot we are planning to configure custom logger to capture gc.log. Could you please let us know some suggestions or class that captures gc.log, so that we can create loggers accordingly. We need to capture under crx-quickstart/logs folder. Kindly let us know some suggestions to proceed further. Thanks,Aishwarya Karthikeyan

I'm managing a couple of thousand pages across 2 websites and I want to automate the processes around identifying pages that haven't been updated recently i.e. by published date. I can output as an excel etc but are there any automations inside of AEM to assist with tasks like this?

Hi Team,I am facing an issue during the Maven build and installation of an AEM package to my local instance.The build completes successfully for all modules, but the All-in-one package fails during the installation step.Environment:AEM Version: (add your version, e.g., AEM 6.5.20 or AEM Cloud SDK)Java Version: (example: Java 11)Maven Version: (example: Maven 3.8.8)OS: (Windows 10 / macOS, etc.)Local AEM running on: http://localhost:4502  Full Error Snippet:Request to http://localhost:4502/crx/packmgr/service.jsp failed, response=Moved Permanently...Error while installing package. Check log for details.

I am encountering an unexpected behavior in AEM during the Page Publish workflow rollback scenario.When a parent page is activated (using Replicator.replicate) using a custom replication agent, the replication framework correctly triggers one invocation of PackageContentBuilder.create(which is an implementation of ContentBuilder class, and is configured through serializationType in the agent) for the parent payload.However, when the same parent page is deactivated (as part of rollback), the replication framework triggers multiple implicit invocations of PackageContentBuilder.create() — first for the parent, then for each of its child pages.This occurs even though only the parent path is explicitly passed to the Replicator.replicate() call. Raised adobe ticket and they confirmed that this is the OOTB functionality and we want to implement  a custom replication deactivation flow. Can anyone please suggest  how to  implement that.

I have encountered an issue while updating the page properties. There is a deny rule for everyone group as shown in the below screenshot. Users belonging to a specific group are unable to update page properties, even though they have Read, Modify, Create, and Delete permissions for the required path. The necessary permissions for /content have been granted, but these users continue to receive an error.To resolve the issue, I added the jcr:modifyProperties privilege, after which the error was resolved. However, I noticed that jcr:modifyProperties was not listed among the original privileges, and I verified the rep:policy node as well.Interestingly, when I remove the rep:write privilege and add only jcr:modifyProperties, I can see the entry, which suggests that jcr:modifyProperties is an aggregate privilege of rep:write. This raises the question: why did it not work when rep:write was granted, and why wa

Hi Everyone, I am developing an AEM component on AEMaaCS instance (headful approach).I need to get content fragment data and display it on the page using the AEM component in headful architecture. I am using Sling model to make a call to graphql endpoint. I used Apache libraries HttpGet, CloseableHttpClient to make a GET call to graphql endpoint.The code works fine in local AEM instance  but on AEMaaCS, it gives a "read timed out" error while making the graphql call. Any help in resolving this issue?  

 I have a package that install the etc map entries on my Publishers.I currently have some mapping configs there that are obsolete, but must be removed because they break the new correct mapping.all my mappings are located underneath /etc/map.exampleThe rule in the filter.xml is<filter root="/etc/map.example" mode="replace"/>so I would expect the whole tree underneath to be wiped and replaced (according to https://jackrabbit.apache.org/filevault/filter.html ), but this is clearly not what happens - I checked in the AEM cloud Publish Repository Browser and the old nodes are still there.Unfortunately the Repo Browser has no option to delete stuff. The nodes I need to delete are as follows:/etc/map.example/integration.publish/https/integration.example.com/redirect_old/etc/map.example/integration.publish/https/integration.example.fr/etc/map.example/integration.publish/https/integration.example.de/etc/map.example/integration.publish/https/integration.examp

Hi Everyone, We are currently encountering an issue with our AEM as a cloud setup. Our cloud instance is multi-tenant and includes five repositories. We have established Groups specific to our content paths, including an admin user group that has read, write, modify, delete, and replicate access to our content paths. The issue arises when any user who is part of this admin group attempts to move pages from one hierarchy to another. The move operation completes successfully, but it triggers a workflow called "Request to Complete Move Operation," which then accumulates in the workflow instances. However, when I, as the environment admin, perform the same move operation, the workflow mentioned above does not trigger. Could you please advise on how to ensure that the workflow does not trigger when users with all permissions (write, read, delete, modify, and replicate) perform the move operation? Thank you for your assistance in resolving this matter.

AEM Assets Content Hub serves as a centralised distribution hub for brand assets across marketing teams, agencies, and partners. It delivers fast search, curated collections, and governed asset delivery at scale. This blog explores how Content Hub’s extensibility model, powered by Adobe App Builder, enables organisations to embed custom workflows directly into the asset distribution experience. We’ll outline the business challenges and explain how extensibility works. Business Problem: Last-Mile Workflows in Content Hub For many organisations, Content Hub has become the go‑to portal for accessing brand assets across internal teams and external partners. While it excels at asset discovery and delivery, the “last mile” of work often happens outside the platform. Once an asset is found or downloaded, critical follow-up actions typically occur in disconnected systems, such as:  Task and ticket creation in project management or IT systems  Approvals in separate review tools  Rights and us

Adobe’s next‑generation video player for AEM Dynamic Media marks a meaningful shift in how customers can understand and elevate video engagement. With faster load times, improved accessibility, and adaptive streaming built directly into the viewer, customers now have the foundation they need to truly measure—not assume—how audiences experience their video content.Key ConceptsDynamic Media video viewer Blog Link Video Engagement ReportThe ChallengeVideo has become one of the most powerful storytelling mediums, yet most organisations struggle to see what actually happens after someone hits play. Even strong video content can underperform when the experience surrounding it creates friction. Slow starts or buffering can discourage viewers within seconds. Playback inconsistencies across devices can distort engagement results. Many teams rely on simplistic metrics such as views, which offer little insight into whether the story resonated or where audiences disengaged. This is why improving t

Hi All.Is there a risk in having more than 5k+ redirects managed by the Dispatcher? Is there any recommendation from Adobe to manage this specific scenario?Thanks.

In our Unlocking Content Hub Extensibility, we discussed the business value of extending AEM Content Hub. This technical guide outlines how developers can use Adobe App Builder to embed custom panels and workflows directly into the Content Hub UI. We will walk through a real-world implementation of an "Extend Expiry" integration.  Overview  Content Hub extensibility, powered by Adobe App Builder, allows developers to embed custom panels and workflows directly within Content Hub—bring business actions closer. Adobe App Builder is Adobe’s enterprise extensibility platform for building and deploying secure, scalable applications on Adobe-managed infrastructure. Core Capabilities:  Custom React UIs rendered inside Content Hub  Serverless backends via Adobe I/O Runtime  Modern development workflows with CI/CD support  Secure hosting and authentication managed by Adobe  Zero infrastructure to maintain   The Extension Point  The primary extension point is the Asset Details extension. This

Hi Team,I am using AEM as a cloud with Core Components-based Adaptive Forms and integrated form in my aem site. When the form is submitted, a default loading spinner appears.I would like to customize or replace this spinner so it matches our site’s branding.Could someone please clarify:    •    What is the recommended way to override the default submit spinner?    •    Which CSS class or JS event controls the submitting state?    •    Should this be handled through a custom client library (Sites or Forms-specific)?    •    Is there a supported, upgrade-safe approach without modifying /libs?Any guidance or implementation examples would be appreciated.Thanks

I am trying to create configuraion to purge workflows which are older than 100 days for AEM as clouds service.Documentation -https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/operations/maintenance Above link says to create a node under /conf where as the link below asks you to create node under /apps for maintenance window.Sample configuration - https://experienceleague.adobe.com/en/docs/experience-cloud-kcs/kbarticles/ka-25921#environment  I'm trying to determine the correct way to create a maintenance window. I used the sample configuration and it worked, but after reviewing the documentation for second time, I realized that the maintenance window is supposed to be created under /conf. So what is correct place to keep this configuration?