Adobe Experience Manager

Request for Feature Enhancement (RFE) Summary: Currently in AEM DAM AVIF file are not supported. It would be required to support this format whenever user upload the image and want to use it in the content Use-case: When Author upload AVIF file (file with AVIF extension, file in AVIF format) to DAM THEN file is processed correctly, thumbnails are generated AND Author can use file in AVIF format on a page (eg. in the Image component) Current/Experienced Behavior: Author can't use file in AVIF format on a page (eg. in the Image component) Improved/Expected Behavior: Author can use file in AVIF format on a page (eg. in the Image component) Environment Details (AEM version/service pack, any other specifics if applicable):   Customer-name/Organization name:   Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: AEM sites Rollout and publication issue Use-case: When a editor rollout and publishes a master page, the publication process start publishing the live copies in random order and fails when it encounters any market page that is locked to a user. This results in inconsistencies leaving the page changes published to few random markets. Ideally this should have completely stopped or skip the locked page, deploy to rest and notify about skipped page. Current/Experienced Behavior: The rollout/publication does not follow a predictable sequence and succeed for markets until it encounters locked pages then silently fails making it difficult to track progress There is no summary or report indicating which locales were successfully published and which were skipped. This results in inconsistent rollout and makes it hard to identify which pages need manual intervention Improved   Before initiating rollout publication,

Request for Feature Enhancement (RFE) Summary: The new editor for content fragments allow to see translations (see screenshots) but doesn't allow to create a translations and you need go with the old editor with a bad UX experience Use-case: I'm an editor and I want to add a translations to a content fragments from the new editor and I need disable new editor go to assets folder and see translations versions and add new translations Current/Experienced Behavior: I'm an editor and I go to edit a content fragment. I click in the right panel and I see if has a translations if case I don't have a translation I can add a new translation Improved/Expected Behavior:   Environment Details (AEM version/service pack, any other specifics if applicable):   Customer-name/Organization name:   Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: API to get variation of Content Fragment Use-case: There is content fragment. Have to create variation of CF eg: FB , LinkedIn. Want to automate variation creation. Suppose we send content along with params like audience, Tone etc. On API hit we get the variation data. Current/Experienced Behavior: We have editor where we input data and get dariation. This variation we can copy paste or export as variation. Improved/Expected Behavior:   Environment Details (AEM version/service pack, any other specifics if applicable): AEM cloud service Customer-name/Organization name:   Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: display number on assets in list view Use-case: to have an easy way to know how many asset we select Current/Experienced Behavior: today we have a clear view of the total amount of assets in list view, but if we need to select only 35 assets (because of limitation on other flows for ex) then it's quite complex to do Improved/Expected Behavior: if in each line we have the number of line, then it's easier to do the selection Environment Details (AEM version/service pack, any other specifics if applicable): display number on assets in list view Customer-name/Organization name: Louis Vuitton Screenshot (if applicable):   Code package (if applicable):  

  Request for Feature Enhancement (RFE) Summary: Allow custom headers with dynamic value for assets to be added from AEM (for example, set header in the filter). Use-case: Integration of 3rd party search solutions to index content for search, for example AddSearch, but can be extended to any use case when custom header is needed. In case of AddSearch, pages are indexed by adding HTML meta tag, but for the assets this approach is not feasible. To enable indexing for the assets, HTTP header needs to be added as described in https://www.addsearch.com/docs/indexing/defining-custom-fields/ . Value of the header is dynamically defined by application (for example contains document type and file name). Current/Experienced Behavior: HTTP Headers are not present in the response. Filter is triggered and solution works fine on the Local SDK (screenshot attached), displaying proper values both on publish and dispatcher. Header is removed when redirecting asset request towards bin

Request for Feature Enhancement (RFE) Summary: Provide the ability to add custom validation to the OOTB fields created via the CF model editor. Use-case: We have the following use case: two multifields. If one contains X items, then the other one needs to contain X items, or the validation should fail and show an error message to the editor. Current/Experienced Behavior: Currently, custom validation can only be added for custom fields. However, we do not want to add custom fields, we only want to add custom validation to the existing OOTB fields. Improved/Expected Behavior: Add an extension point for developers to define custom validation using an Adobe IO plugin. Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS 2024.10.18311.20241017T104455Z Customer-name/Organization name: Assa Abloy Screenshot (if applicable): Code package (if applicable): No example documentation found in: https://developer.adobe.com/uix/docs/services/aem-

Request for Feature Enhancement (RFE) Summary: Provide the ability to define which RTE plugins to show to editors Use-case: In different CF models using richtext, we do not want editors to have all RTE options available, and we want to limit them to only a few, like: bold, itand alic, bulleted list. Current/Experienced Behavior: Currently, all default RTE plugins are shown to editors, and we have an option to add custom plugins. Improved/Expected Behavior: Have an option to define which RTE plugins to show, define a subset. Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS 2024.10.18311.20241017T104455Z Customer-name/Organization name: Assa Abloy Screenshot (if applicable): Code package (if applicable): No example documentation found in: https://developer.adobe.com/uix/docs/services/aem-cf-editor/api/

Request for Feature Enhancement (RFE) Summary: Add the ability to select/pick a folder in the new CF editor Asset picker Use-case: In some CF models, our editors must pick a folder, not an asset. We have a logic in our web component to display all assets within that folder. Those assets may change over time, and we always display all of them; we do not want editors to pick assets 1 by 1. Current/Experienced Behavior: Editors can only pick assets, not folders. Improved/Expected Behavior: Editors should be able to pick both assets and folders. Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS 2024.10.18311.20241017T104455Z Customer-name/Organization name: Assa Abloy Screenshot (if applicable): Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Add mimetype of svg files to DAMUtil.java as it is read only file. Use-case: Since it is an image mimetype, replace should happen between svg/png/jpeg etc. Current/Experienced Behavior: Currently we are unable to replace a jpeg/png with svg as it is not treating it as image mimetype in Dynamic Media Improved/Expected Behavior: We should be able to replace. Environment Details (AEM version/service pack, any other specifics if applicable): DEV/STAGE/PROD Customer-name/Organization name: Signify  Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: When bulk editing assets after selecting multiple assets and opening the details, the interface should allow for editing meta data individually as well as in bulk.    Use-case: When uploading multiple files it is often necessary to create individual as well as group metaproperties. With the suggested feature, one can do this is one single step instead of opening and editing all files individually.   Current/Experienced Behavior: 1) Selecting multiple assets 2) opening details 3) editing common meta data, e.g. attaching a meta property, tag, description etc to ALL files at once 4) when saving ONLY the common attributes applied to all assets are saved   Improved/Expected Behavior: 1) Selecting multiple assets 2) opening details 3) editing common meta data, e.g. attaching a meta property, tag, description etc to ALL files at once while all are selected 4) selecting only certain desired assets individually (in the

Request for Feature Enhancement (RFE) Summary: Scheduled content sets for content sync Use-case: We have more than 60 sites on our AEM instance (and growing). There are days where we use to create content packages to sync all these sites content from Prod to lower enviroments.We were very happy to see the feature "Content sets", which made sync easy. Now we have to manually run sets for the sync process every two weeks. Current/Experienced Behavior: Executing the Content sets manually Improved/Expected Behavior: Ability to schedule the executing of content sets Environment Details (AEM version/service pack, any other specifics if applicable):   Customer-name/Organization name:   Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Re-label the home icon with "Experience Hub" as this is exactly to which the editor is routed once he clicks on the icon. He is actually already in the Experience Manager itself - in this case the start page! Use-case: The newly introduced icon confuses our editors. For them the AEM start page is their entry point to maintain websites and they are in the Experience Manager - if they click on the icon they will routed to Experience Hub and not like the label tells them to Experience Manager. Current/Experienced Behavior: Label is totally misleading and conflicts with the indicator in the upper left corner which actually tells you that you are in Adobe Experience Manager already. If editor click on the icon they will end up on Experience Hub. Improved/Expected Behavior: The home icon should be correctly labeled with "Experience Hub" to make it clear to where the editor is routed, once he clicks on it! Environment Details (AEM vers

Request for Feature Enhancement (RFE) Summary: Adobe Assets currently provides limited reporting capabilities for shared links. Admins lack visibility into which assets within specific folders were shared, how often, and whether those links were engaged with, clicks or downloads. This feature request proposes an enhanced Share Link Report that allows folder level targeting and includes detailed engagement metrics.  Use-case: As an admin, I want to:  Identify which assets in a specific folder were selected and shared via link.  See who created the share link.  Track whether the link was clicked.  Determine if the asset was downloaded via the share link.  This visibility is crucial for understanding asset engagement, optimizing content strategy, and ensuring proper usage and compliance.  Current/Experienced Behavior: The existing Share Link Report under Assets > Reports provides a basic overview of shared assets. It includes the asset name,

Request for Feature Enhancement (RFE) Summary: Content picker in the New CF Editor allows only browsing assets, not sites/pages. Use-case: Our CF models contain CTAs linking to pages. Current/Experienced Behavior: Editor needs to manually find and copy and paste the correct link to a page. Improved/Expected Behavior: Editors should be able to use Sites Content Picker pupup to select a page Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS 2025.8.22171.20250828T220440Z Customer-name/Organization name: Assa Abloy Screenshot (if applicable): Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Implement PSAs so that they can appear in all of the AEM UIs Use-case: The content operations team is looking to create a PSA or Alert bar/popup that would appear for all/some users on the platform when they log in. Current/Experienced Behavior: Adobe proposed this solution: https://adobe-consulting-services.github.io/acs-aem-commons/features/system-notifications/index.html Results research: I have researched and tried out the ACS Commons System Notifications in the past already. Those only work in the "old" AEM UI, not in the "new" CF Admin/Editor or Universal Editor. So any author directly going into those UIs would never see the notifications. And even authors accessing the old UI might be confused since it disappears on the new UIs. They might think only the old UI is affected by whatever the notification says. Improved/Expected Behavior: 1- it would stay up as long as we need it (if we posted a message about an o

Request for Feature Enhancement (RFE) Summary: AEMaaCS - CloudManager - Track disk usage  Use-case: Ensure that AEMaaCS clients are aware of their disk usage. Especially in times of performance issues, a transparently available monitoring of disk usage would help AEMaaCS projects to improve their setup. Current/Experienced Behavior: There is no disk usage monitoring available in AEMaaCS (in the CloudManager or elsewhere). Without Adobe Support input, a customer doesn't know this parameter. Alternatives via ACS AEM Commons reports are too time-consuming (XLSX work afterwards) or limited in scope (Asset reports only, no other content or full OS).   VW's Adobe Ultimate Support recommended I open a ticket here when they couldn't find a suitable functionality in AEMaaCS (E-001835519) Improved/Expected Behavior: In AEM 6.x Cloud Manager, such a feature already exists: https://experienceleague.adobe.com/en/docs/experience-manager-cloud-manager/content/using/monitori

Request for Feature Enhancement (RFE) Summary: Introduce a visual indicator and count display for hidden components within containers, sections, and background elements in AEM’s page editor interface. Use-case: Content managers need to easily identify and manage hidden components on a page during editing. This visibility is crucial for maintaining content accuracy, avoiding duplication, and ensuring that hidden elements are not unintentionally overlooked. Current/Experienced Behavior: Hidden components are not clearly distinguishable in the AEM page editor. There is no count or visual cue indicating how many components are hidden within a container or section. Additionally, the content tree does not reflect hidden components, making it difficult to locate and manage them across different device views (desktop, tablet, mobile). Improved/Expected Behavior: Display the number of hidden components within each container, section, or background element directly in the edit mode. S

機能改善要求（RFE）概要： Show each item's path in the CF console list ユースケース： We live-copy the master CF to multiple paths. We need a way to find live-copy items other than the master item and to edit or unpublish items only in selected paths.  現在／体験した動作： Even after filtering, numerous items with the same title and identical folder names are shown, making it impossible to identify the item's path. We spend a lot of time each day managing CF. 改善／期待される動作： Show an item's path in the search results, or reveal the path when you hover over the item. 環境の詳細（AEM バージョン／サービスパック、もしあればその他の詳細）： AEM as a Cloud Services 顧客名／組織名 - スクリーンショット（ある場合）   コードパッケージ（ある場合）  

Request for Feature Enhancement (RFE) Summary: Implement consistent error state styling and behavior for "aem-content" fields in Universal Editor, following the example of "text" fields Use-case: Required "aem-content" field validation in Universal Editor Current/Experienced Behavior: "aem-content" fields lack a red outline, a "red triangle with exclamation mark" icon on the right side of the input box and an aria-invalid="true" attribute. Improved/Expected Behavior: "aem-content" fields have a red outline, a "red triangle with exclamation mark" icon on the right side of the input box and an aria-invalid="true" attribute. Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS v2025.8.21994.20250818T175115Z-250700 Universal Editor Service v20250828133131 Customer-name/Organization name: AVIS BUDGET CAR RENTAL LLC Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Display complete configuration values in Cloud Manager. There is no need to truncate the values with (...). Better to wrap at line endings (as is done on the keys). I want to be able to validate/share/document the configuration at one glance without having to open each individual variable.   Use-case: Sharing / Documenting Environment configuration Current/Experienced Behavior: Values of environment variables are truncated after n characters  Improved/Expected Behavior: Values are displayed in full and wrapped if table width exceeded Environment Details (AEM version/service pack, any other specifics if applicable): Cloud Manager Sep. 22th 2025 Customer-name/Organization name: all Screenshot (if applicable):   Code package (if applicable): n/a

  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.