Application: Integrated Statement (Industry Banking, VI Level: L2)
Workflow Documentation

Data Environment
(Describe the typical sources of data and format in this type of application.)
The data for this type of a statement would typically be generated from an application program in a line data format. The sample data did not provide such data. Provided was database information, on the investor and investment plans. Account activity was not provided.

Supplemental Data
(File names and format and include any supplemental data that was used to produce the application.)
Lytrod took the liberty to create a typical transactional data file using the data sample provided as real customer line data file formats. The “investor” and “portfolio summary” databases were used to create a line data file with account activity added.

Web Integration
(If applicable, describe the process for enabling web-based data input into the application.)
Data can come from any source, including the web. Typically application software would process the data in print ready format in a billing statement such as this. This type of job would be unlikely to be enabled from web-based data input.

Data Conditioning
(What, if anything, had to be done to make the data usable in your application?)
Lytrod took the liberty to create a typical transactional data file using the data sample provided as real customer line data file formats. The “investor” and “portfolio summary” databases were used to create a line data file with account activity added.

Quark File Conditioning
(What if anything had to be done to the Quark file provided to make it usable in this application.)
When applicable, Quark static portions of the design were saved as an EPS and used as a background image.

Asset Library
(Describe the architecture and formats that the static and variable assets were stored in.)
VIPP Project folder or VIPP Project Container

Coding
(Describe the business logic and coding methods for enabling the composition and assembly of variable pages.)
Lytrod’s Proform Designer creates VIPP code that ultimately composes and assembles the pages. GUI based logic wizards in Proform Designer allow all business logic to be created.

RIP and Print Process
(Describe the production print stream and the composition, imposition, RIP and print process? Document all file names needed to load and run your application.)
The VIPP enabled engine does the composition, imposition, RIP and print process.

Provided is a VIPP Project Folder, JOB2, the project folder contains all files, including the data file, needed to run the application. Simply copy the JOB2 folder and its contents to the XGFC/Projects folder on the VIPP enabled engine.

Since not all DFEs support Project Containers, a VIPP Project Folder, JOB2, is also provided. The project folder contains all files, including the data file, needed to run the application. Simply copy the JOB2 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 intgratedstatement.txt, which contains the VIPP job ticket and the line data as described above. 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: intgratedstatement.txt.

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
(How large a record set can your solution support? What are the productivity implications and/or caveats associated with scaling the run to larger thresholds?)
Unlimited. This is the advantage of the dynamic document construction method used by VIPP. The document is composed at the RIP in realtime, as the data is sent to the printer.

Turnaround Time
(Document the time for an end-to-end process from trigger event to delivery.)
Need clarification. Design? Or print processing?

Overall Caveats and Considerations
(Anything that we need to know about this application such as workarounds, or special conditions e.g. limited number of data formats supported, etc.)
Since a VIPP workflow is being used, the caveat is that you must have a print ready file prepared. In real customer accounts, an application program would generate this print ready file from data sources.