Build better products with our product team
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.) Environment Details (AEM version/service pack, any other specifics if applicable): AEM Release 2024.5.16461.20240524T172309Z Customer-name/Organization name: Panasonic Screenshot (if applicable): Code package (if applicable):
Description Right now, the "Time on Page" event type is firing even if the page is not in focus e.g., when the user clicked a link that opened in a new tab. It would be great if there was an option that allows to pause the timer to only tick when the page is in focus. Why is this feature important to you This will improve the overall reliability of rules trigger by the Time on Page events, giving a more accurate view on actual user behavior on the page. How would you like the feature to work Add a checkbox that can be used to signal that only active time on the page shall be counted Current Behaviour The timer keeps ticking, even if I temporarily switch to another tab. The dummy code below more or less shows the solution. Have it running in the console and switch between tabs to see how it stops and restarts the timer upon visibilitychange events. // Sample code let timer = 0; // Stores the elapsed time in seconds let intervalId = null; // Stores the interval ID let startTime = null; // Tracks when the timer started // Function to start the timer function startTimer() { if (!intervalId) { startTime = Date.now(); intervalId = setInterval(() => { const currentTime = Date.now(); timer += Math.floor((currentTime - startTime) / 1000); startTime = currentTime; console.log(`Timer running: ${timer} seconds`); }, 1000); // Update every second } } // Function to stop the timer function stopTimer() { if (intervalId) { clearInterval(intervalId); intervalId = null; } } // Event listener for visibility change document.addEventListener("visibilitychange", () => { if (document.visibilityState === "visible") { console.log("Page in focus. Timer started."); startTimer(); } else { console.log("Page out of focus. Timer stopped."); stopTimer(); } }); // Start the timer initially if the page is in focus if (document.visibilityState === "visible") { startTimer(); }
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 violated. Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5 , AEMaaCS Customer-name/Organization name: Screenshot (if applicable): Code package (if applicable):
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):
I'm sure you've seen in most calendars, when you are in a date far away from today, there is a button to click on that takes you to "today". That isn't there in the calendar that pops up in the due date fields in the tasks. Could that be added? We often have due dates that have been missed, and need to add in a more updated date. If we could have the option to take us to "today" that would save a lot of clicks (and we need to save as many clicks as we can LOL!). Since this is a basic feature of most calendar popups I have seen, hoping it could be an easy add.
We can add a column what shows when a report is created to views and reports, but we can not add a column to show when a Dashboard was created. We need to be able to see when a dashboard was created just like we would for a report, project, etc.
We need to be able to see tasks assigned to a team even after someone has "claimed" it. There is no filter that allows this in the My Work widget and disappears from the Team widget too. Meanwhile, other team members still need to see it and keep it on their radar until it is completed.
In addition to the current character count, we need to be able to limit the number of characters that a user can input to a given custom form field.
Description - Our team tracks all projects by fiscal year rather than the calendar year. Currently, the available views in Workfront do not support this tracking method. Could you please enable or support a product development request with a Gantt chart view that aligns with our fiscal year (October-September)? This adjustment will greatly enhance our project tracking and reporting accuracy. Why is this feature important to you - We work in fiscal year and will help us more accurately track our projects How would you like the feature to work -We would like to be able to customize our fiscal dates in the gantt view Current Behaviour - It only allows for weekly, monthly, quarterly, and yearly
Create a more robust reporting source to identify internal users within my organization who are actively accessing Adobe Analytics. In order to help with account management, having the ability to filter for things such as specific dates without having to select multiple users will bring a greater ease. I think it would be beneficial it the reporting was to how client data is filtered by date and whatever else data is available in the standard Adobe Analytics UI Currently, we have to navigate to the "Last Analytics Access" for any user you want by following these steps: 1. Login to experience cloud, Go to Analytics. 2. In the top toolbar click on Admin. 3. Then click on Analytics users and assets. 4. Here, you can view the list of users. There is a column titled "Last Analytics Access," which indicates the date and time when a particular user last accessed Adobe Analytics. You can sort this column by oldest to newest or newest to older by clicking on it then selecting the users you want by clicking the checkbox next to their name. From there a option appears to export the data.
Description -Moving WorkFront into the Adobe Unified Experience removes all branding from the system. This now looks like a generic system. We used to leverage universal branding for the system, and department specific branding through layout templates so that the interface was recognizable to our users. Since the overall site cannot be branded, it would be nice to brand request forms. Why is this feature important to you -Since the site is not branded anymore, having branding on request forms would help our requestors. These are not everyday users of the system so their knowledge about the system is limited. With the many security and phishing issues out there, branding on the form would help "legitimize" the portal to requestors. How would you like the feature to work -I would like to add a logo at the top of the request form based on the Request Type. Would also be open to the logo being placed under the Request Type so that it appears after you select the request type. Current Behaviour -Currently, we can add some branding/logo within custom forms attached to request queue's but this mean the placement is after the the standard Request Queue fields (Subject, Description, Priority, etc.). The placement of branding/logo should be at the top of any form.
Ability to mark the mentions as Read so we can only see New mentions. Keeps the list cleaner like the notifications list functionality in the top menu bar
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 newly added field using hardcoded value for default case. Improved/Expected Behavior: Have a more smart way to track, visualize and update references and reflect changes on the fly. Phase 1: We can start with a simple tool that initially tracks the references. Have the tool available for authors. Have the tool display a dependency graph and help authors check references routes. Is would display something like in the attached screenshot. Phase 2: Depending on the selected route, it would be helpful to generate a query that would match the returning results with the graph selection. For example, if I am clicking on Component 2, it should generate a query that I know it would return Page 1, 2 and 3 (where the actual instances of this component will be). Then later developer can use the query safely to programmatically update the content according to the needs. Phase 3: Changes should be done automatically by the system behind the scenes, or manually with one click away, but in both scenarios without any development needed. Authors should get a report of what content got updated. Notes:1. Approach can be extended to cover also CF and XF references, or templates usage.2. Each component could have a on/off switch flag for the capability, to auto propagate or not the changes on the referent content Maybe this is feasible idea only for a limited area or maybe is not feasible at all. Or maybe I am not fully evaluating every possibility or practicability of such tool, but I believe is worth analyzing the potential of it. Mermaid link: https://mermaid.live/edit#pako:eNp9kUtvhCAUhf8KuWvHyAg-WDTpjH0sumjaXccu6Eh10gpGIalV_3vJUCdO0wwbuPd851wCA-xVIYBB2fKmQg9PuUR23e22qm6UFFIj8opWq6vRdKJASo7ofvfIS2HbDr1eoNihnWlEi3TfWMdbP6LNAlnPtvPQrQvFv-rm35xskROekZdzTuqNU-c7ZBe9f9Rbp7q5jsil28GDWrQ1PxT2IYejDroStciB2WPB248ccjlZjhutnnu5B6ZbIzxolSkrYO_8s7OVaQquRXbg9jfqU7fh8kWperbYEtgAX8CixKeEkpAGcZxQHK496IFhHPmERnGESRrENCBk8uD7GID9ICVpSpMYE4ojGuDpB74zm00 Environment Details (AEM version/service pack, any other specifics if applicable): For all AEM environments a architectural deployments Customer-name/Organization name: Tetchich.com Screenshot (if applicable): Code package (if applicable):
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 applicable):
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 the recipients for a completed-mail. This feature would be helpful for every customer using the Integrated Translation Framework! 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: 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 precise and reliable search capabilities. The requested enhancement is critical to ensure accurate partial and full-text search for SKUs and other metadata properties containing dots and hyphens, which are key identifiers for assets in the customer's repository. Customer Impact:The inability to perform searches with strings containing dots (.) and hyphens (-) limits the customer’s ability to retrieve assets effectively. This impacts search efficiency and accuracy, resulting in significant delays in workflows and operational inefficiencies. Since LG Electronics' SKUs often include these special characters, the current behavior does not meet their requirements, hindering productivity and disrupting processes dependent on seamless asset retrieval. Current/Experienced Behavior: When querying for strings containing a dot (.) or dash (-), the search functionality does not return the expected results. These characters are currently treated as delimiters, splitting the query into separate tokens. This disrupts partial search capabilities. For example, searching for OLED48B46LA.AEUQLHX fails to retrieve the correct asset. This behavior prevents accurate retrieval of assets when metadata properties, such as SKUs, include dots and dashes, which are commonly used in their structure. Improved/Expected Behavior: Dot (.) and hyphen (-) should not be treated as delimiters during indexing or querying. Metadata values containing these characters should be indexed as a single token to fully support partial and full-text searches. Users should be able to retrieve assets by searching for SKUs or other metadata values containing dots and dashes without any issues. Environment Details (AEM version/service pack, any other specifics if applicable): AEM as Cloud (2024.8.17569.20240822T203847Z)) Customer-name/Organization name: LG Electronics Screenshot (if applicable): Code package (if applicable):
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 "The page you have selected has not been added as the source page has not been modified since last translation" 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):
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
