Customize proof decision options

Transcript

Customized Proof Decision Options In this video, you will learn what a proof decision is, how to rename proof decision options, and how to hide unneeded proof decision options. Those assigned as either the approver proof rule or reviewer and approver proof rule have a very important responsibility when it comes to proofs. They decide what gets approved. The Make a Decision option automatically appears at the top of their Proof Viewer screen so they can quickly mark their decisions and complete their review. These decision makers at your organization could be project managers, creative directors, legal representatives, or product managers. As the system administrator, you establish what the decision options are as part of the proofing setups. You can customize the terms to suit your organization’s workflows. A few things to keep in mind. The decision settings are global, so they’re the same for all proof users. Changing the decision terminology affects existing proof workflows, so it’s best to customize these during initial system setups. From Workfront’s main menu, select Proofing to access the proof system setups. Then go into the Account Settings and select Decisions. Workfront’s default decision options are Approved. The proof is fine, as is, and is ready to go. Approved with changes. Make the changes indicated, and then the proof is ready to go. Generally, this option also means a new version of the proof is not necessary. Changes required. Make the changes indicated, and then upload a new version of the proof. Not relevant. The proof isn’t relevant to the reviewer, and a decision from them is not needed. The pending option is used by Workfront to indicate decisions have not been made on the proof yet. If your organization does not need one of these options, Workfront recommends hiding the option rather than deleting it. Many customers hide Not Relevant because that decision isn’t part of their workflows. Just click into the field and change the name. When you rename a decision, it’s a good idea to keep the meaning behind the new term, the same as the meaning behind the default term. For example, if Approved isn’t language used at your organization, you can change it to Ready for Release. Instead of Changes Required, maybe your organization uses Corrections Needed. Then click again outside the field to save. Once everything is set up, do a quick test in the Proof Viewer to ensure everything appears as desired.