Adobe Workfront

Hello, I know i can bring this in a task report, but Is there anyway I can bring in lastnote: note text in a note report?

Can a validation rule be setup that only allows users from a particular group to access a form field?  I’m trying something along these lines but I can’t get the syntax correct.IF($$USER.groupIDs="69fcf9d70002183a0944fbb90b78a5ab", "Only members of the LP Approval group can edit this field.")Any help would be appreciated.ThanksFrank

Hi, Looking for some ideas and support here -  I am the admin for a financial services company, we have lots of regulations. We received a request that we now need to have our approvers “certify” that they checked the asset in the proof for x, y, z. My initial thought is to add a custom form to the document but this would be brand new behavior for our approvers to fill out and don’t love this. We also had someone bring up adding a comment, I also don’t love this because it is manual and think that we will be chasing down approvers to add this (also will mess up my automated workflows). Has anyone ever experienced this or has any idea? TYIA

Our migration experience has been challenging to say the least. Our assigned techs have tried their best to get everyone on the same page but we’ve had gaps in getting back to us over the past few months. We recently were told all users of the cloud have to backup their data before we migrate. We asked for directions to send out to our users and Adobe does not have any we are told. Support keeps kicking us back to our techs for the answer and our techs tells us to contact support...you get the idea. We’re 11 business days until Adobe will ‘force migrate’ us regardless if we’re ready. Any idea what happens when that happens? Trying to be positive but we’re on a three day streak of non-response to questions. I want to provide our almost 7K end users the best heads up on what is needed to be done in advance. Christina

Hello!I need to write a report that captures how many total active jobs there were in any given month of a year. My main problem is our active status’ are custom fields and WF doesn’t seem to want to work with those.How do I get this report?ThanksJustin

Buried in the extremely large feature release last month, were a number of layout template enhancements which I wanted to call out for those of you who might have missed it. The LT enhancements are applicable to all contracts as far as I can tell. https://video.tv.adobe.com/v/3483245/Please watch the recording if you’re interested in the new LT functionality below.-- Determine the options that appear in the More menu (proj, task, issue, portfolio, program)-- Determine toolbar options (e.g. you can hide everything except Create Project from Template)-- Customize header fields to include custom fields. (the 5 field limit remains unchanged)-- Customize left nav bars for groups, teams, users, templates Tagging in ​@user01245 for the 4th bullet point -- this might fix your issue more efficiently if you lock your casual requesters out of this section on their details page.

We’ve sporadically encountered this issue over the past four years, and no one has been able to resolve it. When a request comes in, we respond with an update or comment in the request, tagging the requestor. The requester responds to our comment, but the reply does not appear in the thread within the request; instead, it shows up in their own Profile ‘Updates’ area. No other users are tagged in these updates. We have no idea how these updates are reaching the user’s profile. Has anyone else experienced this? We only discover this when we check in with a customer after not hearing from them, and they say, “oh no, I replied to you!” We then have to search to find their comment, and most of the time, it’s on their own profile. My thought is that maybe they are replying to the notification email, and somehow it’s not being routed to the correct thread. Or perhaps there’s a link in the email that’s supposed to direct them to the existing comment thread, but instead is taking them to their

Join us for a panel discussion focused on building and advancing your career as a Workfront Admin. Hear from experienced professionals as they share what has fueled their growth, how they have expanded their skills, and the moments that helped shape their career paths.This session will focus on real world insights, from what makes the role fulfilling to how Workfront expertise, Adobe connections, and emerging tools like AI can open new opportunities. Whether you are looking to grow in your current role or take the next step, you will gain practical advice and perspective from those who have been in your shoes.What you will learn: What makes a career as a Workfront Admin rewarding and sustainable How building Workfront expertise can impact your long term career growth Tips for leveling up your skills and positioning yourself for new opportunities How to start incorporating AI into your day to day work Career advice panelists wish they knew earlier This is a session you will not

Currently, External Lookup fields support JSON-based data sources, but only a single property can effectively be used/returned. This becomes limiting in real-world integrations where systems require a stored value that differs from the user-facing label.Example:[ { "label": "Not Applicable", "value": "not_applicable" }, { "label": "Brand New", "value": "brand_new" }]Today, we can only expose either the label or the value. In practice, this forces us to expose technical/internal values to end users so downstream systems can properly consume the data.A common example is AEM Tags:label → human-readable value shown to users value → internal identifier/path required by AEM for storage and integrationsWith the current limitation, users see implementation-specific values instead of clean UI labels because the native connector must send the correct stored value to AEM.Suggested improvement:Allow External Lookup fields to:display one property in the UI (e.g. label) store/send another property

Has anyone figured out a way to exclude holidays in calculated fields in an efficient way?Our use case is we have 8 calculated fields and need the ability to not pull in the business holidays. Our back up solution is to create another set of fields where a user can do manual override dates but this adds additional work, additional fields we need pull into reports and adds more clutter to the form so wanted to gut check if there were any workarounds.Thank you!

Thanks to everyone who joined today’s workshop on Mastering Business Rules and Validation Logic in Adobe Workfront! The session was led by Adobe Workfront’s Tina Craig, Principal Business Consultant, Content Supply Chain, who shared several examples and best practices for using these new features to help with governance (and reduce the redundant reminders from admins)! Workshop Summary:Validation logic prevents form submission when criteria are met; business rules prevent object creation, deletion, and editing across system. Validation logic uses if-then statements on custom form fields; business rules are configured in the Setup area with broader scope (only available to customers on the Workflow Ultimate package). Practical examples like special character restrictions, character limits, date constraints, SLA enforcement, and multi-option selections were demo’ed.  Remember! Always test in Sandbox before production deployment to prevent workflow disruption. If you weren’t able to join

A user is unable to see the deadline in the report. I have raised this ticket multiple times, but the issue still persists.Upon checking, I found that this is related to how the stage deadlines are configured. For example, if there are two stages and the user is a reviewer only in Stage 1 (with no involvement in Stage 2), Adobe Workfront appears to consider only the overall (final) deadline rather than the stage-specific deadline. As a result, the relevant deadline is not visible to the user in the report.Could you please confirm:Is there an option to display stage-specific deadlines for users based on their assigned stage within reports?If not, is there any recommended workaround to achieve this?Looking forward to your guidance on this.

I’m hoping someone can help me understand why reviewers/approvers on a proof are receiving two different approval experiences. In some cases, reviewers are prompted to “make a decision,” while in other cases they are only given the options “Approve,” “Approve with Changes,” or “Needs Work,” which is the workflow we want to use consistently. Because the options presented are not the same for all reviewers/approvers, it creates confusion in our review and approval process. Could you clarify what causes these different approval methods to be sent, and whether there is a setting or configuration that controls this behavior?I’m also seeing what appears to be a related issue when I upload a new document to a project. I automatically receive an approval notice in my Home widget, even though these documents do not actually require my approval. Note: when we upload documents, they automatically create a proof.   In this situation, I am consistently asked to ‘Make a Decision’.   This clutters th