Customize proof comment actions
In this video, you will learn:
- What an action is
- How actions used on comments
- How to customize action labels
Actions for Proof Comments In this video, you will learn what an action is, how they’re used on comments, and how to customize action labels. Comment actions help proof users keep track of what has been done or should be done with each comment thread on a proof. A click of the flag icon lets you select the appropriate action. For example, internal stakeholders reviewed the design for the new product packaging and made their comments. Some of the comments are conflicting, so the product manager needs to let the creative designer know which corrections to make. A quick way to do this is with actions, marking some comments to do and others as ignore. The designer can then filter by action type and focus on the right comments. Actions are a global proof system setting, so all proof users will see the same list. As the system administrator, it’s a good idea to talk with all of the teams using proofing and make sure that the actions list is suitable for everyone. Click proofing in Workfront’s main menu, then go into the account settings. You’ll find the action setups in the settings section. Workfront recommends renaming existing actions. Click the setup link and then enter the new name, then click save. If you do need to create a new action, just click the link, give it a name, save and establish its order in the list.
Commonly used actions are to do, stat and clarification required. If your teams aren’t going to use an action, just turn it off so it doesn’t appear in the proof viewer. Click setup, then the deactivate button. Be sure to save. The actions appear in the order seen here in the system settings. Reorder them by clicking the up and down arrows, which appear only in the active actions. It’s up to your organization to determine if actions are needed, what they should be called and how they’re used. Workfront recommends that you keep the total number of actions manageable by keeping the list short, make the names meaningful and clear, ensure everyone knows how actions fit into the proofing process and deactivate actions that are no longer used.
Your turn
Look at the proof workflows you’ve already created and reflect on the discussions you’ve had with the teams using review and approval workflows. Will actions be needed? If so, update the documents where you recorded the workflows to include the actions.