LAW 4.0 ReadMe File

Legal Access Ware 4.0

Recent Changes to LAW by Version

This file details changes made to Legal Access Ware by version number. The changes can be categorized into 3 major types: Bug fixes, new features, and modifications. The categories have been color coded for easier recognition. Bug Fixes will appear as Red, New features in Blue, and Modifications in Green. Versions labeled as Critical Update should be installed immediately due to major bug fixes.

Version 4.3.11

-------------------------

(NEW FEATURES)

1) Images can now be replaced, or added for records without images by selecting Edit -> Replace -> 'Image from File' on the main form.

2) New hotkeys have been added to toggle between B&W, Greyscale, and Color scanning. The new hot keys are: Ctrl+1 = B&W, Ctrl+2 = 8-bit Greyscale, Ctrl+3 = 24-bit color. The user will be notified of the status change via message box.

3) Introspect export has been modified to support multi-entry fields. To set a field as multi-entry, set the ‘Multi-Entry Del.’ field value to the character that defines the break between the entries in LAW. The batch name for Introspect exports has also been updated to auto-increment between volumes.

4) OCR embedded in a Summation load file (*.dii) with the @OCR/@OCR-END token is now supported during Summation imports.

5) Missing page records will now be detected when opening a document and any missing pages will be re-inserted into the database with blank Page ID's. Inconsistencies between the actual image page count and the database page records will also be detected. When either situation occurs, the user will be notified of the inconsistency, and given a chance to open a page level grid display of the current document. From the grid, individual pages may be deleted (Edit -> Delete Record or Delete key) if they are actually invalid. Deleting pages will update the PgCount field and EndDoc#, and renumber pages if the user has created gaps in the page numbering. **NOTE: If missing page records are detected, the error and results of re-adding the pages will be added to a system log (law32_log.csv in application path) in the event a scan operator fails to report this to an administrator.

6) Rotation direction setting for auto-rotate has been added to batch print options.

7) Added new default field, <FolderRng>, to the export utility. This will provide the bates range (based on the specified image tag) of the folder containing each document.

8) Ringtail export now has additional capability to split field values into multiple records. To specify a field to be treated as a multi-entry field, press the [Multi-entry fields] button from the custom Ringtail options dialog. This allows you to select all fields to be treated as multi-entry, as well as the delimiter (default is semi-colon) used to split the field values.

(BUG FIXES)

1) Load file imports into SQL cases may fail to properly attach documents to their parent, and log a "Cannot create new transaction because capacity was exceeded" due to implicit transactions imposed by the SQL server.

2) Scanning in duplex mode with barcode folder breaks causes first image in a new folder to be lost.

3) Documatrix export no longer writes <AddImage> tag for every image of single page exports. It is now written only once for each document.

4) Blank images (with an endorsement) cannot be unendorsed due to a safety check to prevent blank output images. This check is now ignored if the original image area was blank.

5) Loading of OCR text on main form has been modified to allow loading of extremely large text files that previously caused an "Out of Memory" error.

6) Z-Print import may get stuck in an endless loop with counter increasing if a soft return (<CR>) is found within a field value.

7) Z-Print imports terminate prematurely if an ASCII 26 character is present in the log file. This character is interpreted as an EOF character, so all data after it is ignored.

8) Hardware keys do not work for licensing if 'Language for non-Unicode programs' is set to 'Japanese' in the Regional and Language Options of the Control Panel. This causes application to shut down immediately with a run-time error of 'Invalid procedure call or argument (5)'.

9) A bug in the Expervision OCR engine can provide invalid hit coordinates, which may result in an ‘Overflow (6)’ error if exporting OCR word information to IPRO, and premature termination of the record entry.

10) Exporting a document with missing page records can cause multiple output files to be named ".TIF" if a Page ID-based naming scheme is used, or blank Page IDs to be recorded in certain load files. These pages cannot be detected by a blank Page ID scan because the records do not exist in the database. These types of documents will now be detected, logged, and skipped if encountered during the export. These situations can also now be detected and corrected prior to exporting by using the Scan for Errors tool (Find missing/blank Page IDs process).

11) Summation export incorrectly puts the OCR text of each record with the next record in the load file if the OCR text is embedded directly in the dii file by setting the 'Include OCR text directly in dii file' option. **NOTE: This option is still not recommended over the default method. It leads to very large and hard to manage dii files, and is actually slower and less stable than leaving the text in separate files for each record.

12) Re-importing a Z-Print log after a TIFF conversion sets the NativeFile field back to a relative path which prevents LAW from launching the native file.

13) OCRing to a non-text format (ie. PDF) with the Expervision engine will fail to save the text output for any pages over 999.

14) The Opticon load file created with single-page Concordance exports uses the same Page ID entry for all pages if a user-defined index field is selected as the image tag causing Opticon to not display all pages of the document. A unique Page ID will now be auto-created in such cases to prevent repeated entries for this value.

15) Spaces are removed from BegDoc#/EndDoc# for Summation exports, but not from attachment fields which can result in invalid attachment links in Summation when loaded.

16) Merging parents and attachments to PDF during an export may fail with memory errors if too many attachments are included.

17) SQL Server cases will not allow multiple stations to perform raw image imports simultaneously.

18) If the Expervision OCR engine crashes and raises the following error, "An invalid PRTKClient was specified", all further documents fail with the same error.

19) Some functions (ie. Auto-numbering a folder) may cause a timeout error if a database command exceeds 30 seconds.

and various other minor fixes...

(MODIFICATIONS)

1) Image cleanup functions are now skipped on images with annotations. Previously, any annotations on a page would be removed by the image cleanup functions.

2) Watermarks (endorsed or printed) applied via batch processing must now be re-enabled for every batch session. This change has been made as a safety precaution to prevent unknowing users from branding an entire set of images which cannot be undone.

3) Concordance export has been modified to allow for extremely large text files to be embedded directly into the load file, although this is NOT RECOMMENDED, due to the size of the load file it will create, and the extra time it requires during the import. The recommended solution is to link to the text files, and use a CPL script to import the text. If text files are embedded however, the text will now be broken into sequential fields with a limit of ~8MB per field to adhere to Concordance's field size limitations.

4) If the connection to a hardware key times out due to intense processing (only applies if connecting to key thru a server), LAW will now attempt to re-establish the connection before terminating the application.

5) Images with invalid resolutions may not endorse as the correct positioning of the text cannot be determined without an accurate image resolution. Such images will now have their resolution approximated and updated so they can be properly endorsed.

6) Registered trademark symbols (®) have been removed from all export names to prevent issues with foreign languages. This may require reselecting of formats the first time this version or higher is run, but the individual format preferences will be preserved.

7) Re-arranged order of checks during Z-Print import to eliminate unnecessary image processing if 'Check for Matching Records' is selected with option to 'Ignoring incoming record' specified.

8) @T token in Summation exports has been moved to first line of record, for compatibility with CT Summation Enterprise.

9) The Scan for Errors utility has been enhanced to catch and/or correct additional database problems. The find blank page ID's function has been improved to now find and reinsert missing page records, in addition to just blank Page ID's. This function now has an additional option to auto-number missing pages when they are re-added. This will eliminate having to locate any documents that did have missing pages, and renumber them, so long as the range does not contain gaps. A new function, 'Remove duplicate/orphan page records', has also been added to remove duplicate page records and orphaned page records (page records whose parent no longer exists) that can be created in rare cases. This was previously available as the pagecleaner.exe utility, and has been further optimized for very large databases. And a new option has been added for the verify page counts function. The ability to update the database is now optional. It may be desirable not to update the database in all cases, as a discrepancy in the page count in the database versus the actual image could indicate image corruption. Leaving the discrepancy until the image is validated and/or replaced ensures it can always be detected, in the event the scan log is deleted.

10) A new template called "E-Discovery" is now included that provides all the required fields for E-Mail and E-Doc jobs.

11) Setting to 'Prompt to continue export when volume is full' has been moved from Preferences tab of main Options dialog to the Documents tab of export utility in the Output Location section.

12) Import delimited text has been enhanced to allow the user to specify the data delimiters and a newline replacement, move fields up and down once selected, and add a placeholder value to skip specific fields (<!-SKIP FIELD->).

13) When inserting new pages into existing documents, the 'Auto-number to end of folder' setting is now retained between sessions.

14) Optimized reorganize documents function to dramatically increase the processing speed for extremely large cases.

15) Optimized table opens for extremely large SQL cases (200K+ records) to avoid delays when performing functions (ie. scan) that open the main tables to add records.

Version 4.3.10

-------------------------

(NEW FEATURES)

1) SQL Server support is now available and is enabled by default. If enabled, the user will be forced to choose the database backend for all new cases. When specifying a SQL Server backend, you must specify the name of the SQL Server (computer name where SQL Server is installed). To use the current Windows user for database access, you may check the ‘Use Windows NT integrated security’ setting under the server name. If using this setting, when creating the case, the current user must have database create permissions. If not using this setting, a default username/password (LAW_User/law32sql) will be used and must be created on the SQL Server. This mode requires that the security mode on the SQL Server be set to 'SQL Server and Windows' or mixed-mode authentication (See the SQL Server documentation for instructions on how to do this). NOTE: If your site does not have SQL Server available, SQL Server support can be disabled by unchecking the ‘Enable SQL Server/MSDE support’ option on the Preferences tab of the general options dialog.

2) A new endorser has been added that is 3x faster on color images, and much more stable than the previous endorser. This new endorser requires the latest image libraries to be installed to avoid a potential bug. The latest image libraries are available for download at ./Law40/pixel72.exe.

3) PDF OCR and OCR word location information (*.ocr) files are now automatically merged and split during the merge and split document functions.

4) Opticon load files are now supported for import.

5) DocuMatrix has been added to the list of supported export formats.

6) Export utility now has ability to merge parents and their attachments. To enable this feature, check the 'Combine parents/attachments' setting on the Options tab of the export utility. **WARNING: This feature is currently only recommended for PDF-only exports or exports without the need for OCR text. It does not currently support merging of text-based OCR. It will also automatically merge all attachments for any selected parent, regardless if they are included in the current recordset, if performing an export based on a query.

7) A custom configuration dialog has been added for the PDF export. Custom settings include the ability to create bookmarks for merged documents (using the 'Combine parents/attachments' setting) and populate PDF metadata. Bookmark captions can be set individually for the parent and attachments based on index fields. Metadata for the Title, Subject, Author, and Keywords fields in the PDF document can be mapped to index fields as well. NOTE: Metadata is currently only populated when merging parents and attachments.

8) Added ability to number pages exported to IPRO with proprietary IPRO annotations. This feature can be enabled from the IPRO custom configuration dialog in the export utility.

9) An updated Expervision OCR engine is now available and can be downloaded at ./Law40/openrtk7.exe. This must be installed on all OCR stations. If running a shared installation, the file can be saved to the Law32 folder and LAW will automatically install it on all stations sharing the same executable, provided the user has administrative privileges.

10) The ability to create thumbnails in PDF OCR is now optional. This feature can be enabled/disabled using the 'Create PDF thumbnails' setting on the OCR tab of Options dialog. NOTE: This requires version 7 of the Expervision OCR engine.

11) Deskewing images before OCR is now optional when using the Expervision OCR engine. It can be enabled/disabled with the 'Auto-Deskew' setting on the OCR tab of Options dialog.

12) Added XP theme support.

13) A grid view of the current folder can be opened by selecting Folder -> Grid View from the main form. This function is not recursive; it only selects records in the immediate folder.

14) Multiple folders can be auto-created by selecting Folder -> Auto-Create N Folders.

15) An option to endorse only the first page has been added for the batch endorse process. This option is only supported with the new endorser. **WARNING: If the first page contains annotations, they will be lost.

16) Added new setting to hide annotations on printed images. To prevent printing of annotations on printed images, check the ‘Do not print annotations’ option on the batch print options dialog.

17) A modified JFS export format has been added. The alternate format lists only exported field names (per line) with the corresponding field value. This modified format can be specified by selecting 'Use alternate format' from the JFS fields tab of the export utility.

18) The Ringtail export now has option (available on Ringtail configuration dialog) to 'Allow long folder names (over 20 chars)'. This will disable the default behavior required by Ringtail to force each folder level to be 20 characters or less. **WARNING: Ringtail does NOT officially support folder lengths over 20 characters. This setting is NOT recommended.

19) The export status can now be logged by assigning the results to a specified index field. Logging can be enabled from Options tab of export utility. Status will be logged as "Y" for success, or "E" for error. The option to 'Reset export status' can be used to clear the export status before beginning the export, setting the value to "N" for all records in the case.

20) "PDF (Image Only)" has been added as a new output format for export settings (Options tab). Selecting this format will force LAW to save an image-only PDF during the export process.

21) Barcode break sheets may now be dropped and ignored during the scan phase if desired by specifying the values to be ignored in the barcode values section of the Options dialog (Tools -> Options) of the main form. Multiple values to ignore may be specified by separating them with a semi-colon.

22) Insert functions are now supported for records without images.

23) Changing records without saving index changes will now prompt user for action.

(BUG FIXES)

1) 'Reset at each folder' option for auto-numbering does not work on multipage exports.

2) Deleting records from grid view does not update attachment information.

3) Inserting new pages from scanner inserts first page before current page and remaining pages after the current.

4) Deskew filter for OCR can shift portions of image very near edge of page off of the page if a significant skew is detected and corrected.

5) Summation export does not use proper @FULLTEXT token when exporting single page OCR.

6) Importing raw images with 'Mirror original structure' enabled will fail to retain the folder structure of folders under a parent with a pound sign (#) in the name.

7) Rename Folder will allow the user to specify a folder name ending in period, which is invalid in Windows. When the folder is actually created, the period is dropped without error, resulting in a path in the database that does not match the actual name in Windows, causing the images in that folder and below to “seemingly” disappear.

8) Compact Database function may fail on some systems with ADS cases.

9) Endorsed watermarks aligned to any corner but top left do not position correctly if the watermark image is a different resolution than the image being endorsed.

10) IPRO export uses incorrect image type for JPEG and PDF images.

and various other minor fixes...

(MODIFICATIONS)

1) Quality setting for OCR has been modified for the Expervision engine (this setting was previously ignored). New values include: Normal, Normal (Degraded), Dot Matrix, and Dot Matrix (Degraded). The "Degraded" settings force the OCR engine to spend longer on degraded documents, which may yield additional recognized text, but can significantly slow the OCR process if there are a large percentage of degraded documents.

2) Parents and attachments are now grouped together in the same partition if exporting in volumes, as long as they are sequential in the selected set.

3) Added A4 page size to set of predefined scanner page sizes.

4) Summation control list export (from grid) now defaults to long file names. If necessary for Summation 5.21, short file naming can be re-enabled via ini setting.

5) Index fields now accept drag-n-dropped text from the OCR tab or other applications.

6) Query builder now contains the ability to group clauses and edit existing conditions in place.

7) 'Page ID/Numeric' file naming scheme for export utility has been modified. It now uses the rightmost numeric portion starting with the first numeric digit. For example, a Page ID of "ABC_001_001" would be exported as "001_001.tif". The prior scheme, which searched from the right, would have yielded "001.tif", which can easily lead to duplicate names if Page IDs with multiple numeric portions separated by non-numeric characters are used.

Version 4.2.42

-------------------------

(NEW FEATURES)

1) Case templates can now be assigned to existing cases. To apply a template to an existing case, open the case and select File -> Administration -> Apply Case Template.

2) New field selection dialog has been added to the grid view to make field selection easier. A field list will now be displayed when selecting the 'Fields' menu item, or right-clicking on a column header. The last used view for each case will also now be saved for each workstation.

3) Summation export now has a configuration dialog with several new options. Select Summation from the list of selected export formats and press the [Configure] button to display the configuration dialog. New settings include support for advanced (iBlaze compatible dii files) that can include unlimited index (@C) fields, and OCR text directly in the dii file (**WARNING: Inserting OCR text directly in the dii file appears to have bugs in Summation. Formfeed characters to delimit text pages are not supported, and you may receive errors about unsupported operations, although all the data does appear to get imported). There is also an option to force all index fields into a separate delimited text file, and to optionally include field names as the first record. The data delimiters for the delimited text file can be set from this dialog as well, allowing Summation to now have its own delimiters separate from other formats. The dii path notation is also set from this dialog, and no longer located on the Options tab.

4) The IPRO export now has a configuration dialog. Select IPRO from the list of selected export formats and press the [Configure] button to display the configuration dialog. There is a setting to include index fields, include OCR word information (requires images to be OCR'd with Expervision engine), place the OCR information in a separate LFP file, use new folder flags (DocBreak=F) for document breaks at the start of new folders, and write path in volume notation. If option to write path in volume notation is unchecked, a full path (with drive letter) will be used, and no volume will be specified. If specifying index fields, press the [Edit] button to configure the selected fields. Fields may be included as tag/issue (IS) fields, or information only (IO) fields. NOTE: The fields exported with IPRO are independent of other formats, so they must be specified directly, and not on the default Fields tab.

5) Concordance export now has option to include OCR text directly in the load (DAT) file. This option can be set from Concordance's configuration dialog.

6) Ringtail export now has a configuration dialog and several modifications have been made to the Ringtail export. The OCR text is now included (by default) as a separate file, and not directly in the database. The previous method of placing the OCR text in a field however can still be accomplished by selecting the ‘Include OCR text as a field in load file’ option from the configuration dialog. Special OCR page markers can also optionally be inserted or replace any existing OCR page markers. Folder levels will now have spaces replaced with underscores and be truncated to 20 characters so they do not exceed the Ringtail limitations.

7) Summation imports (*.dii) now support @C fields for populating index information. If index information is detected, the user will be given the choice to include it, and any necessary fields will be auto-created. In the event that an incoming fields conflicts with a system field, it will be named "<Field Name> (dii)". Attachments are also supported, provided that each attachment contains a "@PARENTID" token, or an "@C PARENTID" field with the image tag of the parent document.

8) A document page limit may now be forced during batch scans. This will limit the number of pages scanned per document. To set this limit, select Scan -> Scan Options -> Scan Page Limit from the main form.

9) A 'SourceApp' field has been added to the 'E-mail (Default)' case template. This is a list field with the names of all supported Z-Print applications used for printing. It will be populated during Z-Print imports if this field is present. This field may be used within LAW to change the application used to print a document. When updating Z-Print flags for printing, if this field is present, you will have the option to update this field as well, enabling LAW to override the print source that was previously set from within Z-Print.

10) Alignment setting has been added for endorsing with watermarks. The watermark can be aligned to any of the four corners of a page, and may be set from the watermark selection dialog (Options -> Watermark from Batch Processing form).

11) The ability to move pages within a multi-page document has been added. To move a page (or pages), select the desired page(s) from the thumbnail view and once the pages are highlighted, left-click on any of the selected pages (the icon will change) and drag the cursor to the selected insertion point (notated with solid bar between thumbnails). **WARNING: This does not currently move any page information (page id, header/footer size, etc.), so pages may need to be renumbered after the move. Also note that since header/footer size info will not be moved, pages should ONLY be moved within a document in which all or no pages have been endorsed with the same settings, or unexpected results may occur if re-endorsed.

12) Z-Print import has new option to ignore unflagged documents during the import. If this option is set, all records in the log with a Status value of N (do not print) or D (duplicate) will be skipped during the import process. To access this option, press the [Options] button after selecting a Z-Print log file to import.

13) LAW can now scan all pages of the current document for any barcode values. To access this feature, select Tools -> Barcodes -> Scan All Pages from the main form. All pages of the current image will be scanned, and any recognized barcodes are saved to a delimited text file in the structure: Value, Page, BarcodeNo. If no region is active, the entire page will be scanned. If a region has been created, only this area of every page will be scanned.

14) A new export folder-naming scheme (Custom) has been added to the export utility. This custom scheme allows you to define the export folder levels with index fields up to 3 levels deep. When selecting this scheme, at least one level must be specified, and at least one folder level value must be non-blank, or an error will be logged and the document skipped. To specify the folder levels, press the [Edit] button below the folder-naming scheme once "Custom" has been selected.

15) The auto number file-naming scheme of the export utility has a new optional setting to force it to restart at an initial value for every new folder. To enable this feature, select "<Auto Number>" as the file naming scheme, and check the 'Reset at each folder' setting below it.

16) A new export field has been added for bates range (<Batesrng>). This field will be in the form "<Begdoc#> - <EndDoc#>".

17) The query tool now has option to include attachments with query results. When this option is selected, if the parent is a match, all of its attachments will be returned also regardless if they match query condition. **NOTE: Due to the nature of this query, setting this option may take significantly longer to return than without it on large cases.

(BUG FIXES)

1) Large text files split into multiple parts when printed to TIFF via Z-Print are not imported correctly during a Z-Print import.

2) Pre-export scans for blank image tags and page IDs do not ignore native documents (records without images) which can prevent an export from proceeding.

3) Text versions of e-mails are not imported from Z-Print if the text was extracted during the pre-save process, and the e-mails were printed as single-page.

4) Summation export (single page) causes "Overflow (6)" error if the numeric value of the exported image paths exceeds the maximum value of a long integer (2,147,483,647).

5) OCR word information files (*.ocr) and PDF w/Hidden Text OCR files (*.pdf+) are not included with case imports or move operations within a case.

e) Commas in OCR text cause problems with the OCR word list created during an IPRO export.

6) An extra field (for rotation value) at the end of a page record in an IPRO load file (*.lfp) causes the page to be skipped during an IPRO import which can result in missing pages and incorrect document boundaries.

7) Unable to display print setup in batch print options for a printer name with quotes in it

8) Deleting multiple pages of a document and then moving to a new document and trying to highlight another page can cause a "Bad Node Index" error.

9) Selecting multiple documents to attach can allow a document that already has attachments to be attached to another document. This may appear to work, but will give unexpected attachment values on export. This situation can be correct using the Validate Attachments function.

10) Inmagic export may use incorrect path if Hard Path or UNC path is selected

11) Raw image import function can cause an "Invalid procedure call" error if selecting folders and 'Include subfolders' setting is not checked. Also, checking a root drive letter to import causes folder creation errors due to invalid folder names and prevents import (only present in version 4.2.41).

12) Summation export may incorrectly list last image path (using name of previous file twice) if no sequential naming scheme is detected.

13) If the first image in an export will cause the export path to change due to the specified partition size limit, the images will be exported to the new (correct) path, but the data will be logged to the load files of the previous partition. This was only present in version 4.2.41.

(MODIFICATIONS)

1) All OCR text is now converted to ANSI during the export process.

2) Ability to view attachment information from the grid view (View -> Attachment fields) has been extended to support ADS databases.

3) Maximum number of index fields has been increased to 100.

4) Updating Z-Print flags for printing will now also reset the file attribute of the source documents to Normal if the documents are available. This prevents having to manually locate the source documents and un-hide them if they need to be re-printed.

5) The Scan for Errors function has been enhanced to allow scanning of all documents, or just the current folder (and optionally subfolders). The selected scan settings are now also maintained between sessions, and a new option to ignore native documents has been added to prevent native documents (records without images) from being repeatedly scanned and logged as errors.

6) Header/Footer strings may now contain leading and trailing spaces to assist in positioning text for special alignment. NOTE: If trying to position text using spaces, it is easiest to use a font like "Courier New" in which all characters are the same width.

7) Admin licenses now provide access to page (bates) numbering functions

8) Enhanced image merge process to speed resaving of single page files during the endorse process and the Z-Print import. The File -> Save As function has also been enhanced when resaving the file offering tremendous speed improvements, most noticeably when saving large images (200+ pages) to PDF.

9) UNICODE text files (as may be imported from certain versions of Z-Print) can now be displayed properly in the OCR tab. NOTE: UNICODE characters (ie. Asian fonts) are not supported for display in the OCR tab.

10) The 'Build Control List' function (available in grid view) will now name the exported text files (if exporting and not linking directly) as the BegDoc#. It also now allows for sequential folder numbering for exported files to keep a reasonable number of files per folder (default is 1000).

11) Splitting images (TIFF only) to single-page format during the export will force greyscale pages to JPEG (for better compatibility with older image viewers that may not support TIFF w/JPEG compression) if the 'Output Format' setting is set to 'Default'.

12) The partition size for an export is now only calculated once, when the export is ready to start. This avoids potential long delays when loading the export utility and changing export paths. The size calculation is also now skipped entirely if the partition size is set to 0 (unlimited). The method for calculating the size has also been modified to reduce calculation time, when necessary.

Version 4.2.41

-------------------------

(NEW FEATURES)

1) Pre-saved Z-Print e-mail jobs may now be imported without images, and the original documents can be linked to directly from LAW. If a link to the original document is captured (via the ‘NativeFile’ field), a hyperlink will appear below the image. The Z-Print job can then be updated by performing a query, and selecting Tools -> Update Z-Print Flags from the query results form. All records in the current set will have their print flags updated, enabling Z-Print to print only the desired documents. Once the specified documents have been converted to TIFF using Z-Print, the same log file may be re-imported, and LAW will update the existing records with the new images.

NOTE: Records without images cannot currently be exported or batch processed. Errors/warnings will be logged for these records if they are included in these functions.

2) The Expervision OCR engine now saves word information to a separate file (<image>.ocr) and can export this file to the Storm viewer to allow hit highlighting directly on the images. This also allows creation of an IPRO load file with OCR information to allow hit highlighting in the IPRO viewer.

3) The raw image import function now allows detection of document breaks via barcode values or blank pages. If using barcode values, you can further specify to capture any other barcode values (found on a break sheet) in index fields by selecting the option and the first field to receive the values (all other barcode values will be stored in sequential index fields starting with the specified field).

NOTE: Folder and attachment breaks are not currently supported, ONLY document level breaks.

4) The raw image import function now allows forced conversion to binary (B&W) during the import.

5) LAW’s image viewer now supports TIFFs w/LZW compression, and GIF files.

NOTE: Due to UNISYS patent restrictions, this only applies to customers in the United States. This restriction will be lifted on June 20, 2004 for European customers, and July 7, 2004 for Canadian customers.

6) The Concordance export now has its own configuration dialog to control the data delimiters used in the export file, as well as an option to include the field names as the first record. To open the configuration dialog, select Concordance in the 'Selected Formats' list of the export utility, and press the [Configure] button.

7) Auto-rotate functionality during OCR for Expervision engine is now optional and may be toggled from the OCR tab of the Options dialog. It can be set to "Always OFF", "Always ON", or "Binary Images Only". The last setting can be used to auto-rotate black & white images only, which can help prevent color and greyscale images, with little or no text, from being improperly rotated.

(MODIFICATIONS)

1) The Z-Print import now supports single-page images. However, they are merged into multi-page images during the import, so it can be more time consuming than multi-page imports.

2) The batch processing status dialog has been modified. It now displays the exact position in the job, elapsed time, estimated time remaining, and real-time error information. And when complete, the elapsed time, total pages processed, and average speed will be reported.

3) Empty OCR text files (as may occur when importing documents that were OCR'd outside of LAW, or imported from Z-Print using text extraction) will now be detected and replaced with the default OCR text file during the Summation export.

4) Summation export now screens exported OCR text files for a special condition (No CR+LF in first 256 characters) that prevents Summation from detecting them as OCR, and will correct if necessary.

5) Importing raw images using the 'Mirror original structure' setting will now import only the relative structure from the topmost selected folder(s).

6) Increased MaxFileSize of common dialog for insert existing pages operation to allow greater number of files to be selected.

7) Changed line continuation character for Inmagic DB/TextWorks export from a space to the ">" character for embedded OCR text. The ">" character serves as a hard line break in the Inmagic field, which helps to preserve formatting in the OCR text.

8) Modified Summation export so that the <EndDoc#> and <PgCount> fields will only be forced in the dii portion of a multi-file export (dii and txt) if multi-page images are exported.

(BUG FIXES)

1) Temporary files used for endorsing images were not being removed until LAW was closed. This could cause the local disk to fill on extremely large batches, or if hard drive space is very limited.

2) The export utility now checks the current partition size before exporting the next image to determine if that image would cause it to exceed the specified limit. This prevents extremely large images from creating partitions too large to be burned to CD.

3) Data exported to Concordance no longer replaces carriage returns with semi-colons.

4) The raw image import may order incoming images incorrectly if multiple folders on the same level are selected due to slow database writes.

5) Jumping from folder to folder using the up/down arrow keys in the document list may jump to wrong folder (ADS cases only) due to case-sensitive sorting.

6) ADS cases will allow you to appear to successfully rename an existing index field to another or a system field, while in reality, it will generate its own unique name, typically <Field Name>_1 without raising an error. This will cause LAW to believe it has an index field of the specified name, and can lead to very strange results, and possibly render a case unusable until the field names are corrected.

7) The <Attachmt> field may exceed the maximum length of a text field in the Ringtail export and cause errors on every subsequent record. This field is now logged as a memo field in the event it exceeds 255 characters (max length of text field).

8) Creating more than one ADS case in a row fails

9) The auto-size batch print setting may not work correctly for 11x17 pages if "11x17" is not a supported paper size of the specified printer (some printers support 11x17 as "Ledger" or "Tabloid"). The appropriate setting will now be automatically detected from the printer driver.

4.2.39

-------------------------

(BUG FIXES)

1) Delete Folder will fail after the first deletion if trying to delete multiple folders with same parent.

2) Delimited Text export does not display column headers for Image, OCR, Page, or Page ID fields.

3) Deleting pages after a new scan (or insert/append) may result is improperly numbered pages.

4) Importing multi-page documents from load files may result in only last page of document being imported. The process has also been optimized to speed the import process by not rebuilding images unless absolutely necessary.

5) Resolved occasional automation/assertion errors during endorse process (primarily with color pages).

6) Attempting to batch process from the 'Un-endorsed Images' predefined query in the database grid results in an error attempting to calculate the document/page count for processing.

7) Modified sort order for ADS queries to make text sorts case-insensitive in the grid display as well as the All Records processing query.

8) Importing IPRO load file (*.lfp) may result in documents being placed in wrong folder if first document in a folder contains attachments.

9) Importing Doculex/Summation load files into existing folders may cause improperly ordered documents.

(NEW FEATURES)

1) 'Retain color' setting has been added to export options (Options tab) to allow color in annotations to be preserved when merging annotations. NOTE: This requires changing the color format of the page and may significantly increase the size of the images.

2) New Batch Process: Scan for Suspect Footers. This feature scans all pages for suspect footers (those appearing to be 1" or larger) and will flag an index field with Y if any pages in a document contain suspect footers, N if not.

3) Added <ParentID> to list of pre-defined fields for export. This field contains the BegDoc# of the parent document for all attachments.

4) Added ability to run custom commands from Tools->Run Command menu. Custom commands are straight executables that may run custom defined functions on a case. The connection string to the current database will be passed to the executable so that it may open and manipulate the current database. All command executables must be located in the <AppPath>\Commands directory in order to be detected. The file description of the exe will be used as the menu item name, or the filename without extension if no description exists. NOTE: Custom commands may be created by customers, but Image Capture Engineering assumes NO responsibility for any damage done by a user-defined command. See the LAW help file for more information about this feature.

5) Added new increment mode setting: Manual (Auto). This is equivalent to the original manual mode in which the user will be prompted for a starting bates number whenever a new scan is started, but not in the middle of a batch if break sheets are used. The 'Manual' mode has been modified so that whenever a new document is encountered, the user will have to verify the starting bates number, even in the middle of a batch scan.

6) Added ability to auto-size paper based on page size during batch printing (Batch Process… -> Options -> Print Options). Currently, the only supported page sizes are Letter (8.5x11”), Legal (8.5x14”), and Double-Letter (11x17”). ** NOTE: When this setting is used in conjunction with the ‘Send job in batches of N pages’ setting, the separate jobs are printed to file and remerged as one complete job at the printer. Being pooled in this way allows slipsheets to be pulled from an alternate tray, something that is NOT currently possible when the ‘Send job in batches of N pages’ setting is used alone.

(MODIFICATIONS)

1) Hole Removal filter has been disabled due to possible false identification of holes resulting in loss of actual image data. Support for this filter will not be re-added until a fix has been provided and thoroughly tested.

2) Modified Summation export to write the <EndDoc#> and <PgCount> fields to dii file if number of selected fields (7 or more - not including image tag) causes a 2 load file export to be created. If these fields are not written to the dii file, the default behavior in iBlaze 2.5 and higher is to automatically create an EndDoc# and page count during the dii import, which will be incorrect if a multi-page image export is performed.

3) Ringtail export will now specify "PICK" as the field type for exported list fields. Also, hard returns (CR+LF) in memo fields will no longer be replaced with semi-colons.

4) When scanning in Turnover mode, if user cancels before scanning backsides, the pages of front side will not be re-ordered. Turnover mode setting is also now ignored if scanning from the flatbed.

5) 'Extract as Subset' feature has been modified to support ADS cases also.

6) PDF conversion during export has been modified to enhance speed and stability.

7) Additional indexes added to Storm database on export to enhance performance. NOTE: Other modifications for security purposes have been added that require Storm v1.2.1 or higher to access the export sets.

8) Added ability to customize page markers for OCR text, currently only via law32.ini file in <Windows> folder (Key=OCR, Section=PageStampText). If any string is detected, it will override the page/bates settings specified in page marker setting, and only the position mode will be used. Special codes (same as header/footer) may be inserted for replacement at page level: &[page] = page, &[pages] = page count, &[page id] = bates number, &[BegDoc#] = Beginning document number.

9) Number of lines per header/footer has been increased to 8.

10) All documents (including single-page documents) will be split prior to the endorse process. This allows endorsing of pages previously not supported due to compression problems. NOTE: This may cause the loss of the original page color/compression format. Howerver, optimal settings (on a page by page level) will be used when recreating the image (ie. B&W pages will always be saved with Group 4 compression, 24-bit color with JPEG, etc.)

11) Titles for separator pages may now be specified via law32.ini file (global shared setting): Section=Slipsheets, Items=HeaderText|FooterText. NOTE: Sections of text are separated by the pipe character (|), ie. HeaderText=LEFT|CENTER|RIGHT would print LEFT as left-aligned, CENTER in middle, and RIGHT as right-aligned.

12) OCR Region functionality has been enhanced. The results can now be directly sent to an index field, and optionally parsed into name/value pairs (ie. DocType=Fax, DocDate: 12/31/2001). Multiple lines will be parsed and field names and values can be separated via colons (:) or equal (=) signs. Region behavior has also been enhanced for easier accessibility. Right-clicking on an active region will pop-up available region functions, and holding the CTRL key is no longer required to move or resize a region.