You are here: Job and Form Set Rules Reference > JDT Rules Reference > PrintFormset

PrintFormset

Use this form set level rule when you use the GenData program by itself to execute GenTrn and GenPrint processes (single-step processing). In that processing environment, this rule, when combined with the InitPrint rule, prints form sets.


	Note	Do not use this rule if you are running the GenTrn, GenData, and GenPrint programs as separate processes.

Syntax

;PrintFormset;;;

This rule checks the recipients for the form set and then identifies the print batch in which this form set should be included. It then prints the form set.

This rule has no parameters.

When you use this rule, you must also include a BatchByPageCount or BatchingByRecipINI rule to produce print batches and the final print stream. If you omit either of these rules, you’ll get the following error message:

Unable to <PRINTFORMSET>()


	Note	You must define the BatchingByRecip control group to pass parameters to this rule. Use this control group to specify the batch names and search criteria (conditions) for the batches. If you receive this error message, also check the condition.

Example

Here is an example:

;PrintFormset;;;

You can also use the PrintFormset rule to create multiple print files when you run the GenData program in single-step mode to produce PDF or RTF output with multiple transactions. This capability is related to running Documaker under IDS (see the Internet Document Server Guide for more information). To do this, add the PrintFormset control group and these options to your INI file:

< PrintFormset >

MultiFilePrint = Yes

LogFileType = XML

LogFile = (log file name and path)

Option	Description


	Note	You must place this rule before the PaginateAndPropagate rule in the Base Form Set Rules section of the AFGJOB.JDT file when running in single-step mode. When running in multi-step mode, use the MultFilePrint callback functionality.

The log file that is created is either a semicolon-delimited text file, formatted like the file created by the MultiFilePrint callback function or an XML file. Here is an example of the layout of the XML file:

<?xml version="1.0" encoding="UTF-8" ?>

- <LOGFILE>

- <TRANSACTION INSTANCE="1">

<BATCH NAME="Logical Batch Name">.\data\BATCH1.BCH</BATCH>

<GROUP1 NAME="Company">SAMPCO</GROUP1>

<RECIPIENT NAME="INSURED">INSUREDS COPY</RECIPIENT>

<FILE>DATA\0rDcP7WxytE8ECp5jexhWXVqkV840Vw_F-GykT_VMfd.PDF</FILE>

</TRANSACTION>

- <TRANSACTION INSTANCE="2">

<BATCH NAME="Logical Batch Name">.\data\BATCH2.BCH</BATCH>

<GROUP1 NAME="Company">SAMPCO</GROUP1>

<RECIPIENT NAME="COMPANY">COMPANY COPY</RECIPIENT>

<FILE>DATA\0v3l7pBdVqHceoRL5hf2xqjJ7WMxiRVO9U70iFiIcne.PDF</FILE>

</TRANSACTION>

</LOGFILE>

Use the options in the DocSetNames control group to determine which XML elements are created. The values in this control group are the same as those written to a recipient batch or TRN file.

PrintFormset

Syntax

Example

See also