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

BatchByPageCount

Use this form set level rule to check the value of a field supplied for processing against that for transactions currently in the linked list of objects. These transactions are populated by the CreateRecordList rule. This rule is also used with multi-mail processing.

If the field has changed, the system writes the records to the recipient batch file, based on the total page count for all recipients of all form sets in the set of transactions. If you omit the parameter, the system writes records in the generic linked list of objects to the appropriate recipient batch files, based on the page count for the individual records.

If you are using multi-mail, the system updates the TotPage field of the recipient batch record to reflect the total page count for all recipients of all transactions in the multi-mail transaction set.

     
Note Keep in mind this rule calculates the page count at the transaction level, not the recipient level.

Syntax

;BatchByPageCount;;(MMField);

Parameter

Description

   

MMField

(Optional) Name of the INI option in the Trn_Fields control group which defines where the multi-mail code will be found in each transaction.

     
Note If you use this rule, you must also use the PageBatchStage1InitTerm, CreateRecordList, and WriteRCBWithPageCount rules.

Example

;BatchByPageCount;;MMField=MM_Field;

In this example, the system uses the multi-mail code defined in each transaction for batching purposes. The system checks the value in each transaction against that for transactions currently a VMMList, which is populated by CreateRecordList rule.

If the field has changed, the records are written to the recipient batch based on the total page count for all recipients for all form sets in the entire set of transactions.

     
Note Because the end of a multi-mail transaction set is not known until after the following transaction, each multi-mail transaction set (or each transaction, in the non multi-mail situation) is written out during processing of the following transaction.

See also