Export2CM (Image-Master Export Program)

NOTE: Export2CM is an interface between Collection-Master and Image-Master.

Overview

Export2CM is a module designed to extract document data for Collection-Master, import into the Paperless File, and then to return updated field values back to Image-Master. In Collection-Master 8.3, the Paperless File will display the initials of the user who scanned/printed to the file with Image-Master. In previous Collection-Master versions the initials in the Paperless are either blank or simply read "EDI."

This integration component (Export2CM) is required in SQL-only Image-Master sites, and is strongly recommended in SQL-shared sites. In SQL-only configurations, Collection-Master's [4-2-6] import feature will not work. No documents are exchanged, as Collection-Master is unaware of SQL. In SQL-shared sites, document synchronization will still occur, but there will be a delay and the reverse data flow will be incorrect if the document index is edited after it has been saved and synched.

The Export2CM.exe program was designed to be used in place of Collection-Master's [4-2-6] Image Master --> Commercial Legal Software Paperless Importer program.

  • Prior to Collection-Master 8.3, when Collection-Master imported data from Image-Master regarding new scanned images, it recorded the user's initials logged in at the computer where the import into Collection-Master occurred. This was the default behavior.
  • As of Collection-Master 8.3, the initials of the user who actually did the scanning are now available and Image-Master may be configured to pass those initials to Collection-Master so that the scanner's initials will appear in the Paperless File Notes as opposed to the importer's initials.
    • To turn on this behavior, Image-Master must be configured to send the scanners login name to Collection-Master as part of the import process. Once Image-Master is configured, Collection-Master will automatically show the scanner's initials in the notes. New images will have the scanner's initials. Additionally, this will add 16 bytes to each image.

NOTE: This is a "go forward" configuration, meaning previously scanned images prior to changing Image-Master's configuration will continue to show the importer's initials.

  • As of Collection-Master 8.3, the Collection-Master image importer engine will pass the claim's Forwarder Number to Image-Master. This will automatically update the Image-Master database with the correct Forwarder Number.

To turn on this behavior, Image-Master must be configured to send the scanners login name to Collection-Master as part of the import process. Once Image-Master is configured, Collection-Master will automatically show the scanner's initials in the notes. New images will have the scanner's initials. Additionally, this will add 16 bytes to each image.

NOTE:  Image-Master has a 2 GB file size limit, so if your image database is approaching the 2 GB limit, you might consider not turning on this "scanner's initials" feature until you've upgraded to IM-SQL, which allows for databases over 2 GB in size.

Benefits

  • Better data isolation between Image-Master and Collection-Master

  • Faster synchronization, since only the appropriate records are offered to Collection-Master

  • Integrated SQL Server support for Image-Master SQL Version

Field Synchronization

When importing files using the key of forwarder reference number (MASTER.FORW_REFNO), the EDI Type must also be specified on the Image-Master side, and also match the forwarder that is assigned to the claim with the matching FORW_REFNO.

There are two classes of fields involved with data transfer between Collection-Master and Image-Master: Index fields and Non-index fields.

  • Index fields are used to help Collection-Master locate the proper consumer file.
  • Non-index fields are used to return data back to Image-Master after a match has been found.
Key fields (in order of operation) that search for data in Collection-Master.

Within the group of index fields, the import program selects only one to perform a search. Which field is chosen is based on a priority order where all higher priority index fields must be blank.

Index Fields Data Type Length
Fileno C 8
Docket # C 15
Forw Fileno C 20
Coco Fileno C 15
Forw Refno C 10
Forw EDI Type C 10

Field data that is passed back to Image-Master

The table-order of the returned Non-index fields indicates the priority order of the index fields in the returned list.

Non-index Fields Data Type Length
Fileno C 8
Docket # C 15
Forw Fileno C 20
Coco Fileno C 15
Forw Refno C 10

Installation

  1. Create a subfolder under the CLSINC folder named appropriately for the task, such as IM_IMPORT.

NOTE: IMASTER.INI stores scanner, viewer, and OCR engine selections and configuration, as well as parameters for each workstation (or group of workstations) that use EIDMS. The section order is important.

  1. Using any text editor, open f:\IMASTER\IMASTER.INI to add or modify the following section:

[ExportCM]

CMBASE = subfolder name created in step 1

DBNAME = ImageMasterDatabase name, path plus first six characters of your database filename. (This example uses CLS000 as the first six characters of the DB name; it might not be the same as the first six characters of your DB name.)

CMEXEC = Location of Collection-Master executable (wb32.exe/brclient.exe)

UpdateType = numeric type of update to be performed.

Typical Example: (non-SQL)

[ExportCM]

CMBASE=F:\CLSINC\IM_IMPORT\

DBNAME=F:\IMASTER\CLS000 (This example uses CLS000 as the first six characters of the DB name; be sure to use the first six characters of your DB name.)

CMEXEC=F:\CLSINC\WBWIN\BRCLIENT.EXE

UpdateType=0

Typical Example: (SQL)

[ExportCM]

CMBASE=F:\CLSINC\IM_IMPORT\

DBNAME=F:\IMASTER\CLS000 (This example uses CLS000 as the first six characters of the DB name; be sure to use the first six characters of your DB name.)

CMEXEC=F:\CLSINC\WBWIN\BRCLIENT.EXE

UpdateType=2

NOTE: If you are running Collection-Master 8.2D.008 or higher, skip steps 3 and 4.

  1. Open Collection-Master menu path [1-S-4-5].

  1. Change the Image-Master linkage (Imaster DBF) field to reference the CLS000CM.DBF file in the folder path chosen in step #1. (Example: F:\CLSINC\IM_IMPORT\CLS000CM.DBF)

  2. Ensure that Export2CM.EXE resides in the network IMASTER folder; if not, contact CLS Support.

  3. Establish a shortcut or scheduled task to this executable.

Usage

Run the Export2CM program in place of the [4-2-6] function within Collection-Master. Users who attempt to import via [4-2-6] instead of Export2CM will receive a relevant error message.

NOTE: Documents will be added to the Paperless File, and debtor information will be migrated back to Image-Master.

Technical Notes and Options (non-SQL and SQL)

Regarding DBNAME: Only specify the path and the first six characters of your Image-Master database filename.

Regarding UpdateType= The following option types are supported:

  • 0 = Update using DBF tables only (regardless of the Image-Master SQL configuration)

  • 1 = Update using SQL Server based tables for all Image-Master databases that have a valid DSN entry, otherwise behave as in type=0 for databases for which a valid DSN does not exist.

  • 2 = Update using DBF tables as the primary data source, but also update the corresponding tables on SQL server if a file DSN exists for the database.

Regarding Section Header: It defaults to ExportCM, but an alternate configuration can be specified in the IMASTER.INI file. To process that alternate configuration, include the chosen configuration name on the command parameters for Export2CM when it is executed.