Customizing Your Installation
The Client Installer now allows greater customization capability when creating and installing new CopiaFacts users. It uses templates to create user configuration files. Existing user configurations are not affected. If you wish to replace the settings for an existing user using the client installer, you should remove the user first using the client administrator program.
The installer uses the OWNER.INI and OWNER.UJP files located in the Default Client folder under the UserJobs folder located in the FaxFacts folder. You can modify either file using a plain text editor such as NotePad. You may also modify the OWNER.UJP file using CopiaEdit either directly or from within the client administrator program. You may also modify most of the settings in the default OWNER.INI file by selecting Default Client from the user list and editing the desired settings in the client administrator program. If a default OWNER.INI file exists, then the installer will copy the FF_CONSTANT and User Config Data sections, with the exception that the FaxFacts User Profile entry will be set to the OWNER.UJP file for the current user. The following entries are also copied from the User Personal Data section: SendAs, Department, Company, Address Line 1, Address Line 2, City, State, Zip Code, Country, Phone, Fax, and Office. The entire FFClient Special section is also copied. The presence of this special section forces the client to skip the initial setup the first time the user runs the client. When the user runs the client for the first time, the client will attempt to create address books for Outlook, Goldmine, and ACT if it detects that any of these products is installed. It also creates an OWNER.UJP for the user if necessary.
The client installer also copies entries from the default OWNER.UJP file to the user’s OWNER.UJP, provided the user does not already have an OWNER.UJP file. The $owner and $owner_name entries in the OWNER.UJP file are set to the CopiaFacts user name. Refer to the CopiaFacts reference manual for more information on the entries for OWNER.UJP files, which replace and augment user profiles.
Settings from the OWNER.UJP file will override many of the settings that the user makes using the CopiaFacts workstation client software. These settings are saved in the OWNER.INI file. The workstation client software does not modify the OWNER.UJP file. When a fax or email is sent from the workstation client the settings from OWNER.UJP are copied to the JOB00000.UJP file in the user’s NO_JTYPE folder. The workstation client software scans this file looking for commands that may override settings that the user has made. This allows administrators to determine the fax transmission options they want for each user. The client administrator program allows these settings to be applied to multiple users.
The commands from OWNER.UJP that are used to override client settings include the following:
|$fax_send_line||specified line to send fax on|
|$fs_template||commands replace all specified commands|
|$fax_filename||adds fax files to send|
The $fs_template commands in the OWNER.UJP file are effectively the same as commands placed in the FF_CONSTANT section. These must be valid commands for fax send (FS) transmission files. They will be added to FS files created by the workstation client and will replace comparable commands that the workstation client would normally generate. Variable definition ($var_def) commands named here will replace variable definition commands generated by the client, which have the same variable name. Specifying a $fax_tosend command here will override the fax priority user setting.
The phone account entries in the client settings will now update the $phone_account command in the OWNER.UJP file only if this command does not already exist. Using the $phone_account command allows phone account codes to be placed in the dial commands used by the fax server engine to place.
The workstation client will also add notification variables to the fax send (FS) transaction files whenever it detects the presence of notification processing. The variables generated include: FC_NOTIFY_OPTIONS, FC_NOTIFY_EMAIL, FC_NOTIFY_PAGER, FC_NOTIFY_FAX, and FC_NOTIFY_VOICE. These variables are described in the notification document. Notification options can be explicitly set from the workstation client by checking any of the notification options or implicitly set by the presence of post-process commands in the OWNER.UJP or OWNER.INI files. Only those infobox post-process commands that begin with notify_ or that specify FCPPOST.EXE as the post-process trigger positive notification detection. The post-process commands may be specified in the $post_process command or an $fs_template command containing a $fax_post-process command in the OWNER.UJP file. The $fax_post-process command may also be specified in the FF_CONSTANT section of the OWNER.INI file. These settings are maintained in the workstation client under the Setup task. The client workstation software first assembles an FS file using the options specified by the client. It then checks the OWNER.UJP file and adds or replaces commands from entries in the OWNER.UJP file. If any post-process or pre-process commands are detected in the OWNER.UJP file then all such commands generated by the client are removed and replaced by the commands from the OWNER.UJP file. Finally, the client workstation software generates any commands it needs for notification if notification is required. Notification is required if a notification post-process was detected. Valid post-process notification processes include fcppost.exe or any infobox process with an infobox name that starts with “notify_”. Case does not matter. Notification is also required if notification is checked in the client. When no post-process notification is specified in a $fax_post-process command and notification is required the client will generate the post-process command $fax_post-process FCPPOST.EXE internalNT if the FCPPost section exists in FFCFG.INI. Otherwise it will generate the post-process command $fax_post-process notify_smtp infoboxend.