Welcome to the Adobe Workfront General Community! Connect with peers to ask questions, share best practices, explore release updates, and contribute ideas that shape the future of Workfront.
Recently active
A HUGE thank you to @MikeEngel for sharing all his knowledge on the Unified Approvals transition! We realize there were a lot of unanswered questions from the chat so we are working on a consolidated Q&A that we’ll post here later, as well as discussing additional webinars to address these! As discussed today, access to Unified Approvals will be based on your Workfront contract renewal date, but if you want to get access earlier, reach out to your account team to see if you can recontract early! Below are a summary, links to the slide deck, recording, and resources! Senior Product Manager Mike Engel shared updates on the new Unified Approvals experience, bringing enhanced review and collaboration tools for both video and non-video assets. Mike demo’d the new experience, including annotation and collaboration tools. He also discussed the transition, which will allow teams to adopt it in stages (using both legacy and new approvals, as needed) as well as potential future capabiliti
I am unable to turn on the cutom field for the cards on a Board.
I find where I spend most of my time utilizing the log in as feature is on testing new reports - specifically ones where $$USER.ID is involved.I think it would be super helpful if there was a button for admins on the Report Actions to have a “View Report As” feature that allows admin’s to preview a report as a specific user to save all of the clicks between setup and reports.
If I delete old routing rules in a Workfront request queue, does that impact any historical projects that used those routing rules?
Anybody advise on how to/ if it’s possible to pinpoint proof comments when creating them in Fusion? The rest API lets me narrow them down to page X but I need to go a stage further and pinpoint them to specific X and Y co-ordinates with the arrow as if the user was doing it via the UI.I’ve tried recreating the calls the UI makes but I can’t make it work. It calls https://us.my.workfront.com/proof/rpc/index.php and passes a session ID in the request body but both the session ID returned via the ProofHQ rest API and the main WF API result in errors when creating comments.
A huge thank you to everyone who joined today's Champion Chat: Things We Changed Our Minds About with Workfront! And an extra special shoutout to our amazing Workfront Champions - Carol @CarolMajewski , Kellie @KellieGardner , Monique @MoniqueEvans , Olya @OK18 , and Tim @TimWy1 - for being so open about their lessons learned, sharing their real-world experiences, and helping make our community such a welcoming place to learn. We're incredibly grateful for people like you who are willing to keep it honest and help others grow! Panelist Questions & Answers: What's a Workfront hill you used to die on that you've since climbed down from? Panelists said they’ve shifted from rigid, one-size-fits-all approaches to more flexible, practical use of Workfront. They also embraced "good enough to launch" implementations and accepted that Workfront isn't meant to replace every system. What's a feature or capability you initially disliked but now love? Custom forms, groups/group admins,
I’d like to propose a fairly simple idea. We create reports with many OR sections. I would say it takes some time to go back over time to remember what each section was filtering for. There could be a simple solution where there is a label and description box for each OR section.
Hi WF community,Looking to hear from folks that are in a mixed legacy/cloud storage environment, I have some questions around environment promotions and refreshes. What are you experiencing?When you refresh a sandbox, I assume it reflects storage of what’s in prod? I.e. if you convert a portfolio to cloud storage (via Preferences) in SB01 to do some testing and whatnot, and then it refreshes, does it go back to legacy storage? I’ve been told there is no rollback, but how does it work with refreshes? When you promote objects from sandbox to prod, is the storage type of those objects respected/carry over into prod? If you’ve chosen to have some user Groups enabled in Preferences instead of Entire Org, does this have any impact on env promo (i.e. if anyone doing the promotion is or is not in a Group)?
Hi there!We may use Workfront a little differently (maybe not as robustly) than others so I’m looking for some insight.We have individuals that create “projects” with “tasks” for more daily tasks / updating of items / check lists / documentation (think that they visited a location and want to document what was discussed/observed there). Then we have true “Projects” that have meetings corresponding to the goals/expectations of a project, tasks, deliverables, etc.How we currently have WF structured these “daily/weekly” documentation project items fall in the same programs as true Projects. I’m looking for any help or insight on how to redesign the system so we have a structure that better distinguishes between Projects and those documentation/one off tasks items.Thank you!
Users have high-priority need to take a Request that has been converted to a Project (using a specific template) and create a second project (with a different template) out of the original Issue/Request. Users would be able to browse from Request list and see all projects created from original request.
Description - The current functionality for routing rules is very limited. We are only able to configure routing rules for specific queue topics. Allowing us to assign specific user/teams to a specific queue topic. The following is functionality that is possible through Fusion, but want to be available without Fusion: 1. Automatically Convert Requests/Issue into a Project If a request is submitted through a specific queue topic, then automatically convert the request into a project using a specific project template. Ideally, we would also have the ability to configure this at the custom form level. e.g. If the requester selects XYZ on the request form, then convert into a project using XYZ template. If the requester selects ABC on the request form, then convert into a project using ABC template. 2. Dynamic Request Routing Based on how the Form was CompletedSimilar to #1, allow us to set routing rules based on how the request form was completed. If c
The Problem: If your company uses Workfront Data Connect on the Ultimate plan, you know it runs on an Adobe-managed Snowflake Reader Account. Because customers don't have admin-level database privileges on these instances, we can't create custom Snowflake Row Access Policies or Secure Views. This creates a huge security roadblock when trying to restrict sensitive data by team, region, business unit, etc.The Solution: Adobe should give its top tier customers native row-level filtering capabilities for Data Connect—either by provisioning provider-side Secure Views/Row Access Policies based on customer specs, or by adding row-level governance controls directly within the Workfront admin interface.Why Vote for This? Unlock Broader Usage: Safely roll out Data Connect insights to more teams without exposing restricted or sensitive rows. Tighter Security: Meet strict enterprise compliance and data governance standards natively. No More Workarounds: Stop building complex, costly ETL pipeli
To reduce the risk of accidental interruptions, we recommend moving the Schedule Sandbox Refresh button from the main Workfront page to the Setup menu.Keeping this action button on the main page makes it easy for users who are not involved in the refresh process to unintentionally cancel or modify a scheduled refresh, which could directly impact planned activities.Since refreshes are typically coordinated internally by the team before execution, placing this option under the Setup menu provides an additional layer of protection, ensuring that only authorized users performing configuration tasks can access it and significantly reducing the likelihood of accidental changes.
I would like there to be a global Workload Balancer setting that automatically hides ON HOLD or DEAD projects without applying status-based filter criteria or needing to update the project tasks so they don’t qualify. Similar to the how completed work can be removed from the Workload Balancer through the Show completed work setting, it would be ideal if there was a Show Dead or On Hold work setting that could be toggled off once in settings rather than having to add criteria [Project: Status -- Does not equal -- Dead, On Hold] to all Workload Balancer active project filters to exclude these projects. USE CASE: When an in-flight project is cancelled or put on hold, setting its status to DEAD or ON HOLD allows the Project Owner to freeze the project where it was in its progress without having to complete or clear the qualifying tasks to remove them from showing in the Workload Balancer. That way if the project happens to come back to life down the line, the remaining tasks are still set
We have a group that would like to make extensive changes to projects and tasks. They want to temporarily disable email notifications for their group while making these changes. I have 2 questions: Is disabling email notifications for the entire group the best way to accomplish this? There are 200+ users in the group. Could this be done at the project level? Will users receive “backlogged” notifications? For example, if you turn off email notifications on Monday and reenable them on Friday, will the users receive all the intervening emails on Friday that were skipped.
Can a calculated field be created on an issue before it converts to a project. I want the portfolio to auto-populate a custom field on the issue request intake form without using Fusion if possible.Thanks in advance!
Has anyone else noticed that the AI Form Fill skips all custom fields that are hidden by display logic? Our requesters are giving up on the AI help and just typing “See attached document”.
We have just enabled Adobe storage and frame.io for review/approval. Our testing has uncovered quite a few bugs. I already have a ticket in with support, but I’m curious if others are experiencing the same thing.A big issue is that when someone starts an approval workflow, it seems to be a bit of a coin toss if the link generates or spins for a minute, then pops up a message “Approval link not available”I’m sure it’s related, but one of our users who is in a ‘new’ project will sometimes see the old document page instead of the new view.The failure to create a link has happened enough that it’s making it impossible to use for reviews right now.Again, just want to see if others are experiencing these bugs as well or if there is just a glitch in our account.
Hi all, We are trying to create a task report filtered specifically to show “not ready” tasks so users can plan ahead. However, when changing the “Task » Can Start” from true to false it turns all of our reporting rows blue. Filter in the reportBlue reporting rowsThere is conditional formatting on the “priority” column as you can see, but there is nothing anywhere (including in those conditions) that uses blue or “apply to entire row.” Even if I attempt to add a condition to override this to a white background, the blue remains. The only way to turn it off is to reset the “can start” filter to true. Any ideas what could be causing this behavior? Is there some sort of global setting I’m missing? Totally stumped. Thanks in advance!
Problem StatementIn Workfront, users submit requests through the system and may need to coordinate with colleagues in other departments on the same request. Today, if a user wants another person to be engaged in the request conversation, the most common process is to wait until after the request is created and then manually add an @ mention in the Updates section.This creates friction and can lead to communication occurring outside the request context—especially when users choose an easier workaround.Current WorkaroundAfter creating the request, users go to the Updates area and @ tag the relevant person.However, many users find it easier to:open the email notification they received for the request, and forward that email to the teammate in the other department.As a result, communication is no longer centralized in Workfront, and the “single source of truth” for the request is reduced.Proposed EnhancementCreate a field type (or input capability) that allows users to @ tag/mention others
Hallo liebe Magento-User,ich benötige einmal eure Unterstützung, da ich aktuell nicht mehr weiterkomme.Wir haben das Problem, dass bei einer innergemeinschaftlichen Lieferung nach erfolgreicher Prüfung der Umsatzsteuer-Identifikationsnummer (VAT-ID) der Steuersatz zwar korrekt auf 0 % gesetzt wird, der Produkt- bzw. Gesamtpreis jedoch nicht neu berechnet wird.Dadurch bleibt der Gesamtbetrag auf dem ursprünglichen Bruttopreis, allerdings ohne ausgewiesene Mehrwertsteuer. Der Kunde zahlt somit effektiv den deutschen Bruttopreis, obwohl die Mehrwertsteuer entfällt. Der Nettopreis wird also nicht korrekt aus dem Bruttopreis berechnet.Unsere Preise sind in Magento als Bruttopreise hinterlegt. Entsprechend ist unter Shops → Konfiguration → Umsatzsteuer → Steuern die Preisberechnung ebenfalls auf Bruttopreise eingestellt. Zusätzlich ist unter Shops → Konfiguration → Allgemein als Standardland Deutschland hinterlegt.Nach meinem Verständnis sollte Magento laut Dokumentation unabhängig davon kor
Join Senior Product Manager, @LilitM for this deep dive into one of the most impactful innovations in Workfront Planning: Global Record Types. This session walks through how global record types enable you to standardize key data structures across workspaces while still supporting the unique needs of individual teams. If you weren’t able to attend live — or want to revisit any part of the session — you can access everything below: Intro Slide Deck with Resources & Event Links Lilit’s Slides Webinar Recording One of the requests we discussed was gaining access to the companion spreadsheets that support the Adobe Summit - Marketing Planning and Metadata Strategy Lab. We’ve attached them as links below:Taxonomies Activities CampaignsAs Lilit mentioned during the session, we’d love to keep the conversation going here in the community. What questions do you still have? Are there any use cases you'd like to explore further? What features are you most excited about? Drop your thoughts,
Adding an Employee ID field to the user profile would be a valuable enhancement for organizations that rely on unique employee identifiers across multiple systems.In our environment, duplicate names are fairly common, making it difficult to distinguish between users. An Employee ID field would provide a reliable way to identify the correct person and improve data accuracy.This would be especially helpful in Fusion integrations that map Workfront user information to Salesforce, where we often need a unique identifier rather than a user name.It would also be great if the Employee ID field could be added as a selectable column in user views and reports, enabling administrators to easily reference and validate user records.I hope that you will consider this enhancement request.
Curious what actually goes on inside a Workfront user group session? Here's a taste. In a recent Workfront Central session, Deborah Baker (Marketing Workflow Leader) and Megan Lehman (Workfront Developer) walked through how they built a fully connected marketing system of record using Workfront Planning, Core, and Fusion, the kind of hands-on, behind-the-curtain walkthrough you won't find in the docs. This recap is the technical companion to their Perspectives article, Designing Workfront adoption for the long haul, which covers the strategy behind the build: people first, process second, system third. Here's how it comes together in practice.The challengeThe team set out to build an end-to-end template environment for a marketing-heavy organization, a major consolidation effort that condensed multiple separate intake requests into one streamlined flow. A request now comes in through Planning, spins out a program, a hero deliverable, and a request queue for one-off derivatives tied bac
What happens todayThe Workfront MCP Connector refuses to write any object name containing a colon, forward slash, double quote, or curly brace. This applies to both workflow_create_any_object and workflow_update_any_object.Workfront itself accepts all of them. The UI saves them, the database stores them, and the connector's own read path returns them intact. Reads pass. Only writes are blocked.Where it standsI raised this with Support. The engineer reproduced it and took it to Product, who confirmed it is a known, open discussion covering all Workfront object types with no decision yet. It is currently treated as a feature request rather than a bug, on the basis that the validation follows OS-level filename restrictions.That reasoning is worth a second look. The blocked set does not match any OS restricted set, curly braces are blocked but are legal in filenames on Windows, macOS and Linux, while several genuinely reserved characters are not blocked at all. And object names are not fil
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
