Proof for Content Approval

You can use the Proof for Content Approval task for generating a content proof and sending it automatically to your proofer. You typically make a content proof to check whether the contents of your file (layout, text, barcodes...) are correct.

At that stage, you are typically not checking the color accuracy of your proof yet, so the Proof for Content Approval task only performs some default color management, based on the ISO standard, in the background (for example to convert RGB objects to CMYK so they are printable).

When you are satisfied with the content proof and want to make a contract proof with color management, you can use the Image to Unscreened Proof task.

Proofing with the Proof for Content Approval Task

The Proof for Content Approval task sends the ready-to-proof files to the workflow of your choice on the Esko Proof Server , who then proofs it automatically on the proofer connected to that workflow. This proofer can be one of many types of proofing devices supported by the Esko Proof Server.

Note:

To use this task, you need to have created a printer, workflow and media in Fiery Command WorkStation (the client application of the Esko Proof Server). Make sure that the correct media is selected in the Media Associated option in the Print Settings tab of the workflow.

For information about creating a Proof Server workflow, please see the Esko Proof Server documentation, available from the Pack Proof documentation page.

Attention:

You can use several Proof Servers, but in this case, make sure that every workflow has a unique name, even across Proof Servers.

If there are workflows with the same name on several Proof Servers, you will not be able to send files to those workflows through the Proof for Content Approval task.

Task Parameters

In the Device field, select the imaging device that you configured.

Then use the tabs at left to show more settings to fill in. See:

Using the Proof Server Workflow Parameters

If you are using a Proof Server workflow that already has proofing parameters defined (for example the number of copies to print, or the rotation or scaling to apply to your file), those parameters will be filled in by default in the Proof for Content Approval task, so that you don't have to go check them in the Proof Server workflow and copy them into the task.

Note: This is not the case if you are using a SmartName or a public parameter to select your Proof Server workflow.

You can of course change those parameters as desired in the Proof for Content Approval task.