pub:defineformset
Differences
This shows you the differences between two versions of the page.
| Previous revision | |||
| — | pub:defineformset [2022/06/25 17:02] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | < | ||
| + | |||
| + | ====== Work With Form Sets ====== | ||
| + | |||
| + | A form set is a method to select a form or check application to process a particular input spool file page based on the content of that spool page. Form sets allow the user to toggle between seperately defined form applications, | ||
| + | |||
| + | To create or change a form set go to **menu IDOCS**, take option | ||
| + | |||
| + | < | ||
| + | 3. Work with Form Set Applications | ||
| + | </ | ||
| + | |||
| + | Use F6 to create or select an existing form set with option 1. | ||
| + | |||
| + | |||
| + | ===== Create or Change a Form Set ===== | ||
| + | |||
| + | This is the Form Set definition screen. | ||
| + | |||
| + | < | ||
| + | |||
| + | 5/ | ||
| + | | ||
| + | | ||
| + | Form Set Name: OFDEFEXTRA | ||
| + | | ||
| + | or *NONE to preempt processing | ||
| + | | ||
| + | Type And/ Form Relational | ||
| + | Prior (F/V) Or Application Op | ||
| + | ity | ||
| + | 1 | ||
| + | 2 | ||
| + | 3 | ||
| + | 4 | ||
| + | 5 | ||
| + | 6 | ||
| + | 7 | ||
| + | 8 | ||
| + | 9 | ||
| + | | ||
| + | | ||
| + | More... | ||
| + | | ||
| + | | ||
| + | </ | ||
| + | |||
| + | < | ||
| + | |||
| + | **Form Set Header Information** | ||
| + | |||
| + | * **Form Set Name**: Name of the form set definition. Do not use embedded blanks. This is the name specified in the manual merge or engine definition. | ||
| + | * **Description**: | ||
| + | * **Default Form**: Name of the form or check application to process the current spool file page if no other application is selected via the tests below. Note that *NONE is not an acceptable entry. | ||
| + | * **Burst Output**: Close the spool file and open a new one when the form or check selected changes. Y or N. See [[defineformset# | ||
| + | * **Relative Duplex**: For form sets containing all form applications, | ||
| + | < | ||
| + | |||
| + | **Form set Detail Information** | ||
| + | |||
| + | * **Priority**: | ||
| + | * **Type F/V**: Test a **F**ixed location in the spool file or **V**ariable location. | ||
| + | * **And/Or**: Used to create a multiline test. | ||
| + | * **Form Application**: | ||
| + | * **Relational Operator**: Test to use with the specified trigger value and the spool file text. **=** is almost always specified. | ||
| + | * **Trigger Value**: The text value to test for at the row/col location specified. The values can be blanks. | ||
| + | * **Begin Row/Col**: Beginning row / column to look in the spool file page for the trigger text. Not used if the test type is **V** (variable location). | ||
| + | * **End Col**: Ending column of the spool file text in which to look for the specified trigger text. | ||
| + | |||
| + | |||
| + | * **[[extrapages | F10=Extra Pages]]**: Add a last page macro i.e. Terms & Conditions after the last page of a form set print job (iDocs 6.91 4/30/2018 enhancement). | ||
| + | |||
| + | **In the example above**, the spool page is tested at row 5, column 15 for 10 characters that must match " | ||
| + | |||
| + | < | ||
| + | |||
| + | **When specifying a form Set to an engine** or performing a manual merge, ARCHECK, the form set name, is how the form set is referenced. | ||
| + | |||
| + | |||
| + | ===== Notes ===== | ||
| + | |||
| + | |||
| + | ==== Bursting ==== | ||
| + | |||
| + | If one is toggling between forms in the form set that have differences in the core page attributes, such as page size or page orientation, | ||
| + | |||
| + | < | ||
| + | |||
| + | ---- | ||
| + | < | ||
| + | |||