Build better products with our product team
When creating a user profile in Workfront, the option to automatically generate a proof when a document is uploaded should not be selected by default. Instead, this setting should be an optional, manual selection during user profile creation. Making this change would reduce confusion and help minimize troubleshooting tickets from end users who simply want to upload a document without initiating a proof.
We are on AEMaaCS, we are working on introducing msm in our experience fragment hierarchy, we have created an xf in language masters in /content/experience-fragments/myProject/language-masters/en/header, now as it happens in site pages when we roll out a page from language masters, it automatically creates a live copy in /content/myProject/en/en_US, but in case of xf we have to manually create a live copy using create button, is there a way to automate this like it is there in sites pages.
It would be good to have a Splunk Connector for Workfront and Splunk
In the old Report Builder, it was possible to set a "reference date" when refreshing a report. For example, you could configure the report to show "last month" and then decide at refresh time whether "last month" should be calculated from today or from an earlier date. In the new Report Builder, this feature seems to be missing or only possible through multiple formulas.It would be very helpful if we could reference a "reference date" from a cell, so that the report calculations (e.g., "last month") are based on the date specified in that cell. This would make it much easier to analyze data from different time perspectives without having to adjust multiple formulas.
Description:Add a way to be indicated that tasks are late on the My Tasks widget Why is this feature important to you:Users need an easy way to see that they are late on tasks. Currently, there is no indication with color or an icon letting them know that task(s) are late. The old home had a Late grouping and colored red which made it clear to pay attention to the tasks. Currently, with our team working by the hour, it is very easy to miss late tasks and puts our projects at more risk to meeting deadlines. How would you like the feature to work:3 options:1. Add red color to the background of the tasks and have them be shown at the top of the list for My Tasks widget 2. Add a caution icon (similar to team request tasks that are late) next to the due date of the task 3. Create a new "Late Tasks" widget so tasks live in their own space to make it quick and easy for users to find late items Current Behaviour - Does not exist in new home
Description - The current fields for Risks and issues is very limited, I want to be able to add custom fields for each Risk/Issue, currently there is no way to to that. Why is this feature important to you - If I cannot add fields then I have to track Risks and Issues in a spreadsheet. How would you like the feature to work - I should be able to create fields for Issues and Risks that will let me input unique information for each Risk. Current Behaviour - There ar eonly a few standard fields that are not useful to me. If I add custom fields in a form they are for the project not for individual risks.
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
Sobha One World is envisioned as more than just a residential address—it’s a thoughtfully curated living experience that blends modern architecture with a sense of openness and calm. Designed for those who value both sophistication and comfort, the development brings together sleek urban design, expansive green spaces, and a lifestyle that feels elevated yet grounded.At its core, Sobha One World emphasizes balance. Towering structures rise with clean, contemporary lines, while landscaped surroundings soften the environment, creating a seamless connection between city living and nature. The residences are crafted with attention to detail—spacious layouts, abundant natural light, and premium finishes come together to create homes that feel both luxurious and livable.What sets Sobha One World apart is its focus on everyday ease. From thoughtfully planned amenities to spaces that encourage relaxation, fitness, and social connection, every element is designed to support a well-rounded lifestyle. Whether it’s a quiet morning overlooking green vistas or an evening spent in vibrant community spaces, the experience feels intentional and refined.
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 from the sync. In reality, this may reduce a 10,000-file sync to only the relatively small number of files that are genuinely out of date. This would reduce unnecessary data movement, improve efficiency, and likely shorten sync durations considerably. A practical way to introduce this would be as an optional setting within Content Sync, perhaps via a checkbox labelled “Enable Comparison”. If enabled, the sync would perform a comparison-driven transfer; if disabled, it would continue to run the existing full copy behaviour. Granular and targeted synchronisation Another highly valuable enhancement would be the ability to perform more targeted sync operations. For example, users could be given the option to select an individual file through a “Browse” function and sync only that file to a lower environment. Similarly, users could select a folder and sync all associated child pages or assets within that structure. In addition a ‘Claim dependencies’ button would be helpful where if it is ticked it also grabs any dependencies such as assets, references or content fragments that are required for the selected page or folder and children of that folder. This would provide much greater precision and control, allowing teams to refresh only the content they actually need rather than relying on broader synchronisation tasks. Combined Author and Publish execution Finally, while the separate Author and Publish options should remain available, it would be beneficial to introduce an additional “Both” option. This would allow users to initiate a single action that executes both Author and Publish syncs sequentially, removing the need to trigger each process independently and improving the overall user experience.Thank you for your time and consideration.
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 configurations between report suites via API.This would ensure continuity for projects currently relying on 1.4, while aligning with the modernized API framework. Benefits / Use CasesScalability: Easily update or configure variables across multiple report suites in bulk instead of relying solely on the UI.Transparency: Retrieve all processing rules in one call, making it much easier to audit mapping when there are 100+ rules.Consistency: Compare variable configurations across report suites to ensure alignment in enterprise environments.Efficiency: Save time and reduce manual effort by automating repetitive admin tasks.Call to ActionPlease consider adding these configuration endpoints to the 2.0 API roadmap to avoid losing critical functionality when 1.4 is deprecated. This would greatly benefit customers managing multiple report suites and complex implementations.
Description - (I am sure this has been asked many times, so I just wanted to revive the idea) We need an automatic "Previous Period" date range component that automatically creates a dynamic lookback window relative to the selected date range on the panel. Why is this feature important to you It is basically not practicable to have fixed previous date range components in place that only work until one changes the panel date range. Example Freeform table using the last 7 full days (Panel date range) vs the previous 7 days (custom date range in the workspace project). Now, someone decides to change the date range on the panel to "last 30 full days" Result the custom date range still displays only 7 days, the rest is 0 the comparability between panel date range and freeform table is completely useless this becomes even more obvious / erroneous if you are applying a summary change visualization on the two columns, not taking the same number of data points into consideration How would you like the feature to work The "Previous Period" date range automatically calculates the previous x days / weeks / months before the currently selected date range, based upon that value. Should I change the panel date range, this will automatically update the data that has been filtered by this date range e.g., in a "Summary change" visualization Current Behaviour once you change the panel date range, your data is messed up, becoming unusable this is extremely annoying for all levels of analytics consultants. I don't know how many times I have explained this to clients or had the same issues myself other analytics tools like Looker Studio do not seem to have that problem, see https://support.google.com/looker-studio/answer/9272806?hl=en For an analytics solution as mature as Analysis Workspace, this should be a standard feature. @ericmatisoff your two cents on this idea would be amazing. You seem to have the best connections to the product team
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 is not a minor limitation — it is a migration blocker. We currently: Cannot fully migrate to API 2.0 Must continue using API 1.4 in parallel Lose visibility into critical configuration logic ✅ Requested Solution Option A (Preferred) Extend existing endpoints to include missing metadata fields. Option B Provide new endpoints for full report suite configuration management (parity with 1.4). 💬 Additional Context This is not a request for new functionality, but for feature parity with API 1.4, which is still required for enterprise use cases.
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 consistent configurations through code Integrate Analytics setup into their development workflows Scale variable management efficientlyRequested Solution:Please add endpoints to API 2.0 that provide full CRUD (Create, Read, Update, Delete) operations for Adobe Analytics variables, matching or exceeding the functionality currently available in API 1.4.This is essential for maintaining operational efficiency and preventing workflow disruptions when API 1.4 is discontinued.En savoir plus :1image.png
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 this time making it difficult to find important updates.
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.
The older version of the API, 1.4, allowed us to download a JSON of the processing rules in a suite. Since these are instrumental in transforming data into eVars, Props, and Events, they are an essential part of maintaining the data quality of a suite. The newest version of the API, 2.0, does not currently support accessing the processing rules, and it's been stated on Github that, as of this idea submission, processing rules access is not even on the roadmap. Unless Adobe is going to eliminate these rules (and the eVars and Props that are driven by them), a mature multi-site installation of Adobe Analytics, esp. across mobile and web, relies on a constant overview of processing rules for maintenance, QA, and to aid site and mobile app developers.Please make sure that processing rules are accessible via the APIs, not just in version 2.0, but in all future versions. Leaving 1.4 up is not a complete solution, as Adobe may deprecate it at any point.
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 creation more robust, efficient, and aligned with real-world data variability, ultimately driving better segmentation and campaign performance.
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 revenue as well as customer experience. Automation through APIs would ensure consistency, reliability, and faster response times during data-related incidents. Feature DetailsThe API should support the ability to start, stop, pause, and resume multiple journeys and campaigns simultaneously, rather than requiring individual actions per journey or campaign. This bulk-control capability is essential for effective operational management at scale. Thanks,Mithil
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.
