Ascent Advanced Forms 3.8 Validation Module SR01 SP3

New Features

This Ascent Advanced Forms 3.8 Validation Module Service Release 01 SP3 provides the following new features.

• Documentation has been updated to support the new service pack features.

This Ascent Advanced Forms 3.8 Extraction Module Service Release 01 SP3 provides the following new features.

• A new version of the online Help and User's Guide document the new service pack features.
• The Invoice Totals field can now read negative amount values and be used to process credit notes. (SPR 18303)
• The BetweenKeys field can now be used as the value field of a KeyValue or KeyMultiValue field. The start and end key areas are, in this case, the same as the search area of the field.
• Invoice option fields InvoiceNumber, InvoiceDate, InvoiceTotals, and InvoiceVendor have been extended for processing invoices from the Czech Republic, Slovakia, and Slovenia.
• The Date field can now detect date values that do not contain separators (for example, 20112006). The former property SeparatorExistence has been replaced by a new property SeparatorAppearance with the values "character," "blank," and "none." The "character" and "blank" values correspond to former property values "mandatory" and "optional," respectively. The Date field uses the "none" value to detect date values that do not contain separators.
• The Document Type Wizard that opens when you choose the Add Types & Classes from Directories command from the context menu on the Types tab in the Project Explorer view now allows you to automatically create a new document class for each document type.
• The new image preprocessing function RepairMatrix allows you to repair broken dot matrix characters. A special filter allows you to extend or connect separate dots so that character recognition performance improves.
• The width of the File menu can be optionally extended so that it always shows the complete path of available projects.
• For performance reasons, the Regular Expression field returns the first found match for the first alternative when you specify alternative expressions using the "|" operator and set Occurrences to "first." If you want to find the first match on a document, use the new "||" operator for alternative expressions.
• The Amount field can now detect and return the Yen currency symbol (¥) if Country has been set to "Hong Kong" in the project settings.
• A new Save command in the Document window context menu allows you to save the current image (including a preprocessed image) to a file.
• PDF files can now be processed. If a document consists of several pages, only the first page is processed.
• Classification now returns a confidence value that is computed from the confidence values of the evaluated classification features.
• The new Page Number field allows you to search for page number information.
• Two new fields for processing U.S. checks are available: CAR and MICR. The CAR field reads the handwritten amount value. The MICR field reads the code line and returns its associated values. Both fields use character recognition settings optimized for processing U.S. checks.
  

Resolved Problems

Service Pack 03 for the Ascent Advanced Forms - Extraction module SR01 resolves the following problems.

• Since version 3.8 SR01, Ascent Advanced Forms has stored large amounts of recognition data within the Ascent Capture database. This resulted in long load times for batches in Ascent Advanced Forms and performance issues with large files in Ascent Capture Internet Server (ACIS). Now recognition data is stored outside the Ascent Capture database in separate files: in x_sceData.xml if Single Click Entry (SCE) data exists and in x_ocrDetails.xml if at least one field contains OCR details, where x is the image number. Also, there is no longer an Extraction performance issue since only unrejected Quality Control documents (rather than an entire batch) are processed through extraction. (SPR 27292, SPR 27294, SPR 27641)
• If the current document type contains a Table field and the document type is changed by Quality Control, the error "Element <...> does not exit in Enumerator <...>" no longer occurs when the document is reprocessed by Ascent Advanced Forms Extraction.
• When a document has been modified in Validation, Ascent Advanced Forms Validation, or Quality Control (for example, the document type has been changed or a page has been deleted) and the batch is processed again by Ascent Advanced Forms Extraction, the index fields of the modified document will now be extracted.
• Runtime no longer increases considerably if the SaveCharacterDetails option is selected in the project settings.
• If a field is copied and inserted as a value field of a KeyValue field, the search area size is no longer changed to the default size of the respective field type.
• If an InvoiceItemsCustom field is added, the Navigation and Image views no longer become empty.
• If an operating system language is neither English nor German, the installation user interface for patches and service packs now uses the English language instead of German. (SPR 28299)
• If two adjacent columns of type Text are specified in a Table field, the second text column can now be read.
• The end-of-line symbol for the Regular Expression field now functions correctly.
• In a Table field, the text of a table cell is no longer assigned to the incorrect column when the header of the respective column is correctly found.
• During Run Classification, documents in the test document folder of the document type Unknown that were classified as "Unknown" are no longer erroneously handled as rejected documents.
• If an InvoiceDate field is copied, the copy no longer shows a Zone property and an invalid value at the LowerLimit property.
• If a column with HorizontalPositionActive set to "on" is selected in a Table field, the corresponding bar in the Image view is now selected.
• Advanced Form Extraction now functions correctly if no Reader license is available.
• If a KeyValue or FirstOf field is used as the key field in a KeyMultiValue field, the results of the key field are now correctly returned in the result.
• If a project of a prior version was loaded and saved with version 3.8, it now functions correctly if Ascent Advanced Forms abnormally terminates.
• The Design Studio now functions correctly when a global field is deleted from a document class.
• If a Table field is used as a value field of a KeyValue field, the coordinates of HorizontalPosition properties now remain unchanged during a test run if the left border of the current value search area is outside of the image.
• The FuzzyDb field now functions correctly.
• The Design Studio now functions correctly after a table defined as a value field of a KeyValue field is deleted.
• The Phrase field no longer counts repetitive phrases as distinct, different phrases with respect to the MatchCount property. The field now returns "success" when finding the specified minimum number of different phrases.
• The start-of-line expression element ('^') of the Regular Expression field now functions correctly.
• If a word or character subnode of the CharacterDetails node is selected in the results of a test run, the NodeProperties view no longer shows the result details of the complete line.
• If a test document is specified in the Navigator view under Use Own Documents, Ascent Advanced Forms now functions correctly when a (US)InvoiceItems(Custom) global field type is added.
• If the Boundary property of a Phrase field is set to "word," the field no longer returns a phrase that is part of a geometrical word (that is, a word that contains characters and no blanks).
• If AutomaticFontSelection is set to "on" at the OcrParam node, a second Font subnode is created with FontName "hand" and Confidence "0.0" as default values. If AutomaticFontSelection was set to "off" at a Regular Expression field and FontName was set to "hand" afterwards, during a test run the Confidence value of the second Font node with the default value "0.0" was copied to the first subnode, erroneously overwriting the original value. If the project was saved afterwards, these errors were also saved to the project file. Now the second Font subnode is deleted when AutomaticFontSelection is set to "off." When you have installed this service pack you will need to check and repair the Confidence values of all Regular Expression fields in affected projects.
• When the CodeSearchOrder property of the BarCode field is set to "special size," the properties BarCodeHeight and BarCodeWidth are preserved when the project is reopened at a later time.
• If the key field of a KeyMultiValue field returns alternative results and the value field returns alternative results for a single key value, the result format is now correct.
• The patch code recognition now functions correctly.
• If the FieldLayoutProcessing property of the OcrParam node is used, KeyValue fields and global fields now process correctly and return correct results.
• If a BetweenKeys field is used as a global field, setting the UsedZone property to "local" now functions correctly.
• Licensing of unlimited fields is no longer required when a collector node is used for classification. (SPR 27979)
• If a LineCondition of a Table field specifies a single column, single-cell table rows of the specified column can now be found.
• If an InvoiceVendor field uses a vendor database file with a DBBLOCKID column, the field no longer returns an erroneous result if the corresponding item of the attribute file is empty. It now returns the same result as if the DBBLOCKID column were not present in the database file.
• If a field using field-specific image processing is copied, links are now handled correctly. If a project contains erroneous links prior to the installation of Service Pack 3, remove and reinsert the field-specific image processing to repair the project.
• An error no longer occurs if an attribute file controls the loading of an InvoiceVendor field database file.
• The most-recently-used projects now appear in the correct order in the recent files list.
• If the search area coordinates of a field are copied to the clipboard by pressing Ctrl-C, the complete field is no longer inserted as a subnode when the coordinates are pasted into a field's Zone property by pressing Ctrl-V.
• For index fields reading from an attribute (that is, the Source property did not contain the Image value), the values of successful results are now shown in the Design Studio.
• The DDSDemo demonstration software no longer shows several "Permission denied" errors if the current user is not a domain user or administrator.
• Invalid regular expressions that cause errors during runtime can no longer be entered successfully.
• The kill.exe program in the bin folder is no longer detected as a virus by some scanners.
• The FileOpenAutoRotate method of the DOKuStarResult##.dll no longer abnormally terminates due to a large, invalid box coordinate.
• Like the InvoiceTotals field, the InvoiceItems field now handles VAT rates correctly if a comma is used as decimal point (for example, "7,6" is no longer converted to "7.0").
• If a new test document is added to the Use Own Documents list of the Navigator view while the Result Image tab of the Document view is active, the new document is now selected and shown.
• If a batch that has finished processing in Ascent Advanced Forms Extraction causes an error in Ascent Capture during closing, Ascent Advanced Forms Extraction now displays a message box with an appropriate message. (SPR 25133)
• After Ascent Advanced Forms Extraction processes a batch, the AutoIndexed field in the Ascent Capture database is no longer set for all index fields, causing issues with the page barcode feature in the recognition server. The AutoIndexed field is now set only for those index fields that are actually filled by Ascent Advanced Forms.
• To remove a logical expression at the document type level, you must use the Remove Logical Expression command in its context menu. If you simply delete the value of the Logical Expression property, the document type always returns a value of true. Now a warning message appears reminding you to use the Remove Logical Expression command.
• If an image is selected in the Navigator view and Run Selection is used to start a test run, another image with a result is no longer selected and erroneously shown.
• If the Save Changes Before Run option is selected, the Design Studio no longer displays a Save As dialog box starting with the incorrect folder when a test run is started. Now a project will be saved without displaying a prompt for confirmation.
• The Orientation image preprocessing function no longer rotates an image incorrectly.
• The ACDoku.log file no longer contains non-localized items. (SPR 30835)
• The Invoice Totals field can now read negative amount values and be used to process credit notes. (SPR 18303)

Service Pack 02 for the Ascent Advanced Forms - Validation module SR01 resolves the following problems.

• If the Field State Filter is set to "reject/error," fields with state "none" are now activated correctly.
• SCE FieldRules are now applied during Table Auto-Completion.
• If a previously-suspended batch containing alternate values without a zone or assigned page number is opened, Ascent Advanced Forms Validation now functions correctly.
• If a project name contains the string "-I", automatic Validation is no longer started when "Validation Scripting" is chosen in the Administration module. (SPR25442)
• During manual validation, the state of all empty fields is no longer set to the value "empty." Functionality is now compatible with the behavior of version 3.7.
• The method Form.Show vbModal now opens a form modally, as it did prior to Service Pack 1. (SPR26315)
• If multiple instances of Ascent Advanced Forms Validation are started remotely within an Ascent Capture workflow using the Microsoft Terminal Service, Validation now functions correctly. Problems occurred because these Validation instances could not recognize each other. Now each Validation instance uses a unique identifier consisting of a date and time stamp. This affects the log file names which now have the format DOKuStarValidation_<identifier>.log (for example, DOKuStarValidation_20061016091056123.log). Log files are deleted automatically after five days.
• When recovering a batch, Ascent Advanced Forms Validation now functions correctly if the batch includes extensive User Data or Single Click Entry data. (SPR 27314)
• If the Presentation Service is used to hide fields and the Field Filter is used, Ascent Advanced Forms Validation now functions correctly even if the specified state doesn't occur for any field of the currently-loaded batch.
• If Internet Explorer 7.0 is installed, a script error no longer occurs when a project is opened in Ascent Advanced Forms Validation. (SPR 27746)
• The method FileOpenAutoRotate of the library DOKuStarResult26.dll now functions correctly.
• The "Cannot find scan.exe file in History" error no longer occurs. (SPR 27173)