Application Integration Installation

The following sections contain specific information on setting up the integrated applications in SoftSolutions and on using the integration options. Any applicable menu modifications notes and error messages are also provided. Each of the integrated applications can be installed with the main SoftSolutions Installation program.

ODMA Integrations

To register SoftSolutions with ODMA, the following keys need to be set up in the REG.DAT file for Windows:

\

|

-ODMA

|

-SOFTSOL=[Path]\SSWODMA.DLL

|

-DEFAULT

The following line may be set in SOFTSOLW.INI (optional):

[Integration]

ODMNonProfiled=Yes

If this line is placed in SOFTSOLW.INI, it allows users to save and create documents without creating Profiles for them by displaying a "Non-Profiled Document" button in the SoftSolutions NEW dialog box. Selecting this button causes the application's SAVE AS dialog box to be displayed, instead of SoftSolutions'.

The application record for an ODMA-compliant application should be as follows (this is a WordPerfect for Windows example):

Field	Field Entry

App Description	WordPerfect 6.1 for Windows

App Code	WPWIN

Command Line	f:\wpwin\wpwin.exe ::odma\softsol\311\%d\%n\%v %win:int:wpwin61.exe

Create File	Y

Creation Template	^f:\wpwin\empty.wpd

Note in the Command Line above, ODMA uses a file ID for specifying documents, which ID has the following format:

::ODMA\SOFTSOL\[Internal SoftSolutions Version Number]\[Dataset ID]\[Document Number]\[Version Number]

Example command lines for a few other ODMA compliant applications:

Field	Field Entry

App Description	Quattro Pro 6.0 for Windows

App Code	QPW6

Command Line	f:\qpw\qpw.exe ::odma\softsol\311\%d\%n\%v %win:int

Create File	Y

Creation Template	^f:\qpwin\empty.wb2

Field	Field Entry

App Description	Presentations 3.0 for Windows

App Code	PRW3

Command Line	f:\prwin\prwin.exe ::odma\softsol\311\%d\%n\%v %win:int:prwin30.exe

Create File	Y

Creation Template	^f:\prwin\empty.wpg

Field	Field Entry

App Description	Informs Designer 4.1 for Windows

App Code	DESIGNER

Command Line	f:\inf41\fdwin.exe ::odma\softsol\311\%d\%n\%v %win:int:fdwin41.exe

Create File	Y

Creation Template	^f:\inf41\empty.wpf

SoftSolutions General Interface DLLs

To better integrate with some Windows applications, SoftSolutions has written application macros or DLL interfaces to modify certain menu options so that SoftSolutions is accessed directly when these options are selected. Specific information concerning the unique capabilities and options of each integrated application, their setup procedures, and error messages that may be applicable are contained in this manual. For general usage information on performing adds, changes, searches, etc., in SoftSolutions, refer to the User's Reference.

As of this printing, SoftSolutions has created integration modules for WordPerfect for Windows 5.1/5.2/6.0, Microsoft Word for Windows 2.0/6.0, Ami Pro 3.0, Lotus 1-2-3 1.1/4.0, Lotus Notes 3.0, Microsoft Excel 4.0/5.0, Reach WorkMAN 1.02, WordScan Plus 1.1/2.0, PaperWise ImageWise Software, Watermark Discovery Edition, CompareRite 4.x/5.0, and Novell MHS. The number of options displayed in the dialog boxes can be modified for some applications by making changes to the macros supplied by SoftSolutions. (See each application section for more information concerning which menu options are used. See the readme file, READDLL.TXT, on the diskette for information on SSAPPINT.DLL and on making modifications to the macros which use this DLL.)

The following general interface DLL integration files are shipped with SoftSolutions for Windows. Other than these general interface DLLs, only the integration files associated with the selected applications will be installed.

SIBILL.DLL	This DLL is used by the utility, SIWINBILL.EXE, and provides enhanced billing capabilities for all integrated applications of a Retrieve application type as defined in the SoftSolutions APPLICATIONS window. Using SIBILL allows SoftSolutions billing records to contain data and calculations based on keystrokes, and active time, and pages printed for the supported applications. SIBILL.DLL is placed in the SoftSolutions programs directory during installation and a copy is also placed in the Windows SYSTEM directory. (See "SIWINBIL" in the Utilities Reference for information on using this utility.)

SSINT.DLL	This DLL serves as an interface between SSAPPINT.DLL and SoftSolutions for Windows. SSINT.DLL is placed in the SoftSolutions SYSTEM directory, a subdirectory of the SoftSolutions programs directory, during installation, and a copy is also placed in the Windows SYSTEM directory.

SSAPPINT.DLL	This DLL serves as an interface between SSINT.DLL and all other applications that are integrated with SoftSolutions. It is responsible for displayed dialog boxes for the integrated options (File|Open, File|New, etc.), and tracks which SoftSolutions documents are open and which applications are using those documents. SSAPPINT.DLL is placed in the SoftSolutions SYSTEM directory, a subdirectory of the SoftSolutions programs directory, during installation, and a copy is also placed in the Windows SYSTEM directory.

Specific Application Integration Files

The following integration files are shipped with SoftSolutions for Windows. Other than the general interface DLLs, only the integration files associated with the applications you select will be installed.

Ami Pro for Windows 3.0

AMIPRO.INI	This file is modified by the integration install program when installing Ami Pro for Windows. The line AutoMacroLoad= will be modified to have the following information:

AutoMacroLoad=[Ami Pro Macros Directory]\SSAIAP3.smm!DoMenuChange RecFiles=0

This file is found in the Windows programs directory (e.g., C:\WINDOWS ).

CUSTOM.SMM	This file is an Ami Pro macro that invokes the CUSTOMDLGBOX routine in SSAPPINT.DLL.

INTONOFF.SMM	This macro turns the Ami Pro integration ON and OFF.

SSAIAP3.SMM	This file is an Ami Pro macros document that contains all of the macros used in the integration with SoftSolutions for Ami Pro 3.0. It is placed in the Ami Pro 3.0 programs directory (e.g., C:\APPS\AMIPRO ).

SSAIAP3M.SMM	Ami Pro integration file.

SSAIAP3N.SMM	Contains functions used for automatic document and footer creation.

SSAIAP3X.SMM	Ami Pro integration file.

Installation

1.	Perform an installation of the Integrations as described in the SoftSolutions Installation Guide, choosing Ami Pro 3.0 to be installed.

2.	Once the installation process has begun, the following information must be provided for the Ami Pro 3.0 integration files:

a.	The drive and path to the Ami Pro 3.0 programs directory, such as F:\APPS\AMIPRO30.

b.	The drive and path to the Ami Pro 3.0 macros directory, such as F:\APPS\AMIPRO30\MACROS.

c.	The drive and path to the Ami Pro 3.0 styles directory, such as F:\APPS\AMIPRO30\STYLES.

3.	The installation program automatically performs the following:

a.	The following files are copied into the SoftSolutions INT directory, a subdirectory of the SoftSolutions programs directory:

SSAIAP3.SMM

INTONOFF.SMM

SSAIAP3M.SMM

SSAIAP3X.SMM

SSAIAP3N.SMM

CUSTOM.SMM

FDEFAULT.SAM

b.	The following application record is created in the APPLICATIONS window:

Field Name	Field Entry

Code	AMIPRO30

Description	Ami Pro 3.0 for Windows

App Type	R

Index Text?	Y

Create File?	N

Echo Docu?	N

Ext	SAM

Command line	[Ami Pro Programs Directory]\amipro.exe %win:int

Creation Template	(no entry—field is left blank)

Preview Command	%ossvieww.exe %r[%sc %p%f]

Location Segment	AmiPro30

The command line used to open Ami Pro should not be a DDE command line. The default command line which calls AMIPRO.EXE opens documents in Ami Pro while at the DOCUMENT PROFILE window.

If the users wants the Create File flag set to Yes, the Creation Template field should contain a blank Ami Pro document on which to base the new document (e.g., ^EMPTY.SAM ). This will allow the user to create a new Profile and then press the Retrieve option and SoftSolutions will start Ami Pro and load in the document.

It is recommended, however, that the Create File flag be set to No and that all documents are created through the File|New menu option after the user has already started both SoftSolutions and Ami Pro.

4.	The workstation installation program automatically performs the following:

a.	The following files are copied from the SoftSolutions INT directory to the Ami Pro macros directory:

SSAIAP3.SMM

SSAIAP3M.SMM

SSAIAP3X.SMM

SSAIAP3N.SMM

i.	The following file is copied from the SoftSolutions INT directory to the Ami Pro styles directory:

FDEFAULT.SAM

ii.	The AMIPRO.INI text file found in the main Windows directory is modified as follows:

(a)	The following key is added to the [AmiPro] section:

AutoMacroLoad=1,[Ami Pro Macros
Directory]\SSAIAP3.SMM!DoMenuChange

(b)	The key, RecFiles, is set to :

recfiles=0

5.	When the installation is finished, edit the SOFTSOLW.INI text file found in the main Windows directory as follows:

i.	If necessary, add [AppTable] as a section.

ii.	Add the following key to the [AppTable] section:

[Path to Ami Pro programs directory]\AMIPRO.EXE=[Application Code],^O

For example:

F:\APPS\AMIPRO30\AMIPRO.EXE=AMIPRO30,^O

cc:Mail

The following provides information on the integration with cc:Mail 2.x from Lotus Development Corporation in SoftSolutions 3.x and 4.0 for Windows. The integration will also work with cc:Mail 1.x, but with slightly different steps required for installation and use. Contact the SoftSolutions Support Center if you wish to integrate SoftSolutions with cc:Mail 1.x.

cc:Mail permits sending attachments of SoftSolutions documents by linking or embbeding these files with its messages.

Linking:	This method is faster and more efficient than embedding. The sender of an attachment that is linked must have SoftSolutions running, and the recipient is required to have access to SoftSolutions and the dataset containing the linked document. The actual document is accessed by the recipient upon viewing or opening.

Embedding:	This method is slower, and creates a much larger message file. The sender of an attachment that is embedded must have SoftSolutions running, but the recipient does not require access to SoftSolutions, nor the dataset containing the original of the embedded document. A copy of the original document is attached to the message for viewing or opening.

NOTE

cc:Mail's linking or embedding does not perform OLE linking or embedding. A cc:Mail "link" simply passes the Document Number and Dataset ID, while an "embed" copies the entire document to pass as the attachment. Neither option uses Windows OLE in any way.

Installation

To install cc:Mail, do the following:

1.	Copy SSMAIL.EXE from the diskette to the SoftSolutions programs directory.

2.	Copy TEMPLATE.SSM from the diskette to each user's cc:Mail users directory.

NOTE

The WIN.INI file contains a cc:Mail section that has a username line indicating the user's cc:Mail users directory.

3.	Using a text editor, edit each user's WIN.INI file. In the [Extensions] section, add the following (if necessary):

SSM=D:\[Path]\SSMAIL.EXE ^.SSM

where D:\[Path] is the SoftSolutions programs directory where SSMAIL.EXE was placed in Step 1.

CompareRite 4.x

The following provides information on the integration with CompareRite 4.x by Jurisoft in WordPerfect 5.2 for Windows.

Installation

1.	If an installation of the WordPerfect 5.2 for Windows integration files is not being performed, replace SSAPPINT.DLL in the Windows SYSTEM directory with the updated file found on the diskette.

2.	If an installation of the WordPerfect 5.2 for Windows integration files is not being performed, replace SIWP.DLL with the updated file found on the diskette. This file is located in the directory specified in the WPC.INI file.

3.	Using the Microsoft Windows PIF Editor, create a PIF file with the following components:

Program Filename

•	The full path and filename to COMPARE.EXE, such as F:\COMPRITE\COMPARE.EXE.

Optional Parameters

•	Simply enter %1 %2 %3. SoftSolutions replaces %1 and %2 with the files to be compared. %3 will be replaced with the output filename.

Startup Directory

•	The directory in which COMPARE.EXE is located, such as F:\COMPRITE.

4.	Using any text editor, edit the SOFTSOLW.INI file to indicate the location of the batch file. In the [WP Integration] section, add the following line:

DOCCOMPARE=[Path and filename to the PIF file]

CompareRite 5.0

The following provides information on the integration with CompareRite 5.0 by Jurisoft in WordPerfect 6.0 for Windows. (CompareRite 4.0 integration does not work with WordPerfect 6.0 for Windows files.)

Installation

1.	If an installation of the WordPerfect 6.0 for Windows integration files is not being performed, do the following:

a.	Replace SSAPPINT.DLL in the Windows SYSTEM directory with the updated file found on the diskette.

b.	Replace SIWP6.DLL with the updated file found on the diskette. (SIWP.DLL is located in the directory specified in the WPC.INI file.)

2.	Using any text editor, edit the SOFTSOLW.INI file to indicate the location of the batch file. In the [WPWIN 6.0] section, add the following line:

CompareRite=[Path to CompareRite]\COMPARE.EXE

where [Path to CompareRite] is the full path (including drive letter) to the CompareRite 5.0 directory.

Lotus 1-2-3 for Windows 1.1, Release 4

SILOTUS.ADW	This DLL changes the actions of certain menu commands in Lotus 1-2-3 for Windows, version 1.1. As menu functions are "trapped" by this DLL, functions are called from the SSAPPINT.DLL to allow a user to access SoftSolutions directly from Lotus 1-2-3. This DLL is placed in the Lotus programs directory as indicated by the user during installation (e.g., C:\APPS\123W).

SILOTUS4.ADW	This DLL changes the actions of certain menu commands in Lotus 1-2-3 for Windows, Release 4. As menu functions are "trapped" by this DLL, functions are called from the SSAPPINT.DLL to allow a user to access SoftSolutions directly from Lotus 1-2-3. This DLL is placed in the ADDINS directory, a subdirectory of the Lotus programs directory (e.g., c:\apps\123r4w\programs\addins).

Installation for Version 1.1

1.	Perform an installation of the Integrations as described in the SoftSolutions Installation Guide, choosing Lotus 1-2-3 for Windows 1.1 to be installed.

2.	Once the installation process has begun, provide the drive and path to the Lotus 1-2-3 programs directory, such as F:\APPS\123W.

3.	The installation program automatically performs the following:

a.	The SILOTUS.ADW file is copied into the SoftSolutions INT directory, a subdirectory of the SoftSolutions programs directory.

b.	The following application record is created in the APPLICATIONS window:

Field Name	Field Entry

Code	123WIN

Description	Lotus 123 for Windows

App Type	R

Index Text?	Y

Create File?	N

Echo Docu?	N

Ext	WK3

Command line	[Lotus Programs Directory]\123w.exe %win:int:main123w.exe

Creation Template	(no entry—field is left blank)

Preview Command	%ossvieww.exe %r[%sc %p%f]

Location Segment	123win

4.	The workstation installation program automatically performs the following:

a.	The following file is copied from the SoftSolutions INT directory to the Lotus programs directory:

SILOTUS.ADW

b.	The 123W.INI text file found in the main Windows directory is modified by adding the following key to the [AutoLoad AddIns] section:

SILOTUS.ADW=[Lotus Programs Directory]\,0,0,0

5.	When the installation is finished, edit the SOFTSOLW.INI text file found in the main Windows directory as follows:

a.	If necessary, add [AppTable] as a section.

b.	Add the following key to the [AppTable] section:

[Path to Lotus programs directory]\MAIN123W.EXE=[Application Code],%FO

For example:

F:\APPS\123W\MAIN123W.EXE=123WIN,%FO

Installation for Release 4

1.	Perform an installation of the Integrations as described in the SoftSolutions Installation Guide, choosing Lotus 1-2-3 for Windows, Release 4 to be installed.

2.	Once the installation process has begun, provide the drive and path to the Lotus 1-2-3 programs directory, such as F:\APPS\123R4W\PROGRAMS.

3.	The installation program automatically performs the following:

a.	The SILOTUS4.ADW file is copied into the SoftSolutions INT directory, a subdirectory of the SoftSolutions programs directory.

b.	The following application record is created in the APPLICATIONS window:

Field Name	Field Entry

Code	1234W

Description	Lotus 123 Rel 4 for Windows

App Type	R

Index Text?	Y

Create File?	N

Echo Docu?	N

Ext	WK4

Command line	[Lotus Programs Directory]\123w.exe %win:int:main123w.exe

Creation Template	(no entry—field is left blank)

Preview Command	%ossvieww.exe %r[%sc %p%f]

Location Segment	1234w

4.	The workstation installation program automatically performs the following:

a.	The following file is copied from the SoftSolutions INT directory to the ADDINS subdirectory of the Lotus programs directory:

SILOTUS4.ADW

b.	The 123R4.INI text file found in the main Windows directory is modified as follows:

i.	The following key is added to the [AutoLoad AddIns] section:

SILOTUS4.ADW=[Lotus Programs Directory]\ADDINS\,0,0,0

ii.	The key, RecFiles, is set to 0.

recfiles=

iii.	The key, Auto_Save, is set to 0.

auto_save=

5.	When the installation is finished, edit the SOFTSOLW.INI text file found in the main Windows directory as follows:

a.	If necessary, add [AppTable] as a section.

b.	Add the following key to the [AppTable] section:

[Path to Lotus programs directory]\MAIN123W.EXE=[Application Code],%FO

For example:

F:\APPS\123R4W\PROGRAMS\MAIN123W.EXE=1234W,%FO

Lotus Notes 3.0

SSNOTES.EXE	This is the main integration executable. It is invoked by Notes every time an integration function is chosen. It transfers data back and forth between Notes and SoftSolutions using the Notes and SoftSolutions APIs.

SSNOTES.NTF	This file is a Notes database template. It holds form definitions and views that make use of the SoftSolutions integration. Notes system administrators may create databases for external documents based on this template or they may copy any or all of the forms and views from this database into any other database which will hold references to external documents. These forms and views are samples. They may be modified or customized to fit users' needs as discussed later in this chapter.

SS2NOTES.EXE	This utility can be used to copy Profiles from an existing SoftSolutions dataset into a Notes database. It can copy all of the Profiles in a dataset or a subset of the Profiles returned by a SoftSolutions Profile or full-text search. This utility will be installed as a launch application in the current dataset when the Notes integration is installed.

SYNCNOTE.EXE	This utility can be run at any time to make sure that all of the Profile Notes in a Notes database properly reflect the field values from the SoftSolutions Profiles which they represent. It is necessary to run this utility periodically if some users are using SoftSolutions without Lotus Notes. Without it, the Profile Notes would not reflect changes made to the SoftSolutions Profiles by users outside of Notes.

Installation

1.	Perform a complete installation of SoftSolutions and all the desired application integrations, including Lotus Notes 3.0.

2.	Once the installation process has begun, the following information must be provided for the Lotus Notes integration files.

a.	The drive and path to the Lotus Notes programs directory, such as F:\NOTES.

3.	The installation program automatically performs the following actions:

a.	The following files are copied into the SoftSolutions INT directory, a subdirectory of the SoftSolutions programs directory:

SSNOTES.EXE

SS2NOTES.EXE

SYNCNOTE.EXE

b.	SSNOTES.NTF is copied directly to the Lotus Notes programs directory.

c.	The following application record is created in the APPLICATIONS window:

Field Name	Field Entry

Code	SS2NOTES

Description	Copy Profiles to Lotus Notes

App Type	L

Index Text?	N

Create File?	N

Echo Docu?	N

Ext	(no entry—field is left blank)

Command Line	ss2notes.exe /data=%b /strdir=%o /delta %r[%sr]

Creation Template	(no entry—field is left blank)

Preview Command	(no entry—field is left blank)

Location Segment	(no entry—field is left blank)

This launch application invokes the SS2NOTES utility, allowing users to copy any group of SoftSolutions Profiles (as specified by a search) from a SoftSolutions dataset to a Notes database.

4.	The following actions will be performed by the workstation installation. Workstation installation occurs immediately for the user who is performing the original installation. For all other users, it occurs after their initial login to SoftSolutions.

a.	The following files will be copied from the INT directory to the Lotus Notes programs directory.

SSNOTES.EXE

SS2NOTES.EXE

SYNCNOTE.EXE

NOTE

The database template file SSNOTES.NTF is copied directly to the Notes program directory of the user who performs the original install. It is not copied for each individual user during workstation install because this might result in data loss if the Notes programs directory is shared by multiple users. It is typically not necessary for each user to have a copy of the database template. The Notes administrator uses the database template to create databases on the Notes server where external documents may be stored.

5.	After the install program has completed its work the system administrator must perform the following steps:

a.	The Notes programs directory must be on the search path for all users. If it is not, Notes will be unable to invoke SSNOTES.EXE. The NOTES.INI file for each user must also be stored in a directory that is on the search path.

b.	The database template file, SSNOTES.NTF, should be copied to the Notes data directory on the Notes server, if a remote server is being used. The system administrator should then use the template to create new Notes databases, which holds external document Profiles. Alternatively, the administrator could copy forms and views from the template to existing Notes databases where external document Profiles need to be stored.

The forms and views in this template are samples. The system administrator may modify them to meet users' needs as long as the minimum requirements mentioned later in this section are met. (See "Modifying the SS Profile Form Definition" for details.)

c.	SoftSolutions must be completely installed and configured before the Lotus Notes integration will work. If any of the custom fields on the SoftSolutions Profile are set to a type other than alphanumeric, the corresponding custom fields in the SS Profile form definition may need to have their data type changed, as well. (See the description of the Custom1 − Custom16 fields below.)

d.	If a SoftSolutions dataset with documents already exists, the Profiles for these documents may be copied into one or more Lotus Notes databases using the SS2NOTES utility which is documented later in this section.

Microsoft Excel for Windows 4.0, 5.0

SSAIXL4.XLA	This file is an Excel 4.0 macro sheet that contains all of the macros used in the integration with SoftSolutions. It is placed in the XLSTART directory, a subdirectory of the Excel 4.0 programs directory (e.g., C:\APPS\EXCEL\XLSTART ).

The following macros are imbedded in the SSAIXL4.XLA file.	IntOnOff	Used to toggle the integration with SoftSolutions for Windows ON or OFF.

SIMenuChange	Modifies the Excel menus to call the integration macros.

SIExcelOpen	Runs the SSAPPINT function SIFILEOPEN.

SIFinishOpen	Opens a document returned from SIFILEOPEN.

SIExcelClose	Runs the SSAPPINT function SIFILECLOSE.

SIExcelNew	Runs the SSAPPINT function SIFILENEW.

SIFinishNew	Creates a new document from the name returned by SIFILENEW.

SIFileDelete	Runs the SSAPPINT function SIFILEDELETE.

SIExcelExit	Runs the macro SIExcelClose for all of the open documents and then exits Excel.

SIExcelSave	If the current document does not have a name, the macro SIExcelSaveAs is run; otherwise, a normal save is done.

SIExcelClear	Runs the SSAPPINT function SICLEARDOCTEMP.

SIExcelSaveAs	Runs the SSAPPINT function SIFILESAVEAS.

SIFinishSaveAs	Saves the current document as the name returned from the SIFILESAVEAS function.

SSAIXL5.XLA	This file is a compiled Excel 5.0 macro workbook that contains all of the macros used in the integration with SoftSolutions. It is placed in the programs directory and the .INI file is updated with:

[Microsoft Excel]

Open=c:\apps\excel\ssaixl5.xla

The following macros are imbedded in the SSAIXL5.XLA workbook file.:

1. Functions/Definitions	All DLL functions that are accessed are declared on this sheet. Several constants are also defined here.

2. Startup Macro	Modifies the menus and toolbars when Excel 5.0 starts so that they will access the proper integration macros.

3. Open−New Engine	Handles the opening and creation of documents. Called by many other macros that need to open or create documents.

4. Open Macro	Macro run when File|Open is selected.

5. New Macro	Macro run when File|New is selected.

6. NewListDialog	A dialog definition that displays a list of document types that can be used when creating new documents.

7. Summary Info Macro	Macro run when File|Summary Info is selected.

8. Find File Macro	Macro run when File|Find File is selected.

9. Format Macro	Macro used to determine the format of the current document.

10. Close Macro	Macro run when File|Close is selected.

11. Exit Macro	Macro run when File|Exit is selected.

12. Save As Macro	Macro run when File|Save As is selected.

13. Save Macro	Macro run when File|Save is selected.

14. Set Window Title	Macro used to put Profile information on the document title bars.

SSAIXL5.XLS	This file contains the same information as the SSAIXL5.XLA workbook, but in an uncompiled format. This makes it possible to edit and make changes, as needed, to the workbook. It is placed in the Excel 5.0 programs directory.

Installation For Excel 4.0

1.	Perform an installation of the Integrations as described in the SoftSolutions Installation Guide, choosing Microsoft Excel 4.0 to be installed.

2.	Once the installation process has begun, the drive and path to the Excel 4.0 programs directory, such as F:\APPS\EXCEL40, must be provided for the Excel 4.0 integration files.

3.	The installation program automatically performs the following:

a.	The following files are copied into the SoftSolutions INT directory, a subdirectory of the SoftSolutions programs directory:

SSAIXL4.XLA

SIWB.XLS

b.	The following application record is created in the APPLICATIONS window:

Field Name	Field Entry

Code	EXCEL40

Description	Excel 4.0 for Windows

App Type	R

Index Text?	Y

Create File?	Y

Echo Docu?	N

Ext	XLS

Command line	[Excel Programs Directory]\excel.exe %win:int

Creation Template	[Excel Programs Directory]\empty.xls

Preview Command	%ossvieww.exe %r[%sc %p%f]

Location Segment	Excel40

4.	The workstation installation program automatically performs the following:

a.	Renames SSAIXL4.XLA found in the XLSTART subdirectory of the Excel programs directory to SSAIXL4.BAK.

b.	The following file is copied from the SoftSolutions INT directory to the XLSTART subdirectory of the Excel programs directory:

SSAIXL4.XLA

c.	The following file is copied from the SoftSolutions INT directory to the Excel programs directory:

SIWB.XLS

5.	When the installation is finished, edit the SOFTSOLW.INI text file found in the main Windows directory as follows:

a.	If necessary, add [AppTable] as a section.

b.	Add the following key to the [AppTable] section:

[Path to Excel programs directory]\EXCEL.EXE=[Application Code],%FO

For example:

F:\APPS\EXCEL40\EXCEL.EXE=EXCEL40,%FO

Installation for Excel 5.0

1.	Perform an installation of the Integrations as described in the SoftSolutions Installation Guide, choosing Microsoft Excel 5.0 to be installed.

2.	Once the installation process has begun, the drive and path to the Excel 5.0 programs directory, such as F:\APPS\EXCEL50, must be provided for the Excel 5.0 integration files:

3.	The installation program automatically performs the following:

a.	The following files are copied into the SoftSolutions INT directory, a subdirectory of the SoftSolutions programs directory:

SSAIXL5.XLA

SSAIXL5.XLS

b.	The following application record is created in the APPLICATIONS window:

Field Name	Field Entry

Code	EXCEL50

Description	Excel 5.0 for Windows

App Type	R

Index Text?	Y

Create File?	N

Echo Docu?	N

Ext	XLS

Command line	[Excel Programs Directory]\excel.exe %win:int

Creation Template	(no entry—field is left blank)

Preview Command	%ossvieww.exe %r[%sc %p%f]

Location Segment	Excel50

4.	The workstation installation program automatically performs the following:

a.	Renames SSAIXL5.XLA found in the Excel programs directory to SSAIXL5.BAK.

b.	The following file is copied from the SoftSolutions INT directory to the Excel programs directory:

SSAIXL5.XLA

c.	The following file is copied from the SoftSolutions INT directory to the Excel programs directory:

SSAIXL5.XLS

5.	When the installation is finished, edit the SOFTSOLW.INI text file found in the main Windows directory as follows:

a.	If necessary, add [AppTable] as a section.

b.	Add the following key to the [AppTable] section:

[Path to Excel programs directory]\EXCEL.EXE=[Application Code],%FO

Example:

F:\APPS\EXCEL50\EXCEL.EXE=EXCEL50,%FO

Microsoft Word for Windows 2.0, 6.0

2NORM31A.DOT	These template files contain all of the Word for Windows macros

SSNORM.DOT	that are used in the integration with SoftSolutions for Windows. This file is placed in the Word for Windows programs directory (e.g., C:\APPS\WINWORD) for Word for Windows 2.0 and in the template directory for Word for Windows 6.0.

The following macros are embedded in 2NORM31A.DOT or SSNORM.DOT:

AutoExec	Runs each time Word is opened. Checks for AutoSave files and checks to see if the most current version of integrations has been installed.

AutoOpen	Runs each time a document is opened. (Word for Windows 2.0 only.)

DocClose	Closes the active window.

File1	Displays a message when the user selects the first file in the Last Opened Files List.

File2	Displays a message when the user selects the second file in the Last Opened Files List.

File3	Displays a message when the user selects the third file in the Last Opened Files List.

File4	Displays a message when the user selects the fourth file in the Last Opened Files List.

FileClose	Runs the SSAPPINT function SIFILECLOSE.

FileEditDataFile	Opens a print merge data file. (Word for Windows 2.0 only.)

FileExit	Runs the macro FileClose on all of the open documents and then closes the application.

FileFind	Runs the SSAPPINT function SIFILEOPEN.

FileNew	Runs the SSAPPINT function SIFILENEW.

FileOpen	Runs the SSAPPINT function SIFILEOPEN.

FilePrint	Prints active document and updates SoftSolutions billing information.

FilePrintDefault	Prints active document using current defaults and updates billing information.

FilePrintMerge	Combines files to produce form letters. (Word for Windows 2.0 only.)

FilePrintMergeCheck	Checks for errors in a print merge document. (Word for Windows 2.0 only.)

FilePrintMergeReset	Resets a print merge main document to a normal Word document. (Word for Windows 2.0 only.)

FilePrintMergeSetup	Prepares a main document for a print merge. (Word for Windows 2.0 only.)

FilePrintMergeToDoc	Collects the results of the print merge in a document. (Word for Windows 2.0 only.)

FileSave	Runs the SSAPPINT function SIFILESAVE.

FileSaveAll	If a document does not have a "name" it runs the FileSaveAs macro; otherwise, it just saves all of the open documents.

FileSaveAs	Runs the SSAPPINT function SIFILESAVEAS.

FileSummaryInfo	Runs the SSAPPINT function SIACTIVATESS.

InsertFile	Runs the SSAPPINT function SIFILEOPEN in the "Open only" mode.

InsertPicture	Inserts a picture from a graphic file.

InstallSS	SoftSolutions integrations installation macro.

IntOnOff	If the integration is turned ON, this macro turns it OFF. If the integration is OFF, this macro turns it ON.

MailMergeHelper	Dialog box that is used to create mail merge documents. (Word for Windows 6.0 only)

NewDocMac	Creates a new document based on the SoftSolutions Document Type.

PrintMerge	SoftSolutions File|Print|Merge integration macro. (Word for Windows 2.0 only.)

SetHandle	Determines the handle of the active window.

SSWMain	SoftSolutions integration macros.

SSWMain2	SoftSolutions integration macros.

ToolsCompareVersions	Compares the active document with an earlier version. (Word for Windows 2.0 only.)

ToolsRevisions	Compares the active document with an earlier version. (Word for Windows 6.0 only.)

Win1 - Win9	Activates appropriate window.

WindowNewWindow	Opens another window for the active document.

TNT2.DOT	This template document is used by the Word for Windows macros

TNT6.DOT	when creating new documents. 2NORM31A.DOT/SSNORM.DOT has an internal macro named NEWDOCMAC that determines a Profile's Document Type and opens a template document based on this information. This template file is an example of a Trial Notice Document Type and contains Word for Windows insertion fields that prompt the user to enter information as the document is created. This document is placed in the Word for Windows programs directory (e.g., C:\APPS\WINWORD) for Word for Windows 2.0 and in the template directory for Word for Windows 6.0.

SUMM2.DOT	This template document is used by the Word for Windows macros

SUMM6.DOT	when creating new documents. 2NORM31A.DOT/SSNORM.DOT has an internal macro named NEWDOCMAC that determines a Profile's Document Type and opens a template document based on this information. This template file is an example of a "Summons" Document Type and contains Word for Windows insertion fields that prompt the user to enter information as the document is created. This document is placed in the Word for Windows programs directory (e.g., C:\APPS\WINWORD) for Word for Windows 2.0 and in the template directory for Word for Windows 6.0.

FOOTER2.DOC	This document serves as a template used by an internal Word for

FOOTER6.DOC	Windows macro when creating a footer. This is a Word for Windows document that should be formatted to the user's needs. It can contain different fonts, even graphics—anything that a regular Word document can hold. It should have SoftSolutions Command Line parameters where the user desires to have information inserted from the Profile. For example, to get the document number, %N should be typed where the document number from the Profile should appear. Each variable used must be followed by another % symbol. By renaming this document, you can create types other than footers. By default, this document is placed in the Word for Windows programs directory (e.g., C:\APPS\WINWORD) for Word for Windows 2.0 and in the template directory for Word for Windows 6.0.

Installation for Word 2.0

1.	Perform an installation of the Application Integration Files as described in the SoftSolutions Installation Guide, choosing Word for Windows 2.0 to be installed.

2.	Once the installation process has begun, the following information must be provided for the Word for Windows 2.0 integration files:

•	The SoftSolutions installation program creates a Retrieve application in the SoftSolutions APPLICATIONS window.

a.	The drive and path to the Word for Windows 2.0 programs directory, such as F:\APPS\WINWORD2.

b.	The drive and path to the SoftSolutions programs directory.

3.	The installation program automatically performs the following:

a.	The following files are copied into the SoftSolutions INT directory, a subdirectory of the SoftSolutions programs directory:

2WORD31A.INT

2NORM31A.DOT

FOOTER2.DOC

SUMM2.DOT

TNT2.DOT

b.	The following application record is created in the APPLICATIONS window:

Field Name	Field Entry

Code	WINWORD2

Description	Microsoft Word for Windows 2.0

App Type	R

Index Text?	Y

Create File?	N

Echo Docu?	Y

Ext	DOC

Command line	[Word for Windows Programs Directory]\winword.exe %win:int

Creation Template	(no entry—field is left blank)

Preview Command	%ossvieww.exe %r[%sc %p%f]

Location Segment	WinWord2

The command line used to open Word for Windows should not be a DDE command line. The default command line which calls WINWORD.EXE opens documents in Word for Windows while at the DOCUMENT PROFILE window.

If the users wants the Create File flag set to Yes, the Creation Template field should contain a blank Word for Windows document on which to base the new document (e.g., ^EMPTY.DOC). This allows the user to create a new Profile and then select the Retrieve option and SoftSolutions will start Word for Windows and load in the document.

4.	The workstation installation program automatically performs the following:

a.	The following files are copied from the SoftSolutions INT directory to the Word for Windows programs directory:

INSTALL2.DOT	(2NORM31A.DOT is copied and given the name INSTALL2.DOT)

FOOTER2.DOC

SUMM2.DOT

TNT2.DOT

b.	The WIN.INI text file found in the main Windows directory is modified by adding the following key to the [Microsoft Word 2.0] section:

NOFILECACHE=YES

5.	When the installation is finished, the following should be performed:

a.	Edit the SOFTSOLW.INI text file found in the main Windows directory as follows:

i.	If necessary, add [AppTable] as a section.

ii.	Add the following key to the [AppTable] section:

[Path to Word programs directory]\WINWORD.EXE=[Application Code],%FO

For example:

F:\APPS\WINWORD2\WINWORD.EXE=WINWORD2,%FO

b.	Locate NORMAL.DOT and ensure it is not a "read-only" file.

c.	Make a backup of NORMAL.DOT.

d.	In Program Manager, use File|Run and enter the following command:

[Path to Word Programs Dir]\WINWORD.EXE /mInstallSS [Path to Word Programs Dir]\INSTALL2.DOT

For example:

F:\WINWORD2\WINWORD.EXE /mInstallSS F:\WINWORD2\INSTALL2.DOT

•	This copies the SoftSolutions-Word Integration macros to NORMAL.DOT, and saves NORMAL.DOT.

Installation for Word 6.0

NOTE

Microsoft Word 6.0 for Windows requires SHARE to be loaded and on your path. The following call to SHARE is suggested by Microsoft:

SHARE.EXE /L:500 /F:5100

SHARE must be loaded in conventional memory (within the first 640kb of RAM).

1.	Perform an installation of the Application Integration Files as described in the SoftSolutions Installation Guide, choosing Word for Windows 6.0 to be installed.

2.	Once the installation process has begun, the following information must be provided for the Word for Windows 6.0 integration files:

a.	The drive and path to the Word for Windows 6.0 programs directory, such as F:\APPS\WINWORD6.

b.	The drive and path to the Word for Windows 6.0 STARTUP directory.

c.	The drive and path to the SoftSolutions programs directory.

•	The SoftSolutions installation program also creates a Retrieve application in the SoftSolutions APPLICATIONS window.

3.	The installation program automatically performs the following:

a.	The following files are copied into the SoftSolutions INT directory, a subdirectory of the SoftSolutions programs directory:

6WORD31A.INT

SSNORM.DOT

FOOTER6.DOC

SUMM6.DOT

TNT6.DOT

b.	The following application record is created in the APPLICATIONS window:

Field Name	Field Entry

Code	WINWORD6

Description	Microsoft Word for Windows 6.0

App Type	R

Index Text?	Y

Create File?	N

Echo Docu?	Y

Ext	DOC

Command line	[Word for Windows Programs Directory]\winword.exe %win:int

Creation Template	(no entry—field is left blank)

Preview Command	%ossvieww.exe %r[%sc %p%f]

Location Segment	WinWord6

The command line used to open Word for Windows should not be a DDE command line. The default command line which calls WINWORD.EXE opens documents in Word for Windows while at the DOCUMENT PROFILE window.

If the users wants the Create File flag set to Yes, the Creation Template field should contain a blank Word for Windows document on which to base the new document (e.g., ^EMPTY.DOC). This will allow the user to create a new Profile and then press the Retrieve option and SoftSolutions will start Word for Windows and load in the document.

4.	The workstation installation program automatically performs the following:

a.	The following file is copied from the SoftSolutions INT directory to the Word for Windows STARTUP directory:

SSNORM.DOT

b.	The following files are copied from the SoftSolutions INT directory to the Word for Windows programs directory:

FOOTER6.DOC

SUMM6.DOT

TNT6.DOT

5.	When the installation is finished, the following should be performed:

a.	Edit the SOFTSOLW.INI text file found in the main Windows directory as follows:

i.	If necessary, add [AppTable] as a section.

ii.	Add the following key to the [AppTable] section:

[Path to Word programs directory]\WINWORD.EXE=[Application Code],%FO

For example:

F:\APPS\WINWORD6\WINWORD.EXE=WINWORD6,%FO

b.	Make a backup of NORMAL.DOT.

6.	At the time Word is opened, you will be prompted to install the new integrations. Perform one of the following:

a.	Choose Yes to automatically copy the AUTOEXEC macro to NORMAL.DOT.

b.	Choose No to open Word without updating integrations.

PaperWise ImageWise Software

SoftSolutions provides a feature-rich document management solution for local and wide area networks. The types of documents that are managed by SoftSolutions include letters, memos, spreadsheets, graphic files, and even scanned images of paper documents. The source application for scanned images is PaperWise's ImageWise Software. By integrating the imaging software with SoftSolutions, scanned images can be managed in the same manner as spreadsheets, word processor documents, etc.

A general description of how images are managed by SoftSolutions is as follows:

•	The user creates a new Profile in SoftSolutions.

•	Information is entered into the Profile that identifies the image or images associated with the Profile.

•	Whenever this Profile is opened by the user, the images can be opened by launching, from SoftSolutions, the imaging application in which the images are displayed.

Note that this process is identical to managing other document types such as letters, memos, and spreadsheets.

Software Requirements

The SoftSolutions-PaperWise integration requires the following versions of the respective software:

•	SoftSolutions Version 4.0 or later

•	PaperWise ImageWise Version 3.304 or later

Installation

1.	During the SoftSolutions installation, perform an installation of the Application Integration Files as described in the SoftSolutions for Windows Installation Guide, choosing "PaperWise ImageWise" to be installed.

2.	Once this integration completes, you will be asked to run the PaperWise Integration program that is installed with the ImageWise Software. To run this program, double-click on the "PaperWise Integration" program icon located in the PaperWise program group.

•	The PAPERWISE INTEGRATION window appears.

3.	Select "SoftSolutions 4.x" from the "Available Applications" listbox and click the "Done" button.

•	The SOFTSOLUTIONS 4.X window appears.

4.	Using this window, specify the path to the SoftSolutions programs directory and click on "OK."

•	The path is [Drive Letter]:\[Path to SoftSolutions Programs Directory], such as L:\APPS\SOFTSOL\PROG.

•	After specifying the path to the SoftSolutions program, the SOFTSOLUTIONS INTEGRATION OPTIONS window appears. This window is used to provide additional information for the SoftSolutions integration. The data fields and checkboxes are explained as follows:

Dataset

This is the name of the SoftSolutions dataset to which to integrate. Default value is SOFTSOL.

Data Path

This is the directory where the SoftSolutions data files for the selected dataset reside. The default is determined from the path to the SoftSolutions program supplied above in step 4.

Add PaperWise application names and paths?

Selecting this checkbox adds the PaperWise applications to the SoftSolutions application list. Adding the PaperWise applications is required in order to launch the imaging programs from SoftSolutions.

If this checkbox is selected, an application called QUERY is added to the SoftSolutions list of applications. The values of the fields associated with this Query application record are shown below. Notice that the "Command Line" field includes several parameters, namely references to Custom Prompt fields. These parameters are explained in more detail in "How Custom Prompt Fields Are Used" on page 190.

Code	QUERY

Description	ImageWise Software

App Type	O

Index Text?	N

Create File?	N

Echo Dots?	N

Command Line	[Path]\QUERY.EXE -e%01D -q"%02","","",""

Creation Template

Preview Command

Location Segment	QUERY

Add PaperWise document types?

Selecting this checkbox adds an IMAGE document type to SoftSolutions. All images profiled in SoftSolutions using PaperWise's ImageWise Software will be labelled as type IMAGE. The values associated with the new IMAGE document type are as follows:

Code	IMAGE

Description	Image

Echo Life	0

Doc Life	0

Arch/Del	A

Index Text?	N

Max Ver	1

Change the Custom Prompt definitions?

At minimum, two of the SoftSolutions custom Profile fields are required for integrating the ImageWise Software. By selecting this checkbox, the names of the first two Custom Prompts will be changed to "Database" and "Document ID," respectively. These two fields are used to store information that identifies the images associated with the Profile.

If the first two Custom Prompts are already in use in your SoftSolutions dataset, you can select two other Custom Prompts to use for Database and Document ID. To do this, use the spinner controls located to the right of Database and Document ID and select different custom fields.

The "Database" field identifies the database in which the images are located. The "Document ID" identifies the document within this database. This document therefore corresponds to the Profile.

Note that if this checkbox is selected, every user must exit out of SoftSolutions for the integration to work properly.

Add the following PaperWise environments:

This checkbox and the corresponding spreadsheet are used to add imaging databases to the "Database" Custom Prompt list. As mentioned, a database and document ID are required for each image document profiled in SoftSolutions. Every imaging database on your system that will be integrated with SoftSolutions must be included in the list.

To add a database to this list, select the "Add" pushbutton. The SELECT AN ENV FILE TO INTEGRATE window appears.

Use this dialog to traverse the directory structure and select the database file to add to the list. After doing so and selecting "OK," the specified database is added to the spreadsheet.

Continue adding all databases to this spreadsheet. All databases added to the spreadsheet are added to the SoftSolutions custom field "Database" list. After integration is complete, verify this by looking at the custom field "Database" in SoftSolutions.

5.	Enter information for the data fields and checkboxes in the SOFTSOLUTIONS INTEGRATION OPTIONS window as explained above.

6.	Select the "OK" button.

•	A status window appears showing the progress of the integration.

•	One additional step in integration is running the SoftSolutions string compiler. This is necessary to update SoftSolutions with the new Custom Prompt names.

•	A window will appear notifying you that the SoftSolutions String Compiler will be run.

7.	Select the "OK" button to proceed.

•	Note that all users must exit from SoftSolutions for the String Compiler to work properly.

When the integration is complete, a window will appear informing you of this. You are now ready to add images with the PaperWise ImageWise Software and use SoftSolutions to manage these images. (Refer "Using PaperWise Integrations" below for details on this.)

Watermark Discovery Edition

This manual provides information on the Watermark Discovery Edition integration. Integration is not available in any version purchased from Watermark. In order to have the integration, Watermark must be purchased through SoftSolutions Technology Corporation only. Following the Installation Procedures, the integrated options are listed in alphabetical order.

Installation

1.	Perform an installation of the Application Integration Files as described in the SoftSolutions Reference, choosing Watermark to be installed.

2.	Once the installation process has begun, provide the drive and path of the Watermark programs directory when prompted. For example, C:\APPS\WATERMRK.

•	The SoftSolutions installation program automatically creates a Retrieve application, WATER, in the SoftSolutions APPLICATIONS window. This application has the following Command Line:

[Watermark Programs Directory]\WATERMRK.EXE %WIN:INT:MULTINST

3.	To run a shared copy of Watermark on the network, perform the following on each workstation using Watermark:

a.	Copy WATERMRK.INI to the WINDOWS programs directory.

b.	Using any text editor, edit WIN.INI to include the following:

To the [Extensions] section add the line:

TIF=[Watermark Programs Directory]\WATERMRK.EXE ^.TIF

To the [Embedding] section add the line:

WATERMRK=IMAGE OBJECT,IMAGE OBJECTS,[Watermark Programs Directory]\WATERMRK.EXE,PICTURE

c.	Using REGEDIT /V, modify REG.DAT to include the following:

_______Watermrk = Image Objects

|	|___protocol

|	|___StdFileEditing

|	|____verb

|	| |___0 = edit

|	|_____server = [Watermark programs dir]\watermrk.exe

|_______.tif = Watermrk

WordPerfect for Windows 5.1, 5.2, 6.0

Files

*.BIF	When installing and setting up the WordPerfect 6.0 integration, the WordPerfect for Windows BIF Editor is used to add a new item to the Third Party section of the WPCNET.BIF file (when running WordPerfect from the network), or the WPCSET.BIF file (when running WordPerfect locally). (See installation instructions for the WordPerfect 6.0 integration for additional information.)

DDEMAC.WCM	This WordPerfect 5.1/5.2 macro is used to create DDE links between the SoftSolutions Profile and its associated document. This can only be done in the main body of the document because DDE links cannot be created in headers or footers. The links created are based on the template DOCPLATE.WP located in the WordPerfect shared code directory. (See below for more information about the DOCPLATE.WP template.) This macro is placed in the WordPerfect shared code directory.

DOCMAC.WCM	This WordPerfect 5.1/5.2 macro is used to create documents based on the entry in the Document Type field in the SoftSolutions Profile. By default it looks for three document types: 1) MEMO − a memorandum; 2) SUMM − a court summons; and, 3) TNT − a trial notice.

The macro can be modified to check for and handle any number of document types. If the document type is MEMO, then another macro, MEMOMAC, is run to create the memo. If the document type is SUMM or TNT, then a template document is used to create the new document. As the document is created, certain information required by the merge fields will be requested. (See the information about MEMOMAC.WCM, SUMM.WP, and TNT.WP below for a more detailed explanation of each of these files.) This macro is placed in the WordPerfect shared code directory.

DOCPLATE.WP	This WordPerfect 5.1/5.2 document serves as a template used by the DDEMAC macro when creating DDE links between the SoftSolutions Profile and the associated document. This is a WordPerfect document that should be formatted to the user's needs. It can contain different fonts, even WordPerfect graphics, anything that a regular WordPerfect document could hold. It should have SoftSolutions Command Line parameters where the user desires to have information inserted from the Profile. For example, to get the document number, %N should be typed in the place that the document number from the Profile should appear. Each variable used must be followed by a blank space. This document is placed in the WordPerfect shared code directory.

FOOTER.WPD	This document serves as a template used by the HDRORFTR macro when creating a Footer B in WordPerfect 6.0. This is a WordPerfect document that should be formatted to the user's needs. It can contain different fonts, even WordPerfect graphics—anything that a regular WordPerfect document can hold. It should have SoftSolutions command line parameters where Profile information is to be inserted. For example, to get the Document Number, %N should be typed where the Document Number from the Profile should appear. Each variable used must be followed by a blank space. By renaming this document, you can create types other than footers. For example, if this document were renamed to HEADERA.WP, the HDRORFTR macro would create a Header A instead of a Footer B. This document is placed in the WordPerfect programs directory.

FOOTERB.WP	This document is the same as FOOTER.WPD, but is used in WordPerfect 5.1/5.2. This document is placed in the WordPerfect shared code directory.

HDRORFTR.WCM	This WordPerfect 5.1/5.2 macro is called by the NEWMAC and OPENMAC macros. It creates a header or footer based on the name of a template document. WordPerfect can have up to two headers and two footers in each document. These are named, respectively, HEADERA, HEADERB, FOOTERA, and FOOTERB. This macro searches the WordPerfect macros directory for a document named either HEADERA.WP, HEADERB.WP, FOOTERA.WP, or FOOTERB.WP. The name of the document determines which of the four types will be created. It then creates the header or footer based on the template document that it finds. (See FOOTERB.WP above for more information about the template document.) The macro is placed in the WordPerfect shared code directory.

INTONOFF.WCM	This macro turns WordPerfect 6.0 integration ON and OFF. This macro is placed in the WordPerfect programs directory.

MEMOMAC.WCM	This WordPerfect 5.1/5.2 macro is used to create a memorandum. It places the author's name at the top of the document and prompts the user to enter the name of the person that will be receiving the memo and the topic of the memo. This macro is placed in the WordPerfect shared code directory.

NEWMAC.WCM	This WordPerfect 5.1/5.2 macro is called each time a File|New menu command is executed and a new document is created. By default it does nothing, but by removing the comment notations for a few lines in the code, it can perform up to three different actions:

1)	Create a header or footer in the new document by calling HDRORFTR.WCM;

2)	Create DDE links between the new document and the associated SoftSolutions Profile by calling DDEMAC.WCM; and,

3)	Create a document based on the Document Type specified in the SoftSolutions Profile. For example, if the document type is MEMO, a blank memorandum is inserted when the document is created by calling DOCMAC.WCM.

This macro is placed in the WordPerfect shared code directory and must exist even if it is performing no action.

NOTE

This macro can perform none, one, two or all of the functions described here. By default, none of the macros will be called. The system administrator must tailor the NEWMAC macro so it performs the functions required. Generally, the HDRORFTR macro and the DDEMAC macro should not both be enabled at the same time. However, if the user wants both of them to run, NEWMAC.WCM can run both of them. For SoftSolutions to run macros based on a document type, a File|New|Now must be done, which requires the Profile to be completed before the document is created.

ON&OFF.WCM	This macro turns WordPerfect 5.1/5.2 integration ON and OFF. This macro is placed in the WordPerfect shared code directory.

OPENMAC.WCM	This WordPerfect 5.1/5.2 macro is called each time a File|Open menu command is executed and the document is opened. By default it does nothing, but by removing the comment notations for a few lines in the code, it can update the header or footer that exists in the document being opened. This is done by calling HDRORFTR.WCM. By default, this HDRORFTR.WCM is not called, and, unless the Profile is frequently changed once is has been created, this macro need not be called.

Calling this macro can slow the performance of the document open, and, if the Profile has not been changed, updating the header or footer is unnecessary. This macro is placed in the WordPerfect shared code directory and must exist even if it is performing no action.

SIWP.DLL	This DLL allows changing the actions of certain menu commands in WordPerfect 5.x. As menu functions are "trapped" by this DLL, functions are called from the SSAPPINT.DLL to allow a user to access SoftSolutions directly from WordPerfect. This DLL is placed in the WordPerfect programs directory.

SIWP6.DLL	This DLL allows changing the actions of certain menu commands in WordPerfect 6.0. As menu functions are "trapped" by this DLL, functions are called from the SSAPPINT.DLL to allow a user to access SoftSolutions directly from WordPerfect. This DLL is placed in the WordPerfect programs directory.

SSWMAIN.WCM	This WordPerfect 6.0 macro contains all of the macros used in the SoftSolutions integration. This file is placed in the WordPerfect programs directory.

SSWMERGE.WCM	This WordPerfect 6.0 macro used to perform an integrated merge. This file is placed in the WordPerfect programs directory.

SUMM.WP	This WordPerfect 5.1/5.2 document is a template document for a summons and contains WordPerfect merge fields. When the document type in the Profile is SUMM, DOCMAC opens this file in merge mode and begins prompting for the information to be inserted. This document is placed in the WordPerfect shared code directory.

TNT.WP	This WordPerfect 5.1/5.2 document is a template document for a trial notice and contains WordPerfect merge fields. When the document type in the Profile is TNT, DOCMAC opens this file in merge mode and begins prompting for the information to be inserted. This document is placed in the WordPerfect shared code directory.

WPC.INI	This file is modified by the integration installation program when installing WordPerfect for Windows 5.1/5.2 only. The following key is added to the [WPWP−3rd] section:

SIWP=[WordPerfect Programs Directory]\SIWP.DLL

This file is found in the Windows programs directory.

Template Documents in WordPerfect 5.1/5.2/6.0

The template documents used by the HDRORFTR and DDEMAC macros have the same format. Each is simply a WordPerfect document formatted in the way that the user would like it to look. Different font styles, sizes, etc., may be used when creating the document. In the places where the SoftSolutions Profile information is to be placed, the user may use the SoftSolutions command line parameters. For example, if you wanted a Footer B in all of your "new" documents, you would create a file FOOTERB.WP and save it in the WordPerfect for Windows shared code directory. The text of the document could be as follows:

Document Number: %N%

Document Name: %M%

Author: %AD%

Each command line parameter must be followed by a % character so the macro can create the header, footer, or DDE link correctly. But, for 6.0, the very last % character in a template document (e.g., "Author: %AD% in the above exmaple) must be preceded by the !@! characters. For example:

Document Number: %N%

Document Name: %M%

Author: %AD!@!%

Again, all template documents must be placed in the WordPerfect for Windows shared code directory for WordPerfect 5.1/5.2, and for WordPerfect 6.0, place the template in the WordPerfect programs directory. Otherwise, the macro will not run correctly.

Installation

1.	Perform an installation of the Integrations as described in the SoftSolutions Installation Guide, choosing WordPerfect 5.1/5.2 or 6.0 for Windows to be installed.

2.	Once the installation process has begun, the following information must be provided for the WordPerfect for Windows 5.1/5.2 or 6.0 integration files:

a.	The drive and path to the WordPerfect 5.1/5.2 or 6.0 programs directory, such as F:\APPS\WPWIN for WordPerfect 5.2 or F:\APPS\WPWIN60 for WordPerfect 6.0.

b.	The drive and path to the WordPerfect 5.1/5.2 shared code directory, such as F:\APPS\WPC.

3.	The installation program automatically performs the following:

a.	The following application record is created in the APPLICATIONS window for WordPerfect 5.1/5.2:

Field Name	Field Entry

Code	WPWIN5

Description	WordPerfect for Windows

App Type	R

Index Text?	Y

Create File?	N

Echo Docu?	N

Ext	(no entry—field is left blank)

Command line	[WordPerfect 5.1/5.2 Programs Directory]\wpwin.exe /u=%u %win:int:wpwinfil.exe

Creation Template	(no entry—field is left blank)

Preview Command	%ossvieww.exe %r[%sc %p%f]

Location Segment	WPWin5

b.	When installing WordPerfect 6.0 integration, the following application record is created:

Field Name	Field Entry

Code	WPWIN60

Description	WordPerfect 6.0 for Windows

App Type	R

Index Text?	Y

Create File?	N

Echo Docu?	N

Ext	(no entry—field is left blank)

Command line	[WordPerfect 6.0 Programs Directory]\wpwin.exe %win:int:wpwin60.exe

Creation Template	(no entry—field is left blank)

Preview Command	%ossvieww.exe %r[%sc %p%f]

Location Segment	WPWin60

When using WordPerfect for Windows with SoftSolutions for Windows, the above Create File flag settings in the APPLICATIONS window can be used.

No is the default flag setting. It is used when no creation template is to be used. Dynamic Profile information can be inserted into a newly created document using the NEWMAC.WCM and FOOTERB.WP files which can be set up to be invoked automatically when File|New is chosen.

The NEWMAC.WCM and FOOTERB.WP files can still be used to put dynamic Profile information into the document's footer. When using the Task Switcher with SoftSolutions for DOS, the /A parameter can be used to invoke a macro which can put the Profile information into the document.

If both WordPerfect for Windows and WordPerfect for DOS (without the Task Switcher) are being called from the same application record and dynamic information is needed in the document, then the Create File flag must be set to Yes and an ASCII file used as the creation template (placing something like "Doc ID: %D%_%N%_%V%" on the command line). This allows dynamic information to be passed to WordPerfect from SoftSolutions.

When using SoftSolutions for Windows with this setup, a File Formats box will be displayed each time a document is created. This permits documents in formats other than WordPerfect to be opened in WordPerfect.

•	Requirements: If the /u or /ps switches are being used on the WordPerfect command line, create the environment variable WPWIN for these switches. If WPWIN contains the /u and /ps switches, these switches can be removed from the WordPerfect command line. Refer to the WordPerfect 5.2 manual for information on command line switches in environment variables.

4.	The installation program automatically performs the following:

a.	The following files are copied from the diskettes to the WordPerfect programs directory:

WordPerfect 5.1/5.2	WordPerfect 6.0

SIWP.DLL	SIWP6.DLL

SSWMAIN.WCM

SSWMERGE.WCM

FOOTER.WPD

INTONOFF.WCM

b.	The following WordPerfect 5.1/5.2 integration files are copied from the SoftSolutions INT directory to the WordPerfect shared code directory:

MEMOMAC.WCM

NEWMAC.WCM

OPENMAC.WCM

FOOTERB.WP

DDEMAC.WCM

HDRORFTR.WCM

TNT.WP

SUMM.WP

DOCMAC.WCM

DOCPLATE.WP

c.	The WPC.INI text file found in the main Windows directory is modified for the WordPerfect 5.1/5.2 integration by adding the following key to the [WPWP−3rd] section:

SIWP=[WordPerfect Programs Directory]\SIWP.DLL

•	If WordPerfect for Windows is being run from the network, WPC_NET.INI should not be used for integrating with SoftSolutions. Doing so will cause many problems with the integrations module for WordPerfect. Only the WPC.INI file, found in each user's Windows programs directory, should be modified.

5.	When installing WordPerfect 6.0 integration, the WordPerfect 6.0 for Windows BIF Editor (BIFED20.EXE) located in the WordPerfect 6.0 for Windows WPC20 directory must be run and the following must be added to the WPCNET.BIF file (when running WordPerfect from the network), or the WPCSET.BIF file (when running WordPerfect locally). In the WordPerfect Groups, Third Party section, the following item is added:

Group	WordPerfect.

Section	Third Party.

Item	This is "DLL," immediately followed by the next available number. For example, if the last item in the Third Party section is DLL2, the name for the new item would be DLL3 (in all capital letters).

Item Type	ANSI.

Value	This is [Path to Integration DLL]\SIWP6.DLL, where [Path to Integration DLL] is replaced with the full path to the integration DLL (SIWP6.DLL). This should be the WordPerfect 6.0 for Windows programs directory. For example:

F:\APPS\WPWIN60\SIWP6.DLL

6.	Edit the SOFTSOLW.INI text file found in the main Windows directory as follows:

a.	If necessary, add [AppTable] as a section.

b.	Add the following key to the [AppTable] section:

For WordPerfect 5.1/5.2:

[Path to WordPerfect programs directory]\WPWINFIL.EXE=[Application Code],%FO

For example:

F:\APPS\WPWIN\WPWINFIL.EXE=WPWIN5,%FO

For WordPerfect 6.0:

[Path to WordPerfect shared code directory]\MXWIN20.EXE=[Application Code],%FO

For example:

F:\APPS\WPC20\MXWIN20.EXE=WPWIN60,%FO

c.	Also, add the following key to the [WPWin 6.0] section:

MainMacro=[WordPerfect Programs Directory]\sswmain.wcm

7.	Integration is not available when opening a file using the list of the last four opened files in the File menu. For this reason, SoftSolutions recommends that this display be turned off. This is done by performing the following:

a.	Choose Preferences from the File menu.

b.	Choose Environment.

c.	Click the Display Last Open Filenames in the Menu box to its OFF position.

WordScan Plus 1.1, 2.0

This paper provides information on the integration with Calera's WordScan Plus 1.1/2.0. WordScan must be installed prior to installing the WordScan integration.

Installation

1.	Perform an installation of the Integration files as described in the SoftSolutions Installation Guide, choosing the appropriate version of the WordScan files to be installed.

2.	Once the installation process has begun, the following information must be provided for the WordScan integration files:

a.	The drive and path to the Calera programs directory, such as F:\APPS\CALERA\BIN for 1.1 or F:\APPS\WORDSCAN for 2.0.

b.	The device name for the Calera engine. The following information provided by Calera can be used in determining the correct entry for this field:

i.	When using WordScan Plus, the device is:

RSP:WINOCRVI,1,0

This is the default when first installing the WordScan integration files.

ii.	When using Future Domain (Western Digital), the device is:

WD:[buf_size], [target_id], [host_id], [I/O], [DMA], [lun]

where

buf_size	= the size of the DMA buffer to allocate

target_id	= the SCSI id of the CRD (default = 4)

host_id	= the SCSI id of the host adapter card (default = 7)

I/O	= the I/O address of the host adapter card, as configured by switches on the card (default = 320H)

DMA	= the DMA channel number assigned to the host adapter card (default = 6)

lun	= the logical unit number of the CRD

•	In an MM2400, the lun parameter is used to access individual cards. The logical unit numbers for the cards are 0,1,2, and 3.

For either SCSI card, increasing the size of buf_size beyond about 4kb will not significantly improve the communication speed. You may wish to keep the buf value at 4kb, especially when using multiple engines.

iii.	When using Adaptec 1542B, the device is:

ASPI:[buf_size],[target_id],[lun]

where

buf_size	= the size of the DMA buffer to allocate

target_id	= the SCSI id of the CRD (default = 4)

lun	= the logical unit number of the CRD

•	In an MM2400, the lun parameter is used to access individual cards. The logical unit numbers for the cards are 0,1,2, and 3.

For either SCSI card, increasing the size of buf_size beyond about 4kb will not significantly improve the communication speed. You may wish to keep the buf value at 4kb, especially when using multiple engines.

When using an Adaptec host adapter, you must install the Adaptec ASPI4DOS driver in the first line of your CONFIG.SYS file. You must turn on the M/Series before you turn on the computer so that the driver can find and register the device as the computer boots.

Only the following Adaptec host adapters are supported:

1540/1542B

PC/AT bus

iv.	When using M/Series Accelerator Card, the device is:

ATRS:[memory_segment], [I/O addr]

where

memory_segment	= the first two hexadecimal digits of the starting memory address to which the card is configured

I/O addr	= the hexadecimal I/O address to which the card is configured

3.	WordScan integration is then installed. Upon completion of operation, exit Windows and perform the following:

a.	Edit the PATH to include the Calera programs directory.

b.	Edit AUTOEXEC.BAT to contain an environment variable to the Calera directory, such as SET CALERA=F:\APPS\CALERA for 1.1 or SET CALERA=F:\APPS\WORDSCAN for 2.0.

c.	Reboot the workstation.

4.	For WordScan Plus 2.0 integration only, the following must be performed in addition to the previous steps:

a.	Create a \LIB directory in the WordScan directory, such as F:\APPS\CALERA\LIB.

b.	Copy the following files from the WordScan directory to the \LIB directory: CIL.ERR, WTFORMAT.DAT, and WOFORMAT.DAT.
NOTE

WordScan Plus 2.0 users who have upgraded from WordScan 1.1:

When version 1.1 is installed, it places a [Calera] section in the WIN.INI file. This section is not changed by version 2.0 when it is installed. The [Calera] section contains the path to the 1.1 programs directory. Therefore, if version 2.0 is installed in a directory different than that of version 1.1, WordScan will not work correctly because the path in the WIN.INI file will point to the older version.

The integration for WordScan looks for the *.DAT files it needs to display the output file formats. If the WIN.INI file points to the 1.1 programs directory, the following error message will be displayed:

Text format list error:−3007

The best way to fix this problem is to edit the WIN.INI file and comment out the [Calera] section.

The following circumstances can also cause the above error message to be displayed:

1)	The WordScan programs directory is not in the current path.

2)	The "CALERA" environment variable is not set to the WordScan programs directory.

3)	The WTFORMAT.DAT and WOFORMAT.DAT files are not copied to the \LIB directory under the WordScan programs directory.

5.	The SoftSolutions Installation program automatically creates the Launch application, SSOCR, in the SoftSolutions APPLICATIONS window. The Command Line is as follows:

[SoftSolutions Programs Directory]\SSOCR.EXE %R[v %N %V!! /DATA=%B /USER=%U /PROG=%O /TMPDIR=%TMP]

The following additional Launch application records may be created in the SoftSolutions APPLICATIONS window. SSOCRM is a Launch using several marked documents. SSOCRSR is a Launch using the search results.

App Code	Command Line

SSOCRM	[SoftSolutions programs directory]\SSOCR.EXE ^[SoftSolutions programs directory]\SSOCRM.RSP

SSOCRSR	[SoftSolutions programs directory]\SSOCR.EXE ^[SoftSolutions programs directory]\SSOCRSR.RSP

WorkMAN 1.02

Installation

1.	Perform an installation of the Application Integration Files as described in the SoftSolutions Installation Guide, choosing WorkMAN 1.02 to be installed.

2.	Once the installation process has begun, the drive and path to the WorkMAN Tools 1.02 directory, such as C:\WMTOOLS, must be provided. If you do not have WorkMAN Tools installed, enter a temporary directory name and the files can be deleted later.

3.	The installation program automatically performs the following:

a.	The following files are copied into the SoftSolutions WORKMAN directory, a subdirectory of the SoftSolutions programs directory:

WORKFLOW.BTR

APPL.ICO

COLOR.SCR

INITRACK.SCR

SSROUT.SCR

TRACKFNS.SCR

USERFUNC.SCR

WKFLOW.WOB

FILES.LST

WKFLOW1.SCR

WKFLOW.BTD

b.	The following file is copied into the SoftSolutions WORKMAN\SS40_LIB directory, a subdirectory of the SoftSolutions programs directory:

WFTYPES.REC

c.	The following files are copied into the SoftSolutions WORKMAN\SS40_LIB\CTS directory, a subdirectory of the SoftSolutions programs directory:

WKFLOW.BTD

WKFLOW.CTL

WKFLOW.ICO

WKFLOW.SCM

d.	The following files are copied into the SoftSolutions WORKMAN\SS40_LIB\CTS\SCRIPTS directory, a subdirectory of the SoftSolutions programs directory:

APPL.HLP

BTRVTRK.DLL

FORMSDLL.DLL

MISC.DLL

WMSSAPP.DLL

SS.BMP

e.	The following files are copied into the SoftSolutions WORKMAN\SS40_LIB\CTS\FORMS directory, a subdirectory of the SoftSolutions programs directory:

COMMENTS.FRM

FUNCTION.FRM

IMFMAIN.FRM

LISTVIEW.FRM

PRIMARY.FRM

RESPONSE.FRM

STEPVIEW.FRM

VUEATACH.FRM

4.	The workstation installation program automatically performs the following:

NOTE

A workstation install is only needed if WorkMAN tools will be used to develop new WorkMAN integrated applications.

a.	The following files are copied from the SoftSolutions WORKMAN directory (and subdirectories of the WORKMAN directory) to the WorkMAN SS40_TD\DEFN\SS−C4!.WOB\ directory (a directory that SoftSolutions creates during installation):

APPL.HLP

APPL.ICO

BTRVTRK.DLL

COLOR.SCR

COMMENTS.FRM

FILES.LST

FORMSDLL.DLL

FUNCTION.FRM

IMFMAIN.FRM

INITRACK.SCR

LISTVIEW.FRM

MISC.DLL

RESPONSE.FRM

SS.BMP

SSROUT.SCR

STEPVIEW.FRM

TRACKFNS.SCR

USERFUNC.SCR

VUEATACH.FRM

WKFLOW.BTD

WKFLOW.WOB

WKFLOW1.SCR

WMSSAPP.DLL

b.	The following file is copied from the SoftSolutions WORKMAN directory (and subdirectories of the WORKMAN directory) to the WorkMAN SS40_TD\DIR directory (a directory that SoftSolutions creates during installation):

WORKFLOW.BTR

c.	The WORKMAN.INI text file found in the main Windows directory is modified by adding an entry for the SS_40 shared application library (containing the SoftSolutions Demonstration Correspondence Tracking System).

d.	The TDMSDK.INI text file found in the main Windows directory is modified as follows:

(for WorkMAN Tools) Add an entry for the SS40_TD type definition directory (containing the source code for the Demo application and .DLL files to access SoftSolutions from the WorkMAN script).

i.	The [SystemUpdate] will change to reflect when the system update was performed.

ii.	The [IntegrationUpdate] section will add information as to when the WorkMAN integration was updated.

5.	The following must be done within WorkMAN:

a.	From File|Manage|Applications, add the SoftSolutions Demo Correspondence Tracking System (in the SS_40 shared library) to the MAIN library.

b.	Any other SoftSolutions WorkMAN integrated Application can be added at this time.

Error & Confirmation Messages

Appendix A

A document has already been entered in the Document Information Array that has the FileName and FileID specified.

The user tried to open a document that has already be opened and stored in the Document Information Array.

Close the document before trying to delete it.

The user called SIFileDelete to delete a document that is still active in SoftSolutions. The user needs to close the active document and they try to do the deletion again.

Document requested does not exist or the user does not have security access to it.

An attempt was made to open a document that does not exist in the current dataset or that the user does not have rights to access.

Document requested is already in use or checked out.

The In Use flag on the Profile is set to Y or C, making the current user unable to open it.

Error: Document requested was not found.

The function looked for the document specified, but was unable to fine it in the Document Information Array. It was therefore unable to perform the action requested on that document.

Error: Document requested was not found and cannot be closed.

The user tried to close a document that was not stored in the Document Information Array.

Error in accessing document requested, or document is already in use.

A general error occurred when opening a document.

Invalid Document Number.

An invalid number was entered by the user when using the Document Number button from the SIFILEOPEN dialog box.

Invalid Flag parameter.

An invalid number was passed in the Flag parameter of one of the following functions: SIFileOpen, SIFileNew, SIFileClose, SIClosed, SIFileSaveAs.

Invalid Flag1 and Flag2 combination.

The user entered values for the Flag1 and Flag2 parameters of the SIFileOpen function that are not allowed to be used together.

No DDE information can be returned because the document specified does not have a SoftSolutions Profile.

The user requested DDE information for a document that does not yet have a SoftSolutions Profile associated with it.

No Search has been performed yet.

The user attempted to display the Previous Search Results list before any previous search had been performed.

SoftSolutions is busy performing another function.

If SoftSolutions is anywhere but at the DOCUMENT PROFILE window when the user tries to search for or create a Profile, this message will be displayed.

Too many Applications used.

The user tried to open documents in more that fifteen different applications in one session of SoftSolutions.

Too many Documents are open.

The user tried to open more than fifteen documents in a single application.

Unable to clear the Document Information Array Storage Area.

A general error occurred in the function SIClearDocTemp.

Unable to Close the document requested.

A general error occurred in the function SIFileClose.

Unable to create a new Profile or version for the document requested.

A general error occurred in the function SIFileSaveAs.

Unable to create a new version because the document does not have a SoftSolutions Profile yet.

The user tried to create a new version for a document that was opened in the application, but does not have a Profile for it yet.

Unable to CREATE a Profile for the document requested.

A general error occurred in the function SIFileNew.

Unable to delete the document specified.

An error occurred in the function SIFileDelete and the document specified in the dialog box was not deleted.

Unable to find or insert the application ID: *****.

This message is displayed when the user tries to open documents in more that fifteen different applications in one session of SoftSolutions or passes an application code that has never been used before to any of the following functions: SISetFileID, SIFileClose, SIClosed.

Unable to finish closing the document requested.

A general error occurred in the function SIClosed.

Unable to OPEN the document requested.

A general error occurred in the function SIFileOpen or SIActivateSS.

Unable to store the document in the Document Information Array.

A general error occurred in the function SISetFileID.

User does not have open access to the document requested.

Access is denied because of security restrictions.