Multiple Output Streams

1. Unit Objectives

The aim of this unit is to understand how preview works and extend our knowledge of publishing.

2. Preview

Previewing allows you to run a publication through the Series 5 production engine within the Work Center, itself without the need to go through the formal publication and deployment process. It produces a PDF version of the intended output and displays it in a Work Center window for your review.

Previewing uses the sample data currently assigned to a publication as the input data that would normally be passed to DOC1 Generate in a true production run.

If you have unresolved data aliases in your publication design you will be asked to map them to actual data elements (as defined in a data format) just as you would with the regular publishing process. As with regular publishing you must have a data format for your publication in place before you can run preview.

1. 1. Double click on the Table().
2. 2. Select the General Tab.
3. 3. Number of transactions to display in editor select, All ratio button.
4. 4. Click OK.
   

3. Publication View

1. 1. In the logic map, right-click, select View Publication.
   

1. 2. In the logic map, double-click on Publication ().
2. 3. Label, type, Transactional Statement.
3. 4. Data Map, click
.

1. 5. Double-click the Company Letters project folder.
2. 6. Click Transactional data map.
3. 7. Click Open.
4. 8. Click OK.

Now we are ready to preview the document.

1. 1. In the logic map, right-click, select View Document.
2. 2. Highlight Transactional Statement.
3. 3. From the main menu select Task/ Preview.
   

1. 4. Click on the *.pdf to display.
   

4. Multiple Publishing

We can also set up a publishing task that will create more than one output document. We can output multiple, different documents in one run, or output one document in multiple formats. We will go through the steps for publishing our transaction document, and create an output .pdf and .afp.

1. 1. In the Work Center Manager click on Design tab, Publications bar.
2. 2. Double-click the Company Letters project folder.
3. 3. Highlight, Transactional Statement publication.
4. 4. From the main menu select Tasks/ Publish Current Draft
5. 5. Click Next..

We do not need to associate a data map because we already associated it in the Publication View.

Lets continue with the Publish Wizard and select multiple output devices.

1. 1. Click on Next.
2. 2. Processing Options, click, Use multiple output devices checkbox.
3. 3. Output Devices, click, Split PDF and AFP300 checkboxes.
4. 4. Click Next.

Next we will specify the location of the sample data file.

1. 5. In Input File, browse to the resource directory and select transsample.svd.

The Output1 files window specifies the location and output datastream file.

1. 6. In the Output Files window, double-click, Output2.
2. 7. File, type, c:\DOC1Resources\%1transactional.pdf.
3. 8. Click OK.

Now we are going to add the .afp output stream.

1. 1. In the Output Files window, double-click, Output1.
2. 2. File, type, c:\DOC1Resources\transactional.afp.

1. 3. Click OK.

1. 4. Click Finish.
2. 5. Name, type, transactional.
3. 6. Click OK.
   

1. 7. Click Yes.
   

A .hip file will be created and placed into your resources folder.

 

 

5. *.OPS File

An override production settings (.ops) file allows you to specify supplements and alternatives to some of the job settings that were used when publishing a publication design.

The use of an OPS file is optional unless you have not specified all file references and/or license data in the publishing task.

An OPS is a text file. Options are coded as keywords and associated parameters within several distinct sections. Sections must be introduced with the relevant name within angle brackets, for instance: <Journal>.

No sections or keywords are compulsory and you should code only those options that suit your requirements. All missing options are assumed to have been specified as part of the publishing task.

All file references can include both path and file name as required. Ensure that you code all such references in a format suitable to the operating system under which you are running the production engine.

We will create an ops file that will send the pdf to our resources folder, and send the afp directly to the c: drive root.

1. 1. Open, Notepad.

6. Ops Complete Example

An OPS file can allow you to override production setting. The use of an OPS file is optional unless you have not specified all file references and license parameters within several distinct sections. Sections must be introduced with the relevant name with angled brackets (<>). Comments can be included in the OPS file but they must be prefixed with a semicolon character. No sections or keywords are compulsory and you should code only those options that meet your requirements. All missing options are assumed to have been specified as part of the publishing task.