Product Communities

Description - It would be great if your company logo could be added to WorkfrontWhy is this feature important to you - It would help embed the technology into the business and help colleagues see that Workfront is an approved internal systemHow would you like the feature to work - Be able to add a company logo onto the workfront landing page and boardsCurrent Behaviour - No company branding currently available 

Description - Would like to be able to mark messages as read on the @ mention widget and have them drop off the listWhy is this feature important to you - This would allow a clean view of items not read yet and remove items that have already been read or actioned.How would you like the feature to work - Add buttons overall to clear all messages or at the individual message level.Current Behavior: This does not exist.  

Description -This is related sending emails from workfront Fusion. We need to use this feature to send emails via Oauth2 basedCurrently, It is using Username and Password to send emails. 

Cloud Manager’s Content Sync capability is an important tool for keeping lower environments aligned with production. However, in its current form, the process can feel unnecessarily broad in scope and operationally inefficient. I believe there are several enhancements that could make the feature significantly more effective, flexible and performant.Intelligent indexing and comparison A valuable improvement would be the introduction of an indexing or comparison mechanism during content sync execution. At present, the process appears to operate as a full content copy. In scenarios where Production and Pre-Production both contain large volumes of content — for example, 10,000 files in each environment — it would be far more efficient to compare the target environment against the source before initiating the transfer. Such a mechanism could assess whether each file already exists in the target environment in an identical state. Where no difference is detected, the file could be excluded fr

DescriptionCurrently, Adobe Analytics 1.4 API provides several powerful endpoints that allow administrators to manage report suite configurations programmatically. These include the ability to:Fetch and update eVars, props, events, and classifications.Retrieve configured processing rules for a given report suite.Adobe has announced that the 1.4 API will be deprecated in favor of the 2.0 API next year. However, these configuration-level features are not yet available in the 2.0 API. Once 1.4 is removed, these critical capabilities will be lost.For many enterprise-scale implementations, this functionality is not just convenient — it is essential. Proposed ideaExtend Adobe Analytics 2.0 API to include endpoints for:Variable Management: Create, update, and fetch eVars, props, events, and classifications at the report suite level.Processing Rules: Fetch and (if possible) update processing rules for a given report suite.Cross-Suite Comparison: Provide efficient ways to compare variable

Hello Adobe Workfront team,Whenever a User is de-assigned from a Task; its Auto Assigned to the User’s Job Role. We don’t use the Workload / Resource planner functionality. Therefore this functionality of auto assignments to Job role, serves no benefit. Moreover its cumbersome, as a user has to remove a user from a Task & also remove the job owner role from the task even if the user was accidentally added.Can you therefore make this Auto assignment to Job-role functionality as optional (perhaps a system-wide setting that could toggle it on/off).ThanksHarish

 🧾 Description We are currently migrating from Adobe Analytics API 1.4 to 2.0 and have identified critical gaps that prevent us from fully deprecating API 1.4. API 2.0 does not provide feature parity with 1.4 in terms of report suite configuration and variable metadata, which creates a blocker for automation, governance, and documentation use cases.  🚨 Key Gaps  1. Missing eVar Metadata The API 2.0 /dimensions endpoint does not return essential configuration fields such as:  expiration_type expiration_custom_days merchandising_syntax allocation_type  These fields were available in API 1.4 and are critical for:  Automated documentation Data governance Attribution validation Migration verification   2. Missing Admin / Configuration Endpoints API 2.0 does not support:  Creating or updating eVars, props, events Managing Marketing Channel rules Accessing or modifying Processing Rules  Equivalent functionality existed in API 1.4 via ReportSuite.* endpoints.  🎯 Impact This

The Adobe Analytics API 1.4 is scheduled for decommissioning this summer, yet critical endpoints from this legacy API have not been integrated into API 2.0. This creates a significant gap in functionality that will impact many organizations relying on programmatic management of Adobe Analytics configurations.Missing Critical Functionality:The most important missing feature is the ability to programmatically:Create new Adobe Analytics variables (props, eVars, events) Modify existing variable configurations Delete variables when no longer neededCurrently, API 2.0 forces users to manually manage these variables through the Adobe Analytics interface, which is:Time-consuming for bulk operations Error-prone for complex configurations Incompatible with automated deployment workflows Difficult to integrate with CI/CD pipelinesBusiness Impact:Without this functionality in API 2.0, organizations will lose the ability to:Automate variable management across multiple report suites Maintain consiste

Description - Would love to have the option to pin and unpin a certain update to the top of the updates thread. This would allow for easy visibility on the most up to date items, etc. Would also love the option to filter updates by date, time, etc. to quickly search through and locate a certain update.  Why is this feature important to you - This would increase productivity within the Workfront platform tremendously and would avoid confusion and clearer communication with cross-functional partners looking for information via updates. How would you like the feature to work - A button that says "Pin" next to "Reply" and " Like" - Once pinned there would be an option to "Unpin" For the filter, some sort of filtering option at the top right of updates then you can click and customize certain date, time, latest comments, etc)  Current Behaviour - Updates are ordered in the time in they are posted, and all replies and updates are not able to be customized at thi

Hi Everyone,Recently, Adobe shipped a feature (SITES-33594) that enables out-of-the-box OIDC support, removing the need for custom authentication handlers. While this works well for standard flows, we’ve encountered a limitation when integrated with Identity Providers like Okta.The Issue:When implementing RP-initiated logout, Okta (and similar providers) requires the id_token_hint=<id_token> request parameter to successfully terminate the session on the IDP side.Technical Gap:Currently, org.apache.sling.auth.oauth_client.impl.SlingUserInfoProcessor is only designed to store the access_token and refresh_token on the user node. Since the ID token is not persisted, we cannot retrieve it to complete the logout handshake OOTB.Requirement:We need a standardized process within the OIDC implementation to store and access ID tokens on the user node, similar to how access and refresh tokens are handled.Thanks,Martin

Currently it is not possible to clone Programs that contain emails using the new designer across Workspaces. A key part of how many organisations work with Marketo is through the use of Program templates or ready-to-go Programs that can be cloned and adapted, this is also one of the key benefits Marketo used to advertise with.The new email designer currently removes this possibility, blocking many organisations from using what could be a really nice upgrade. Without this feature, using the new email designer would increase roll-out times for new campaigns/Programs, which should never be the desired outcome.It’d be nice to hear from other organisations if this impacts you as well.

Currently, buyer group role creation in AJO B2B relies on exact-match or limited matching logic for job titles and attributes. This creates constraints when mapping real-world data, where job titles are often inconsistent, varied, or unstandardized.Introducing a “contains” logic would significantly improve flexibility and accuracy in buyer group definition. It would allow roles to dynamically capture a broader and more realistic set of relevant contacts (e.g., capturing variations like “Sr. Director of Radiology,” “Radiology Director,” or “Director, Imaging Services” under a single word - contains “radiology”).This enhancement would:Improve coverage and completeness of buying groups by reducing missed matches Reduce manual effort and dependency on exhaustive title mapping Increase scalability across regions and datasets with inconsistent naming conventions Enable more accurate downstream activation (e.g., LinkedIn, email targeting)Overall, adding “contains” logic will make buyer group

Description - The current proof zooming while reviewing a proof allows up to 400% zoom. While this may sound sufficient, it is not always in most cases. It would be great if the proofs could be zoomed in even more.Why is this feature important to you - On some files we review, there is small text that cannot be read at the current zoom level. In those cases we need to download the document and then add in comments seperately.How would you like the feature to work - If the zoom could be increased to 500% or more, it could solve the issue. 

Description -Why is this feature important to you - This feature is required for security requirements for client organization.How would you like the feature to work - Support to MTLS in HTTPs mode for Workfront and Fusion integrationCurrent Behaviour - currently MTLS is only available in our HTTP mode and not HTTPS Thanks, Prasanna Nagarajan

Description -Why is this feature important to you - We want the ability to control whether the select all option appears in a mutifield dropdown or checklist. How would you like the feature to work - Add an option in the custom field that allows the admin to instruct WF to add the Select All option.  If not selected, then do not allow the ability for the user to select every option. Current Behaviour - Workfront adds the Select All/ Deselect all option automatically. 

Hi Team, Below are the details :  Detailed Use CaseThere are multiple scenarios in which source data for batch campaigns or journeys is delayed. In such situations, we are required to manually start, stop, pause, or resume all related journeys and campaigns. This significantly increases operational overhead.Once the data issue is resolved, the same set of journeys and campaigns must be manually resumed, meaning the effort is duplicated for every data disruption. As a result, each data failure forces us to perform the same manual operational task twice, which is both inefficient and error-prone.Business JustificationProviding API-level capabilities to start, pause, stop, and resume journeys or campaigns would enable full automation of this process. This would lead to substantial reductions in manual effort and operational burden, while also minimizing the risk of human error.When handled manually, it is very easy to accidentally miss a journey or campaign, which can directly impact reve

We would like to have the option to prevent an issue from being converted to a project more than once. Sometimes we have more than one person managing an issue and the second person does not see that the issue has already been converted. This causes the original project to be “lost” because it is no longer linked and opens up the potential for double work.

Description - On the Home Screen My Task Widget, there are only 11 possible column options. I would propose being able to customize this more or at least adding a few more.Why is this feature important to you - Our company heavily relies on this widget and a little additional information can prove very helpfulHow would you like the feature to work - The most useful additional column on the "My Tasks" widget would be "Task Details" since this is being used as notes on a specific task. An additional helpful column would be "Project Owner" and/or "Project Sponsor" (Understanding this might be more difficult as it is at a project level instead of task level). 

Use case: We would like to target customers on below qualified dates and be suppressed if they don’t meet qualified date. So, looking for the solutions to manage dynamic qualified date in the journey if possible. 2 days before 1st Friday of each month e.g. Apr 1, 2026 1st Friday of each month e.g. Apr 3, 2026 1 month after 1st Friday (on 1st Friday only) e.g. May 1, 2026 2 months after 1st Friday (on 1st Friday only) e.g. Jun 5, 2026 3 months after 1st Friday (on 1st Friday only) e.g. Jul 3, 2026

The Concept: In sourcing, identifying cost pattern shifts or rogue spend requires heavy week-on-week spend analysis and deflation tracking. Adobe Analytics has built-in AI for this exact type of monitoring.The Adobe Connection:Intelligent Alerts & Anomaly Detection: Instead of using these features just for spikes in website traffic, they can be configured on internal B2B platforms to flag sudden spikes in unclassified spend or deviations from contracted pricing structures.The Conversation Starter: "Adobe's Anomaly Detection isn't just for spotting a sudden surge in website visitors. Imagine applying that same AI-driven alert system to internal B2B portals to instantly catch 'tail-spend' leakage or week-on-week deflation shifts without manual Excel tracking."

In the AEM Assets Omnisearch UI, when a user opens the filter rail and selects any filter (file type, date range, tags, etc.), a search is automatically triggered on every single filter interaction. This causes: Multiple overlapping HTTP search requests fired in rapid succession Server-side query timeouts under normal DAM load UI freezing while waiting for responses Users unable to combine multiple filters before seeing results Required behavior: User selects multiple filters freely without any search firing A custom "Execute Search" button is visible in the filter rail Search only fires when the user explicitly clicks "Execute Search" This is a production workflow issue affecting all DAM users performing filtered asset searches.

Packaging design plays a crucial role in shaping customer perception and influencing buying decisions. A well-designed package not only attracts attention but also communicates the brand’s identity effectively.Here are a few important benefits of strong packaging design:Enhances product visibility on shelves Builds brand recognition and trust Creates a memorable unboxing experience Helps differentiate from competitorsAt Design Concepts Creative, we focus on creating packaging that not only looks appealing but also drives real business results.You can explore some of our recent packaging design projects here:👉 our packaging design portfolio

In Adobe Orchestrated Campaign (OCM) Provide functional significance to the "Enable for Segmentation" toggle present on relational schemas. Why is this feature important to you UI elements that have no backend functionality create confusion for data architects and marketers during implementation, leading to unpredictable behaviors and wasted configuration effort. How would you like the feature to work If the toggle is present, it should actively allow the fields within that relational schema to be leveraged in the standard AEP segment builder. If this is not technically viable, the toggle should be removed from the UI to prevent confusion. Current Behaviour The “Enable for Segmentation” toggle on relational schemas has no current significance

Enable Adobe Journey Optimizer (AJO) Journeys to natively query and consume data residing in relational tables. Why is this feature important to you Siloing relational data strictly to Orchestrated Campaigns creates a disjointed architecture. Real-time journeys often need contextual data (like store inventory or loyalty tier lookups) that is best suited for relational storage. How would you like the feature to work Allow AJO journey conditions and personalization syntax to securely reference and pull data from relational schemas linked to the primary profile. Current Behaviour Relational tables are designed for OC only and cannot be directly consumed by AJO Journeys

In Adobe Orchestrated Campaign (OCM) Introduce a native, automated feature to clone XDM profiles into relational stores without dual-ingestion or Query Service workarounds. Why is this feature important to you Architectural simplicity reduces technical debt and maintenance costs. Forcing data engineers to ingest data twice or build scheduled Query Service scripts just to populate relational tables is an inefficient use of platform resources. How would you like the feature to work Provide a UI-driven toggle or standard data prep mapping function that allows specific XDM profile attributes to automatically sync or "clone" into designated relational schemas upon ingestion. Current Behaviour There is no free auto clone feature for xdm profiles into relational stores; data must be ingested twice or derived via Query Service