Use this procedure to add blank or filler pages to a form set. You add these pages to make sure each physical printed page has a front and back. This lets you change a simplex form set or a form set which contains both simplex and duplex forms into a fully duplexed form set.
For instance, you can use this to make it easier to add OMR marks, which are often printed on the back, to simplex forms.
|
Parameter |
Description |
|
FAP |
Enter the name of the FAP file you want the system to use as a filler page. The default is blank. |
| Options | (Optional) Enter a string containing ‘T’, ‘S’ or both to indicate that this function should consider a tray change (‘T’), a staple state change (‘S’) or both (‘TS’) when deciding whether to add a blank or filler page. The default is to not consider either of these. |
Omit the path and extension of the FAP file.
One way to add blank pages is by using banner page processing in the GenPrint program. You can specify a DAL script which runs at the start of each transaction. The DAL script calls the AddBlankPages procedure.
This tells the system to convert each transaction into a fully duplexed form set with blank pages added as needed. To do this, you need these INI settings:
< Printer >
EnableTransBanner = TRUE
TransBannerBeginScript = PreBatch
< DALLibraries >
LIB = BANNER
Here is an example of the BANNER.DAL file:
BeginSub PreBatch
AddBlankPages()
EndSub
| Note | See the Documaker Administration Guide for more information on using banner processing. |
Here is a table which shows when blank pages will be added, based on the duplex setting of the two current pages and the duplex setting of the next page. Blank means a blank page will be added, As is means no blank page is needed and the form will be left as is.
If either of the tray or staple options is used and the tray and/or staple state changes then those conditions marked as “As is*” should be read as “Blank” (a blank page is needed).
|
If the current page is |
And the next page is |
|||||
|
Unknown |
Front |
Back |
None |
Short |
Rolling |
|
|
Unknown |
Blank |
Blank |
As is |
Blank |
Blank |
Blank |
|
None |
Blank |
Blank |
As is* |
Blank |
Blank |
Blank |
|
Front |
Blank |
Blank |
As is* |
Blank |
Blank |
As is* |
|
Short |
Blank |
Blank |
As is* |
Blank |
Blank |
As is* |
|
Rolling (Front) |
Blank |
Blank |
As is* |
Blank |
Blank |
As is* |
|
Back |
As is |
As is |
Blank |
As is |
As is |
As is |
|
Rolling (Back) |
As is |
As is |
Blank |
As is |
As is |
As is |
You can also add blank or filler pages using custom code or by using the DPRAddBlankPages function, which is available with Docupresentment. See Using the Documaker Bridge for more information on the DPRAddBlankPages function.
The API to call from custom code is:
DWORD _VMMAPI FAPAddBlankPages(
VMMHANDLE objectH, /* formset or form handle */
char FAR *sectionname)/* if NULL, "Blank Page" */
If the section name is NULL, a blank page is created when a filler page is needed. If the section name is not NULL, the section name is loaded when a filler page is needed. If you include a section name, include only the name of the FAP file—omit the path and file extension.
To specify that either tray and/or staple state changes should be considered then the following API should be used in custom code:
DWORD _VMMAPI FAPAddBlankPagesEx(
VMMHANDLE object, /* form set or form handle */
char FAR *sectionname, /* if NULL, “Blank Page” */
ULONG options) /* consider trays and/or staples */
In the above API ‘options’ should be either FAP_ABP_CONSIDER_TRAYS, FAP_ABP_CONSIDER_STAPLES or (FAP_ABP_CONSIDER_TRAYS | FAP_ABP_CONSIDER_STAPLES). If ‘options’ is 0 (no flags set) then FAPAddBlankPagesEx behaves exactly like FAPAddBlankPages.
© Copyright 2014, Oracle and/or its affiliates. All rights reserved. Legal notices.