Build better products with our product team
Description - (I am sure this has been asked many times, so I just wanted to revive the idea) We need an automatic "Previous Period" date range component that automatically creates a dynamic lookback window relative to the selected date range on the panel. Why is this feature important to you It is basically not practicable to have fixed previous date range components in place that only work until one changes the panel date range. Example Freeform table using the last 7 full days (Panel date range) vs the previous 7 days (custom date range in the workspace project). Now, someone decides to change the date range on the panel to "last 30 full days" Result the custom date range still displays only 7 days, the rest is 0 the comparability between panel date range and freeform table is completely useless this becomes even more obvious / erroneous if you are applying a summary change visualization on the two columns, not taking the same number of data points into consideration How would you like the feature to work The "Previous Period" date range automatically calculates the previous x days / weeks / months before the currently selected date range, based upon that value. Should I change the panel date range, this will automatically update the data that has been filtered by this date range e.g., in a "Summary change" visualization Current Behaviour once you change the panel date range, your data is messed up, becoming unusable this is extremely annoying for all levels of analytics consultants. I don't know how many times I have explained this to clients or had the same issues myself other analytics tools like Looker Studio do not seem to have that problem, see https://support.google.com/looker-studio/answer/9272806?hl=en For an analytics solution as mature as Analysis Workspace, this should be a standard feature. @ericmatisoff your two cents on this idea would be amazing. You seem to have the best connections to the product team
Currently requestors can view their submitted requests in the Classic interface and then choose to copy their request allowing a new request to be edited and submitted as new. Our teams have many year/over year requests (i.e Open Enrollment, Events etc) so this prevents manual copying & pasting. I was informed the there is no official Adobe documentation confirming whether the Copy feature will be added to the New Workfront Experience in the future. Since this is a newly introduced feature, it may be considered for inclusion once the Classic interface is fully retired. I would love this feature to be included.
DescriptionBefore the migration, users who logged directly into Workfront without an existing account were automatically assigned a requestor account. This functionality is no longer working. Now, admins must manually create accounts for these users, which causes delays in our operations since requestors cannot submit tickets until access is granted.Why is this feature important to you?After the migration, the lack of this functionality has increased the workload for admins and slowed down ticket processing.How would you like the feature to work?Ideally, users who access Workfront without an account should be automatically provisioned with one and assigned to the appropriate product.Current BehaviorUsers receive an account, but they are not assigned to the product automatically.
When an output is selected on a module, move that item to the top of the outputs list for easier access to those fields. It's painful to scroll through 100's of fields to find one that you selected as an output.
Description - We love the new Custom Form Enhancement that gives our users the ability to collapse sections they are not interested in. While this feature is awesome we're hoping it can be enhanced further. Please give the Custom Form owners the ability to default certain sections to be collapsed automatically. Why is this feature important to you - This will ensure that anyone looking at the custom form is not distracted by sections that are not applicable to most users. How would you like the feature to work - A checkbox on the Section field within a custom form would be beneficial. Perhaps it could be a checkbox that states "Collapse section by default". Current Behaviour - When you uncollapse a custom form, all sections are uncollapsed by default. This setting would give the custom form owner control over what sections are uncollapsed when the user first views the form.
Non-Standard Marketing Attribution does not utilise persistence from eVars and Marketing Channel, utilising only the instance of each of these variables during the lookback window. As such, there is a large "none" bucket for Marketing Channel, although Marketing Channel without using these non-standard attribution metrics does not contain a none - all channels are account for. This is because the Marketing Channel Processing Rules sets channels based on what can or cannot overwrite previous channels. For example - if someone comes via PPC and then via Direct - if the PPC is outside your look back window, but the Direct is not, the non-standard attribution would give credit to "None" because Direct was not set-up to overwrite any other channel. Since the non-standard marketing attribution events ignores this persistent, it would be good to have an options for the following:1. Follow the Marketing Channel persistence, ensuring the last "paid" channel continues to be given credit.2. Follow current standards, BUT re-run the marketing channels rules to show what was the channel for each instance was, ensuring None shows the non-overwritable channels. Thanks
Description - Auto-populate assignees to assignments when tactics are requested.Why is this feature important to you - Assignments are a recurring and tedious tasks that project managers have to do for every single tactic. If we could identify assignees at the tactic initiation request, it would save significant time setting up projects and tactics. How would you like the feature to work - When a tactic is requested, the requester would identify assignees for the task assignments, and the assignments would be updated when the tactic is created.Current Behaviour - A tactic is created with assignments, the project manager has to update the assignments to the specific assignee using Workload Balancer < Bulk Assignments.
Request for Feature Enhancement (RFE) Summary: In AEM Cloud UE, I want to update language copies or create structure. I want to be able to select particular languages without having to check all 33 languages first and then uncheck the ones that are not needed so that I can work efficiently and without wasting time. Use-case: Select a page, go to the left Current/Experienced Behavior: The language copy update dialogue only shows after selecting all 33 languages at once. If I want to work with (a) particular language(s) only, I need to uncheck all languages that are not needed. Improved/Expected Behavior: After the language copy rail opened, I want to be able to check the language layer I want to update immediately, without having the need to select all 33 languages first and THEN select my language Environment Details (AEM version/service pack, any other specifics if applicable): AEM Cloud, Universal Editor, EDS Customer-name/Organization name: SAP SE Screenshot (if applicable): Code package (if applicable):
It is nice to be able to store/move and organize Templates in a folder structure. But when you start to have many Templates and you want to organize them, it is hard to know witch Template is in witch folder, and if a Template has been placed in a folder or not.So to be able to work faster and easier we would like to have a feature that could show the name of the folder where a Template is stored in the folder structure. It would/should then also be easy to see if a Template is still on Root, and has not been moved into any folder.This option would make it easier for the user to manage the Templates in a folder structure. And with a increasing number of Templates a fast and easy working process is needed to not spend to much time on administration that should be used on running you business.
Request for Feature Enhancement (RFE) Summary: I'd like the possibility to add default environment variables for cloud manager pipelines. Those variables would available and up to date on any new pipeline execution.We would still be able to override those variables at pipeline level. Use-case: I'd like to setup default version of NODE for FE pipelines as well as some tokens for private npm registry. Current/Experienced Behavior: Env variables needs to be set for each FE pipelines. When a secret token expires, every pipelines need to be updated. Improved/Expected Behavior: Set some variables at program level, that are automatically assigned during pipeline build phase. Environment Details (AEM version/service pack, any other specifics if applicable): AEM as cloud service Customer-name/Organization name: Danone Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: AEM Guides Content Authors face the issue of not able to use UI in Author to insert the new Attribute Value, instead they have to go to source view to add it. However, to make it come in Author view, the only option Authors find is to add in Folder Profiles, Conditional Attribute which seems difficult for Authors to understand and follow, Is there a way Authors can create new Value as they do in Source in Author view itself. Currently how it is handled:https://experienceleague.adobe.com/en/docs/experience-manager-guides/using/user-guide/map-management-publishing/output-gen/conditional-content/generate-output-conditional-attribute-profilinghttps://experienceleague.adobe.com/en/docs/experience-manager-guides-learn/videos/advanced-user-guide/folder-profiles#edit-conditional-attributes-in-the-global-profile Use-case: AEM Guides Content Authors face the issue of not able to use UI in Author to insert the new Attribute Value, instead they have to go to source view to add it. However, to make it come in Author view, the only option Authors find is to add in Folder Profiles, Conditional Attribute which seems difficult for Authors to understand and follow, Is there a way Authors can create new Value as they do in Source in Author view itself. Currently how it is handled:https://experienceleague.adobe.com/en/docs/experience-manager-guides/using/user-guide/map-management-publishing/output-gen/conditional-content/generate-output-conditional-attribute-profilinghttps://experienceleague.adobe.com/en/docs/experience-manager-guides-learn/videos/advanced-user-guide/folder-profiles#edit-conditional-attributes-in-the-global-profile Current/Experienced Behavior: Authors have to learn to add values in folder profiles Improved/Expected Behavior: Values saved OOTB on first type and suggests for future without adding in Folder profile conditional profiling Environment Details (AEM version/service pack, any other specifics if applicable): Adobe Experience Manager 2025.10.23122.20251023T134343Z-251000 AEM Guides 2025.10.0.278 Customer-name/Organization name: Sub-Zero and Wolf Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Option to edit the comment of a particular version of the Page in AEM as Cloud Service in AEM SITES. Use-case: When trying to add comment for each version of a page, if done mistakenly, there is no option to update the comment OOTB. Current/Experienced Behavior: When trying to add comment for each version of a page, if done mistakenly, there is no option to update the comment OOTB. Improved/Expected Behavior: Provide an option to update the comment OOTB. Environment Details (AEM version/service pack, any other specifics if applicable): Adobe Experience Manager 2025.10.23122.20251023T134343Z-251000 AEM Guides 2025.10.0.278 Customer-name/Organization name: Sub-Zero and Wolf Screenshot (if applicable): Code package (if applicable):
As we are working more and more with AJO, the content in the platform increases every day with audiences, templates, fragments, Journeys etc. Since there are many users working with different activities in the same base, against the same customers each user as a set of "most used content/features" Therefor it would be nice if each user could mark there personal favorites from there total list of created audiences, Journeys, email templates and fragments. This would make it easier and faster to work with if you dont need to navigate in the list of the total every time you are looking for something. If you then could filtered on your personal favorites you would get to your most important stuff faster and easier.
Today we can see if the templates are organized or not when viewing the root folder or "view all" feature. But if we "fast and easy" want to check if the templates is organized in thee right folder, we need to check all folders and see what is inside. A typical use case is when you need to reorganize the structure - witch you need to do from time to time. If we from the "view all page" could have a column with folder name, where the template i stored, we could fast and easy just browse the list and see if the templates is organized in the right folder. It could be a config, that you can turn on/of in the table view in the GUI. Like you can do with other columns in other parts of AJO.
Request for Feature Enhancement (RFE) Summary: When using private GitHub repo for our AEM code on Cloud Manager it always triggers FS code quality pipeline, even if the repo is actually meant for FE pipeline. Use-case: Use private github repo in cloud manager for FE pipeline. Current/Experienced Behavior: For each pull request, a full stack code quality pipeline is created automatically. Improved/Expected Behavior: Add the possibility to disable that check when not relevant, in that case for FE only projects. Environment Details (AEM version/service pack, any other specifics if applicable): AEM as cloud service Customer-name/Organization name: Danone Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Asset Selector Microfrontend - Rule-based hiding of Assets Use-case: AEM is used to manage and host the website. Assets are delivered from Publish.A 3rd party, external, customer-facing application uses AEM as delivery system for their assets. The according backoffice application uses the MFE to select assets. Users of the 3rd party application must not see or select assets that are in a certain state (e.g. have not been published or approved or are expired or ...). Otherwise the app would store references that have not been approved (in this case "published") and cannot be served from Publish.IMPORTANT NOTE:"Hiding assets" is not the same as filtering for assets (which can be configured): "Filtering" always triggers a search, i.e. it would display all assets of the current and _all subfolders_. Also, this is a user action. "Hiding" in turn would a) not be a user action, but configured by the administrators. And b) would be applied automatically when users browse through the folder structure (I believe a majority still uses folders and browsers over search/metadata). This hiding of course also needs to be applied to the results when a user does an explicit search. Current/Experienced Behavior: All assets are displayed - regardless of their state Improved/Expected Behavior: Administrators can define a set of rules that prevent certain assets to be displayed. ORThe MFE calls a callback on each asset tile / row it wants to render and a customizer can provide code to return a value to enable/disable/hide the asset's tile. Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS latest Customer-name/Organization name: any Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Asset Selector Microfrontend MFE: Make Status field Configurable to display publication status Use-case: The Status indicator on the MFE seems to have been designed for an Assets-only installation, and with the new Asset view in mind, only. On Enterprise installations, i.e. where one has an Author and a Publish system, tasks and the approval status are rarely used. Instead user would "publish" an asset, which implicitly means "approved" (otherwise why would you publish).Use Case: AEM is used to manage and host the website. Assets are delivered from Publish.,A 3rd party, external, customer-facing application uses AEM as delivery system for their assets. The according backoffice application uses the MFE to select assets. This application needs to know which assets have been published. Otherwise it would store path references that have not been approved (in this case "published") and cannot be resolved on Published. Current/Experienced Behavior: The field dam:status is rendered hard-coded in the MFE. Improved/Expected Behavior: Make the status field in the MFE configurable, so that the provider of the MFE can choose what to display here. In the described use case, show the publication status (not the approval status). Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS latest as of Nov. 2. 2025 Customer-name/Organization name: any Screenshot (if applicable): Code package (if applicable):
The Home area as well as Document Version reporting needs to have the ability to filter out all the proofs a users is tagged to Review, even if they are not an Approver. The My Work area had this but the Home area never received this feature and ther are no reporting options to show a user their proofs as a "Reviewer". This is a very big gap that is causing my users significant frustration. Please vote this up! Thanks!
Request for Feature Enhancement (RFE) Summary: The "Assign to" selection dropdown menu within the AEM Guides review process does not filter results when a user's name is typed into the field. This requires users to manually scroll through the entire list to find and select a name.This issue significantly hinders workflow efficiency, especially in projects with a large number of registered users, making the process time-consuming and prone to selection errors.Steps to ReproduceNavigate to the AEM Guides interface and select content for review.Initiate a review process (Menu -> "Create Review Task").Click on the "Assign to" dropdown field.Begin typing the name of a known user into the field.Feature Request:Implement a type-ahead search or filter functionality for the user selection dropdown menu to allow for quick and efficient searching. Use-case: Ease of functionality Current/Experienced Behavior: Typing into the field has no effect on the list. The full, unfiltered list of users remains visible, forcing the user to manually scroll to locate the correct person. Improved/Expected Behavior: As characters are typed into the field, the dropdown list should dynamically filter in real-time to display only the users and groups whose names match the entered text. Environment Details (AEM version/service pack, any other specifics if applicable): 6.5 Customer-name/Organization name: Red Hat Screenshot (if applicable): Code package (if applicable):
We have found an issue in AJO making us concerned about how to handle emails in an always on activity - when the master email template is been updated. It seems like there is now obvious way of changing and updating a template, and at the same time keep the content that is created in a template used in an running Journey. Changing the master template directly in prod, or from a upgrade package is no problem. The issue is how to keep the created and customized content used in that template you are updating. In many cases you are just updating the "framework" like header/footer or other more than less static content in a template. And in a Journey you create the relevant content for this activity using the "static" framework. But when you need to change/upgrade the framework, and change the template in use with the new and updated version, the customized content is been deleted. Is is not able to update just the template, and keep the customized content inside the template. We strongly suggest that there could be a feature making it possible to update an email "master template" that is in use, and at the same time be able to keep the customized content that has been created using this template. The template is still a template and that framework is used in several Journey's. We run into serious problems it we need to re-create all content just because the the template has an update in the static frame content. If you in the back end could split between what is template code and content code this might not be a problem. It seems like those two things is merged together and AJO cant see the difference between template code and customized content code.
As we are working ahead with the AJO platform, we are also creating more and more email fragments. Today there is only a "Show more" option when the fragment list becomes longer than the screen size. The length of the list becomes that long because it shows all fragments, even those in draft status. When you are creating a new email, or a new template, it would be great if we could have more filtering options. Like just showing the Published once or just the one in draft f ex. It could be done by using check boxes like jo do other placed where you could filter tings in AJO..And buy the way: when you have used todays "show more" it is not any "show less" to go back if you want to.
Description - I would like to be able to append an unique coupon code/url link to an individual email. This would be a 1:1 append. Why is this feature important to you - My client has different retail partnerships they would like to send a coupon to as part of a "surprise and delight" or nurture program. How would you like the feature to work - I would like to be able to load the coupons into AEP and during deployment have AJO append a coupon to the email. Example, if I have an audience of 200K and 200K unique coupons, AJO would select a coupon, append to email during deployment and "burning" the coupon once used. Current Behaviour - Does not currently exist in AJO
OverviewThis change request proposes adding functionality to allow users to delete multiple journeys simultaneously from the Journey overview, with built-in dependency checks to prevent deletion of journeys in active states.Current BehaviorCurrently, users can select multiple journeys in the Journey overview (indicated by a blue line showing the number of selected items), but must delete journeys individually through each journey's ellipsis menu.Proposed ChangesEnable bulk deletion of multiple selected journeys through a single actionImplement/Keep as is - dependency checks to prevent deletion of "Published" (including "In review", "Dry Run") journeys. Only delete when status is Draft, Draft (Test), Finished or similar. Add a "Delete Selected" button that appears in the blue selection bar when multiple journeys are selectedDisplay a confirmation dialog showing:Number of journeys that will be deletedNumber of journeys that cannot be deleted (with their states)Option to proceed with deleting eligible journeys onlyValidationOnly journeys in Draft, Draft (Test), Finished or similar status can be deletedIf mixed selection (some eligible, some ineligible), provide clear feedback on which can be deletedAfter deletion, the selection counter should accurately reflect remaining selected itemsError HandlingIf deletion fails for any journey, show appropriate error messageProvide detailed feedback on which journeys were successfully deleted and which weren'tBenefitsImproved user efficiency when managing multiple journeysReduced risk of accidentally deleting active journeysConsistent user experience for bulk operations
BackgroundAudiences currently tracks Audience lifecycle statusThere is no way to know when the lifecycle status was last changed or who changed itBusiness NeedTrack the timestamp when an Audience's lifecycle status changesTrack which user or system process made the lifecycle status changeEnable reporting and analysis based on status change dates and responsible partiesSupport accountability and audit trail for audience managementProposed SolutionAdd two new columns to the Audience table/entity:"Lifecycle Status Updated Date" - timestamp of the last status change"Lifecycle Status Changed By" - identifier of the user or system that made the changeConfigure both columns to automatically update whenever the lifecycle status field is modified:Date field: current timestampChanged By field: current user ID or system identifierMake these fields visible in the IU interface alongside the lifecycle statusInclude these fields in relevant reports, audit logs, and analytics viewsBenefitsComplete audit trail of audience lifecycle changesAccountability for status changesAbility to measure time spent in each lifecycle stageSupport for time-based automation and workflowsEnhanced reporting capabilitiesAbility to follow up with specific users who made changes when questions arise
Description -Why is this feature important to you - Client requirementHow would you like the feature to work - On the kanban board we want to show the details of checklist items or sub task which we added into the ticket can show on board itself along the with ticket name. So user no need to go inside the ticket everytime to see the checklist items and can mark complete from the board.Current Behaviour - We need to go inside of each ticket to get the details.
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.
