Use this form set level rule to identify form sets from a particular source and place those form sets into a special batch for review purposes. For instance, you can use this rule to identify policies from a particular agent, operator, or branch and place those policies into a special batch.
Note | You can insert several AssignToBatch rules in the base rules file (AFGJPB.JDT). All that return true will be placed in the appropriate recipient batch. |
Parameter |
Description |
Name |
The recipient batch name to which the transaction should be assigned. |
Delimiter |
An equal sign (=). This is required. |
Search mask |
One or more pairs of offsets and data (search criteria) in a comma delimited list. Here is an example: ;AssignToBatch;;Manual=1,Patch399,31,AssignToBatch; This example searches the records of each transaction for the string Patch399 at offset 1 and the string AssignToBatch at offset 31. If a match is found then this transaction will be assigned to the Manual batch. |
This table explains the order in which rules are assigned to recipient batches:
Batch |
Order of precedence |
Error |
If an error occurs that causes the batch assignment of the transaction. |
Manual |
If the POWType rule exists in any triggered section. |
Manual |
If the KickToWIP rule exists and its condition are met. |
xxxxxx |
AssignToBatch rule assignment if the rule exists and its search criteria is met. |
xxxxxx |
Base form set rules such as: IfRecipUsed, BatchingByPageCountINI, BatchingByRecipINI, and so on. |
Here is an excerpt from an AFGJOB.JDT file:
<Base Rules>
;RULStandardJobProc;;;
…
…
<Base Form Set Rules>
;RulStandardTransactionProc;;;
…
…
;AssignToBatch;;Manual=1,Patch399,31,GVM,190,AssignToBatch;
;IfRecipUsed;2;Batch1=Customer;
…
…
Any transaction that has a record that matches the search criteria (character strings: 'Patch399' at offset 1, 'GVM' at offset 31 and ' AssignToBatch' at offset 190) will be assigned to the Manual batch.
© Copyright 2014, Oracle and/or its affiliates. All rights reserved. Legal notices.