Known Issues with Quick Fields 7.1.

January 11, 2005 | KB: 1000842
Quick Fields 7.1

Summary

This article documents known issues with Quick Fields 7.1.

More Information

Quick Fields Known Issues:

1000855 A "Cannot write to file." Error Occurs During OCR. (18063)
1000856 An "Unexpected File Format" Error Occurs When Opening a Session. (17712)
1000857 Laserfiche ScanConnect is Not Available After Reinstalling Laserfiche Quick Fields. (16498)
1000858 Reinstalling Quick Fields can Reset Quick Fields Agent Log File Configuration Options. (18343)
1000859 Reinstalling Quick Fields Can Prevent the Quick Fields Agent Icon From Displaying in the Taskbar Notification Area. (18335)
1000707 Uninstalling Laserfiche Scanning can Disable Laserfiche Quick Fields.
1000708 Uninstalling Laserfiche Quick Fields After Upgrading to Quick Fields 7.0 Can Disable Laserfiche Scanning.

  • Photo Capture may encounter issues when scanning large numbers of documents from multi-sessioned burned DVDs. (18281)
  • The Class Manager occasionally is not displayed. Reopen the session to resolve the issue. (17974)
  • Changing the tags for a document class does not prompt you to save the session. For example, if you open a session, select a document class, select a new tag, and close the session, you are not prompted to save the session. (17918)
  • The ability to zoom in by selecting a region can be occasionally disabled after you test a process. (17891)
  • Sending or deleting a large number of documents (over 50,000) can result in the tree pane not displaying. Reopen the session to resolve this issue. (17799)
  • Quick Fields may not uninstall correctly on a Windows 98 or Windows Server 2003 computer. If this occurs, then you should try uninstalling it again. (10768)
  • The shortcut key to toggle the status of the Task pane was changed from F2 to F4. Occasionally, pressing F4 may not toggle the task pane. If this occurs, then you can toggle it by selecting Task Pane from the View menu. (10754)
  • The Dynamic Thresholding image enhancement currently doesn't support the Optimize for shaded backgrounds option when processing regions. (10439)
  • Certain special characters will not display correctly in the Browse Folders dialog box. However, this is only a display issue and it should not affect the performance of Quick Fields. (10240)
  • Installing certain scanner drivers may cause older scanners to invert black and white TIFF images. (8494)
  • Quick Fields may become unstable when the drive on which a session resides runs out of disk space. If this occurs while images are being captured into Quick Fields, then you may lose up to the five most recently scanned images. (7526)
  • Closing a session while the task pane and output pane are undocked will cause the tree pane to cover the entire window the next time that a session is opened. If this happens, you may simply drag the right edge of the tree pane back to its original position. (6720)
  • Certain words are reserved for use as tokens within Quick Fields. The name of a process in your session should not be any of the following words: Count, Date, Name, Path, and Time. (6674)
  • If the data assigned to a list field does not exist in the list, a blank value will be assigned to the field instead of the default value for that list field. (6643)
  • When using a session across multiple workstations, you may encounter the following issues:
    • If a session will be opened from a different workstation, then you should make sure that the path used to open the session matches on both computers. If a different path is used to open the session, then you may incur data loss.
    • If a session is opened from a different workstation and the session had been previously configured to send documents at a scheduled time, then the session's scheduling options will be reset to deliver documents manually to a Laserfiche repository. If the session is saved, then whenever the session is opened it will appear as if the session's scheduling options have been changed. However, the workstation from which the session was originally scheduled may still send processed documents at the scheduled time.
    • A new installation of Quick Fields on a computer running Windows 98 may generate an error when the application is being loaded. If this occurs, then you should uninstall Quick Fields and then reinstall it. After reinstalling, Quick Fields should load normally. (5386)
  • When using Laserfiche Quick Fields with a local repository (version 6.02 or lower), you should not attempt to send documents while Laserfiche Capture Engine is retrieving documents from a Laserfiche repository. This will prevent your documents from being properly retrieved and sent back to the Laserfiche repository. This type of configuration occurs when using Laserfiche Capture Engine along with the "Send documents to their destination immediately" option. If you currently have this type of configuration, you should change the delivery schedule to manually send documents or to schedule your documents to be sent after all your documents have been processed. Scheduling options can be configured from the Schedule tab of the Session Settings dialog box. This dialog box can be reached by selecting Session Settings from the Tools menu.
  • When a data extraction process is deleted, the corresponding token is not removed from any settings by which it was being used.
  • Most processes allow an administrator to preview the result of performing a process on a sample image. International OCR, Real-Time Lookup (Field Verification), and Form Registration (Forms Processing) processes are exceptions. Although the Test Process link is available, these types of processes can't be tested. (4905)
  • Structural changes made to a template are not applied to document classes or processed documents. This may have varying effects, including field data loss, depending on the type of change made to the template. If a change has been made to a template assigned to a document class, then you may update the structure of the template by performing the following steps (4562):
    1. Select the Document Properties tree item for the desired document class.
    2. From the Document Properties task pane, click Modify Destination Properties.
    3. Proceed through the wizard. Upon the completion of the wizard, the template assigned to the document class will be updated.
  • If the name of a Laserfiche document contains a backslash (\), then it will not be retrieved by Laserfiche Capture Engine. If the name of a folder in the path from which documents will be retrieved contains a backslash, then no documents will be retrieved from the specified path. If you would like to process affected document(s), then you should rename the offending document or folder so that the name no longer contains a backslash. A document or folder can be renamed through the Laserfiche Client. (5916)
  • A user will not be allowed to browse to a Laserfiche folder whose name contains a backslash (\). If you would like to browse to such a folder, then you should rename the offending folder so that the name no longer contains a backslash. A folder can be renamed through the Laserfiche Client. (6011)
  • The Rescan feature has not been implemented for Laserfiche Capture Engine. As a result, the Rescan option will not be available when the scan type for the session has been set to Laserfiche Capture Engine.
  • When a field of type date in a processed document is assigned an invalid date and a two digit year format is used, then the day, month, and year will be switched around until a valid date is created. For example, if the value "Sept 31, 02" is assigned to a field of type date, then the date would be converted to "09/02/1931". (6014)
  • Field status specifies whether a field has been assigned a valid or invalid value. Field status is only updated during document processing. Modifying a field value will not toggle the status of the field.

Quick Fields Agent Known Issues:

  • Renaming a scheduled task can causes it to lose its history. (18258)
  • The Scheduler window may flicker when started. (17797)

Real-Time Lookup Known Issues:

  • Dynamic field lookup only works on the original processed document. If the processed document is split, then dynamic field lookup can only be performed on the original processed document. (10830)
  • Modifying the data for a field designated as a Lookup field will not update Lookup tokens used to specify the document's name or destination (Laserfiche folder). (8337)
  • A dynamic field lookup cannot trigger another dynamic field lookup. In other words, a Lookup process will not be activated when a field designated as a Lookup field is updated due to dynamic field update. (8345)
  • Modifying the data assigned to a field that has been designated as a Lookup field will append updated repository information to the fields marked for population. (8341)
  • The default database configured for a SQL Server System DSN will only be saved for the current Windows user. If a Real-Time Lookup process uses such a System DSN and the default database has been configured, then all other Windows users on the current machine will receive an error when attempting to use the Real-Time Lookup process. Additionally, the configuration for that process may be partially cleared. If this occurs, you may resolve it by reconfiguring the Real-Time Lookup process to use the desired SQL Server System DSN. You will also need to set the default database that will be used by the SQL Server System DSN. (6703)
  • When the data source used by a Real-Time Lookup process is not available, then Quick Fields will momentarily become non-responsive. (6678)
  • When using Real-Time Lookup with an Excel database to look up numbers, columns containing mixed data types will not return data. (5699)
  • When using Real-Time Lookup with an Excel database, date values will not be returned when the column from which data will be retrieved contains more character than date entries. (5699)
  • An Excel file that has been specified as a data source for a Real-Time Lookup process should not be opened while a Quick Fields session that uses it is open. Opening such a file may cause configuration issues inside of the session. (6514)

Universal Capture Known Issues:

  • Scanning files with Universal Capture may occasionally generate a spurious error (Error: ImgSnow error: -2). If this occurs, then you should simply resume scanning. (10914)
  • The Scanning inactivity has exceeded n seconds option does not retrieve files that are placed into the capture (Look for images in) folder during the n seconds of scanning inactivity. All files that are placed in the capture folder during the n seconds of scanning inactivity can be captured when the user resumes scanning. (4967)