UnForm integrates with Addon via a simple modification to the config.bbx file.
After installing UnForm, verify it is operating by
testing the Version option: On Unix, run
UnForm -v; on Windows, run the
UnForm Information option from the Start menu. You should see a screen display
of UnForm version and copyright information.
Config.bbx Changes
Once you have verified that UnForm is operating, then you can modify the Addon
config.bbx file to add one or more UnForm printers. Detail is available in the
UnForm manual about this, but here are a couple of examples that may be of use:
Unix spooled alias
alias PUNF "|uf70c -f aon605.rul| lp -dhp -oraw 2>/dev/null" "UnForm Printer" CR,SPCOLS=132,SP=1B451B287331362E3636481B266B3247
Windows Laser Printer
alias PUNF PUNF.TXT "UnForm Printer" CR,LOCK=PUNF.LCK,O_CREATE,SPCOLS=132,SP=1B451B287331362E3636481B266B3247,EXECOFF="uf70c.exe -ix PUNF.TXT -o LPT1 -f aon605.rul"
Windows Print Driver
alias PUNF PUNF.TXT "UnForm Printer" CR,LOCK=PUNF.LCK,O_CREATE,SPCOLS=132,EXECOFF="uf70c.exe -ix PUNF.TXT -p winpvw -f aon605.rul"
Note that as you add printer aliases, you may need to increase the aliases=n line
as well.
If you will be customizing forms, you may also want to define a printer for cross-hair
pattern output. This is an UnForm option that simply prints the first page of Addon output
with a grid layout, which you can use to determine the exact locations of form elements.
To define a crosshair printer, just add a -x option to the UnForm command line
in the printer alias.
AddonSoftware Configuration Changes
If you add new aliases (instead of modifying existing ones), you will need to use the
printer configuration option from the Addon SYM menu to add each new printer alias to
the Addon printer configuration, and then add the printer to any user's printer list.
Note that any PCL codes you add to Addon's printer definitions are removed by UnForm
for any enhanced jobs, but passed through for non-enhanced jobs.
Multi-company Setup
Since the AddonSoftware programs don't print company name and address information on
forms, there are limited choices for installations with multiple companies. Here are
some methods to deal with this type of installation:
Use different rule files for each company
Copy the aon605.rul file to a unique name for each company, and edit the company
name information in each. Then create a unique printer alias line for each company,
referring to the proper rule file with the -f rule-file argument in
the UnForm command line. The user will need to select the correct printer for a
given company.
Use different substitution files for each company
Like rule files, you can associate a unique substitution file with a particular printer.
Again, train users to select a particular printer for a given company. Here are the
steps to accomplish this:
- Create as many copies of the subst file as there are companies. Edit these
files as follows:
company=Company Name
address1=Address line 1
address2=Address line 2
phones=Phone/Fax line
logo=logo file name
- Modify the rule file constants to use the substitution file parameters:
const COMP_NAME=@company
const COMP_ADDR1=@address1
const COMP_ADDR2=@address2
const COMP_PHONES=@phones
const COMP_LOGO=@logo
- Create additional alias lines in the config.bbx file, one per company, adding
the -s substitution-file argument to the UnForm command line.
Modify Addon to print company information
If you modify Addon to print company information on the forms, then you can change
the aon605.rul file to use that information. You can print the desired information
to the correct position, and optionally use an UnForm font command to change the
font for that information. Company logo file names can be printed to an available
position, and referred to as {get(col,row,length)} in the
image commands, then erased with an erase command.
Avoid changing the column or row position of existing data, as the rule sets are
already designed based upon that information.
UnForm and CirrusPrint are registered trademarks of SDSI. General and
MailCall are trademarks of SDSI. Other product names
used herein may be trademarks or registered trademarks of their respective
owners.
SDSI uses Google analytics and conversion tracking on some site pages.
Site design by ZiMDesign.
