Product Communities

Provide a native Workfront notification capability for asset status changes in AEM Assets.ProblemWhen an asset submitted from Workfront changes status in AEM Assets, the user who originally uploaded or submitted the asset should receive a notification in Workfront. The notification should be configurable so customers can define whether notification is required and/or which asset status changes should trigger a notification.A two way Fusion integration between AEM Assets and Workfront can be used today to sync updates between the two systems. However, there is currently no native notification capability for the Workfront users to track the status change. ImpactThis would provide better visibility into the asset lifecycle and reduce the need for users to manually check asset status or coordinate with other teams. It would also allow users to take immediate action when an asset is rejected or requires changes, reducing delays in the content production and approval process.

Native dependent dropdowns in custom forms, where an admin defines which child options are available for each parent value, and the child dropdown shows only those options at runtime. It should work with forms used on projects, tasks, requests and documents, so the values map cleanly to AEM metadata. Problem StatementIn Workfront custom forms, a dropdown can't limit its choices based on the value picked in another dropdown. Form logic can show or hide fields, but it can't filter the options inside a dropdown. Validation logic can block an invalid combination, but users still see every option and only find out after they choose wrong.ExampleA manufacturer's form has two fields: Model Range and Model Derivative. When the user picks Model Range = Range A, Model Derivative should only offer the derivatives that belong to Range A. Today it shows all of them, and nothing stops the user picking an invalid pair at runtime.  ImpactUsers can submit invalid combinations, such as a derivative that

Currently, when sharing Adobe Workfront ( as well as Firefly and Express) links through Microsoft Teams and Outlook, the links are not distinguishable from each other, which makes searchability and quick referencing a challenge. It would be amazing if those links could be prepended by the Project Name or for it to display in the image preview. 

It would be useful to be able to use Regex when creating segments in Adobe Analytics to help segment based on patterns/sequences rather than on specific values. It would also prevent the need for building complex, “stacked” segments with multiple criteria/containers.

When the duration of a Task or Issue exceeds 1000 days, Workfront's Workload Balancer and related services reset or fail to evenly distribute planned hours across the entire duration. This is not due to the total number of planned hours, but specifically the duration threshold. The Workload Balancer documentation mentions that allocations display as zero after the 1000-day or 1000-hour limit is reached, but does not explicitly clarify that you cannot continue allocating hours beyond this limit. It is recommended to break Issues or Tasks that span longer than 1000 days into smaller, sequential Issues/Tasks (e.g., annual or biannual segments).This is a design flaw and needs to be remediated.

Currently in Realtime CDP, using tracked event data that is also evaluated in Adobe Analytics, it is not possible to segment profiles based on the number of visits (as metric “Visits” in Adobe Analytics) that they have since there is no “visit-id” that is exposed on the UI or even the possibility to select audiences based on “count unique” [element]. The number of visits in a given timeframe is an important KPI for our department and we would like to select profiles in different intervals of it.Thanks!

When writing queries in Adobe Experience Platform Query Service, the editor provides assistance for selecting available tables. However, after selecting a table, users still need to leave Query Service and inspect the corresponding schema to identify the available schema paths and fields.It would be highly beneficial to provide an integrated schema viewer within Query Service. Once a table is selected, users should be able to browse the related schema and select from the available schema paths directly in the query editor.Suggested functionalityDisplay the schema associated with the selected table or dataset. Provide a searchable, expandable list of available schema paths and fields. Support autocomplete for schema paths while writing a query. Allow users to click a schema path to insert it into the query. Display useful metadata, such as field data type and whether a field is nested. Keep the schema information synchronised with the selected table or dataset.BenefitsThis enhancement w

 Removing the background from a car is usually simple. A coffee mug can be even easier. But isolating a person with curly hair against a detailed background can quickly become one of the most time-consuming parts of photo editing.Hair is difficult because it contains thousands of individual strands. Some strands are clearly visible, while others are thin, soft, or partly transparent. Curly hair can be even more challenging because the strands move in different directions and often blend into the background.Fortunately, Photoshop now offers several tools that make hair selection much easier. By combining automatic selection features with careful manual adjustments, you can create a natural-looking result without manually tracing every strand.Start With Select SubjectFor many portrait projects, Select > Subject is a useful starting point. Photoshop automatically analyzes the image and tries to identify the main person or object.When the subject is clearly separated from the background

The most common complaints from my company’s users are the number of emails they recieve, not receiving notifications when they should, or not receiving the same emails as their coworkers. This is often caused by mismatches in notifications settings between users, with the root cause of the issue being that the admin must update each new user’s notification settings manually.It would be extremely helpful to have a system-wide notification settings where individual notifications can be turned on or off, and set to instant or daily, then those settings would apply to all new users.

As an admin who handles licensing and onboarding of new users in an instance with many teams, groups, and multiple companies, it would be very helpful to be able to see a user’s groups, teams, and company from their details section.Having the ability to add any user field to the details area, would save me several clicks and scrolling to update a user’s team, group, or company, especially when I’m onboarding several users at once.

WorkFront has no ability to 'undo last action' - in some cases this can be very troublesome - as it is quite easy to make a change to basic project behaviour, critical path and end dates. An 'Undo' last change function would be very useful if the Project owner has in-advertantly made a change that has caused multiple activities to be impacted. Even a - revert to last saved version function might be useful - at least allowing the project owner to go back to a version that they have already reviewed and approved with their team.

I’d like CJA lookup table dimensions to natively differentiate between "Unclassified" and "No Value".Using a Campaign ID (CID) lookup as an example: "Unclassified" (ideally customizable in the UI): The event has a CID, but that specific CID is missing from the lookup table (or the CID is missing the specific attribute) "No Value": The event does not have a CID present at all. Currently, CJA groups both scenarios under "No Value". While the Data View UI allows you to rename "No Value Options," it applies blanket-style to both types of events, so you lose visibility into unmatched lookup entries versus traffic completely missing the key.While this can be solved today using a derived field, native support in CJA lookup dimensions would eliminate the need for derived field workarounds, save contract derived field slots, and provide immediate clarity into missing lookup data right out of the box.

We have observed that there is currently no reporting capability available to track AI Assistant usage and adoption.From an operational, governance, and business value perspective, it is important for Business to understand how the AI Assistant is being utilized across the organization. At present, we are unable to determine key metrics such as user adoption, usage trends, interaction volume, or overall utilization of the feature.We would like to request that Adobe consider adding a Workfront AI Assistant Usage Report feature that provides visibility into:Active users of the AI Assistant Usage and adoption trends over time Number of AI Assistant interactions/prompts Group, team, and organization-level usage metrics Dashboard and export capabilities for reporting purposes API access to usage data, if availablePlease let us know if such reporting capabilities are currently available, planned on the product roadmap, or if this request can be submitted as a formal product enhancement to th

 1. High-LevelThe architecture is a state-of-the-art, event-driven ecosystem designed for an "Always-On" digital business model. It separates operational concerns by funneling distinct data types through purpose-built, highly available pipelines, converging them within the Adobe Journey Optimizer (AJO) for real-time communication, which orchestrates instant, reliable delivery via a scalable Email Delivery Network. The entire design is structured to prioritize the seamless, instantaneous transmission of high-value transactional communications.2. Design Philosophy for "Zero Disruption"A "Zero Disruption" guarantee cannot rely on a single system's uptime. It must be designed as a System of Systems with fundamental principles of resilience.Core Resilience Pillars of this Design: Loose Coupling via Async Messaging: By using Kafka / Azure Service Bus / AWS Kinesis, we decouple the core CRM/ERP transactional databases from the marketing delivery network. Even if the entire Adobe suite is offl

I wanted to suggest a idea.    If a page or Asset is published, the users should not be able to delete the item from the Author.  The Author should have logic to let the user know the item is published and cannot be deleted until it is unpublished.We are having this issue with our Users deleting items from author and then they have to restore it from trash, and unpublish the asset.   this creates a lot of work and time to do so hoping a proactive alert box can be setup to notify the user that the item is published and cannot be deleted from author. 

Something that should be table stakes - but is not is the ability for users to only see their requests from Project Intake.We did find a nice use using the Home widget - but there’s 2 issues with this that would make great enhancements:If a user is on the New Experience and they have switched to New Home experience - it provide proper limited visibility. Allowing ability for Group Admins to set the default User experience for their users would be a great enhancement.OR just allow the ability to remove the “ALL Requests” Filter from Requests OR Home Widget 

With the new segment release on 23rd April 2014, it's become impossible to add multiple countries to a segment at once. We're now forced to add each country as its own rule, and when you're trying to build segments for entire market areas at once, this gets old very quickly. We used to be able to set a "contains one of" rule, that would allow us to space separate a list of countries. Can we please go back to doing that?Or at least find some way that doesn't mean I have to do three clicks for each extra country I'm adding?  I'm trying to make segments with 50 to 70 countries in. So as to get a sense for how different areas of the world are behaving on our site, with this new UI that's an incredibly frustrating process.

Description - Before the migration to Adobe console, we were able to have two email addresses associated to each Workfront account. One email (FedID) is what our users used to login through SSO and the other (Username) is where their email notifications from Workfront went. With console this is now no longer possible and support has been unable to suggest a workaround. Would love to see this functionality restored! Why is this feature important to you - Some of our users need their notifications routed to a shared inbox for coverage purposes/so it is easy to jump in and help each other with workloads.  How would you like the feature to work - I would like to be able to have a field on the user profile again where I can input an email to send Workfront notifications to.  Current Behavior - Functionality no longer exists.

As we roll AI Form Fill and AI Assistant out to our organization, we’d love the ability to create and add to a prompt library, or work to establish a general prompt library across Workfront instances. Given our end users all operate differently, there’s enough variability that we can’t pin down what they may input and what the AI Form Fill tool may output as a result, so establishing guidelines/prompts feels like a great starting point.

Adding this product enhancements request for a customer - Background: Journey testing has been a significant hurdle for our organization.  We are unable to use dry run fully as we have API calls to manage our opt outs and dry run stops working when there is an API call.  Test mode is very limited because we, as a product team, do not have access to build test profiles in AEP to match the journey strategy scenario - business rule decision. It requires one of our engineers to manually build them for us, and we need to put that request in far ahead and we are unable to adjust test profiles in the midst of a testing cycle.  With this, we have limited access to test mode.   Simulation Experience and Requests: When simulation mode came out, we were very excited as it "solved" all our issues.  It is a valuable tool to streamline the testing process and also to ensure we are testing all potential scenarios.  With test mode (prior to simulation mode), we would require 2-3 sprints of time (4-6 w

I was recently blocked from sending an email due to one of the URLs in a button being too long, and not adhering to Marketo’s URL shortener. Because there was no error message that would have alerted me to the cause of this email not sending, I spent a lot of time (and tokens) trying to diagnose the root cause.  In Marketo Engage, erroneous email components should clearly display the error that will cause the email to not send or be delivered, so the editor can resolve the issue. 

Our team frequently uses optimize nodes for various journey orchestration use cases. The ability to reorder these paths in the menu would improve organization and usability. Currently, if a path needs to be moved higher in the list, users must rename paths or recreate the Optimize node entirely and rebuild the associated logic. This increases effort, introduces risk of configuration errors, and makes maintaining complex journeys cumbersome. We are requesting drag and drop functionality or simple move up/down controls that allow users to reorder paths within an Optimize node without impacting existing configurations or logic. This would reduce the risk of configuration mistakes when modifying production journeys and improve operational efficiency for managing large, complex journeys. Overall, it would be a nice quality of life upgrade. Our current workaround is just to recreate the optimize node with the paths in the correct order.

I would like to share a key feature enhancement request for Adobe Experience Platform (AEP) Real-Time CDP architecture regarding data modeling flexibility. Ideally for B2C, B2B & B2P editions as we have consolidated all into single Prod & Dev sandboxes as advised by Adobe Ultimate Support.The Feature Upgrade:Enable native Many-to-One (N:1) schema relationships between non-B2B XDM schemas. This will allow multiple custom data records to link directly to a single parent account record within standard XDM profiles, without requiring both B2B XDM classes.Use Case & Business Need:Current Scenario: We have custom data entities (e.g., competitor products, telemetry, certifications) where multiple rows of data map to a single core business account. The Problem: Standard non-B2B XDM schema relationships are restricted to lookup options, which force data into arrays. This results in complex architecture and confusing schema building UI. Proposed Solution: A flexible parent-child rela

Managing enterprise-scale Digital Asset Management (DAM) requires more than traditional repository searches. With millions of assets, organizations need intelligent, scalable, and governed metadata management.This architecture introduces an AI Agent-based approach for Adobe Experience Manager (AEM) Assets:🔹 Business Users interact through chat interfaces or portals using natural language.🔹 AI Agent Layer understands intent, extracts entities, and selects the right tools.🔹 Custom Metadata Services provide governed access for search, validation, authorization, audit, and updates.🔹 External Metadata Repository enables high-performance search across 1M+ assets without scanning AEM repositories.🔹 AEM Assets Cloud Service remains the System of Record for all metadata updates.🔹 Synchronization Services maintain consistency through events and scheduled reconciliation.Key Architecture Principles✅ AI agents access enterprise systems through controlled APIs✅ External indexing enables fast m

A comprehensive guide to isolated Dev and QA environments with AEM Author, Publish, Dispatcher, Nginx, persistent storage, and WKND validation Local AEM development often begins with a single Author instance. That is sufficient for early coding, but it does not validate the complete delivery path. A mature local setup should make it easy to test Publish behavior, Dispatcher filters and caching, environment-specific configuration, content activation, reverse-proxy routing, and repeatable environment lifecycle management.   PURPOSE  This guide presents a reproducible, Docker-based approach to local development and QA validation. It mirrors production engineering practices but does not replace AEM as a Cloud Service environments, Cloud Manager, or Adobe-supported production deployment models.  What you will buildTwo isolated environments: Development and QA AEM Author and Publish services in each environment Apache HTTP Server with Dispatcher in front of Publish Optional