Build better products with our product team
Request for Feature Enhancement (RFE) Summary: Translate entire website in AEM automatically with GenAI Use-case: Set up a Translation Workflow in AEM as a Cloud Service ( AEMaaCS ) by integrating with GenAI models that can translate entire websites automatically in minimum clicks. The workflow can be finetuned to translate only single pages and only specific fields in specific components. Current/Experienced Behavior: There is no such workflow/feature available in AEMaaCS as of now. Improved/Expected Behavior: Have a Translation Workflow created and made available in AEM as a Cloud Service ( AEMaaCS ) by integrating with GenAI models that can translate entire websites automatically in minimum clicks. Environment Details (AEM version/service pack, any other specifics if applicable): AEM as a Cloud Service ( AEMaaCS ) Customer-name/Organization name: UnitedHealth Group ( UHG ) Screenshot (if applicable): This is a sample screenshot from some customized code on AEM 6.5 Code package (if applicable): The reference regarding the GenAI integration code and workflow to be created can be taken from this URL : https://medium.com/@jlanssie/translate-entires-websites-in-aem-automatically-with-openai-944875cbfa22 A similar functionality has been requested to be created in AEMaaCS using Adobe and UHG Approved GenAI models.
Request for Feature Enhancement (RFE) Summary: Enhance Content Fragment OpenAPI for List Fragments to include eTag Use-case: List Content Fragment documentation reads, API would return `etag`. But when testing against AEM, the etag field is missing in response. This leads to a problem when updating CF, we dont have CF etag to pass into If-Match header. So update CF requires 3 trips: Find CF ID using List Find etag using Get Edit CF using Patch Fixing List CF API to return eTag will reduce UpdateCF to 2 trips Current/Experienced Behavior: List CF API is NOT returning eTag in response Improved/Expected Behavior: List CF API must return eTag in response Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS Customer-name/Organization name: SGWS Screenshot (if applicable): provided above Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: - AEM EDS Integration (cross-walk) for Adobe Target is currently very limited. - Clients heavily use the long existing feature, to upload experience fragments, created in AEM to the Adobe Target server for personalization usage. - This is currently a broken workflow in EDS cross-walk, as one can not create Experience Fragments from EDS Blocks - That's why - on behalf of our client DVAG - we request to have the possibility, to create Experience Fragments from EDS Blocks in the Universal Editor in order to export and update those to and on the Adobe Target Server in order to run A/B Tests and personalized Experiences in Adobe Target with provided Experience Fragments Use-case: 1. Editor creates Experience Fragment from EDS Block in Universal Editor (see provided draft image) 2. Editor creates variants of this Experience Fragment (existing feature for classic AEM Components) 3. User uploads the Variations to Adobe Target Server (existing feature for classic AEM Components) 4. User can change the Variants and update those in Adobe Target Server if ExF was already uploaded to Adobe Target before (existing feature for classic AEM Components) 5. The ExF's made available with this workflow are not ready to be used in Adobe Target VEC and also Form based (existing feature) Current/Experienced Behavior: 🔴 Currently it is not possible to create ExF's from EDS Blocks Improved/Expected Behavior: Creating editable ExF's from EDS Blocks is possible and consecutive handling of existing features like Uploading and syncing with Adobe Target Server is possible Environment Details (AEM version/service pack, any other specifics if applicable): Lates AEMaaCS - nothing specific Customer-name/Organization name: DVAG - Deutsche Vermögensberatung Aktiengesellschaft Screenshot (if applicable): provided in file upload Code package (if applicable): not applicable
Request for Feature Enhancement (RFE) Summary: Use-case: Current/Experienced Behavior: As the number of created collections continues to grow, we’re observing some usability and maintenance challenges. Please refer to the attached recording for reference. Key Issues: Difficulty for users to find or filter relevant collections Increasing need for better maintenance and hygiene of collections in AEM Assets Improved/Expected Behavior: Filter Option: Public vs. Private Collections Allow users to filter collections by: Public (shared) Private (created by the user) This would simplify navigation and reduce clutter in the list view. Expiration Date for Collections Enable users to set an expiration date when creating a collection. After expiry, the collection could either: Be automatically deleted, or Moved to an Archived state for review before deletion Bulk Management Capabilities Provide tools to: Select and delete/archive multiple collections at once Assign or update metadata like owner, expiration, or tags in bulk Owner/Creator Information Display Display the collection creator’s name in the list view, to help teams manage ownership and follow up with the right person. Usage Insights / Last Accessed Date Add metadata showing when a collection was last accessed or used. This helps in identifying inactive collections for cleanup. Environment Details (AEM version/service pack, any other specifics if applicable): AEM Cloud service (Assets or Admin view) Customer-name/Organization name: HUGO BOSS Screenshot (if applicable): Code package (if applicable):
Description - For all datasets, allow the ability to force lowercase all or certain fields. Why is this feature important to you - Currently, if the casing in matching keys doesn't match exactly, enhancement data from lookup and profile datasets isn't available in CJA. How would you like the feature to work - A toggle to force lowercase all fields in a dataset. Checkboxes to force lowercase certain fields Current Behavior - Attributes can be forced lowercase once ingested via data view component settings. However, this isn't possible before setting matching keys for lookup/profile datasets.
Description - I would like to be able to report on which issues are submitted by an intake email address. Why is this feature important to you - This is another metric to identify where issues derive from, which can be helpful for analyzing requestor behavior. Additionally, requests received by email is a backup when nonusers need to use your request queue, which is increasingly a need due to the absence of autoprovisioning after migrating to the Admin Console, OR when traditional submission routes are borked for whatever reason. How would you like the feature to work - Create a native field to identify an issue as having been submitted to the system by an intake email address. Alternately, remove the topic path. Current Behaviour - Per conversation here, there is no way to identify requests that are submitted to a queue by way of an intake email address.
Description - I spent several days and even posted to the community to try to figure out why Can Start was false on some follow-on tasks. Come to find out there is a sneaky little inconsistency in task status behavior. Why is this feature important to you - There are two reasons: We rely a fair amount on the Percent Complete field instead of status because it adds more context to work in progress. When we see Percent Complete is 100%, we assume that the task is complete. When a project has outstanding issues, we can't change the status to Complete. Therefore, any field that indicates a task is complete (or greatly implies) should follow the same behavior as a project because it's darn helpful for quality control. How would you like the feature to work - If a user tries to set Percent Complete to 100%, present them with an error message describing alerting the user that there are open issues and default the value to the previous value. Current Behaviour - A user can set Percent Complete to 100% and the task remains In Progress.
Similar to Instagram - i would love to be able to save certain conversations or posts to my profile to reference later. Many times a need comes up and i search the content on experience league but i don't have time in the moment to research it. Would love to not forget what i was going to go and do / edit it by being able to save everything.
Request for Feature Enhancement (RFE) Summary: Feature Idea:Adobe Content Copy Tool (CCT) Enhancements - Enhance the Adobe Content Copy Tool (CCT) to improve performance, usability, and flexibility for handling large content sets, environment constraints, and exclusion rules. Use-case: Syncing a large amount of content between different cloud environments Current/Experienced Behavior: The CCT is not practical for back-staging large content sets; it takes an excessively long time and often does not finish when handling large amounts of content. Content cannot be copied from lower environments to higher environments. The tool cannot be used if another pipeline is currently running in the same environment. No support for wildcard-based exclusion or inclusion patterns in content sets (e.g., excluding all subdirectories under a given path using regex or wildcards). Building packages in crx/packmgr works but has a timeout of 10 minutes which makes it hard to split content up in small enough packages Improved/Expected Behavior: Performance optimizations to allow faster and more reliable copying of large content sets. Enable content copying from lower environments to higher environments. Allow the tool to function concurrently with other running pipelines in the same environment. Introduce wildcard-based includes/excludes for content sets (e.g., support for patterns such as "modifier": "exclude","pattern": "/content/experience-fragments/heliux/adhesive/pro-now/language-masters(/.*)"). Environment Details (AEM version/service pack, any other specifics if applicable): 2025.3.20133.20250325T063357Z Customer-name/Organization name: Henkel AG & Co. KGaA Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Give the editor who creates a translation project the option to switch easily with one click to the project which has been created. Use-case: As an editor I wanted to have a efficient way of working once I want to sent my page out for translation. I create the page in the source language and with only some clicks without leaving the Sites console I want to start the translation job. Current/Experienced Behavior: If I am in the editing mode of my source page I can not start a translation job (btw. Lionbridge connector offers that option in the page menu), so I have to switch to the Sites Admin. Here I create the translation project via the left rail but after creating, system just says "Project created". I have to switch to Projects, look for the project created and start the translation. This is not a fluent way of working and not efficient!I have attached a screen recording to make it clearer. Improved/Expected Behavior: To improve the current situation the hint which pops up, telling you that project has been created successfully, should contain a link to the created project so that the editor just can click on it to open the project where he can also start it.And, in the left rail there could be a new category be introduced which shows the project in which the selected page is included. Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS Customer-name/Organization name: Carl Zeiss AG Screenshot (if applicable): Code package (if applicable):
There is an external account which is deleted accidentally. We are tried to get the details of operator , timestamp and action from the audit log. We did not able to extract the required entry from audit log which will give the clear message of deletion. Please help and share ideas how we can manage.
When converting an issue to a project, you are prompted to add that project to a portfolio. The portfolio drop down only shows your first 20 portfolios. This limit should be increased to show all portfolios available, or at the very least, have an arrow indicating there are more portfolio options that exist.
The submitted requests page is important as it provides users the ability to copy requests and submit as new entries rather than a pure copy you get off a dashboard report. It would be great if we could have a couple common elements that we see on most other areas: 1. Views - ability to add/customize views by adding and adjusting columns as appropriate2. Filters - Ability to create custom filters to switch between different types of submissions. The filter option that is there appears to be limited and does not allow customization. Looks like this was previously suggested with pretty good amount of likes but that idea was locked due to inactivity, so resurfacing this idea: Ability to adjust view on the Submitted Requests p... - Adobe Experience League Community - 528472
Description - The filters you create in the Workload Balancer do not become available in other areas where the workload balancer is embedded. If you create a filter in a Project's Workload Balancer, it's not available in a Teams Workload Balancer of the Resource Management page's Workload Balancer. Instead you have to create everything from scratch in each area that you are interacting with the Workload Balancer. Why is this feature important to you - Cuts down on the amount of rework needed for creating and sharing filters. How would you like the feature to work - If you are creating a filter for the Workload Balancer that filter should be accessible on any of the pages that the Workload Balancer is embedded on. Current Behaviour - If you create a filter for the Workload Balancer in the Resource Management page, that filter is not automatically available for use when you pull up the Workload Balancer in a Team page or a Project page. If you want the same filters you have to create them from scratch.
Description - Similar to this old idea, it would be helpful to configure approvals based on a few more options. Why is this feature important to you - We're always looking for ways to reduce the number of clicks a user has to make. In our case, we have an intake process that is purely approval-based. Without approval logic, my decision-maker must also close the request after approving. How would you like the feature to work - Allow logic to define what happens upon approval (ex. upon approval, close this issue). Also prompt the decision-maker to provide comments and have those comments appear in the object's Updates. Current Behaviour - For an issue approval, we can only define what happens when the issue is New and then when rejected.
Description - Assigning approval flows to be used by certain groups is helpful for group admins. It also allows easier auditing of approval flows by who is using them. However, when we have separate request queues that are owned by different groups, they need unique approval flows. Several of our request queues send approvals to the same type of person. Why is this feature important to you - I have to create copies of approval flows for child groups. Then, when approvers change, I have to update multiple approval flows. Yes, I could workaround this with a Team, but when there is just one approver, a Team is extraneous. How would you like the feature to work - When an approval flow is set to be used by a certain group, any child groups should inherit the ability to use the approval. Current Behaviour - Currently only specific groups can use their approval flows.
Description -Why is this feature important to you - Allowing users to change individual line colors in graphs is essential for clear data visualization. This feature enhances the distinction between multiple datasets, making it easier to identify trends and patterns at a glance. Additionally, for a large business with multiple Lines of Businesses, customizable colors, enable better alignment with branding guidelines, creating visually consistent and professional reports.How would you like the feature to work - Being able to say lock "Value X" to blue, and "Value Y" to red across all visualizations (regardless of which one has the highest count), or just being able to make specific visualizations look better and to match our different brands' colors by adjusting their colours specifically would be a fundamental feature.Current Behaviour - You cannot change individual visualizations. What one can do is change the colour palette for the entire project.
Description: The update to the Custom Form Field Logic in version 25.4 introduced some frustrating issues. Clicking 'Add Logic' opens a full-screen view unnecessarily. The primary concern, however, is that the Field Name is no longer displayed—it only shows the front-end Label.Why this feature matters to you: When working with multiple fields, being able to see the Field Name serves as a valuable point of reference, especially when using numbered references for better organization.Desired functionality: The feature should operate in a smaller view screen while ensuring the Field Name is displayed alongside the front-end Label.Current behavior: The logic editor opens in full screen and does not display the Field Name.Example:
We are on a Quarterly product release schedule and in the upcoming "24.7" Release, Adobe has stated that they will be replacing the legacy form builder with the new "Form Designer". In the legacy form builder, for each field, we have ability to enable the option "Track field changes in update feeds". This option was removed from the new Form Designer and now the only way to set this option is from the Interface tab under Setup. (Setup > Interface > Update Feeds > Tracked Fields > Custom Fields). I submitted a ticket to Support, and received the following suggestion: If you would like to see this checkbox to track these fields be retained within the Custom Forms area as it was in legacy, please submit this as a feature request via our Workfront community on our Experience League site. So here I am, requesting that this ability be retained in the new Form Designer tool. Please!
Idea: Allow ability to expose project level information on a request or issue form. We have a need to expose things like dates that allude to key deadlines or even things like key project data when submitting through issues on in process projects. This would help create much more flexible use of calculated fields and functionality that appears to be essentially there already. Current behavior: There is already the ability to add a calculated field to a form that reads from the project level, but this simply is just not updated (or calculated) until after the form is submitted. How could this work? The idea would be to turn on the dynamic calculations or even simply calculate upon opening of a queue topic form to expose the current values. The amazing thing is this essentially already works today! Just need to have a calculation upon opening to capture the data from other objects levels! Attached a mocked up sample that shows how a simple {project}. indicator in front of a field will read the project level data, just not until after submission.
Description - It would be great if Adobe could give recommended schema-level governance labels on their own standard field groups to speed up labelling. Why is this feature important to you - Applying field labels to the schema fields is a process that is new to many clients, especially to people from legal departments. With Adobe's recommendation to stick with standard field groups as much as possible, it would be amazing to give recommended labels for the fields contained in these field groups. That would surely make many people's live a lot easier and reduce the room for errors. How would you like the feature to work - upon selecting a field in the Labels tab, show additional information like "often labelled as" Current Behaviour - Every field has to be labelled, and no recommended label is given which is a cumbersome process.
Request for Feature Enhancement (RFE) Summary: Functionality improvement to allow users to define the tag order for CF Use-case: The order in which tags are displayed is very important because it is a selling point of the product. Currently, they are displayed in the order specified, but in the new CF editor, they are displayed in ascending order of tag name. Please improve the function so that users can define the display order of tags themselves, because it has a large impact on business. Current/Experienced Behavior: The old editor displays tags in the order you specify, but the new editor displays them in ascending order by tag name. Improved/Expected Behavior: The tag order specified by the user is maintained even in the new editor. Environment Details (AEM version/service pack, any other specifics if applicable): AEM aa CS 2025.03 Customer-name/Organization name: TOPCON POSITIONING ASIA CO LTD Screenshot (if applicable): Code package (if applicable):
Description - Currently the "Post as update..." message shortcut in Slack App does not accept links or show the name of the @mention tags making the feature to lost part of the relevance since people want to understand who is being tagged (we just see a bunch of codes) and also it simply removes any links from the post update.Why is this feature important to you - with the ability to share a Slack update on Workfront we want to make sure to understand who was tagged and also which links were shared. Currently we're not able to see that, which loses the need for us to connect the update to Workfront.How would you like the feature to work - When we post a Slack update to Workfront, I'd like to bring the name of the person that was tagged and also any links that were shared in the update.Current Behaviour - Currently the "Post as update..." message shortcut in Slack App does not accept links or show the name of the @mention tags making the feature to lost part of the relevance since people want to understand who is being tagged (we just see a bunch of codes) and also it simply removes any links from the post update. Thank you!
Request for Feature Enhancement (RFE) Summary: Link Reference Update inside experience fragment when creating a live copy or rollout an experience fragment Use-case: When we rollout or create a site/live copy of a page the link reference gets updated from language master/language to respective country/language inside components with in that page. But in experience fragment this feature is missing Current/Experienced Behavior: Link Reference does not get update inside experience fragment when creating a live copy or rollout an experience fragment Improved/Expected Behavior: Link Reference Update inside experience fragment when creating a live copy or rollout an experience fragment Environment Details (AEM version/service pack, any other specifics if applicable): Customer-name/Organization name: Screenshot (if applicable): Code package (if applicable):
It would be useful to be able to delegate work to multiple people. I am in an agency environment and one person may support multiple accounts (portfolios in our instance). When they are out it would be ideal for them to be able to say delegate tasks in this portfolio to person 1 and in this portfolio to person 2.
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.
