Build better products with our product team
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):
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 administrators groups and ask for adding users each time a new project is created. And, also normal user can not be in the administrators group. Improved/Expected Behavior: The editor who creates the translation project should be able to add other users or at least user groups to the project. This is essential in an enterprise environment where you have a lot of people starting translations and need to see which projects are running. 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):
We have a Fusion scenario which calls our AEMaaCS instance to make a Http Post call to a custom API (Sling Servlet). The success scenario runs as expected but when there is a validation error returned by the API, e.g., an HTTP 400 response, the module doesn't receive or process the error messages.The API returns an error message in the body with the status code, but the AEM module in Fusion only processes the status code, not the message.
Description - It's great to be able to share a dashboard with anyone, even if they don't have Adobe Analytics accounts. However, it would be amazing if whatever this user is changing in terms of selected dropdowns or date ranges would be reflected in the URL, so a deep link can be created. Why is this feature important to you - Sometimes it is needed to show something to a client or colleague, and it would awesome if I could prepare a shared dashboard with a set of preselected elements and date range for instance, to show a certain finding, without affecting the overall shared dashboard to other users. How would you like the feature to work - A shared dashboard link looks something like this https://www3.an.adobe.com/spa/?linkId=<some UUID>&dpc=lon So, if I now make a selection to a dimension drop down, I would hope that the SPA URL reflects this somehow e.g., https://www3.an.adobe.com/spa/?linkId=<some UUID>&dpc=lon#dim1=ch&... and once opening the URL, it will preselect the segment(s) and/or date range for me, so I can easily show my colleague an interesting aspect of the data or even make a bookmark to reopen it at any given time. Current Behaviour - The URL stays the same, I cannot easily share or bookmark a view on the dashboard
Previously, the domain change associated with WorkFront was changeable. Incidentally, the original domain name is no longer appropriate for our uses and we now have no course of action to ensure the platform works for all of our internal partners. Currently, the domain name represents only 1 of the two brands that currently use the platform. It would be helpful when sharing the platform with external clients if the domain reflected our brand as well. If a domain change is not feasible, then masking and/or aliases should be allowed.
Description - I want to be able to use the checkbox interface to mark multiple projects for bulk-template loading. Why is this feature important to you - It would save time in setting up projects that need multiple modular templates. I would use kickstart to add these templates in bulk, but kickstart also does not allow more than one template at a time. How would you like the feature to work - Check more than one existing project box in a project list, click "edit" navigate down to "Templates", select an existing template to load into all checked projects. Current Behaviour - Unable to load a template into an existing project except in the "attach template" interface on the triple dot option next to the project name.
Introduce an AI-powered virtual assistant within Adobe Analytics to help users navigate the platform, create segments, set up reports, and analyze data more efficiently. The AI assistant would understand natural language queries, allowing users to ask questions and receive insights or recommendations based on their data.Key Features:Natural language processing: Understand user queries in everyday language, making it easier for users to interact with the platform without needing deep technical knowledge of Adobe Analytics.Personalized recommendations: Provide users with tailored suggestions for segments, reports, and visualizations based on their data and previous activities.Automated data analysis: Perform complex data analysis tasks and provide actionable insights, helping users identify trends, anomalies, and opportunities within their data.Voice or text input: Enable users to interact with the AI assistant through voice or text input, depending on their preference and context.Integration with Adobe Experience Cloud: Seamlessly connect with other Adobe Experience Cloud products, allowing users to leverage insights from the AI assistant across their marketing, advertising, and customer experience efforts.Why is this feature important? The Adobe Analytics AI Assistant would make the platform more accessible and user-friendly, particularly for users who are new to Adobe Analytics or have limited technical expertise. It would also help users save time and improve decision-making by automating data analysis tasks and providing personalized recommendations based on their data.How would the feature work? Users would interact with the AI assistant through a chat interface or voice commands within the Adobe Analytics platform. The AI assistant would process user queries, analyze data, and return insights or recommendations in a conversational manner. Users could also ask the AI assistant to create segments, set up reports, or generate visualizations based on their questions.
Description - Having the ability to press enter to start a new line of text of selections in checkbox or radio button fields would allow for different text formatting and layout rather than only using commas and waiting for the system to break the text to a new line.Why is this feature important to you - Using commas in a choice can make it look messy sometimes and we have no control on when it breaks to a new lineHow would you like the feature to work - Be able to press enter to start a new line in a choice field that turns it into a multiple line field. This would allow for some choices to be listed in a cleaner fashion rather than a long string of text using commas.Current Behaviour - Users have to use commas when listing a series in a choice and let the text run on before it breaks to a new line rather than being able to press enter and start a new line.
Our users like utilizing calendar groupings in the Calendar module of Workfront to view their projects however the system only allows 15 calendar groups to be added. If you try to click on the "Add to Calendar" link once already have 15 the system presents a message stating "You've reached the limit of calendar groups". I'd like to increase or remove this limit altogether so that teams within our organization can utilize one central tool for roadmap exercises.
Description - When users are submitting issues via our WF intake, it is hard to see the full description field. Can we make this field bigger?Why is this feature important to you - Improves user experience. If copying and pasting text in it's easier to see if it worked properly.How would you like the feature to work - Display/Editing of description field is bigger.Current Behaviour - Relatively small description window. Hard to see all of the text sometimes. (Not sure if there is already a way to do this, if so please share.)
Description -Why is this feature important to you - Easier to see at a glance if we can "show all" in the widget.How would you like the feature to work - Just like how you can choose to see 10, 25, 50, or ALL.Current Behaviour - You can only view five before having to toggle to the next page(s).
Through 2024 Adobe has done this repeatedly and does not appear to understand how this impacts enterprise level organizations. We have 600+ users and Mutiple departments and teams and it is CRITICAL that we precisely control what each of them sees. Layout templates and permissions have been created to that end, but it seems every update you change something that subverts these controls. Two of the most problematic examples are the 'Home' screen that I cannot prevent people from using, only try to hide. The second one is the new 'Add a Dashboard' link inside each object record. When I sit in meetings and people stare at me as the Workfront Admin and ask why they don't know about their proofs, tasks, approvals, and custom workflows, I have to now check to make sure they haven't changed to the Home screen and/or added a dashboard that shows them who-knows-what. You have created Layout Templates for enterprise level control, and then you create ways to make this feature moot... understand this need for control - it is not a minor one.
Description - The bynder upload asset module needs to have a field mapping to map accessRequestID.Why is this feature important to you - It helps to bundle up multiple assets which are pushed to bynder through fusion.How would you like the feature to work - The upload asset module should have a field mapping for accessRequestID, through which when we pass the accessRequestID of the 1st uploaded asset it should club all the remaning assets together as a collection.Current Behaviour - There is no field mapping for accessRequestID.
Description - All the API data should be visible and accessible in the module output in the bynder upload asset moduleWhy is this feature important to you - Need to bundle up multiple assets pushed to bynder using fusion.How would you like the feature to work - Upon an asset upload in Bynder using upload asset module in fusion the module should output all the metadata which is returned as part of the API call.Current Behaviour - The module output does not contain all the metadata returned by the API call.
Advanced Reporting Links:- Welcome to Advanced Reporting https://experienceleague.adobe.com/en/docs/workfront-learn/tutorials-workfront/reporting/advanced-reporting/welcome-to-advanced-reporting- Advanced Reporting part 1 https://experienceleague.adobe.com/en/docs/workfront-learn/tutorials-workfront/reporting/advanced-reporting/advanced-reporting-part-1- Advanced Reporting part 2 https://experienceleague.adobe.com/en/docs/workfront-learn/tutorials-workfront/reporting/advanced-reporting/advanced-reporting-part-2- Advanced Reporting part 3 https://experienceleague.adobe.com/en/docs/workfront-learn/tutorials-workfront/reporting/advanced-reporting/advanced-reporting-part-3
Description -When studying the documentation I fund myself doing ('command' + '+', six times) to resize to 200%, specially when looking at images in the docs, and had to do it for every page. I later realized about the hiding with arrows to achieve the same result.Why didn't I use the arrows? perhaps that CTA is not that intuitive at least to me. Even then, I'd have to click 2 arrows for full view mode. Why is this feature important to you -Clicking around becomes repetitive when in study mode. How would you like the feature to work -Add a toggle perhaps labeled '2x' or 'full view mode' so in one click I can get to the mode I want and not 2 or more. Current Behaviour -Hit ('command' + '+', six times) to resize to 200%, the view that I like for those that do not guess the intended UX or have to click on 2 sidebar hiding arrows (intended UX)I know is a minor optimization, but every little counts and just wanted to mention as it could be part of an experiment. Thanks,Rafael Sahagun
Description - Add the advanced assignments option when viewing assignments in the summary panelWhy is this feature important to you - better efficiency in making assignment changes directly from the summary panel rather than having to open the object in a new screenHow would you like the feature to work - Adding the "Advanced" option to assignments in the summary panel viewCurrent Behaviour - there is no advanced option, must open the task or issue to access the advance assignment settings
The new Boards are great, but I want to be able to add a board to a dashboard. I have a lot of team-specific dashboards and we're starting to use Boards for project team to-dos that aren't really tied to projects. Just like we can bring in a report, calendar or external link to a dashboard, I want to be able to bring in a Board.
Description - We need to hide/disable or delete "Recent Path" in New Request page and we don't want to the users to see their "Recent Path" coming in on the front end.Why is this feature important to you - This feature may resolve lot of confusions for the usersHow would you like the feature to work - As soon as possible.Current Behaviour -
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
