Proof View
The Proof View component is used to generate visual proofs of product presentations within the workbench and Web UI, providing a quick view of how a product presentation will look on a printed page. The component is also used to generate PDFs of these product presentations.
Typically, Proof View is used to produce small documents such as single-product datasheets; nutritional information tables; and documents that relate to health, safety, and energy regulations such as MSDS (Material Safety Data Sheet) documents, EPREL (European Product Registry for Energy Labeling) datasheets, and CE certificates. These documents may be as short as one page, or multi-page depending on business requirements.
Product proof views are also useful to product managers who would like a visual representation of the current status of data for different layouts, giving them a better overview of the quality of the data before approval.
Prerequisites
Prior to using Proof View in the workbench or Web UI, the following prerequisites must be met:
- An InDesign server must be connected to your STEP system, since it is the InDesign server that generates proofs. For more information on the deployment of an InDesign server, contact your Stibo Systems account manager.
- The following licenses must be installed on your system. Contact your account manager to begin the process of enabling a license or licenses for your system.
- STEPPublish
- STEPPublish.InDesign
- STEPPublish.ServerSide
- STEPPublish.ServerSide.InDesign
- At least one publication with at least one version must have already been created in the publication hierarchy in the workbench. For more information on creating publications, see the Publication Hierarchy section of the STEP Publisher (Adobe InDesign Integration) documentation here.
- A publication template and at least one product template must have already been configured and attached to the relevant publication in the workbench. For more information on templates, see the Templates in STEP Publisher section of the STEP Publisher documentation here.
Considerations
- Proof View supports both products and entities in the workbench. Entities are not supported in the Web UI Proof View component.
- Proof View can only be used for one product at a time, and only one product template can be used at a time. This requires that all data must be available either directly on the object being viewed or referenced from the object. Tables can also be used to display information from child and/or referenced products. For information on configuring product templates, see the Product Templates section of the STEP Publisher documentation here. For information on configuring tables, see the Tables section of the online help here.
- The proof view functionality for STEP Publisher should not be confused with the unrelated Web UI proof view functionality that uses XSLT to preview how a product will display on the web. The XSLT proof view feature uses a Web UI component called 'Proof View Action,' which uses XML-formatted values and optional XSLT stylesheet transformations. It has no relation to STEP Publisher or Adobe InDesign. For more information on using XSLT in STEP, see the IIEP - Configure Transformation by XSLT PreProcessor topic in the Inbound Integration Endpoints section of the Data Exchange documentation here.
- The same fonts used in your publication and product templates must be installed on your InDesign server for the pages to render accurately. If the fonts are not available, then a generic font (such as Minion Pro) will be used for the rendering.
Topics in this Guide
This guide covers the following topics related to Proof View in the workbench and Web UI: