Adobe Experience Manager

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):  

Request for Feature Enhancement (RFE) Summary: When generating a report on Assets, it is possible to bypass the add details(2/3) step without supplying a date range. However, the validation constraint message only appears after proceeding to the final step(3/3) and creating the report. Ideally, the constraint violation message should appear on the same page as soon as the condition is violated. Use-case:   Current/Experienced Behavior: Steps to reproduce: 1. Navigate to AEM Tools> Assets > Reports 2. Click on 'Create' button on right hand top corner. 3. Select any Type of report and click Next 4. On Add Details screen "/ui#/aem/mnt/overlay/dam/gui/content/reports/createreportwizard.html" add required field without choosing any values under 'Adjust Date' click on Next and then create report An error message 'Date Field Error' popup is shown Improved/Expected Behavior: Ideally, the constraint violation message should appear on the same page as soon as the condition is

Request for Feature Enhancement (RFE) Summary: Extend the content fragments console navigation toolbar to provide an option to start a workflow. Use-case: This is a common scenario where content editors do not have permission to use quick publish/publish management, but are forced to use activation workflows to ensure only approved content is published. A new content fragments console does not have an option to start a workflow. Current/Experienced Behavior: After editing a CF in the content fragments console, an editor has to go to the assets view and find the CF to trigger the workflow Improved/Expected Behavior: An editor can start a workflow for content fragments from the content fragment console Environment Details (AEM version/service pack, any other specifics if applicable): AEM as Cloud Service Customer-name/Organization name: Philip Morris Screenshot (if applicable):     Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: When a reviewer tries to use Enter to create a line break when adding comments, AEM submits the comment. They actually have to use Shift-Enter to just get a line break, which isn't intuitive. Use-case: Enable reviewers to hit enter to include a line break. Current/Experienced Behavior: Hitting enter submits the comment. Improved/Expected Behavior: Enable reviewers to hit enter to include a line break. Provide either a 'Submit' button, or make the behavior configurable.  Environment Details (AEM version/service pack, any other specifics if applicable): https://author-p108955-e1062829.adobeaemcloud.com/ Customer-name/Organization name: Workday Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Have a direct link to the specific topic submitted for review from within the email notification that's sent to the reviewer. Use-case: We ask PMs to review topics, and have received feedback that the current process is confusing for them as they need to navigate within AEM to find the relevant topic to review. Current/Experienced Behavior: The email takes the reviewer to the review inbox Improved/Expected Behavior: Take reviewer directly to the topic that the email was about Environment Details (AEM version/service pack, any other specifics if applicable):   Customer-name/Organization name: Workday Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Improve UX by adding contextual help/tooltips/instructional help within AEM. Use-case: Technical writers currently find it difficult to know the purpose of many icons, buttons, and menu items when navigating the AEM UI as they don't have any/sufficient tooltips or instructional help. Current/Experienced Behavior:   Improved/Expected Behavior: Clarity regarding the purpose and meaning of:   Menu items. The distinction between "Experience Fragments", "Assets", and "Content Fragments". Global vs iLX Profile.  It would be helpful to have an easily accessible link to Adobe's documentation within AEM. Environment Details (AEM version/service pack, any other specifics if applicable):   Customer-name/Organization name: Workday Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Move the Inbox icon on top Use-case: On AEM as a Cloud the notification icon(on Navigation bar) opens the popover, where the inbox is at the bottom and kind of hides it from Business users. Why not move it on the same level as Request, Notifications & Announcements or provide an option to configure this. Current/Experienced Behavior: Inbox button at the bottom which moves the focus away for business users Improved/Expected Behavior: Moving the inbox to the top improves the focal point Environment Details (AEM version/service pack, any other specifics if applicable): AEM as a Cloud Service Customer-name/Organization name:   Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: When you're updating a review task in Guides, the Assign To prompt on the Task tab should show the names of viewers who are assigned to the task.  Use-case: When writers see the Assign To prompt is blank, they think they have to add reviewers again, but that's not true. Current/Experienced Behavior: Currently the reviewer names can be seen at the bottom of the Task tab where you're not expecting them and on the Reviewers tab. Improved/Expected Behavior: Show the names of assigned reviewers in the Assign To prompt on the Task tab or move the Assigned list from the bottom of the page to directly after this prompt. Environment Details (AEM version/service pack, any other specifics if applicable): https://author-p108955-e1062829.adobeaemcloud.com/ Customer-name/Organization name: Workday Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: AEM References Manager Use-case: Track references and control changes Current/Experienced Behavior: It is very common situation when for example an AEM component definition gets changed and the changes immediately need to be reflected on the content. For example a new field is added and it needs to set a default value on the component instance. When the component is newly dragged on the page, this new field is stored in JCR. But then when the component already exists on the page, the new field does not get reflected in the JCR. When content is too large, and contains dozens or hundreds of pages that have this component, if becomes very hard or even impossible for the authors to manually make a false edit of the component and do a dummy save just to have the new property in JCR. Usually either developers end up writing specific on-time-use code helpers to updated entire content in subject, or solution codebase is updated to handle n

Request for Feature Enhancement (RFE) Summary: Replicate ACLs as a contributor Use-case: A contributor need to add or revoke access for some users groups on folders on both author and publish Current/Experienced Behavior: As a contributor or even an administrator, i go to a folder properties, set some rights thanks to the tab "permissions" and save. If i replicate the folder with the "manage publication" feature, my rights are not replicated to the publishers. Improved/Expected Behavior: As a contributor or even an administrator, i go to a folder properties, set some rights thanks to the tab "permissions" and save. If i replicate the folder with the "manage publication" feature, my rights are correctly replicated to the publishers. Environment Details (AEM version/service pack, any other specifics if applicable): AEM as Cloud Service - Assets 2024.11.18598.20241113T125352Z Customer-name/Organization name: Valtech Screenshot (if applicable): Code package (if a

Request for Feature Enhancement (RFE) Summary: Email notification recipients struggle to see clickable links in email notifications for Content Fragment updates.  Use-case: When a user is tagged in the comments for a CF, an email is sent to the tagged user's inbox, which contains a link to the CF where the comment is posted. The notification does not appear visually to look like a clickable link.  Current/Experienced Behavior: Cannot discern notifications for comments contain a clickable link to the CF.  Improved/Expected Behavior: Users should easily see the email notification contains a clickable link to the CF.  Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS 18493 Customer-name/Organization name: Workday Screenshot (if applicable):   Code package (if applicable): n/a

Request for Feature Enhancement (RFE) Summary: Enhance the AEM Assets Search to support partial and full-text search functionality for metadata properties containing special characters, such as dot (.) and hyphen (-), as part of their values. Use-case: The customer has integrated a custom property (jcr:content/metadata/dc:suffix) into the filter search form and enabled partial search for this property. This property stores metadata values, such as product SKUs, which frequently include dots (.) and hyphens (-) as part of their structure (e.g., OLED48B46LA.AEUQLHX or OLED48B46-LA-AEUQLHX). However, the current search functionality treats these special characters as delimiters, breaking the search query into tokens and failing to retrieve relevant assets. For example, search for OLED48B46-LA.AEU* is not working where property value is OLED48B46-LA.AEUQLHX. This issue significantly impacts the customer’s ability to locate assets efficiently, disrupting workflows that depend on

Request for Feature Enhancement (RFE) Summary: If you add a page for a translation job which has not been modified since last translation, the editor should get a hint why it is not added! Use-case: As an editor I create a new translation job and add a page. The system recognizes that the page is existing in the target language and therefore gives you the option to "Update language copy". Current/Experienced Behavior: The select page does not appear in the list. There is no hint in the UI showing the reason. Also, there is no hint in the error log. The reason is that it is not added if source page has not been modified since last translation. BUT how should you as an editor working in a team with a lot of pages know that? Why does an enterprise system just don't show a message why the page is not added? It's that basic! Improved/Expected Behavior: System should show an appropriate hint in the UI telling the editor why his selected page has not been added. Something like "Th

Request for Feature Enhancement (RFE) Summary: Please improve the way how a creator of an translation project can add users to the project. Currently only an administrator can do that which is NOT feasible at all under real live scenarios. There this option is currently totally USELESS! The creator should be able to add users and there roles by himself. Use-case: As an editor which has the task to create translation projects, I need to be able to add other users to the translation project so that they can see and maintain it WITHOUT the help of an administrator. Current/Experienced Behavior: As a member of the 'project-administrators' can only add myself and the anonymous user to the project. I got the confirmation from Adobe Support that this by design and only members of the administrators group can see all users in the dropdown. With this the option to add users to the project with different rules is USELESS under normal circumstances! Normal users can not turn to administrat

Request for Feature Enhancement (RFE) Summary: On multifield component dialog: add sufficient space between the validation alert and the up/down arrows so each can be individually selected. This is a bug fix.  Use-case: When a user makes an error in the list component, eg by not filling a mandatory field, they cannot view the validation message that would tell them what to fix, because when they click it, they click into the field to drag items up and down. It is impossible to select the validation alert.  Current/Experienced Behavior: As above - user cannot select or read validation alert to know what to fix.  Improved/Expected Behavior: Sufficient space between the validation alert and the up/down errors so their selection field does not overlap. Then a user can click and read the validation message and / or click and move items up and down.  Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5  Customer-n

Request for Feature Enhancement (RFE) Summary: Chance to select which kind of assets(original or renditions or both) to download from shared assets. Use-case: AEM as Cloud Service: when I share multiple assets with a user through the Share functionality, the receiver can't choose if they want to download only the original assets or the renditions, it automatically downloads whatever was set up by the person initiating the share. Current/Experienced Behavior: When I share multiple assets with a user through the Share functionality, the receiver must download whatever was set up by the sender, not for folders or collections. Improved/Expected Behavior: The requirement is for the person receiving the assets to be able to specify what they want to download, similar to the functionality present when you just use the DAM as a normal user,  both for folders and collections. Environment Details (AEM version/service pack, any other specifics if applicable): 2024.11.18598.2024111

Request for Feature Enhancement (RFE) Summary: Add Sorting Filter in Card View for various asset display variations Use-case: Use and enable Sort By filter in card view. Open AEM Asset Search and sort in card view. Current/Experienced Behavior: Sorting for Asset Search etc. is only available in List View, which only displays very small thumbnails. Card View Sort Filter function is currently only available at Assets>Files. Improved/Expected Behavior: Card View Sort Filter is available in AEM Search etc. like it is in its functionality DAM where you can sort the assets in the folders. We would like to use this existing function in Asset Search and Collection Detailview. Environment Details (AEM version/service pack, any other specifics if applicable): v6.5 AEM Assets Customer-name/Organization name: AIDA Cruises Screenshot (if applicable): possible use Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Optimize the synchronization process to minimize latency, ensuring that user data is available across all pods immediately upon creation. This will enhance user experience by providing real-time data access. Use-case:   Current/Experienced Behavior: it takes 200 to 500 ms in synching user across pods in cloud service Improved/Expected Behavior: it should be almost instant or with in few milliseconds Environment Details (AEM version/service pack, any other specifics if applicable):   Customer-name/Organization name: Munich Re Screenshot (if applicable):   Code package (if applicable):