Use this section level rule to see if the FAP file is loaded, and if not, load the FAP file. You would typically use this rule if there is information needed in the FAP file that is not present in the DDT file, such as bar code information, or variable field rotation information.
| Note | This rule is not necessary if you are developing resources in Documaker Studio. This rule was created for and used in the older, legacy Documaker development tools. In a Studio environment, the system manages the functionality implemented via these rules automatically and offers improved performance. If you are importing a legacy MRL that includes this rule, Studio will ignore it. |
By default, the GenData program loads FAP files. If the LoadCordFAP option is turned on, the GenData program loads all FAP files. Avoid turning on this INI option as it slows performance. For example, make sure this option is set in the FSISYS.INI file as follows:
< RunMode >
LoadCordFAP = No
The GenData program should only write information about dynamic data, such as variables, into the NAFILE.DAT file from the DDT files. You can do this more efficiently by loading the DDT files instead of the FAP files.
There are, however, situations which require you to load FAP files. This rule and the TextMergeParagraph rule handle these situations. These rules let you load data for a single FAP file. Keep in mind that the TextMergeParagraph rule affects a single FAP file while the LoadCordFAP option affects all FAP files.
Since, in some cases, you must load FAP files, the system includes utilities which let you pre-compile FAP files and FXR files. By pre-compiling these files into CFA (FAP) and CFX (FXR) files, you can speed performance by eliminating parsing operations. The system is set up to use pre-compiled FAP and FXR files. You can see this setting in the FSISYS.INI file:
< RunMode >
To turn off this setting, change the Yes to No. For best results leave it set to Yes.
| Note | Using this rule slows performance. Use only as necessary. |
The CheckImageLoaded rule checks to see if the FAP file associated with the DDT file has already been loaded into memory. If the FAP file has not been loaded, the CheckImageLoaded rule loads it.
If you have a section (fap file) which contains four variable fields, each with a different rotation and the fields are not rotated when you run the GenPrint program, make sure you include the CheckImageLoaded rule. This rule is required in this situation.
If you are using the EAN (European Article Numbering) system to represent bar code variables and you are using the Move_It rule to map the bar code variable field to your data, include the CheckImageLoaded rule if your LoadCordFAP option is set to No.
© Copyright 2014, Oracle and/or its affiliates. All rights reserved. Legal notices.