Hi all, I'm Anthony. I'm the Senior (also *only*) Traffic Manager for Health Science Communications and the Scienomics Group (operating under Healthcare Consultancy Group). I've been in my role for 13 years and I'm very proud of my efforts in taking us from a completely analog routing system to our ...

One of my users got an automated email from WF saying that someone had responded to a comment he made in ProofHQ. Unfortunately, the link in the email sent him to the Updates section of the document where there is no way to open ProofHQ to see what that comment refers to (our docs often have hundred...

My company has a separate system for requesting and opening job numbers. We use a Custom Form at the project level to insert that information (among other things) on every project. I'd certainly like at least a set field for our job numbers.

YES! My agency uses a combination of job codes, file name and version numbers to readily identify documents/versions. We run into two issues with the way WF handles docs: 1. Our new file name is not captured, which can cause confusion. I know it can be edited after upload but that just creates addit...

That's a big "Yes, please" from me! Our policy is to run a proof on every version of a doc but my users often forget which can cause an issue later on when we want to refer to an older version.

As mentioned above, there is a way to do this, but my thought is that it this List view should be the default.

I was just looking into that functionality yesterday and was disappointed by the meager options compared to Notifications.

My instance covers multiple agencies operating under a single holding company, so limiting what "Junior Admins" (a term I just made up) can see and do would be ideal.

This should be coming in the next release- July/August.

Understanding that some documents or elements within a document may not be processed as text, having a built-in spell check would be very helpful.