Summary

This article documents some general information regarding Laserfiche Quick Fields 7.0.

• When using tokens to determine the name, path, or field data that will be assigned to a document, you should keep in mind that most tokens are replaced when the document is created in Quick Fields. Tokens are not updated at any other time. The exception to this rule are index card field tokens generated by a document class. These tokens are not replaced until the document is sent to a Laserfiche repository. This type of token should not be confused with the index card field tokens that are generated by Laserfiche Capture Engine. Tokens generated by Laserfiche Capture Engine are replaced as the document is created in Quick Fields.
• Whenever a data extraction process has been deleted, you should also remember to remove any references to the deleted data extraction process (tokens) from all applicable document class settings. Otherwise, you may accidentally populate an index card field, document name, or document path with incorrect data. This type of situation occurs when a new data extraction process with the same name is created. (5417)
• We do not recommend loading Quick Fields during a time period for which documents are scheduled to be sent to a Laserfiche repository. Although we do not anticipate any issues resulting from this behavior, it will cause Quick Fields to perform sluggishly. (5614)
• The Automatically crop black borders feature is only meant to change black borders into white borders. This feature can only be performed on an image whose background color is white. If you would like to remove a black border from an image whose background color is black, then you can invert all of the colors in the image, perform white border cropping, and then invert the image back to its' original colors. (5071)
• Quick Fields keeps track of all scheduled documents that are not sent to a Laserfiche repository in a log file called "QFError.log". This error log can be found in the temporary directory assigned to the user assigned to the scheduled task.
• Among other duties, a document class determines the name of the document that will be generated and the Laserfiche folder to which it will be sent. Document and folder names cannot contain backslashes (\). If the document name contains a backslash, it will not be sent to the Laserfiche repository. If a folder name contains a backslash, the latter half of the folder name will be treated as a different folder. For example, the path "MyRepository1\My \ Folder" would specify three different folders (MyRepository1, My, and Folder). (5735)
• If the Validate folder structure option is enabled for a processed document, then it can only be sent to a valid Laserfiche folder. If the folder currently assigned to the processed document does not exist in the Laserfiche repository, then you may either create it with Laserfiche or you can change the assigned folder. The folder can be changed by simply selecting it from the tree and then type or browse to the new folder from the Laserfiche Folder task pane.
• Windows 2000, Windows XP, and Windows Server 2003 require a user account for scheduled tasks. If your session has been configured to send documents at a scheduled time and a valid user account has not been specified, then scheduled documents will not be sent to the Laserfiche repository. Scheduling options can be configured from the Schedule tab of the Session Settings dialog box. This dialog box can be opened by selecting Session Settings from the Tools menu. (5772)
• Laserfiche Quick Fields generates data files while processing images into documents. After your documents are stored in a Laserfiche repository, these data files are removed from your computer. A session's data files should never be moved. Moving a session's data files will cause your session to stop displaying processed documents. Although the data associated with your processed documents has not been physically lost, you will not be able use Quick Fields to access the data or send it to a Laserfiche repository. If you would like to store data generated by a session in a different location, then you should first send all processed documents from the desired session. You should then manually move the session file (.qfs) to the desired folder using a file management application. Whenever the session is used to process images, it will use the new location to store temporary data files.
• If a data extraction process retrieves inaccurate data or no data at all, then you should try using image enhancement or local image enhancement processes to optimize the conditions under which data will be extracted. For example, if a bar code is not recognized because it is too large on an image, then you may temporarily resize the image to a smaller size using the Resize local image enhancement process. After the bar code has been recognized, the modified image will be discarded and the original image can be used to perform additional processes.
• Bar Code uses proprietary software. Licensing information for the proprietary software has been provided on the Bar Code installation CD. The file is called TCL-TK_License.txt