What follows is a copy of the Readme file and Release Notes that shipped with the PureEdge Viewer version 6.5.
PureEdge(TM) Viewer version 6.5.0
Updated: June 20 2005
Copyright 2005 PureEdge Solutions Incorporated. All rights reserved.
Please read the licenses.txt file before using this software.
This document provides last-minute product information for PureEdge Viewer version 6.5.
Accessibility features, including hot keys, are summarized in the Viewer Help, which you can open by pressing ALT + F1 in the Viewer.
This version of PureEdge Viewer supports version 6.5 of XFDL(Extensible Forms Description Language).
1. About PureEdge Viewer
2. System Requirements
3. Installation Notes
3.1 Client-Side Installation
3.2 Server-Side Installation
4. What's New and Known Issues
5. XFDL Non-Conformities
6. Contacting PureEdge
6.1 Product Support for Registered Customers
6.2 Product Information
1. ABOUT PUREEDGE VIEWER
PureEdge Viewer allows you to view and complete PureEdge e-forms. The Viewer works as an extension to popular browsers, such as Internet Explorer, Netscape, or Mozilla, or as a stand alone application.
2. SYSTEM REQUIREMENTS
Supported Operating Systems:
Windows NT 4.0 sp6a
Windows 2000 sp2, sp3, sp4
Windows XP sp1, sp2
Internet Explorer 5.01 sp2 or later, 5.5 sp2, 6 sp1
Netscape Communicator 4.5 - 4.8
Netscape 6.1, 6.2, 7, 7.1, 7.2
Minimum System Requirements:
Processor: 500 MHz
RAM: 128 MB
Disk space: 40 MB
Resolution: 800 x 600 in 16-bit color
Supported 3rd Party Products (optional):
MSAA compliant screen readers, such as JAWS, Window-Eyes,
Entrust Desktop Solutions 6.0
Silanis ApproveIt Desktop 5.7.1
Interlink ePad Signature hardware with version 6.22
Topaz electronic signature hardware with version 3.61
Any signature capture device compliant with WinTab
Supported Terminal Services (optional):
Windows Server 2003 Terminal Services (must be set to more
than 8-bit color)
3. INSTALLATION NOTES
3.1 Client-Side Installation
3.1.1 Installing Under Windows NT 4.0/2000/XP
To install the Viewer under Windows NT 4.0/2000/XP, you must be logged onto Windows as an Administrator.
3.1.2 Installing for All User Profiles
Regardless of which profile you use to install the Viewer, the installer creates a copy of the Viewer that is available to all profiles.
3.1.3 Using the Viewer with Netscape and Mozilla
The Viewer works with Netscape Communicator 4.5 and 4.8, Netscape 6.1, 6.2, 7, 7.1, and 7.2, and Mozilla 1.7. When used with Netscape and Mozilla, the Viewer operates as a plugin. This requires that the file npmfv.dll be installed in the correct browser directory:
- For Netscape versions before 6.0, this is the Plugins directory:
- For Netscape version 6.x, this is the Components directory:
\Program Files\Netscape\Netscape 6\Components\
- For Netscape version 7.x, the plugin directory is different depending on whether you upgraded from Netscape 6 or installed a new copy of Netscape 7.x. If you upgraded from Netscape 6, the directory is:
\Program Files\Netscape\Netscape 6\Plugins\
If you installed a new copy of Netscape 7.x, the directory is:
- For Mozilla version 1.7, this is the plugins directory:
The installer will install this file automatically; however, if the installer cannot locate your browser you will have to copy the file manually.
The plugin file is always installed with the Viewer in the following location:
<Viewer Install Directory>\Plugin\npmfv.dll
You can copy it from this folder to the correct Netscape folder.
If you are using Netscape version 6.x, you must also register the plugin with Windows. To do this:
1. From the Start menu, select Run.
2. In the Open field, type command and press Enter.
3. At the command prompt, type:
c:\<Netscape installation folder>\regxpcom
"c:\<Netscape installation folder>\Components\
and press Enter.
Note: If you upgrade from an earlier version of Netscape to version 6.1 or later, we recommend that you uninstall and re-install the Viewer. This will minimize installation and setup problems.
3.1.4 Using the Viewer with JAWS 5.0
If you are using a release of JAWS 5.0 prior to build 813, JAWS will not work properly when the Viewer is embedded in a browser. To correct this problem, we recommend upgrading to a later build of JAWS. If that is not an option, you can install a special JAWS script that has been provided.
The JAWS script is installed with the Viewer in the following location:
<Installation Directory>/Viewer x.x/JAWS/
To enable JAWS through the script, copy all of the files to:
<JAWS Installation Directory>/JAWSxx/Settings/ENU/
3.1.5 Using Signature Pads
The Viewer will validate Signature Pad signatures without any additional hardware or software. However, to capture signatures using Signature Pads, you require the signature pad hardware and drivers, as well as the following .ifx files that are distributed as a separate add-on to the Viewer:
- tablet_wintab.ifx (for generic WinTab signing)
- tablet_interlink.ifx (for Interlink signing)
- tablet_topaz.ifx (for Topaz signing)
These .ifx files must be located in the following folder on your computer:
<Viewer installation directory>\API\<version>\System\
If you require any of these files, contact PureEdge Service and Support at support@PureEdge.com.
3.1.6 Using Silanis Signatures
To use Silanis signatures, you must install the Silanis ApproveIt Desktop software.
3.1.7 Rolling Back To Previous Versions
If you install a newer version of the Viewer on your computer, then decide that you want to roll back to an older version, you must first uninstall all versions of the Viewer from your computer. You can then install the version you want to use.
If you do not uninstall all versions first, you will encounter problems using the Viewer.
Furthermore, if you install Viewer 6.5 on a computer with multiple users, roll back to an earlier version of the Viewer, then reinstall Viewer 6.5, you may encounter problems running the Viewer. In this case, the Viewer will not run under any profiles that have previously run the version 6.5 Viewer (with the exception of the account that installed Viewer). If this has happened, you must locate and delete the "RunOnce" file for each user, as follows:
1. Locate the user's application data for the Viewer.
For example under Windows XP this is located at:
C:\Documents and Settings\<user>\Application Data\
2. Delete the RunOnce file in that folder.
The next time that user logs in, the Viewer will run properly.
3.1.8 Uninstalling Older Viewers
The Installer will attempt to uninstall older Viewers. This is intended to ensure that users do not run olderViewers, because they will reset the registry keys and prevent the current of the Viewer from working properly.
3.2 Server-Side Installation
3.2.1 Mapping XFDL Form File Extension
When you set up your server, make sure you map the XFDL form file extensions (.xfdl and .xfd) to the MIME type for XFDL forms (application/vnd.xfdl). You need to enter this map in the same file you enter all other MIME type maps. This file is different for each kind of web server. (For example, some products place this information in a configuration file, others place it in a MIME types file, and still others place it elsewhere.)
3.2.2 Proxy Servers
If your system uses a proxy server for Internet access, make sure you also set up the proxy server to allow the transmission of XFDL forms. The file extensions for XFDL forms is .xfdl and .xfd, and the MIME type is application/vnd.xfdl.
4. WHAT'S NEW AND KNOWN ISSUES
Be sure to read the 'ReleaseNotes_en_US.txt' file for complete information about new features, changes, and known issues.
5. XFDL NON-CONFORMITIES
PureEdge Viewer does NOT support the following:
1. Using the next option to direct the focus to a new page.
2. Justify for images in buttons and labels (images are centered).
3. A printpages option with a borderwidth setting greater than 1. If integers greater than 1 are used, the borderwidth around pages will remain at 1 pixel.
4. Bounding Box Around Items
In the Viewer, the size option in check and radio items changes the size of the bounding box around the check box and radio button, not the item's actual drawn size. To change the drawn size of a check or radio item, change the font size.
6. CONTACTING PureEdge
6.1 Product Support for Registered Customers
PureEdge Technical Support
6.2 Product Information
Release Notes - v6.5 (What's New)
1.1 Version 6.5.0
1.1.1 Support for XFDL 6.5
The Viewer now supports XFDL version 6.5. Note that the
namespace URL for XFDL version 6.5 is:
1.1.2 Support for Silanis Signatures
The Viewer now supports Silanis signatures. This includes
a No-Lock feature that is specific to Silanis signatures.
When a Silanis signature is set to No-Lock, the data that
is signed is not locked in the Viewer. In other words,
the user can change that data in the Viewer even though
it has already been signed. This will invalidate the
signature, but the changes can then be approved by a
second signature. For more information about these
signatures, refer to the PureEdge Viewer User's Manual.
No-Lock signatures are created by adding a "lock"
parameter to the signformat option for Silanis signatures.
For more information, refer to the XFDL Specification.
Before you can sign a form using a Silanis signature, you
must install the ApproveIt Desktop software from Silanis.
1.1.3 Support for No-Delete Signatures
The Viewer now supports No-Delete signatures. Any
signature type can be set to No-Delete, which means that
the signature cannot be deleted through the signature
dialog. For more information about No-Delete signatures,
refer to the PureEdge Viewer User's Manual.
No-Delete signatures are created by adding a "delete"
parameter to the signformat option. For more information,
refer to the XFDL Specification.
1.1.4 New Toolbar Functionality
The Viewer now has two save buttons in the toolbar: "Save
Form" and "Save As". The Save Form button now saves the
form to the current file without prompting the user. The
Save As button prompts the user for a filename and
location before saving the form.
Additionally, the following hotkey now triggers a Save
As: SHIFT + CTRL + S.
If you are using the ufv_settings option to control the
appearance of the save button, be aware that both save
buttons are now controlled by the "save" flag in the menu
setting. See the "Using Viewer Settings" document for
1.1.5 Printing Headers and Footers
The Viewer now supports printing multi-line headers and
footers. Additionally, the Viewer now scales headers and
footers more accurately when shrinking them to fit the
page (see section 3.8). For more information about using
headers and footers, refer to the Using Viewer Functions
1.1.6 Changed Settings for type Option
The Viewer now respects settings of "saveform" and
"saveas" for the type option. "saveform" saves the
form to the current file, while "saveas" prompts the
user for a filename and location before saving.
Note that if a form has been opened from the web,
"saveform" will prompt the user for a filename and
location, because these are not set until the form
has been saved for the first time.
The "save" setting, which behaves like saveas, has been
deprecated. As such, future versions of the Viewer may
drop support for it, and you should update your forms to
use the new settings.
1.1.7 File Extension
The Viewer now defaults to using the .xfdl file extension
rather than .xfd. This addresses some incompatabilities
with other software that also uses the .xfd extension.
When a form is opened, the Viewer will maintain the
original extension for the form. However, when the
Viewer writes temporary files, or if the Viewer saves a
file that does not already have an extension set, it
will default to .xfdl.
The Viewer still supports the .xfd extension, and will
continue to do so in the future.
1.1.8 Fixed Issue When Verifying Certificate Chains
When the Viewer checks a certificate chain, it normally
creates the chain by matching the Authority Key Identifier
of the certificate to the Subject Key Identifier of the
Issuer. However, in cases in which the issuing
certificate does not have a Subject Key Identifier but
the issued certificate has an Authority Key Identifier
(such as when a version1 certificate is used to create a
version3 certificate), this check was failing.
In these cases, the Viewer will now fall back on matching
certificate names to create the chain. This method is
already used when neither the certificate nor the issuer
has the proper extensions.
Rate this page:
Copyright and trademark information
IBM, the IBM logo and ibm.com are trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.