I mentioned a concept last week (in a separate thread about force-adding Favorites to users via the API) that we've adopted, referred to as "Publishing," and that I would speak to it in more detail in a separate post. Publishing is something we do to reduce our reliance on custom Layout Templates. (...

Hi Tracy, Typeaheads are a special kind of field that can be added in your custom forms. In the Typeahead configuration, you can select different object types, like User, Project, Company, etc. Whichever object type you select in the Typeahead configuration, the custom field will then act as a "pic...

If I understand, you have a single project with multiple bodies of work to which you want to associate to different companies? Maybe I'm oversimplifying this, but can you not just add a Company Typeahead to the relevant task and issue forms attached to the work objects? You could update a work list...

Thanks Randy! Looking at it now, I feel like I was just being extremely lazy! Loaded it and it works beautifully.

That's all correct, Randy. And, I should have taken the opportunity to mention that it is possible to report on user's favorites. This is a component of a larger approach, that allows users in supportive roles - perhaps group admins who lack login as rights; or a team SME, to check and see if a user...

Hi Randy, If you're dead set on force-adding favorites to user profiles, I have your API call. It can definitely come in handy for certain situations. Your question speaks to a bigger problem of "how do I push and maintain a persistent view of objects to users that is dynamic and relevant to each ...

In an Issue or Task report, you can add a column with the below text mode: displayname=Assignment Entry Dateslistdelimiter=<div>listmethod=nested(assignments).liststextmode=truetype=iteratevalueexpression=CONCAT(IF(ISBLANK({assignedTo}.{name}),{role}.{name},{assignedTo}.{name})," - ",{entryDate})val...

I don't know if people see the beauty of this. To describe it another way, you can use this EXISTS statement to filter for records where their attached custom form (not a specific custom field) contains the search value in any of its fields. It's like saying "custom form contains value X" instead of...

If I hadn't had access to all his contributions in the Community and later, WF-Pro, I would never have become as capable as I am today., and my career would never have shifted in the direction of Workfront administration. THANK YOU NARAYAN, we owe you the world!

Hi Timothy, this suggestion falls in the general category of "data validation" which is enforcing any kind of rule on an input field. It is currently under consideration, but you can still vote to show your support for it:https://one.workfront.com/s/idea/0870z000000PSEhAAO/detail