You are here: Adding Job and Form Set Rules > Using the Job Definition Table > GenData WIP Transaction Processing

GenData WIP Transaction Processing

GenData WIP Transaction Processing lets you process WIP transactions based on their status code. The transactions are created by one of these processes:

Executing the GenWIP program after the GenData program to process the transactions in the manual batch. Then using Documaker Desktop to:
- Manually view a transaction and update any required data. Then use the WIP, Save option to save the transaction with a status code such as: Approved or Accepted.
- Manually view a transaction and then use the WIP, Save option to save the transaction with a status code of Rejected.
- Manually view a transaction, update any required data, and save the transaction using the File, Complete, Batch Print option. This assigns a Batch Print status code to the transaction.
Creating a new transaction using Documaker Desktop and then using the WIP, Save or File, Complete, Batch Print option to save it with a status code such as Approved, Accepted, or Rejected.

You can then process these transactions as:

New transactions
Transactions appended to an existing MRL recipient batch, NewTrn, NA, and POL files created by a prior run of the GenData program

GenData WIP Transaction Processing creates new recipient batch, NewTrn, NA, and POL files which you can print, archive, or both using the GenPrint and/or GenArc programs.

To do this, you execute the GenData program using a simplified AFGJOB.JDT file that contains rules to replace the existing form set, section, and field rules. In addition, you must add two rules.

Here is a list of the rules used for GenData WIP Transaction Processing. All of these rules are required in the simplified AFGJOB.JDT file.

Rule	Description
MergeWIP	This job level rule initializes WIP Transaction Processing and specifies the status codes for the transactions added or appended to a newly-created NA and POL list.
WIPTransactions	This form set level rule replaces the RULStandardTransactionProc or NoGenTrnTransactionProc rule in the AFGJOB.JDT file and starts form set processing. It also identifies the status codes for transactions to be processed. The status codes specified in this rule’s parameters can include any or all of the status codes specified for the MergeWIP rule.
GVM2GVM	This form set rule to copies GVM variable data from the WIP.DBF file into GVM variables needed by the GenData program. Use the Trigger2WIP control group options to define GVM variable names
WIPImageProc	This section level rule replaces the RULStandardImageProc or StandardImageProc rule in the AFGJOB.JDT file and tells the GenData program to bypass section data processing.
WIPFieldProc	This field level rule replaces the RULStandardFieldProc or StandardFieldProc rule in the AFGJOB.JDT file and tells the GenData program to bypass field data processing.

Note

All WIP file transactions added to the transaction memory list by the MergeWIP rule are deleted from the WIP file after processing. You can remove specific transaction types, such as Rejected, by including the status code in the parameters for the MergeWIP rule and omitting it in the parameters for the WIPTransactions rule.