Here's an idea: The Hub powers the new public Workfront Community. I even hear there's a package for that. We can have it up and running by the weekend if you're game.--Narayana
Hey Doug, It's a genius move that one of my users showed me one day and surprised the heck out of me. He had a three-column layout dashboard with a collection of links he had created pointing to Workfront and SharePoint resources. It's a pretty slick trick if you dare to give it a try. Good stuff! T...
Hi Corey, What you need to do is break this up into two separate fields and then use this shared columns article to stack them with an HTML <br> tag in the middle. Thanks,Narayan
Hi Darin, While I'm sure customers with Fusion appreciate the advice, I'd like to know what you suggest the rest of us do? At Truist, I can only hope that users don't figure out that they can change their email addresses or that they can delete that team they're on that I've set as the default route...
Hey Leif, I’m also interested in hearing what others have to say about this. It concerns me that my users can change their own email addresses. Let’s say someone thinks it would be cool to change it to billygates@microsoft.com. Wouldn’t all of the user’s communications, sent reports, confidential da...
No just make sure you use the exact same fields. The easiest thing to do is to create the issue form first and then copy it to a project form. But if you already have the form, use the “Field Library” to add the existing fields. Here’s the naming convention I like to use:
WFCOE Access Request
WFCOE...
Hi Yolanda,
Yes, you need to ensure that a custom form with the exact same fields exists on the template that you’re using during the conversion to project. With the fields on the template, the data will be copied to the project. Keeping the issue and project custom forms perfectly in sync is highl...