Our company uses automated proofing. The PM creates the proof and uses the appropriate proof workflow. The last stage of every proof is the file owner. They do this so they get notified when the proof is finished going through review and they then mark each comment resolved when they make the edits ...

I have a proof approval report that shows all proofs still awaiting a decision. I want to add a column rule for proofs that had no deadline set but were created more than 15 days ago. Is there any way in text mode to use both of these criteria? 

What we are being asked to do is send an email to an outside email address. That email address will be provided in a field on the custom form. Then when a specific task is activated they want it to send an prewritten email to the address they provided on the form. We do have Fusion and are hoping th...

I spoke with support on this issue and they have a fix that they are hoping to release with this Thursday's update.

We have a department that is asking for Workfront to generate emails to be sent to employees (email address in a field on the custom form) based on a task being activated in the timeline. Does anyone have any experience doing/attempting anything like this that would be willing to share their finding...

Description - Users with the access level of System Admin should be able to access proofs without being added to the proof workflows under the Workfront Stage.   Why is this feature important to you - I work the support channel and often need to access files to troubleshoot. Every time I access a p...

This wouldn't help when converting the requests into projects but if they are creating a project using a template you could train them to open the correct Portfolio/Program first and create the project from within there. That would auto-populate those fields for them.

Description - When a user deletes a task they are not alerted if the task has any documents attached. This results in documents getting deleted in error.   Why is this feature important to you - We store our documents on the task level for ease of use for all those assigned to the task. If the task...

I don't think checking out the document would be a solution for us. We use automated proof workflows that may have more than one user reviewing the document at one time. Also when the review is complete we move the proof to the next proofing task which would require a new version be added on top and...

Is there a way to prevent a task from being deleted when a document lives on that task? We have had several instances lately where the user deleted a task unaware that a document/proof lived on it and it allows them to delete the task along with the document. I tested it and it doesn't give any warn...