Build better products with our product team
Description - In Moment Customer satisfaction survey or feedback Custom form as an Inbuilt offering in Workfront would be good. A STAR rating or Grading based survey on set parameter that can be customised.This form could be used after a issue/project is closed to be filled by the Requestor. Why is this feature important to you - Feedback is important part of improving our processes and best done when fresh in memory and need not be sent as separately as EMAIL. How would you like the feature to work - Survey form / popup should come up when the user logs in to WF if one of his projects / issue has been closed upon completion. The survey form should be an inbuilt custom form that can be modified as necessary. A very simple star based rating for gauging user satisfaction. Current Behaviour - None available
I believe I have seen this in another thread somewhere and wanted to check on it to see if there have been any updates around this feature but can't seem to find it.. This would be a HUGE win for us if this functionality was possible. Description - Ability to utilize the same 'multi-choice' field on multiple custom form hiding certain choices. Why is this feature important to you - We use the same "Asset Type" dropdown field across all of our different custom forms so that we can easily report on this data, however not all Asset Types should be an available option across all forms. For example: How would you like the feature to work - Example: On Custom Form 1 we would like the 'Asset Types' dropdown to include Print, Email, Social, Web as options to choose from. On Custom Form 2 we would like to hide Web as an Asset Type for them to choose, and only display Print, Email, Social. Current Behaviour - Currently (to my knowledge), you cannot hide any options without it hiding on ALL custom forms. We have to create workarounds on each form where (ex.) Web is chosen as an Asset Type on Custom Form 2, we populate descriptive text that says "Sorry this is not an available option, please de-select this choice". However, this is not always a successful method because the form still allows you to Submit, so if a requestor purposely ignores it, or selects multiple Asset Types in which they may miss the message and continue with the form- it causes more work and aggravation on the team to have to reach out and let them know they cannot request that in which we receive a "well why is it an option then?" response 🙂 We are trying to avoid creating multiple versions of the same field so that we can pull clean reporting.
DescriptionCreate a bulk update interface designed to efficiently manage and update multiple multi-site and multi-language experiences simultaneously. Why this feature is importantWe manage a large volume of experiences that often require coordinated updates across multiple sites and languages. Performing these updates manually is not only extremely time-consuming, but it also introduces a high risk of human error. A purpose-built solution would significantly streamline our workflows, improve accuracy, and free up valuable time for strategic initiatives. Ideal functionalityThe feature should provide a centralized interface where multiple activities can be selected and updated at once—without the need to drill into each one individually. This would include the ability to apply consistent changes across experiences, preview updates, and track changes in real time. Current workaroundWe’ve implemented a temporary solution using APIs and spreadsheets, which has helped address some needs. However, it requires ongoing maintenance, lacks flexibility, and presents limitations when scaling. A native solution would eliminate these barriers and create a more seamless, user-friendly experience.
Request for Feature Enhancement (RFE) Summary: In the AEM Assets touch UI (Tools - Assets - Reports) we would like an option to configure the assets reports to run on a repeating schedule. For example, I want to run the asset uploads report every week to get info on the uploads from the previous week. Another example, I would like to run the assets downloads on the first day of the month for the previous months data. Use-case: This will save resource time and improve user experience by having a report ready available at the start of the day, week, or month without the need to configure the settings each time. Current/Experienced Behavior: When selecting Tools - Assets - Reports - [select report] - Craete - The 'Schedule Report' section allows you to select 'Later' but that is only a one time run. Improved/Expected Behavior: When selecting Tools - Assets - Reports - [select report] - Create - The 'Schedule Report' section will have an option to run 'Later' that includes ability to select frequency (daily, weekly, monthly). Environment Details (AEM version/service pack, any other specifics if applicable): AEM Cloud Customer-name/Organization name: Jennifer C. Randle/Accenture Screenshot (if applicable): Code package (if applicable):
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
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.
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):
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 - 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.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.