Use this form set level rule to process the groups (Key1, Key2 combinations) that exist in the form set, as opposed to only a single set of keys specified in the TRNFILE.DAT file.
| Note | This rule replaces the LoadRcpTbl and RunSetRcpTbl rules. You can replace those two rules with this one even if you are not using multiple lines of business (Key2s) in your document. |
There are no parameters for this rule.
Place this rule after the BuildFormList rule in your AFGJOB.JDT file. Insert this rule after any import rule that might be used to create the starter document. For instance, insert the BuildFormList rule first, followed by your import rule, and then include the ProcessTriggers rule to add additional forms or assign recipient counts to the forms included via the import.
This rule does not trigger the Key2 (lines of business), however, if there are multiple lines of business defined at the point where triggering begins, this rule processes the triggers in each group. One way to define multiple groups is via an import file.
The ProcessTriggers rule was added to support multiple lines of business during the triggering process. Normally, the RunSetRcpTbl file only supports the main (Key1+Key2) setting identified with the transaction. The ProcessTriggers rule, however, will process all defined lines of business (each Key1+Key2 combination) at trigger time. This means if you use an import rule to create the transaction, you can have multiple lines of business in batch processing and trigger additional forms and sections. You can use the ProcessTriggers rule with both Documaker Studio and the legacy tools.
If you are only using the Studio implementation model, you may want to use the RunTriggers rule.
© Copyright 2014, Oracle and/or its affiliates. All rights reserved. Legal notices.