Product Communities

  Request for Feature Enhancement (RFE) Summary: When the number of configuration variables grows, it could help to order them  alphabetically to easily spot if sth. is missing. Also, when a setup contains of multiple modules, ordering would keep items clustered, when prefixed: LOGIN_BAR=..LOGIN_FOO=..WORKFLOW_XX=..WORKFLOW_YY=.. Use-case: Validate environment configuration  Current/Experienced Behavior: Variables are mixed randomly, variables with the same prefix are not clustered Improved/Expected Behavior: Variables are ordered by key.  Environment Details (AEM version/service pack, any other specifics if applicable): Cloud Manager Sep. 22 2025 Customer-name/Organization name: all Screenshot (if applicable):   Code package (if applicable): n/a

Request for Feature Enhancement (RFE) Summary: Keep Side Panel Functional After Page Selection Use-case: AEM Author GUI speed Current/Experienced Behavior: In Sites view, the side panel (Filters, Timeline, References, etc.) can only be used before selecting a page. Once a page is selected, the panel becomes not clickable/useable. Keeping it functional after selection would allow authors to filter, check references, or review details without deselecting the page. Improved/Expected Behavior: Side panel remains interactive after a page is selected Functions such as Filters, Timeline, and References are fully usable while a page is selected Applies in Sites view and similar contexts where the side panel is available Environment Details (AEM version/service pack, any other specifics if applicable): AEM Cloud Customer-name/Organization name: Sanitas Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Enable Side Panel in Image Component Dialog Use-case: AEM Author work speed Current/Experienced Behavior: When editing the Image component, the side panel for browsing and selecting DAM assets cannot be opened.  Improved/Expected Behavior: Allowing the side panel to be accessed without closing the dialog would make it easier to choose or replace images directly from the DAM. Environment Details (AEM version/service pack, any other specifics if applicable): AEM Cloud Customer-name/Organization name: Sanitas Screenshot (if applicable):   Code package (if applicable):  

To improve clarity for content editors in AEM, consider adding a visual indicator at the top of the page being edited to highlight that the page has been modified post-publication. This would help address the ambiguity that arises over time with the current "last published" and "last modified" dates shown in months in the page properties dropdown. This would make it easier to spot discrepancies—such as when the page was published on the 5th but last modified on the 23rd—without needing to dig into metadata. See screen capture attached.  

Request for Feature Enhancement (RFE) Summary: In Cloud Manager, sort Pipelines alphabetically Use-case: In Cloud Manager, sort Pipelines alphabetically to more easily find the pipeline one wants to work on and also prevent from accidentally starting the wrong one (after all, they are usually called similarly, and sorting them top to bottom would make it more apparent, that e.g. lower envs are further up).Example00 - dev - Dispatcher01 - dev - Config 02 - dev - AEM 03 - stage - ...  Current/Experienced Behavior: Pipelines are order randomly  Improved/Expected Behavior: Pipelines are order alphabetically Environment Details (AEM version/service pack, any other specifics if applicable): latest CM Customer-name/Organization name: any Screenshot (if applicable):   Code package (if applicable): n/a

Request for Feature Enhancement (RFE) Summary: In AEM, when creating a translation job via References -> select page, the dialog shows the checkbox “Select all subpages” at the bottom. Currently it’s pre-selected by default. This should be disabled. The checkbox should be unchecked. Use-case:   Current/Experienced Behavior: Checkbox “Select all subpages” is checked by default. Improved/Expected Behavior: Checkbox “Select all subpages” is unchecked by default. User can manually check it if they want to include subpages. Environment Details (AEM version/service pack, any other specifics if applicable): AEM Cloud Customer-name/Organization name: Sanitas Screenshot (if applicable):   Code package (if applicable):  

機能改善要求（RFE）概要： Allow users to set the default editor for opening Content Fragments from Assets ユースケース： Editing Content Fragment 現在／体験した動作： The editing behavior for Content Fragments differs between the New Editor and the Legacy Editor.For example, in the New Editor, you cannot disable inheritance from the live copy source, and you cannot enter external links. However, when editing a Content Fragment from Assets, the New Editor always opens. And you always have to switch editors manually. 改善／期待される動作： Allow users to set which editor opens by default. 環境の詳細（AEM バージョン／サービスパック、もしあればその他の詳細）： AEM as a Cloud Service 顧客名／組織名   スクリーンショット（ある場合）   コードパッケージ（ある場合）  

Request for Feature Enhancement (RFE) Summary: Our accessibility audit shows WCAG 2.1 AA violations when using placeholders alongside ARIA labelling on Core Form Fields Use-case: Using Adobe Core Form Fields, with ootb configuration "Display help message as placeholder” Example:  on page https://www.sunstargum.com/gb-en/about-us/contact-us.html Current/Experienced Behavior: 1. **Accessible name vs description conflict**- Inputs with `placeholder` + `aria-describedby` or visible `<label>` lead to inconsistent accessible name computation. Placeholder either doesn’t get announced (e.g., JAWS, NVDA), or is dropped in favor of description text, making it unreliable :contentReference[oaicite:1]{index=1}.- Relying on placeholder as label fails WCAG 2.1 AA: contrast (1.4.3), persistent visible labels (2.4.6, 3.3.2), Name, Role, Value (4.1.2) :contentReference[oaicite:2]{index=2}.2. **Placeholder distractions**- Placeholder text disappears once typing starts—users lose he

Request for Feature Enhancement (RFE) Summary: In the participant step of workflow. Some use cases where we need to double confirm with warning message. to avoid human error. it is not supported out of the box. By adding another step to confirm it becoming a user experience nightmareMay be a checkbox to ask only for specific participant steps in a workflow  Use-case: For example: if approving or publishing we need to double confirm. we need to cancel a workflow and revert to previous version. if user chooses that as the next step by mistake it will revert it and loose the work. Current/Experienced Behavior: it takes the input and moves along.  Improved/Expected Behavior: it will would give popup and ask the author to confirm encase of a condition Environment Details (AEM version/service pack, any other specifics if applicable): aem cloud Customer-name/Organization name: jnj Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Automatic Redirects for URL Changes If a page’s URL changes while it is live (due to a title change, page move, or unpublication), could AEM automatically generate a redirect to the new location? Ideally, authors should also have the ability to specify which URL to redirect to (e.g., another page or a 404 page). Use-case: If a page’s URL changes while it is live (due to a title change, page move, or unpublication), could AEM automatically generate a redirect to the new location Current/Experienced Behavior: A page url is changed, we will have to manually use ACS Common Tools to add in a redirect url.  Improved/Expected Behavior: Have a list of all redirects If a page’s URL changes while it is live (due to a title change, page move, or unpublication), could AEM automatically generate a redirect to the new location.    Environment Details (AEM version/service pack, any other specifics if applicable): &n

Request for Feature Enhancement (RFE) Summary: Bulk Page Movement Right now, AEM only supports moving one page at a time. This makes taxonomy updates and bulk redirects very time-consuming. Could AEM allow authors to select and move multiple pages simultaneously to streamline these workflows and move it to another location? Use-case: Currently, Adobe Experience Manager (AEM) only allows authors to move one page at a time. This limitation makes it inefficient to perform large-scale site restructuring tasks—such as taxonomy updates, reorganization of content folders, or implementing bulk redirects—especially for enterprise-level websites with hundreds of pages. By introducing a Bulk Page Movement capability, authors could select and move multiple pages simultaneously within the AEM interface. This enhancement would streamline content management workflows, reduce manual effort, and minimize human error during site reorganizations. It would also improve overall authoring efficien

Request for Feature Enhancement (RFE) Summary: Enable the ability to add custom fields to the Content Fragment GraphQL schema via code, SlingDataFetcher, or programmatic means, without requiring changes to the Content Fragment Model definition in AEM. Use-case: Developers and integrators need to expose computed, derived, or integration-specific fields in the Content Fragment GraphQL API for headless delivery, without modifying the underlying Content Fragment Model. Current/Experienced Behavior: The Content Fragment GraphQL schema is auto-generated from the Content Fragment Model and system fields. It is not possible to add custom fields via code, SlingDataFetcher, or other programmatic approaches. Business Impact  Limits flexibility for headless integrations, increases maintenance overhead, and requires model changes for every new field, which may not be feasible or desirable in large organizations or for computed/integration fields. Improved/Expected Behavior: Ability