Product Communities

The following are the REST API Enhancements we as a user are expecting to see it in near future. - Asset creator details to be included in the API (Email, Files, Campaigns etc.,)- Flow ID is returned in campaign API, however there is no endpoint to utilize and get the flow details- SmartList Cloning option is there, however there is no SmartList Update option (PUT method for updating the rules/criteria/conditions) via API. Likewise for Files, images can be created via API but there isn't an API option to update (PUT method) it. How come your product team ended up with just providing endpoints for reading and updating the meta data? Why should a development team in a company should create lines of code just to update a file name. I completely don't understand. - Final member count in a smartlist is not able to be pulled via API, again I'm not sure why this not considered as a meta information.- Worst pagination technique followed for returning records. While trying to pull the

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