Workflow Documentation

Data Environment
Realtor Listing application. Delimited format.

Supplemental Data
None.

Web Integration
Data can come from any source, no additional processing needed. If a web data input interface is used, a delimited data file should be created. It's unlikely that a web submission process would be used for such a specialized piece, as custom photos and descriptions would need to be submitted.

Data Conditioning
Open in Excel and save as a delimited file format. Header files cannot have spaces in VIPP. The spaces were replaced with underscores.

Quark File Conditioning
When applicable, Quark static portions of the design were saved as an EPS and used as a background image. Some images were cropped external to Proform Designer.

Asset Library
VIPP Project folder or VIPP Project Container

Coding
The information and photo of the real estate agent are created (using Proform Designer's logic wizards) based on conditional logic from information found in the realtor_database.csv. Conditional page logic was used to determine which records print. This was based on if color images were defined in the database. The RTF files were imported for the house feature descriptions.

Lytrod's Proform Designer creates VIPP code and resources and the document is ultimately composed and assembled at the VIPP enabled engine from the raw data.

RIP and Print Process
The VIPP enabled engine does the composition, imposition, RIP and print process.

Provided is a VIPP Project Container, JOB7.VPC, the VPC file contains all of the files including a job submission file. The VPC can be launched using the VIPP Project Manager or on supported DFEs.

Since not all DFEs support Project Containers, a VIPP Project Folder, JOB7, is also provided. The project folder contains all files, including the data file, needed to run the application. Simply copy the JOB7 folder and its contents to the XGFC/Projects folder on the VIPP enabled engine.

The production print stream is the data file, in this case house_database.csv, which contains the VIPP job ticket and database data. In a production print environment, the data file would be sent to the VIPP enabled printer via LPR (this can be done via Lytrod's Proform Designer or via any standard LPR demon). For demonstration, you may simply open the project folder and "print" the data file: house_database.csv.

It is important to note that Lytrod supports VIPP image caching which dramatically improves job processing, as the variable images are ripped only once for the entire job.

Scalability
Unlimited. This is the advantage of the dynamic document construction method used by VIPP. The document is composed at the RIP in real time, as the data is sent to the printer.

Turnaround Time
3 hours.

Overall Caveats and Considerations
None.