Adobe Experience Manager Sites

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: Provide a notification functionality for translation projects which informs a defined group of the translation project about the completion of a translation, listing all pages that have been translated so that you just need to click on the link to open the pages, review and publish them. Use-case: As an editor which has started a translation job, I want to be informed once the translation is back in AEM in order to check and publish the page. Current/Experienced Behavior: There is no functionality inside the Translation Project, you have do a customization by yourself. Improved/Expected Behavior: As the information about completed translation jobs is essential and no editor wants to check frequently the status of the translations projects, especially when there are hundreds running, I would expect that there is an ootb functionality for that. In the project you already have the chance to add member - here you could simply define

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