Workfront

I have an browser extension call Whatfix - Cost is about 100/year per user.

It allows me to create quick links at the top of Workfront pages and the quick links reference the Workfront release notes

The same application allows me to have a Workfront self help and I put the links in there also.

How do you or your clients typically manage the environment lifecycle in Workfront?

We currently use up to four environments (Production, Preview, and two Sandboxes) to avoid making changes directly in Production. Our process starts in Sandbox 1, then moves to Sandbox 2, and finally to Production. However, we’re facing two main challenges:

1. There’s no reliable and comprehensive way to promote configurations across environments — the package export/import only supports a limited set of objects and settings.
2. Some features (e.g., Proofing) are only available in Production and Preview, making it impossible to test them beforehand.

Do you have any best practices or recommendations to address these limitations?
Maybe we're doing it the wrong way.

Thanks!

Can you provide an example of a roadmap on how you align releases, fixes, and long-term planning?  This is always a challenge to get leaders to see and understand

What would be the best way to pull a report for proofs with no reviewer and approver? We frequently have designers forget to add an approver to the proof.

How do you effectively create project plans in Workfront where you are typing in responses within the project columns? Is there a secret to this? 

I see your sample question "What’s one thing you wish every admin did regularly that would save headaches later?" but have to ask "How do you think two steps ahead so you can see a headache coming?"

External Lookups (Used Internally as Excel Spreadsheet Replacements):

Is anyone actively using external lookup fields to act as a data table in Workfront? For instance, retrieving other custom data on a project's task or issue list to then be used in other spaces? I've built a few versions of it, and run into a few small issues here and there in terms of useability, but overall it seems like a really good spreadsheet replacement tool that is easier to manage than something like a lengthy picklist set and calculated fields or display logic to drive choices in a form. 

Curious to hear other's thoughts!

What are some of the ways that admins/power users communicate with their internal users to cascade information, foster adoption and interest, and get them excited about new features? We have challenges with varied use and falling back into excel documents for certain teams. Would love some tips on how to bring folks along on the journey!

Hello Bridget,

I do that with a third party product we have called Whatfix.  It is a browser extension and it costs approximately $100.00 per user per year.

What fix allows me to do the following that I use to inform users.

1.  You can create a popup message that appears when they login (you decide when and for how long)

2.  You can create what I call quick links - These appear on the Workfront pages and the user can click on them.  When the user clicks on them they can have the following happen

> A popup message is displayed with information

> The click takes them to a link which can have a document, video, etc with information

> The click starts a process flow with tips on each step to guide them thru the process

3. Whatfix provides a self help Icon that is displayed on each Workfront Page.  Self helps has many features

> User can search for a topic (for example:  Documentation on the next Workfront release)

> Folders in which you can create and place Workfront items (videos, documents, links, flows)

> I even have the ability for them to start a webex meeting with me (the admin)

4. I have created about 80 process flows that the user can use

> Some provide a tip on each step of the flow (good for new users learning Workfront)

> Others are what we call Auto Complete flows and these process flows try to complete as many steps as possible automatically and only stops and displays a tip when the user needs to do something in the process.

Hope this is helpful