Build better products with our product team
Description: to have the ability to collapse/uncollapse items in PrioritiesWhy is this feature important to you: Many of us will have several groupings under priorities, specially if we group by project. It will be useful to have the ability to collapse the results.How would you like the feature to work: to have a carrot icon in the top, similar to other groupings in WF, to have the ability to collapse/uncollapse all results at once.Current Behaviour: we can't collapse/uncollapse all results at once.
It seems like it would be enormously helpful for requestor/reviewers to see on the new Home screen a widget containing tasks that were converted from requests they raised. You can do this in custom reports or project filters (using "converted issue originator = me") but it does not work in the Home task widget. The task widget only shows tasks that are assigned to the logged-in user, which only benefits Work license holders and not the vast majority of users with requestor/reviewer licenses. I raised a support ticket on this; the rep was very helpful but confirmed the above and suggested I raise this as an idea.
Description These days, the AEP sources data prep UI for calculated fields is lacking basic functions to (easily) transform incoming data structures like arrays through a computed field into a target structure of any kind which makes it really cumbersome to work with. Also, asterisk syntax is only supported in standard mapping fields. Why is this feature important to you Well, the source data often does not match the XDM schema data and has to be brought into the right format. The provided functions are insufficient. The destinations data prep, however, seems to contain more functions to transform hierarchies. How would you like the feature to work Let's start with something trivial like looping over arrays to transform their data. Destinations Data Prep: transformArray([5, 6, 7], x -> x + 1) Sources Data Prep: ??? Current Behaviour - It seems impossible or at least extremely cumbersome to do even minimal transformations on any array or object data on the Source side. This in turn puts potentially a lot of extra work on the devs to provide the right data input format, potentially increasing the size of the to be imported data significantly if the target structure has to be pre-built. This comes with a lot of implications like necessary adjustments on the data providing side, should anything ever change in the schema.
Description -Add the ability for Workfront Users to create a Custom Fiscal Year "wildcard" filter. Why is this feature important to you - Our Fiscal Year is very different from Calendar Year. Leadership doesn't find value in Calendar Year, they want Fiscal Year.How would you like the feature to work - Be able to have a between "ANY" Year with a specific Month/DateCurrent Behaviour -There is a Calendar Year, but not Fiscal Year.
Suggested improvements:- Fix spacing of left column- Make the additional time slots optional, current feature makes the calendar too clunky/ tall - Have the order of the tasks match the order of the column on the left, don't move completed tasks to the top- Make task information visible by hovering over the task - Add capability to hide Saturdays and Sundays
Description - We've had feedback from a couple teams who manage our automation for different business units. They heavily use calendars to see what emails are going out in a week or month. With a larger volume of email tasks, the new view truncates what they can see on any given day and forces them to click "see more" and scroll through a tiny pop-up to see all their tasks. The weekly view is a little better, but they also need to see what tasks they have scheduled week over week. Why is this feature important to you - Our automation teams have strict regulations on how many emails can be sent to an audience within a period of time. They use calendars to visualize this metric on their weekly calls. How would you like the feature to work - We'd love to see the day squares to expand to allow for all items to show at a glance. Similar to the previous version of the calendar. Current Behavior - The new view truncates what our teams can see on any given day and forces them to click "see more" and scroll through a tiny pop-up to see all their tasks.
There's been previous conversations about how "before" date filters include blank values, and whether or not that is ideal behavior. I think the best solution to this would actually be to add another constraint to date/datetime fields called "include blanks: true/false." That way you could make determinations definitively whether blank dates should be included in each filter.
Description -Why is this feature important to you - We have fusion scenarios set up for specific fields in custom forms. When folks can enter in any information within a single-select drop-down it causes fusion errors, time in me deciphering what the heck was added, and allows to much power to be given to someone in a non-admin role. How would you like the feature to work - Follow the thought process for "mandatory fields" and add a checkbox that says "should this field be locked."Current Behaviour -
Users would like for the Proofing module to behave like a browser (for interactive proofs, webpages), and display the hyperlink at the bottom of the page when hovering your mouse over that respective button. This feature is not currently available and would help them quickly check if the are any blank/not linked buttons on the page they are working on. Please see attached example on how they would like it to work:
Description - Allow for multiple conditions apply to Column Rules, Report View Why is this feature important to you - Sometimes condition on column view in a report is a combination of multiple rules and not only one. How would you like the feature to work - Allow for multiple conditions be selected in Column Rules, Report View Current Behaviour - Only one condition can be defined in the rule, rather than combination of multiple ones.
Description - Update the dimension operator in Annotations from AND to OR. Why is this feature important to you - Currently, if an annotation includes multiple dimensions, it only appears on a Workspace dashboard when all of those dimensions are present. If the dashboard contains only one of the specified dimensions, the annotation won’t be visible.For example, if I create an annotation using both eVar1 and eVar25, I must include both in the dashboard for the annotation to appear. To work around this, I have to create separate annotations for each dimension. How would you like the feature to work - Change the annotation logic so that it uses the OR operator. This way, the annotation will appear if any of the specified dimensions are present in the dashboard. Current Behaviour - Annotations use the AND operator, requiring all listed dimensions to be present for the annotation to display.
Description - Workfront Dark Mode Why is this feature important to you - Default Workfront is incredibly straining on the eyes How would you like the feature to work - Provide a black or dark background instead of white Current Behaviour - Non-existent
Description - Allow classifications based on date dimensions like 'Day'- this would make analysis of custom date periods like financial years, financial weeks, seasons, etc. much easier. Currently if you want to work with something like this you have to create individual date ranges for every value. If you could classify 'Day', you would be able to upload a single .tab file that mapped the Day to all the custom date classifications you want, then to analyse these you would only have to drag in a single dimension in workspace.Why is this feature important to you - My analytics team have asked for better implementation for datespans like financial weeks. They currently use date ranges, which is very manual when analysing long periods that split into many date ranges as they have to drag in each week individually.How would you like the feature to work - In the report suite traffic/conversion classifications tab, add 'Day' to the available dimensions to create classifications based on. Then in classification importer you will be able to upload a classifications file that maps the Day value to custom date classifications. Current Behaviour - Currently the only way I can find to do something like this is to track a custom eVar for the date the user is on the website, then create classifications based on that. The issue with this is that it isn't retroactive, so you can't use these classifications for the time before you started tracking the evar. Currently no date dimensions are available in the classifications settings to use.
Description -For any project, under Hours Tab, the total hours at the bottom shows the addition of the line items. The client's request is, it should show the addition of all the hours at the bottom of the page.
Description - More than one "Regex Replace" functions should be allowed in CJA derived fieldsWhy is this feature important to you - This will allow CJA users to build more refined rule based classificationsHow would you like the feature to work - A derived field should have options to add multiple "Regex Replace" functions in it's definition.This will help in building more refined rule based classifications (similar to Adobe Analytics' Classification Rule Builder) where a field can be created by matching multiple regex strings.A very simple requirement could be a field with two different formats of values in it having different number of delimiters. An example could be below two values,1997:Brand:Model1997:Brand:Model:ReleaseTo create a derived field that extracts all the brand values from these two formats we need to match two regex strings,^(.+)\:(.+)\:(.+)$ and return $2 as value^(.+)\:(.+)\:(.+)\:(.+)$ and return $2 as valueThis can be achieved by adding two "Regex Replace" functions in the derived field but currently we can use this function only one time per derived field.Current Behaviour - Currently CJA allows only one "Regex Replace" function per derived field.
Request for Feature Enhancement (RFE) Summary: Scheduled Copy content activities to lower environments from Prod environment Using GenAI Models in AEM Cloud Manager Use-case: We request the development of a feature in Adobe Experience Manager (AEM) Cloud Manager that leverages Generative AI (GenAI) models to enable the capability of scheduled copy content activities to lower environments from Prod environment. This feature would allow DevOps/Support teams to trigger content copy activities to lower environments on specific dates and times through GenAI-based workflows in a scheduled manner. Key Benefits: Reduction in manual effort : The biggest advantage of this feature would be - a great reduction / savings of manual hours of the AEM support team/application team in the monitoring of Copy content activity , Greater efficiency and reduction in the waiting times during monitoring ( incurred by the support team while content is being copied in Stage and Dev ). Automated Scheduling: Users can set precise times and dates for copying content to lower environments, ensuring updates occur during optimal windows, such as off-peak hours, minimising disruption. This will reduce the manual effort in solving the most common business requirement of content refresh from Prod to the lower environments, after every regular interval like once in 15 days or after every release. Enhanced Efficiency: GenAI models streamline the content copy process, reducing manual intervention and potential errors. Predictive Analytics: Utilize GenAI to analyze past content copy activities and suggest optimal times for future operations, enhancing overall system performance. Customizable Workflows: Tailor content copy workflows to meet specific organizational needs, providing flexibility and control over the process. Improved Reliability: Scheduled content copy activities ensure consistency and reliability, with GenAI models monitoring and adjusting workflows as needed. Implementation Details: Integration with AEM Cloud Manager: Seamlessly integrate GenAI models within the existing AEM Cloud Manager framework. User Interface: Develop an intuitive UI for scheduling content copy activities, allowing users to easily configure and manage the timing of these operations. GenAI Workflow Engine: Create a robust workflow engine powered by GenAI to handle the scheduling, execution, and monitoring of content copy activities. Analytics Dashboard: Provide a dashboard for users to view content copy history, performance metrics, and predictive analytics. This feature will significantly enhance the content management and content backup capabilities of AEM Cloud Manager, offering application support teams a powerful tool to manage content copy activities efficiently and effectively, with very low effort. Current/Experienced Behavior: There is no such workflow/feature available in AEMaaCS as of now for scheduled copy content activities. Improved/Expected Behavior: We request the development of a feature in Adobe Experience Manager (AEM) Cloud Manager that leverages Generative AI (GenAI) models to enable the capability of scheduled copy content activities to lower environments ( at the time as scheduled by the DevOps team ), resulting in saving of manual efforts/hours during the copy content activity and enhanced efficiency. This will be of great help in solving the most common business requirement of content refresh from Prod to the lower environments, after every regular interval like once in 15 days or after every release. 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): N/A Code package (if applicable): N/A
Description:Enable usage of Asset Request ID to allow us to group related assets and populate them as a single package to Bynder, improving our asset management process. Why is this feature important to you:As we enhance our asset management capabilities with Workfront and Bynder, we need a way to group related assets from a single task. This will improve efficiency, organization, and user experience, enabling easier tracking and management of assets. How would you like the feature to work:Introduce Asset Request ID to group assets. When assets are transferred, they should be sent as a package, utilizing Bynder's related functionality. The assets should automatically be marked as related and preferably show the actual user who uploaded them. If Asset Request ID is active in Bynder, Fusion can enable Workfront to bundle assets by leveraging subfolders etc when sending them to Bynder. Current Behavior:Currently, assets are transferred to Bynder individually without grouping or relation, complicating management and tracking.
Business Need: Stakeholders often require Year-To-Date (YTD) comparison of current year vs previous year on a daily/weekly basis to track ongoing performance trends. Challenge: Adobe Workspace does not support dynamic YTD vs YTD comparison directly. Users must manually change the date ranges or use limited preset options, leading to inefficiencies and inaccurate analysis. Adobe's Design Limitation:Workspace logic is snapshot-based, not dynamically contextual to today's date across years.Designed for fixed range comparisons (like Mar 1–Mar 31 this year vs same period last year) Current Gaps:No automatic rolling YTD comparison available.Static date ranges need to be updated frequently.Presets or Date Comparison help partially but fail when YTD is not the same number of days every year (due to leap years, weekends, etc.). Impact: Inconsistent reporting, increased manual effort, delayed insights for performance tracking and business decisions.
Request for Feature Enhancement (RFE) Summary: Reducing Stage/Prod deployment Pipeline execution Time Using GenAI Models in AEM Cloud Manager Use-case: We are requesting for the development of a feature in Adobe Experience Manager (AEM) Cloud Manager that leverages Generative AI (GenAI) models to reduce the execution time required for stage and production deployment pipelines in AEM Cloud manager. This feature would fast-track regular deployment tasks in the Adobe Cloud pipeline using GenAI models , including Unit Testing, Code Scanning, Image Building, Product Functional Testing, Custom Functional Testing, Custom UI Testing, and Experience Audits. Key Benefits: Accelerated Deployment: GenAI models optimize and expedite deployment tasks, significantly reducing the overall pipeline time. Enhanced Efficiency: Automate routine tasks such as unit testing and code scanning, allowing for faster and more reliable deployments. Predictive Analytics: Utilize GenAI to predict potential issues and optimize the sequence of deployment tasks, ensuring smoother and quicker pipelines. Customizable Workflows: Tailor deployment workflows to meet specific organizational needs, providing flexibility and control over the deployment process. Improved Reliability: GenAI models continuously monitor and adjust workflows, ensuring consistent and reliable deployments. Implementation Details: Integration with AEM Cloud Manager: Seamlessly integrate GenAI models within the existing AEM Cloud Manager framework. User Interface: Develop an intuitive UI for configuring and managing deployment tasks, allowing users to easily set up and monitor pipeline activities. GenAI Workflow Engine: Create a robust workflow engine powered by GenAI to handle the optimization, execution, and monitoring of deployment tasks. Analytics Dashboard: Provide a dashboard for users to view pipeline performance metrics, historical data, and predictive analytics. This feature will significantly enhance the deployment capabilities of AEM Cloud Manager, offering users a powerful tool to manage stage and production pipelines efficiently and effectively. Essentially the idea is to reduce the overall execution time of Stage/Prod pipeline and hence making the deployments faster during the release calls etc. This will also reduce the manual effort/time spend during the release calls. Current/Experienced Behavior: Currently it takes around 1.5 hours to deploy the code to Stage and then promote to Prod, using the Stage/Prod pipeline in AEM Cloud manager. Improved/Expected Behavior: Expected or improved behaviour is cut down this execution time to around 30 mins for the entire Stage/Prod production pipeline. This can actually help in saving a lot of man hours/support hours from the application support team during the release calls. This would also make the deployment of breakfix/hotfix items to Prod very quick and easy. 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): NA Code package (if applicable): NA
Description - The native fields of Portfolio and Program do not work the same as they should in the custom form as they do in the Overview. Why is this feature important to you - We need our PMs to select the Portfolio and Program for each project, so we added the native field to our custom form and made it required for them to fill out. Otherwise they miss doing this in the Overview of the project.How would you like the feature to work - Having the native fields of Portfolio and Program to work exactly like they do in the Overview. When you select a Portfolio, only the Programs for that Portfolio will be shown to select from. Current Behavior - Right now, when you select the Portfolio in the custom form, ALL of the Programs are listed. The PMs have to then search and scroll for the right Program. They can also select the wrong one, which they won't know that they did since it allows them to select any Program instead of the ones that are associated with the Portfolio.
Would be nice to lock folders so requesters cannot see assets until ready for them to review. Currently, requesters are viewing the "review" files that are meant for the art directors. Only solution we found was to "unshare" the requester from the project. Not ideal I must say.
Request for Feature Enhancement (RFE) Summary: Scheduled Stage and Production Deployments Using GenAI Models in AEM Cloud Manager Use-case: We request the development of a feature in Adobe Experience Manager (AEM) Cloud Manager that leverages Generative AI (GenAI) models to enable scheduled Stage and Production deployments ( at the time as scheduled by the DevOps team ). This feature would allow DevOps/Support team to trigger stage and production deployments at specific times through GenAI-based workflows. Key Benefits: Reduction in manual effort : The biggest advantage of this feature would be - a great reduction / savings of manual hours of the AEM support team/application team in the monitoring of deployments , and reduction in the waiting times ( incurred by the support team while code is being deployed in Stage and Prod ). Automated Scheduling: Application teams can set precise deployment times, ensuring updates occur during optimal windows, such as off-peak hours, minimising disruption. Enhanced Efficiency: GenAI models streamline the deployment process, reducing manual intervention and potential errors. Predictive Analytics: Utilize GenAI to analyze past deployment data and suggest optimal times for future deployments, enhancing overall system performance. Customizable Workflows: Tailor deployment workflows to meet specific organizational needs, providing flexibility and control over the deployment process. Improved Reliability: Scheduled deployments ensure consistency and reliability, with GenAI models monitoring and adjusting workflows as needed. Implementation Details: Integration with AEM Cloud Manager: Seamlessly integrate GenAI models within the existing AEM Cloud Manager framework. User Interface: Develop an intuitive UI for scheduling deployments, allowing users to easily configure and manage deployment times. This feature will significantly enhance the deployment capabilities of AEM Cloud Manager, offering users a powerful tool to manage Stage and Production deployments efficiently and effectively, saving man hours during the deployment process. Current/Experienced Behavior: There is no such workflow/feature available in AEMaaCS as of now for scheduled deployments. Improved/Expected Behavior: Develop a feature in Adobe Experience Manager (AEM) Cloud Manager that leverages Generative AI (GenAI) models to enable scheduled Stage and Production deployments ( at the time as scheduled by the DevOps team ), resulting in saving of manual efforts/hours during the deployments and enhanced efficiency. 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): N/A Code package (if applicable): N/A
Request for Feature Enhancement (RFE) Summary: The redirect from /security to /libs/cq/security/content/securityadmin.html is part of the out‑of‑the‑box configuration in AEM as a Cloud Service. This affects the functionality when there is a page with the name "security". This page is never reached and always get redirected as per OOTB configuration. Use-case: any page created with the name "security" should be reachable and not redirect to another link. Current/Experienced Behavior: /security redirects to /libs/cq/security/content/securityadmin.html Improved/Expected Behavior: /security should not redirect to any other URL. Environment Details (AEM version/service pack, any other specifics if applicable): Publisher Customer-name/Organization name: Mamta Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Removing white space from generate page source Use-case: Additional white space lines are added in generated page source from sightly code. Current/Experienced Behavior: Additional white space lines increases file size of the page and thus impacts page performance Improved/Expected Behavior: Expected behaviour is all white spaces/white lines that sightly code generates should be removed when viewing page in publish instance Environment Details (AEM version/service pack, any other specifics if applicable): Latest AEM as cloud version Customer-name/Organization name: Abhinav Kumar Sinha / Deloitte consulting UK Screenshot (if applicable): Code package (if applicable):
Description - We want to be able to copy derived fields across connections in CJA. This is important for us, because we need to repeat these steps for every new sandbox that we connect manually.The feature should allow a CJA user to copy a derived field from an existing sanbox to a new one.Current Behaviour - Currently this is only possible within the same connection when copying a dataview. Consequently requiring the adobe user to fill in the derived fields manually --> 2 - 4h additional time/effort required.
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
