Build better products with our product team
Request for Feature Enhancement (RFE) Summary: Enable authors to initiate workflows directly from the Content Fragments console in AEM, streamlining the content approval process. Use-case: Content authors often need to start approval workflows for Content Fragments. Currently, initiating a workflow requires navigating away from the Content Fragments console, which can disrupt the authoring flow. Use-case: Content authors often need to start approval workflows for Content Fragments. Currently, initiating a workflow requires navigating away from the Content Fragments console, which can disrupt the authoring flow. Current/Experienced Behavior: Authors must leave the Content Fragments console to start a workflow, leading to inefficiencies and potential errors. Improved/Expected Behavior: Introduce a "Start Workflow" action within the Content Fragments console, allowing authors to initiate predefined workflows without leaving the interface. Environment Details (AEM version/service pack, any other specifics if applicable): Adobe Experience Manager as a Cloud Service (AEMaaCS)/2024.03.12345.1 Customer-name/Organization name: Screenshot (if applicable): Code package (if applicable):
Description -Why is this feature important to you - users use this widget to understand what they need to approve with projectsHow would you like the feature to work - have the ability to sort the approvals by date - at this time there is no way to sort approvals. Current Behaviour - right now it's just a list - and there is no way to sort the approvals.
Description - Approvals should have a due date fieldWhy is this feature important to you - Many of the processes that require approvals in my line of work are timely and need to be received before certain activity can take place.How would you like the feature to work - I would like a due date field added to the approvals object to drive timely notifications when action is required and when. Example: A campaign (Project) has a list of drops (Tasks), with fixed start and end dates. A drop cannot occur until final approval has been received. I would want to set a Task Approval due date somewhere between 3-7 days prior to the set start date and have that trigger notifications to the Approver that they've been asked to approve and when we would need it, sending reminders as the due date approaches.
If possible, we would be interested in modifying the information included on Workfront's system-generated emails that are sent to our team when a request is entered.
Description - In workfront planning using the calendar view if an event is happening soon can we have a reminder notification so that the team knows/gets a remind to action in advance.Why is this feature important to you - This would avoid users forgetting to action or prepare in advance of a calendar event.How would you like the feature to work - Enable reminder option for an item, allow reminder time and date setting for notification.Current Behaviour - I am not aware of any reminder option. The user would have to tag another user in a comment to remind them I believe...?
Description - Our IT won't allow legacy tokens to be turned back on in Microsoft 365 for security reasons. We would love a version of the Outlook plugin that doesn't rely on these tokens. Why is this feature important to you - Our team relies on the Outlook plugin for request submission How would you like the feature to work - As it did before the update to OutlookCurrent Behaviour - Currently has the error "Unexpected error Unable to get the outlookIdentityToken". Current recommendation is to turn on legacy tokens again, but like I mentioned - our IT team is firm on their stance
Description - I noticed that when users enter start time in Workfront (where the UI allows to specify time with up to a minute's accuracy), Fusion also adds seconds and milliseconds, which later leads to small discrepancies in processing.For example, when the user inputs the start time as 15:00 and the end time as 16:00, Fusion doesn't show 1h as would be expected after calculating the time difference but rather 0.9904197222222223h.I believe this is because 15:00 might be stored in the database as 15:00:01.500. Seconds and milliseconds can lead to subsequent inaccuracies in processing. Why is this feature important to you? Fusion gives inaccurate results when calculating time differences. How would you like the feature to work - fusion always zero out everything smaller than a minute, because UI doesn't allow for specifying anything smaller than a minute. Current Behaviour - Fusion silently and automatically modifies the time values as entered by users using the native Workfront .interface
Description:Introduce a predictive LTV (Lifetime Value) model natively inside Real-Time CDP that scores customers dynamically based on their engagement, transactions, browsing behavior, and other attributes - allowing marketers to automatically prioritize higher-value users for premium campaigns, offers, and loyalty experiences.Why is this feature important?Maximizes ROI by investing marketing resources in users who are likely to bring more revenue over time.Enables smarter segmentation beyond simple past-purchase or recency-frequency models.Enhances personalization by aligning offer types, discount levels, and campaign intensity based on user potential value.Improves strategic planning by giving marketing, sales, and service teams a predictive view of customer quality, not just quantity.Current Behavior:Marketers manually segment users based on historical transactions like total purchase value or number of orders.No predictive scoring available natively in Real-Time CDP; advanced LTV modeling typically requires external data science tools or custom machine learning pipelines.LTV-based prioritization isn't updated in real-time based on new events (e.g., sudden buying spree, major complaints, loyalty program milestones).Use Case:A user shows sudden high engagement with luxury products. The system recalculates their predicted LTV upward and automatically enrolls them in a premium loyalty tier campaign.A segment of users with declining engagement but historically high spend are identified early, allowing for targeted re-engagement offers before they churn.Campaign orchestration tools can use predictive LTV scores to decide who gets personal shopper assistance, exclusive previews, or early access to limited-stock items.
Description - We have times that the answers on the custom forms change and we need to "reset" the form so it clears out the answers. We run an external report and if we don't clear out those answers, they show up on the report. Why is this feature important to you - There are times the answers to the questions change and we need to change them. The answer stick if their is logic involved and they carry out to the external report.How would you like the feature to work - Have a way for system admins or planners to reset the questions in the form. This would save time from taking screenshots, deleting and readding the form so we can change the answers and not have the other answers still "answered". Current Behaviour - If we answer 'yes' to a question and the additional questions show up because of the logic that we have set, they are answered. If we need to change that 'yes' to no' those questions that we answered yes to will continue to show. We want to be able to clear out those answers when we change the questions.
Hello, We see a lot of work getting done end to end. This often means that various people of the same job role may be into the project. There isn't a reason to have multiple roles to tasks (ex. Designer 1, Designer 2) as you wouldn't want to schedule them to the same tasks. If you were able to use balancer at a more granular level around tasks that are bucketed verse the task name option (which are often the same outside parent tasks).
Description:Enable dynamic suppression of users from active marketing campaigns in real time based on recent negative experiences - such as failed transactions, customer complaints, or product returns - using Adobe Real-Time CDP signals and event-based triggers.Suppressed users can be re-evaluated for reactivation once an issue is resolved. Why is this feature important?Prevents wasting marketing budget by sending promotions to frustrated customers who are temporarily disengaged.Improves brand perception by respecting user sentiment and avoiding tone-deaf marketing outreach during sensitive moments.Reduces churn by showing customers you are listening and responding appropriately to their issues.Current Behavior:Audience suppression typically relies on static exclusion lists updated periodically (daily or weekly).No native real-time suppression based on live customer service data, failed transactions, or dissatisfaction signals.There’s no automated mechanism in Real-Time CDP to temporarily pause users from campaigns without manual intervention or external workflow orchestration.Use Case:A customer initiates a return request for a faulty product. Within minutes, they are suppressed from the active upsell email journey and instead flagged for a customer care follow-up.A user reports a poor app experience via feedback forms. The system immediately excludes them from push notification campaigns promoting new features until feedback is addressed.A transaction failure occurs due to payment gateway issues; the user is paused from cart abandonment reminders until the system detects a successful retry.
Description - I feel like this could be a reportable object, but at the very least would like a place to see what email notifications were sent, to who, when, and what triggered it. Why is this feature important to you - We get a lot of complaints that Workfront sends too many duplicative emails. It's really difficult to understand exactly which ones different people need without being able to see exactly what notifications they get. The documentation that explains the different types of emails is not sufficient. It's also difficult to know how the proof email notifications and WF email notifications work together. It seems like they don't at all and constantly send duplicative information.
Request for Feature Enhancement (RFE) Summary: Can we have some option for Property Version History to capture metadata property value changes for an asset or a page Use-case: Property Version history would enable Asset Owners to have a better view of what properties were changed and by whom. Current/Experienced Behavior: There is no such option available as of today. Improved/Expected Behavior: An option for Property Version History to capture metadata property value changes for an asset or a page Environment Details (AEM version/service pack, any other specifics if applicable): AEM Release - 2025.4.20476.20250414T214138Z Customer-name/Organization name: The Coca-Cola Company Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: An Option to define max-width and max-height for Custom Processing Profile in AEM Cloud Service Use-case: max-width and max-height would allow imposing some restrictions from ORG to follow when defining custom processing profile. Current/Experienced Behavior: Currently, while defining a new Processing Profile, there is no option of max-width and max-height. Improved/Expected Behavior: Can these max-width and max-height be added? Environment Details (AEM version/service pack, any other specifics if applicable): AEM Release - 2025.4.20476.20250414T214138Z Customer-name/Organization name: The Coca-Cola Company Screenshot (if applicable): Code package (if applicable):
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.
When we convert an Issue to a Project, we can specify the intended owner of the Project. It would be super helpful if we had the same functionality when adding a Template to a Task, i.e., "Assign template tasks to the Owner of the parent Task" or something similar.
I actually expected the feature to work this way to begin with and was surprised to learn that it didn't. If I have an issue that is resolved by a project I would like that issue to display the planned completion date of the project. Nothing more complex than that.
Please consider changing the radio buttons to checkboxes so we can assign the same template to multiple Tasks at the same time (instead of having to do it one at a time).
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.
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.
