Build better products with our product team
Description - When using the My Tasks widget, would like the ability to see completed tasks. Why is this feature important to you - My creative team like seeing completed tasks so they can quickly jump back to things if needed from this page.How would you like the feature to work - Allow this widget to pull in completed tasks from a preset Workfront filter or a custom filterCurrent Behavior - Currently does not display completed tasks as seen in the compare and contrast example below. Trying to use a filter that pulls in tasks from last week, this week and next week that are both not complete and complete, the widget does not seem to pull in completed tasks. My Tasks with custom filter: A report with the same custom filter:
Description Ensure that standard enumerated field values (such as Loyalty Tier or Subscription Status) populate as selectable dropdown menus within the OCM Audience Builder rather than requiring manual string entry. Why is this feature important to you Forcing stakeholders to manually type exact string values from memory introduces a massive risk for human error. A simple typo or accidental trailing space causes the query to fail silently and return zero profiles. To prevent this teams are forced to maintain external data dictionaries or have architects pre build standardized audiences which adds administrative overhead and severely impacts the usability of the OCM canvas for everyday campaign operators. How would you like the feature to work When a user clicks on an attribute with predefined values in the OCM segment builder the UI should immediately present a dropdown menu of the available enumerated values identical to the standard AEP Segment Builder experience. Current Behaviour The OCM segment builder lacks dropdown menus for enumerated fields forcing users to manually type the exact string values from memory.
Description Introduce the IP warming plan activation toggle natively within the Orchestrated Campaign Module (OCM) email configuration screen to match the functionality currently available in standard AJO Campaigns. Why is this feature important to you When migrating to Adobe Journey Optimizer and standing up a brand new instance systematically warming IPs is a foundational deliverability requirement. The absence of this feature in OCM forces architects to use complex workarounds like exporting OCM audiences into the AEP Audience Portal and wrapping them in segment definitions just to safely throttle email volume in a standard scheduled AJO campaign. This completely disrupts the unified orchestration workflow and adds unnecessary build time. How would you like the feature to work Include the standard IP warming plan activation toggle directly within the Email action configuration of the OCM canvas allowing the system to natively handle safe message throttling without forcing practitioners to leave the orchestrated workflow. Current Behaviour The IP warming plan activation toggle is completely absent from email configurations inside an Orchestrated Campaign despite being a standard feature in AJO Campaigns.
We would like the option to customize standard and event emails in Workfront, similar to how reminder emails can be personalized. This would include editing the subject, body, and HTML, not just the subject line.
Add the ability to pin or favorite linked SharePoint files or folders within Workfront (Documents area) to enable quicker access to frequently used external items, improving efficiency within the Workfront–SharePoint integration.
Current BehaviorThere is no auto-number or sequential ID field available when configuring a Planning record type. Unique identifiers must be entered manually or generated externally and written back via automation.Desired BehaviorA native auto-number field type in Workfront Planning, with configuration options for:Number of digits (e.g. zero-padded to 5 digits: 00001) Format: numeric only, alphanumeric, sequential, or random Optional prefix and/or suffix (e.g. NRD-00001 or 00001-PRINT) Starting count (configurable, not locked to 1)The field value would be system-generated on record creation and read-only after assignment.Business ImpactAuto-generated sequential identifiers are a baseline requirement for any operational record-keeping use case — job ticketing, production requests, vendor orders. Without this, teams either maintain a manual counter (error-prone, breaks under concurrent edits) or build a Fusion scenario to replicate what should be a native field configuration. We’ve encountered three use cases with different teams that have requested this feature as a condition for Planning adoption, so there seems to have broad application.
When using Global record types to aggregate data from regional workspaces into a central, leadership-facing workspace, there is a consistent need to tailor field visibility at the workspace level. Specifically, certain fields that are relevant in the global context are not always appropriate for display in inherited regional workspaces.When using Global record types across inherited regional workspaces, admins need consistent control over which fields are visible to users.Today, fields can be hidden in Table view and the associated record detail panel, but Timeline view does not respect these visibility settings. Instead, the Timeline detail panel displays all fields by default, creating an inconsistent experience and exposing unnecessary fields to end users.The “Show all fields” toggle already exists in the Timeline detail view, but it is disabled and not configurable.Suggested enhancement:Enable the existing toggle in Timeline view Allow it to respect field visibility defined in Table view Provide an admin setting to control the default behavior (e.g., show filtered fields vs. all fields)This would ensure:Consistent field visibility across views Better user experience and cleaner interfaces Improved governance, especially in global/regional workspace models
When using Tab or Accordion components in a page, an issue occurs where, after editing a component on the second or subsequent pages and then closing it, the view unintentionally returns to the first page.Expected behavior: When editing components on the second or subsequent pages, the user should remain on the edited page and be able to continue working without being redirected to the first page.
At this time, there doesn’t seem to be any good options for copying Report Builder requests from one file to another. There is a Copy / Paste request option built into the Add-On which is amazing, but this only works within the same file. You cannot copy a request from one file into another. I tested this by opening and logging into two Excel Reports, copying a simple request from Report A, then going into Report B and selecting a cell… there was no Paste option available. I can understand that this might be an Add-On scope issue, but what about adding an Export / Import function that can export out an XML or JSON formatted file that can then be imported into another Excel instance… and hopefully this would support bulk rules and not just one at a time, as this would make merging reports into one large report so much easier (than the current “rebuild all requests from scratch”). This feature would be a huge time saver to:make copies of common requests to other files merging reports together
The feature that automatically auto tags images in a document needs to be disabled for every user, or the tagging needs to be manual to eliminate obscene language from the tagging. I have an abstract image in my template that I send to clients. If I forget to disable the auto tagging, then the client will read a caption that suggests I am sending them a nude image. There is no figure in the graphic. There is no suggestion of a figure in the graphic, but Ai suggest that there is, and it confuses my clients. Even if it says that it is an “Ai generated caption”, my clients read it as something I, myself, inserted into their document. I have turned it off. I have done it multiple times, successfully. However, I do not love that it is my sole responsibility to work around a program every single time I send out a document. Please let me know if there is a way to disable this function so that I can forget about the fact it even exists. My clients are older and I have to explain to them every single time that this happens that I do not have control over what they are seeing as a caption.
Contributor licenses have considerably less restrictions than light licenses and allows our company to partner with some of our external partners on marketing campaigns without having to spend the resources to onboard them in Admin Console and our companies SSO. Unfortunately the 7 interactions per month is too restricting. We feel it would be beneficial if there is a way to expand that interaction limit. The following are a couple of options Assign limited interactions to a group/team in Workfront instead of an individual. So it can be used across profiles depending on the external partners needs. Add the ability for clients to negotiate increasing the limit in their contracts. Maybe treat it as another tier with the licenses.
Just like we can delegate project/task/issue approvals, and with 22.3 can delegate task/issue assignments, PLEASE have the ability to delegate proof approvals! There are other ideas for this with 'Not Planned' labeled, hoping power in numbers can help sway this bc this is something WF really needs. Hoping it is part of near-future proof enhancements.
Being able to use conditional formatting, specifically background/row colors, is very useful in reports. I want to be able to use this for GROUPINGS in a report so I can visually separate the groupings in reports where we have repeated groupings (like different groupings for different teams that may have more than 1 grouping). I don't want the rows within the grouping all a color because that can get busy, but really wish I can add background color to the grouping rows themselves.
When a report on a dashboard has over 200 records, the current UI doesn’t have the option of “Showing All” records. The “See more” link opens the report in a popup window but the windows size is too small to display just 3-5 rows at a time. We request to improve the UI to allow “Showing All” for reports on dashboards, as well as to increase the “See more” popup window to full browser size.
We use programs as a container with projects as a sub-container for types of work/documentation. It would be nice to be able to copy projects to another program or copy a program all together with the ability to remove issues/tasks/documents.
AEM as a Cloud Service "Copy Content" copies author-tier content only and intentionally strips replication-status metadata (cq:lastReplicated, cq:lastReplicationAction, cq:lastReplicatedBy, incl. the _publish/_preview variants). As a result, after a Prod→Stage copy the destination author has no record of what was published on the source, and nothing is published on the destination's publish tier.The only way teams can reproduce the source's published state today is to build external tooling that:1. queries the source (Prod) for the full activated set (e.g. via QueryBuilder), then2. re-replicates exactly that set on the target (Stage), chunk by chunk.This is inefficient by construction — it re-derives state the source environment already holds, it's bounded by QueryBuilder-over-HTTP result limits and request timeouts, and it doesn't scale to largerepositories (millions of nodes / multi-TB). We built and open-sourced such a tool to prove it works — https://github.com/rwunsch/aem-content-sync — but the fact that every customer has to build this isthe problem: it's redoing work the Content Copy tool itself should do.Requested:- An option to preserve replication status through Content Copy, and/or- Auto-publish copied content on the target (so the destination publish tier matches the source), and- Make these schedulable and scalable (delta/incremental, resumable), so lower environments can be kept in sync unattended without external scripts.This would eliminate a whole class of brittle, slow custom tooling and make environment refreshes accurately reflect production's published state.
A few months ago I built a Post-Purchase journey in Adobe Journey Optimizer that sent a personalised follow-up email based on what the customer bought. The journey had three branches — one each for Electronics, Sports, and HomeDecor — all tested, validated, and live.Then the business expanded into two new product categories: Grocery and Fashion. I updated the journey to add the two new branches and needed to validate them before re-publishing. The Problem with Test Mode To validate the Grocery and Fashion branches in Test Mode, I needed two new AEP test profiles — one with a Grocery purchase, one with a Fashion purchase. Creating new profiles in AEP is straightforward, but it takes time for them to reflect and become available for testing. I could not just create them and start immediately.With a deadline to re-publish the updated journey, waiting for two new profiles to propagate was time I did not have. Simulation Mode: New Users in Seconds I switched to Simulation Mode instead. I created two new Simulated Users directly inside AJO — one representing a Grocery purchase, one representing a Fashion purchase — and they were available to test immediately. No waiting for anything to propagate.I triggered both in the same simulation session and got step-by-step execution logs confirming that both new branches routed and sent the correct email.What would have taken hours of waiting took minutes. Whenever you are adding new branches to an existing journey, Simulation Mode is the fastest way to validate them. You do not need to wait for new AEP profiles to reflect — you define the simulated user you need right inside AJO and test immediately.The existing branches (Electronics, Sports, HomeDecor) were already covered by my earlier test profiles. For the two new ones, Simulation Mode was the clear choice — and it saved me hours.Have you run into a similar situation when updating a live journey? Share your experience in the comments. Referenceshttps://experienceleague.adobe.com/en/docs/journey-optimizer/using/orchestrate-journeys/create-journey/simulate-journey/simulate-journey
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.