Adobe Experience Manager

Request for Feature Enhancement (RFE) Summary: This feature will enable organizations to define metadata validation rules based on compliance or guideline requirements and extract detailed reports for discrepancies. This will facilitate better data governance and streamlined updates to metadata across the organization. Use-case: Organizations often face challenges ensuring metadata adheres to evolving compliance regulations or organizational guidelines. Manual validation processes are time-intensive and error-prone, leading to non-compliance risks and inconsistencies in metadata quality. This feature addresses the need for automated validation and actionable reporting. Current/Experienced Behavior: Metadata validation is performed manually or using scripts, leading to inefficiencies. There is no unified interface or reporting mechanism to validate metadata against dynamically defined compliance rules. Discrepancies or outdated metadata are identified late, causing delays in re

Request for Feature Enhancement (RFE) Summary: Currently we are unable to see the user who last modified the asset. There should be field where the user who last modified the asset should be captured. Use-case:   Current/Experienced Behavior: Unable to see the user who last modified the asset. Some hard coded value like "dam-workflow-service" is seen for now. Improved/Expected Behavior: Instead of "dam-workflow-service" username or user email who last modified the asset should be there. Environment Details (AEM version/service pack, any other specifics if applicable): Prod/Stg/Dev Customer-name/Organization name: Signify Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Allow customize wywisyg inline and richtext. At the moment is limited the wysiwyg and only allow some actions instead to use the full power of the wysiwyg. Use-case:   Current/Experienced Behavior:   Improved/Expected Behavior: With universal editor at the moment is imposible to customize or extend buttons for wysiwyg inline and richtext component. Should be fantastic to have configuration to allow hide/add new buttons in the wysywig. One simple thing as a color picker. Environment Details (AEM version/service pack, any other specifics if applicable):   Customer-name/Organization name: Santander Screenshot (if applicable):   Code package (if applicable):  

機能改善要求（RFE）概要： This is a consultation about applying custom CSS when authoring with AEM. The core component is designed so that you can only change the ID and cannot add classes.In terms of html validation, I don't think you can use the ID of each component when there are multiple identical components. However, in this case, the ID name will be unique and the same style will be written in CSS. Request the addition of the Class property in the core component dialog. ユースケース： Add Custom class CSS in core component dialog 現在／体験した動作：   改善／期待される動作：   環境の詳細（AEM バージョン／サービスパック、もしあればその他の詳細）：   顧客名／組織名 Mitsubishi Electric Corp. スクリーンショット（ある場合）   コードパッケージ（ある場合）  

機能改善要求（RFE）概要： About the menu for text components As attached, only 5 icons are displayed at the top of the text component editing screen. If you display it in full screen, more icons will appear. With the current specifications, you cannot tell if there are multiple icons unless you use the full screen.Very difficult to understand. Request that all types of icons be displayed even if it is not full screen. ユースケース： menu for text components 現在／体験した動作：   改善／期待される動作： view all icon 環境の詳細（AEM バージョン／サービスパック、もしあればその他の詳細）：   顧客名／組織名   スクリーンショット（ある場合）   コードパッケージ（ある場合）  

Request for Feature Enhancement (RFE) Summary: Rework the Translation Projects in a way that also normal users (and not only administrators) can see the members which are also assigned to the project in the tile "Team". Use-case: As a user who starts translation projects, I want to see who else is member of the translation team. And, with which rights. Current/Experienced Behavior: Only member of administrators group can see all members in the "Team tile". The member itself are just seeing one member here - that's his account. System shows always "Team (1)" as title of the tile, which is wrong in this case. So, for the normal user this tile is completely USELESS (and shows actually wrong information in case there are more members). Improved/Expected Behavior: Tile "Team" in the Translation Project should show all members which are assigned to the team also for non-admin users! And, would be quite helpful if there would an hover effect on the avatar icon showing details of the

Request for Feature Enhancement (RFE) Summary: Rework the functionality how settings, which user can adjust, are saved. The current way to do that with a cookie avoid an efficient way of working for editors if they are switching devices and or browsers. Use-case: As an editor, I configure my AEM UI to my needs so that I can work most efficiently. So, e.g. I set up the left pane to show always the content tree. If I use another browser or switch the device, I'm working with, those settings should be still effective. Current/Experienced Behavior: Setting are not kept as the are stored not in the user account in AEM but in a cookie (which by the way expires also at next day, I think) Improved/Expected Behavior: Make those settings persistent in the user account within AEM so that it is not necessary to set them up every time. Environment Details (AEM version/service pack, any other specifics if applicable):   Customer-name/Organization name: Carl Zeiss AG Screenshot (i

Request for Feature Enhancement (RFE) Summary: Develop graphql sorting feature Use-case: If I want to sort graphql results by a name/number field alphabetically, current graphql doesnt support. Current/Experienced Behavior: If I want to sort graphql results by a name/number field alphabetically, current graphql doesnt support. Improved/Expected Behavior: Graphql should support sorting features for text or number or dates fields Environment Details (AEM version/service pack, any other specifics if applicable): All Customer-name/Organization name:   Screenshot (if applicable):   Code package (if applicable):  

Idea Summary: The new Cloud Manager Content Fragment (CF) Editor does not support displaying custom field types such as ColorField, TextArea, and PathField, which were previously replaced in the classic editor. This lack of support significantly impacts users relying on these customizations for structured content authoring. We propose adding native support or a UI extensibility option to render these field types appropriately. Business Use Case: Organizations using AEM depend on custom field types to maintain structured content entry consistency. The inability to render these fields in the new CF Editor forces users to revert to the classic editor, limiting their ability to leverage new UI features. Providing native support for custom client-side renderers would enhance usability and encourage migration to the new UI. Current Behavior: The CF Editor does not recognize or display custom fields such as ColorField, TextArea, and PathField. Custom client-side renderers are ignored, mak

Request for Feature Enhancement (RFE) Summary: a feature to let the user "pin" (save) a specific path on AUP as a starting point when choosing assets or content links within AUP. After pinning a location, next time the user has to browse to an asset or content element, the pinned location is used as a starting point. Use-case: when editing pages on elements such as: -             content grids (articles, case studies) -             content grids (people) -             page configuration (selecting hero banner image, selecting featured image, selecting thumbnail) -             configuring links (CTA buttons, text links etc.)   Current/Experienced Behavior: Expanding the directory path from the starting point is very time consuming, an

Request for Feature Enhancement (RFE) Summary: The "cq-msm-lockable" attribute is used to maintain inheritance when configuring MSM locks on page properties. When the inheritance is cancelled, the property-cq:propertyInheritanceCancelled - is added. However, this does not operate on deep properties. Use-case: Data about an event such as local time-zone, address of the event, etc is stored in jcr:content/metadata. We need to cancel inheritance of the page to update localized data. field level inheritance cannot be operated on deep properties.   Current/Experienced Behavior: Cancel inheritance functionality does not work for deep properties. Improved/Expected Behavior: Leverage the cancel inheritance functionality for deep properties. Environment Details (AEM version/service pack, any other specifics if applicable): AEM Version 6.5.10 Customer-name/Organization name: Rockwell Automation Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Currently in AEM we have option to use Oauth2 (CQ Mailer SMTP OAuth2 Provider) for email integration with SMTP server, along with SMTP(Day CQ mail service) can we have option to use the Oauth2 with Microsoft graph API Use-case: Due to security reasons some clients won't enable the SMTP authentication for the accounts as those accounts are shared within multiple brands and SMTP AUTH is also being deprecated by Microsoft. So thinking to use the Microsoft graph API for email integration it will use the same access token generated using the Oauth OOTB implementation. Current/Experienced Behavior: Oauth2 integration with SMTP  Improved/Expected Behavior: One more option to have Oauth2 integration with Microsoft Graph API Environment Details (AEM version/service pack, any other specifics if applicable): AEM cloud Customer-name/Organization name: Bounteous Screenshot (if applicable):   Code package (if applica

Request for Feature Enhancement (RFE) Summary: Increase the folder depth limitation for the Export Metadata feature in AEM Assets to support folders exceeding 10 levels. Use-case:  Some customers rely on deep folder hierarchies to manage large-scale asset libraries effectively. Their current folder classification system often exceeds 10 levels in depth. The existing limitation prevents the Export Metadata feature from functioning properly for assets stored in these deeper folders, leading to inefficiencies and an inability to extract necessary metadata. Current/Experienced Behavior: When using the Export Metadata feature, it fails to export metadata for assets located in folders deeper than 10 levels. This limitation disrupts workflows for customers with complex folder structures. (Case #E-001458355:  Support Response: I checked the code for AssetMetadataExporterProcess and found that the FULL_TRAVERSAL_DEPTH = 10, which means it only allow 10 levels of depth. 

Request for Feature Enhancement (RFE) Summary: Provide a new report in the Assets Reports which provides the information if asset are referenced and in use or not. Use-case: As an editor I want to ensure that unused asset are deleted from DAM. Therefore I would need a report which asset are not in used anymore = not referenced in pages anymore. With this I can simply go through and delete and free up space in DAM. Current/Experienced Behavior: No report available ootb - need to check each asset individually regarding references. Improved/Expected Behavior: Ootb report which lists all unreferenced assets and provides option for the editors to filter for published or unpublished assets (so, the status of the assets). Background: an unreferenced and unpublished asset could be deleted immediately. An unreferenced but published one could still be in use from some other website using direct link to it - might need some further investigations before deleting it. Environment Details

Request for Feature Enhancement (RFE) Summary: Need functionality for expediting content sync from Production to Lower environments for smaller content sets Use-case: Currently, the available feature in Cloud Manager takes a long time to process content sync request(2-3 pages) from Production to lower environments.  Need functionality for expediting content sync from Production to Lower environment for smaller content sets Current/Experienced Behavior: Even while moving 2-3 pages from PROD to a lower environment, it takes 45-50 minutes in Cloud Manager. There has been instances where moving 1 page takes an hour. Using CRXDE Package manager, this will take only 5 minutes while. Since this access is not given to Production Author instance, we will need a facility to expedite small content package sync from PROD to lower environment. Improved/Expected Behavior: Need functionality for expediting content sync from Production to Lower environment for smaller content sets

Request for Feature Enhancement (RFE) Summary: I have a suggestion that I believe would greatly enhance the user experience within the Assets Folder. My idea is to implement pagination within the Assets Folder UI, especially for users with a large number of files. Currently, scrolling through an extensive collection of assets can become cumbersome and time-consuming. With pagination, users can easily navigate through pages of assets, making it more efficient to find and manage their files. I believe that implementing pagination in the Assets Folder UI as a feature would be a valuable addition to the Adobe product suite and further enhance the overall user experience. Use-case: Manage files in Assets folder for better user experience Current/Experienced Behavior: Currently, scrolling through an extensive collection of assets can become cumbersome and time-consuming for loading assets. Improved/Expected Behavior: With pagination, users can easily navigate through pages of asse

Hi I'd like to be able to sort the display order of my tags if I wish.Currently, I'm obliged to delete everything and recreate the tags one by one in the order I've chosen.This can be very cumbersome when there are a lot of tags. Ideally, there should be a button for sorting in ascending or descending order. With the possibility of moving (up/down or drag&drop) certain tags to make exceptions in order if I wish.   Request for Feature Enhancement (RFE) Summary:   Use-case:   Current/Experienced Behavior:   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: Implement an intelligent content recommendation engine to leverage AI and machine learning to suggest relevant content for each page, driving increased engagement and business outcomes. Use-case: Marketers need a way to deliver the most relevant and engaging content to users based on their behavior, interests, and the current context. By providing AI-powered content recommendations, AEM Sites can help surface the most impactful content to drive conversions and achieve business goals. Current/Experienced Behavior: Currently, marketers must manually curate and select content for each page, which can be time-consuming and may not always align with user preferences. There is no automated way to surface top-performing content or make recommendations based on user behavior and business rules. Improved/Expected Behavior: With the intelligent content recommendation engine, AEM Sites would analyze user interactions, content p

Request for Feature Enhancement (RFE) Summary: Environment variables is a good feature in AEMaaCS to change OSGi service configuration in runtime without redeployment. Sometimes, project has to have a lot of env variables, especially if you are running several sites on the same program. That's why I would like to have an option to set a description or note for env variable in the Environment Configuration modal in Cloud Manager.   Use-case: I can provide few use cases: 1. Imagine you have 2 brand that are running on AEMaaCS. Each of them should pull data from third-party service by schedule. Sometimes there are cases when you need to change a frequency for pulling data for both services or service URL. For example: BRAND1_SERVICE_URL is an env variable with a 3rd party service URL to provide data for brand1, BRAND2_SERVICE_URL is an env variable with a 3rd party service URL to provide data for brand2, BRAND1_SERVICE_CRON is an env variable with a cron exp

Request for Feature Enhancement (RFE) Summary: Please add adjustible columns in the UI for Launchess so that you can resize if necessary in case title is shortened Use-case: As an editor I want to find my launches here quickly. Normally you look for the launch title. But the title is cutted after specific amount of characters and you can not distinguish between those which beginning with same letters. Current/Experienced Behavior: Columns are fixed. You can not adjust the width of the columns in order to see shortened/cutted label like the title! Even on 'on hover' is missing! Improved/Expected Behavior: Just make the columns adjustable like in other view. It's so easy!!! Environment Details (AEM version/service pack, any other specifics if applicable):   Customer-name/Organization name: Carl Zeiss AG Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Delete page in author should auto unpublish the page. Use-case: Content authors who are new to AEM are deleting the pages without unpublishing them, assuming it will reflect the on actual site. Page is deleted in author but not in publish or in live site. Current/Experienced Behavior: Deleting page on author stays on author without unpublishing it. Improved/Expected Behavior: Expected it to auto publish the page if author deletes the page. Environment Details (AEM version/service pack, any other specifics if applicable):   Customer-name/Organization name:   Screenshot (if applicable):   Code package (if applicable):  

機能改善要求（RFE）概要： twitter:cardを指定できる機能の追加 ユースケース： X (twitter)で情報を拡散させる際、OGP画像を大きく表示させたい（summary_large_imageを指定したい） 現在／体験した動作： og:imageの画像が表示され、画像が小さく、目立たない 改善／期待される動作： summary_large_imageを指定することにより、画像が大きく表示され、情報拡散に有利 環境の詳細（AEM バージョン／サービスパック、もしあればその他の詳細）：   顧客名／組織名 Maki_yam スクリーンショット（ある場合）   コードパッケージ（ある場合）  

Request for Feature Enhancement (RFE) Summary: Accurate header/footer and breadcrumb display in page version comparisons Use-case: Comparative display of past and current versions of a page / preview of past versions Current/Experienced Behavior: Header and Footer not displayed. The breadcrumb list is displayed in full path. If this requirement is not met, it is difficult to see what has changed compared to the previous version, which hinders the content update process.Although the function compares differences, the problem is that differences are produced even if the content has not been updated. Improved/Expected Behavior: Headers and footers are displayed correctly. Breadcrumb list displays the correct range. Environment Details (AEM version/service pack, any other specifics if applicable): AEM6.5 ServicePack16 Customer-name/Organization name: Hitachi Construction Machinery Co Ltd Screenshot (if applicable):   Code package (if applicable):    

Request for Feature Enhancement (RFE) Summary: If there is a lot of target data, the current default setting will cause problems. Please change the default setting. Default setting of "Include subpages" when creating a launch: ON → OFF Use-case: If ｗｅ accidentally create a launch with the default setting ON ("Include subpages"), the following problems will occur. 1.All source pages related to the launch will become unmovable, causing business problems. 2.2. Processing will not finish because it involves processing a large amount of data. We have a thorough manual to change the default setting from ON to OFF, but we accidentally worked with it ON, which caused major problems.  For this reason, we would like to change the default setting to OFF. Current/Experienced Behavior: "Include subpages" default setting: ON Improved/Expected Behavior: "Include subpages" default setting: OFF  (If possible, keep it OFF. Do not want it to be possible to change it to ON.) E

Request for Feature Enhancement (RFE) Summary: Currently Max-length of characters is not available for rich text as that of text field and title field Use-case: Character limit for rich text Current/Experienced Behavior: No Character limit for rich text , we are doing custom validation for character limit but it would be great if we have max-length property to limit character limit as that of title and text fields. Improved/Expected Behavior: User should be able to limit the number of characters in rich text Environment Details (AEM version/service pack, any other specifics if applicable):   Customer-name/Organization name:   Screenshot (if applicable):   Code package (if applicable):