How to set up Preview or Message Proofing in EngageOne Content Author

Preview and Message Proofing can be used within the ContentAuthor Admin console to enable the user to see how their messages will appear in the output document.

Previews make use of the .HIP file that controls a Designer publication in the production environment and which is created when it is published in the Designer. Effectively a preview runs an embedded version of the Generate production engine using a sample of the input data that normally drives the application. A preview application (configured for PDF) must be created in Designer and both the HIP file and sample data file made available for Content Author preview. (Note that the HIP file must be a complete publication containing both design and resources.) Any lookup tables used by the application must also be made available or, if they are not required for the preview, can be disabled. All files are loaded to the Content Author repository for use when the preview is run.

Preview Message:
When used by authors and reviewers in the Content Author client a preview forces the current message to be selected for the defined message area so that it can be viewed within the context of the relevant page layouts. The possible effects of other messages are ignored in this mode.

Message Proofing:
A preview can also be used by administrators to view the effects of all the messages in entire projects or folders in the context of publication output. This is effectively previewing the output that would be produced if the selected messages were published. You should also run proofing to verify that the preview application is working correctly before making it available to authors and reviewers.

How to set up a Preview in Content Author:

1. Select View/Previews from the menu or click the Previews icon
2. Click Add to create a new preview application or select an existing preview from the list and click Edit to modify it.
3. Provide details of the Designer application to be used for preview.  Use the Details tab in the properties section to give the preview a name and description, and identify the Designer HIP and sample data files that will generate the sample output.  Use the Lookup Tables tab to specify any lookup tables that are in the Designer application and are to be used for the preview. The lookup tables are imported and stored in the repository.
4. Click OK to save the changes.

To make a preview available for use with messages in the Content Author client, add the preview to a domain and then add the domain to the relevant projects or folders.

Running message proofing
When messages are "proofed" in a preview application the user needs to select the messages that should be included in the sample job. These can only be either Awaiting Production or In Production. Typically the user selects the project or folder that relates to the publication referenced by the preview application, but if required, any combination of projects and folders can be selected for this purpose.

How to set up Message Proofing in Content Author:

1. Select Tools/Message Proofing from the menu.
2. In the Message Proofing dialog box select the projects and folders that contain the messages to be included in the run.
3. Click Next and select an existing preview application for the publication expecting the selected messages.
4. Click Finish.The system will automatically switch to the Message Proofing Output view. This view always contains the output from the last time a message proofing job was run. If a new job is run the content of the view is updated.
5. Check the job log to ensure the job ran correctly, and if not, correct any problems and rerun the proof job.
6. Check the output.The PDF Files tab will contain a separate PDF document for each document produced by the Designer application. The number of documents available will depend on the sample data file specified for the preview application and whether the run completed successfully or not. Double-click any document to load it into a local browser for viewing.

All the above information can be found in the Content Author Administration Guide.
UPDATED:  September 8, 2017