Build better products with our product team
Description - I have created a report to pull historical data on custom fields that their format is Rich text, however the report is not showing data (the fields show empty in the report). As the WF support advised: "What happens normally when you set those fields to be tracked is that it will post the updates in the update stream and it can reference the text of the field at that time to be able to display it in the report. Rich Text is one of the only exceptions to this. Normally you can use the "Old Text Value" and "New Text Value" fields like you have, but Rich Text is stored in an HTML format in order to maintain the formatting that is being used.Because of this, though the update stream can show that updates were made, the journal entry report doesn't have a native field in it that can pull and display that HTML text. It's a rare scenario, I think this only the second time I've seen this in the last 2 years or so.In this case the only way you would be able to go about tracking changes in a report like this would be if you were to create a new field, probably a paragraph text field, so that the text can actually be referenced by the report."Why is this feature important to you - My custom fields are in Rich text format and I would like to show my users history of changes/updates to the filed over time. Unfortunately, I cannot just disregard the already created Rich text format custom fields and replace them with Text fields as there are data populated in them within the system. How would you like the feature to work - I would like there a way to create a historical report of those fields, or at least allow creation of a calculated custom field that pulls data from the Rich text format fields and converts them to text, or change the report code in a way that I can convert the rich text value to text so that the report shows the data. Current Behaviour - Right now, it is not possible to view the data from Rich text custom fields in Journal Entry reports. Journal entry fields cannot even be pulled/accessed in custom fields/forms for a workaround.
To be able to delete batches that is older than 30 days.Today those batches are not available in the view.
I'm a Workfront system admin using the admin console. Recently, I created a test user account within the Workfront instance but then shortly decided to delete that account. I deleted the test account in the console and it was successfully removed. However, it has not been removed from Workfront itself. When I contacted support to see how to delete the account within Workfront, I was told there's no way to do that and that that's intentional because deleting a user account results in that user's history being erased. As an admin, I know it's best practice to deactivate an account rather than delete it permanently. But, as noted above, there are instances when an account, whether created temporarily for testing purposes or in error, serves no purpose and needs to be permanently removed. My recommendation is for the user deletion functionality be restored to admins who are using the admin console. Even better, it would be ideal to have the ability to delete users from within Workfront AND the console depending on where you happen to be deleting from.
If a user is added to Workfront with the wrong email address OR their email address changes, it would be ideal to be able to delete the user OR update the users email address. Right now that is not possible if your organization has been connected to the Admin Console.
This is a feature available in the legacy version of report builder, but not the new one. This feature is a tremendous help in doing reporting for fiscal time periods (WTD, MTD, QTD and YTD) through the previous day without having to manual work in Excel in the form of creating a fiscal calendar reference table, which would then need to get manually updated every year as well. This is an overview of how/why I used this feature:My reports are scheduled to send early in the morning, with reporting through previous day. Our Adobe instance is set up to use our fiscal calendar, and I use fiscal dates for reporting. The issue I have would be when the report is run on day that's the first day of a new fiscal period because I would want this report to actually run the data for the fiscal period that just ended. For example, our weeks start on Sunday. When the report is run on Sunday, I want my WTD reporting to be for the previous Sunday-Saturday. With new report builder, if I just have my weekly data requests set to be current week-current day, the Sunday sends of the report would just show partial data for the current day instead of showing the full previous week. With legacy report builder, I use a cell with a date formula of today-1 and use that as my anchor. So, with legacy report builder referencing that cell as the current day instead of using the day of when the report is running, when the report runs on Sundays, it thinks the current day is actually the previous day, Saturday. So then, a current week-current day setup would result in the previous Sunday-Saturday when the report is ran on Sundays.
Description:Introduce a feature in Adobe Real-Time CDP that utilizes machine learning to predict customer churn based on real-time behavioral and transactional data. The system would allow marketers to define churn-risk thresholds and automatically activate personalized retention journeys (e.g., email offers, push notifications, or loyalty incentives). It would also maintain a version history of churn prediction models for transparency, comparison, and improvement over time. Why is this feature important?Increases ROI of marketing campaigns through targeted retention efforts.Enables real-time action, which is crucial for saving at-risk customers.Provides transparency and iterative improvement through model versioning.Supports personalization at scale with minimal manual effort.Reduces revenue loss by proactively identifying customers likely to churn. Current Behavior:Adobe Real-Time CDP allows segmentation and audience activation, but lacks built-in churn prediction and automated intervention capabilities.Churn analysis typically happens outside Adobe in third-party tools.Manual workflows are needed to respond to churn risk.There is no native model history/version control in audience predictions. Use Case:An eCommerce brand wants to reduce churn among its subscription customers. Using this feature:The brand configures a churn prediction model in Real-Time CDP, trained on past behavior like reduced usage, late payments, or service downgrades.When a customer’s data shows signs of churn risk, the system immediately triggers a retention campaign offering a limited-time discount via email and mobile app.Marketers monitor model performance and view previous model versions to refine targeting strategies over time.
Today it is only possible to include the audience status. Including 'Segment name' and 'Segment ID' is useful directly in the .csv shared, if the receiver platform can't read off of the file naming, but can only evaluate input from the file itself.
Enable the option of configuring a source/destination account after it have been configured, such as changing and/or at least viewing the bucket name, folder path, fily type, include manifest toggle and compression format which is a part of the wizard when setting up the account, instead of having to create a new one.
The folder possibilities for storing Audiences in a folder structure has become a nice function. It save a lot of time to find your right Audiences when you dont know exactly the name. I would like to expand this functionality to also be able to use for Offers and Journeys. It will makes it easier to find what you are looking for. To be able to work even faster it would be nice with f ex a button in/on every folder that with one click could open the folder tree from where you are standing/clicking. It is nice with the tree but we still need to go inn and out from the folders to fint what we are looking for it we operate with a deep folder tree.
Project, Task, and Issue priorities are currently managed globally.We would like this functionality to be pushed down to Groups so that each groups can manage their own conditions lists.
Project, Task, and Issue conditions are currently managed globally.We would like this functionality to be pushed down to Groups so that each groups can manage their own conditions lists.
It would be great if Marketo had an API endpoint for managing fields, such as hiding them.For example, we have dozens of fields that we need to hide that are unused, and it is time-consuming and tedious to hide them one at a time.
Description of change you want to see:I would like the ability to expand or collapse the various top and side interface elements on the Adobe Workfront home page—specifically, the Adobe unified experience bar at the very top, the Workfront top navigation bar, and the "Home and Priorities" left-side panel. Currently, these elements take up significant vertical and horizontal screen space and cannot be hidden or minimized.Why is this feature important to you:This feature would greatly improve usability and workspace efficiency. The persistent interface elements reduce the available area for viewing and working on tasks, especially on smaller screens or laptops. Having the option to hide or minimize these sections would allow for a cleaner, more focused working environment and improve the user experience—especially for users who spend most of their time within the task list or dashboard views.How would you like the feature to work:I would like to see collapsible or toggle-able interface sections—similar to how the object navigation panel on the left side of object pages (like projects, tasks, etc.) can be expanded or collapsed. Ideally, there would be a small arrow, icon, or hover-triggered control to expand or hide each major UI section. The user's preferences (collapsed or expanded) could also be remembered across sessions for convenience.Current Behaviour:Currently, the Adobe bar, the Workfront top navigation, and the Home and Priorities side panel are fixed and cannot be minimized or hidden. This results in a cluttered interface and reduced usable screen space, which can make navigating and managing work more cumbersome.
Description - I have a field that I would like to duplicate and rename without having to create another field manually. Example - I need to manually create fields with drop down options on the open/close time for one of our specific locations (this can get extensive when building it out for each day of the week). Why is this feature important to you - It would save me a ton of time when building out custom forms. How would you like the feature to work - Have an option within the custom form area to copy existing fields (and rename them) similar to how you are able to do this with templates, projects, tasks, etc. Current Behaviour - Inability to copy custom fields (need to manually create each).
Description:Introduce the ability for multiple users to collaboratively build and refine audience definitions in Adobe Real-Time CDP with support for version history, change tracking, and inline comments.This feature would help cross-functional teams (marketers, analysts, data scientists) work together more efficiently while ensuring traceability and reducing errors in audience logic. Why is this feature important to you:Audience building often involves multiple team members, and right now, it’s hard to track who made what changes or why.Sometimes, edits overwrite each other or lead to confusion without proper documentation or context. How would you like the feature to work:Each saved audience should include a version history, showing what was changed, when, and by whom.Users should be able to leave inline comments on specific filters or conditions (like commenting in Google Docs).Rollback functionality should allow users to restore a previous version if needed.Notifications when changes are made would help keep teams in sync.Current Behavior:Audience building is a single-user experience with no built-in collaboration tools or history tracking.Teams must rely on external documentation or naming conventions to manage edits - which is prone to human error. Use Case:A global brand's marketing and data teams are collaborating on a holiday campaign audience.The analyst creates the initial logic, the marketer adds refinements, and both leave comments explaining choices.When the campaign under performs, they review the version history to identify what changed and when - leading to quicker iteration.
Request for Feature Enhancement (RFE) Summary: .aex & .aep (Adobe After Effects ) files are not supported in DAM today. Requesting to extend the support to these file formats Use-case: Current/Experienced Behavior: .aex & .aep (Adobe After Effects ) files are not supported in DAM Improved/Expected Behavior: .aex & .aep (Adobe After Effects ) files should be supported in DAM similar to .ai files. Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5.21 & Cloud Customer-name/Organization name: Mondelez Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Ability to bookmark things in AEM Author Use-case: All types of Touch UI activities Current/Experienced Behavior: Not often you can find yourself working on mid or long term implementations of features if you are a developer, or often working on a specific set of pages and assets if you are a content author, or continuously doing regression testing on specific points of the solution as a tester, or purely having to do only with a small portion of "everything" and not usually go in the entire content or solution all the time.In these often situations I found that the person working on that specific area tends to have lots of browser tabs opened, trying to go back and forth between them to do their work, to do investigations, trying or find things out, oftenly doing mistakes or forgetting where things were, and spending lots of time to untangle stuff and to make sure he is looking in the right place each time before actually addressing the actual underlying need he has. Improved/Expected Behavior: I propose that AEM would provide the possibility to create shortcuts/bookmarks lists within AEM. Different points in AEM should contain a Bookmark button (which points ?, that is something to be analyzed further). Clicking on this button should open a simple Dialog containing two fields for the user to fill in: name, which will be the visible label of the bookmark and group which will be the bucket list where the bookmark will be added to. Environment Details (AEM version/service pack, any other specifics if applicable): I believe this will beneficial as it will increase and boost productivity once the user can create his own lists of places to rapidly go to, not waste time to find same things each time and also avoid doing mistakes as it may happen that he might not go or look at the right place at some point. Example:Assuming I am working on some Dynamic Media implementation, and I often need to go to Tools, to the Dynamic Media cache invalidation page. In the same time I have a huge content of tons of sites but I only need to work on few 5 to 10 pages within the entire content hierarchy. Same for Assets, I only need to work with some specific assets, lets say some Content Fragments that I need to edit, save and publish. Plus, I have some config files stored in JCR and managed through some custom Coral UI tool built in-house. All of these places require for me to navigate to them each time and also take an action on them. Would be good to have a Bookmark button on each of these places so that I can save a bookmark of it. And then visualize all the bookmarks from a single place in AEM. And from there I can always quickly navigate to where I need.Below I added some example screenshots. But I imagine the Bookmark button to be available in way more places within AEM. Customer-name/Organization name: tethich.com Screenshot (if applicable): Code package (if applicable):
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.
OKSorry, our virus scanner detected that this file isn't safe to download.
OK