Section - 4 : PDF417 IDS Rules

---

To implement a PDF417 bar code solution with IDS, you use the P417NYPDF417 rule. This rule handles both gathering the data and building the bar code. See Turning on Tracing for debugging information.

P417NyPDF417

Use this rule to create PDF417 bar codes in IDS implementations.

Syntax

P417NyPDF417 FontID, ECCLevel, BarCodeName

Parameter	Description
FontID	Specifies PDF417 font you want to use for this instance of the bar code. You can choose between two sizes of PDF417 bar codes fonts: 9 dots high by 12 dots wide and 12 dots high by 16 dots wide. While Oracle does not mandate the IDs you can use, it does provide an FXR file which contains the attributes for the two fonts. The IDs for these fonts are: 912 and 1216. Note: Prior to release 11.2, the PDF417_2.FXR and PDF417.FXR files were provided to licensed PDF417 customers. In release 11.2, the new REL112.FXR file contains the PDF417 font references found in the two PDF417 FXR files previously included in this product. See for more information on the included FXR files, see PDF417 FXR Files.
ECCLevel	Specifies the degree of error correction to be used in the bar code. The range is from zero (0) to eight (8). The default is four (4), which is the value recommended by the NYSID. For more information, see Sizing a PDF417 Bar Code.
BarCodeName (or BoxName)	Specifies a name for the bar code. The name typically is the name of a PDF417 barc ode variable field object. Older implementations that pre-date the built-in PDF417 bar code may specify the name of a box object located in the current section or simply a name for the bar code that is used internally when creating the bar code text.

The rule works by first searching for all of the bar code variable field objects with the name given in the BarCodeName parameter and applying the data to the bar codes.

Note: Older implementations that predate the built-in PDF417 bar code type may specify the name of a box object instead. In this case, the rules works by first searching for all the boxes with the name given in the BarCodeName parameter. It then builds the bar code by looking at the INI file, then the current section, and then the form set.

Once it makes the bar code, the rule populates it for all boxes in the section. When the rule finds a box that is in a different section, it remakes the bar code. So you can make each bar code different by putting them in different sections.

Add this rule under the ReqType control group in the DOCSERV.INI file as shown here.

< ReqType:SAMPCO >
function = dpros2->DPRLoadImportFile
function = p417w32->P417NyPDF417,1216,4,barcode
function = dpros2->DPRPrint

where SAMPCO is the group name. Be sure to add this rule after the DPRLoadImportFile rule.