RequiredFieldCheck

Use this form set level rule to have the GenData program send a transaction to WIP when it sees that a field designated as Required does not contain data.

If you include this rule in the AFGJOB.JDT file and the system finds a required field with no data...

• You receive a message (Warning 20030) that lists the fields that are missing data — or as many as will fit into the message.
• The GenData program sends the transaction to manual batch (WIP)
• You receive a message indicating the transaction has been assigned to a manual batch

You can see the results on the console when using Documaker Server or in the Output are when using Studio’s Test manager. Here is an example from Studio’s Output area, which shows the GenData Errors tab:

• The second warning line lists the fields missing data.
• The last warning line indicates the transaction is being sent to manual batch.

Keep in mind the RequiredFieldCheck rule ignores these fields:

• A field defined with the No User Edit attribute
• An X or Space field, because having no data is valid in this case
• A page number field or another print-time generated field that has a name that begins with a tilde (~)
• A Send Copy To field

Syntax

;RequiredFieldCheck;;;

There are no parameters for this rule.

Example

Place this rule in the AFGJOB.JDT file so it runs after the data is mapped but before batch assignments are made, similar to how you would place the IfRecipUsed rule.

<Base Form Set Rules>

;NoGenTrnTransactionProc;;;

;LoadExtractData;;;

;RunTriggers;;;

;UpdatePOLFile;;;

;WriteNaFile;;;

;BatchingByRecipINI;;;

;RequiredFieldCheck;;;

;PaginateAndPropogate;;;

© Copyright 2014, Oracle and/or its affiliates. All rights reserved. Legal notices.

Open table of contents

Open table of contents