Kofax ReadSoft Invoices 6.2.0 Fix Pack 9
Build date: Sep 6, 2024
© 2024 Tungsten Automation. All rights reserved.
Use is subject to license terms.
Introduction
This release contains priority fixes driven by critical on-demand requests in Kofax ReadSoft Invoices 6.2.0.9.
Note: To install Kofax ReadSoft Invoices 6.2.0.9, an existing full installation of Kofax ReadSoft Invoices 6.2.0 is required.
If you need to perform a full product installation, see the Kofax ReadSoft Invoices Installation Guide for instructions.
Issues resolved in this fix pack
| ID | Issue | Solution |
|---|---|---|
| 259757 | ReadSoft Invoices failed to recognize the Israeli currency Shekel (₪) for some Israeli invoices. | The language selection is properly managed to handle the OCR selection. |
| 257088 | The buyer's name in the "BuyerName" field on the Chinese invoices was incorrectly extracted. | Omnipage is upgraded to version 22.1.0.5. |
| 256037 | Some content was missing from the invoices after interpretation. | Omnipage is upgraded to version 22.1.0.5. |
Previous fix packs
This section includes the features added and issues resolved in the previously released fix packs. To see the details, click on the fix pack.
Issues resolved
| ID | Issue | Solution |
|---|---|---|
| 260577 | The title (GST) of the invoice definition could not be extracted in the Optimize module. | Correct language selection is managed to prevent further interpretation. |
| 259160 | The PDF could not be correctly extracted (the orientation was changed, recognition failed, and the Verify module became unresponsive). | The image is not reprocessed again. |
| 257013 | The XML variant definition could not be created when the supplier information was found in the master data. | A new XML variant condition is added to generate a new definition from the description. |
Issue resolved
| ID | Issue | Solution |
|---|---|---|
| 261276 | When XSLT was run while loading an external document, the AllowDocumentFunction constraint was violated. | To enable the AllowDocumentFunction property on the MSXML 6.0 object, a new setting, Enable AllowDocumentFunction for XSLT, is added to the Transfer job description under Output Format. |
Issues resolved
| ID | Issue | Solution |
|---|---|---|
| 257162 | The PDF file could not be processed in the Interpret module. | Several optimizations are performed to handle the PDF file processing. |
| 254371 | The text was right aligned in line items for non-Arabic language. | Adjusted the text alignment within line items to conform with the language requirements. |
| 254362 | The second keyword was not detected in the "keywords.txt" file. | Changed the iteration logic to consider all the lines. |
| 252620 | The Taiwan invoice date was extracted incorrectly. | The Omnipage SDK flags are enabled to improve the extraction. |
| 251196 | The database upgrade and maintenance failed because of the large number of learned documents. | Improved the maintenance for managing definitions with a large number of learning documents. |
| 249425 | The date format produced in the output file after transfer was incorrect. For example, when the DisplayDate=YYYYMMDD, the output date was DDMMYYYY, and when the DisplayDate=DDMMYYYY, the output date was YYYYMMDD. | The format of the invoice date is changed based on the display date. |
| 248874 | When the original email was sent with OFD attachments, the feedback email sent only the XML file without the email body attachments. | A property is added to maintain the original attachment. Note: This fix also applies to ReadSoft Collector, and it is compatible with Collector 6.5.0 Fix Pack 23 and higher. |
| 245973 | The PDF image was blank after extraction with the Omnipage. | OmniPage is upgraded to version 22.1.0.4. |
| 245780 | After the Interpret stage, the first page was identical to the second page, and the original first page disappeared. | OmniPage is upgraded to version 22.1.0.4. |
| 125888 | There was an incorrect VAT rate warning for the first invoice. | If the field is inactive, the warning message does not appear. |
Features added
245444: Keyword detection for numbers is now supported when the format types "Numeric" and "Special characters" are selected for the single item field profile.
58386: Invoices are now supported in the Arabic language.
To create an Arabic profile, do the following (reference change files are available in the patch build location folder):
- Update the Countrycodes.txt file in the user's installation folder with a new entry, ARA=Arabic.
- Update the EHCharset.ini file in the GlobalPath folder with a new character set, [Arabic].
- Update the following entries in the eiglobal.ini file available in the GlobalPath folder:
- OCRExtractionTimeOut=12000 under the [Options] section.
- CurrencyXX=SAR,SAR,SR; Saudi Arabia Currency - Saudi Riyal, under the [InvoiceCurrency] section.
Note: XX is the next currency sequence in the eiglobal.ini file.
- The [FullMonthName] section with Arabic months sequentially.
- The [ThreeCharMonthName] section with Arabic months sequentially.
- Copy the Arabic country profile (ARA) available in the patch build installer to the Country Profiles folder under the GlobalPath folder.
Issues resolved
| ID | Issue | Solution |
|---|---|---|
| 247113 | The maintenance plan did not run in silent mode when the user authorization was enabled. | An extra condition is added to run the maintenance plan without the user authorization. |
| 246345 | A few Chinese characters could not be interpreted for some PDF files. | While processing the invoices in Asian languages, the second-time extraction is done only on the image layer. |
| 246057 | The Chinese currency sign was incorrectly recognized as number 1. | While processing the invoices in Asian languages, the second-time extraction is done only on the image layer. |
| 245939 | The Taiwan invoice date could not be captured automatically. | The recognized character is added as a delimiter and handled the date mapping for Taiwan invoices. |
| 244966 | For the OFD invoices, the UDVs were not created for the fields marked as "Enable sorting by this field." | The UDVs are now created for all the invoice formats (PDF, OFD, XML, and more) when the fields are marked as "Enable sorting by this field." |
| 244963 | Incorrect information was extracted from the QR code. | The QR code is handled as per the specification, and the correct information can be extracted now. |
| 231621 | The rolling bar returned to the top after verifying invoices in the Verify module. | A proper index is set to maintain the focus on the selected row in the grid control. |
| 230511 | Some content was missing from the invoice after interpretation. | OmniPage is upgraded to version 22.1.0.3. |
| 223838 | Some content overlapped after interpreting the PDF, specifically in the "Billing address" and the "Consignee" sections. | OmniPage is upgraded to version 22.1.0.3. |
| 166107 | The OCR SDK "1" (font in italic) was interpreted as "7" on the line-item level. | OmniPage is upgraded to version 22.1.0.3. |
Features added
225858: Use original PDF instead of intermediate file for processing and extracting (OCR).
A new flag value, 2, is added under the flag PDFTextInput, which is now the default flag value.
Flag values:
- 0 = A bitmap image is used to interpret the invoices.
- 1 = The text and image layer of the source PDF file is used to interpret the invoices.
- 2 (default) = The source PDF file is used to interpret the invoices.
96514: A new flag, DoVatTableRowTotalValidation, is added under the [Business_logic_validation] section in eigolbalextra.ini to perform the VAT table row validations.
Flag values:
- 0 (default) = No validations are performed on the VAT table.
- 1 = Validations are performed on the VAT table.
Note: From this fix pack onwards, ReadSoft Invoices supports Windows 11 Enterprise, version 22H2.
Issues resolved
| ID | Issue | Solution |
|---|---|---|
| 229729 | A general COM error appeared when reinterpreting XML invoices in the Interpret module after making changes to the XML definition in the Optimize module. | The creation of the Appendices page caused this exception, which is resolved now. |
| 229726 | When editing the feedback email in the Verify module, pressing Enter did not create a new line. | Support for multiline is added. |
| 229608 | No value could be extracted from the PDF. | OmniPage is upgraded to version to 22.1.0.2. |
| 228173 | The quantity field "1szt" in LineItem was incorrectly recognized as "lszt" or "15zt". | OmniPage is upgraded to version to 22.1.0.2. |
| 225650 | Czech characters could not be copied correctly from the output PDF file. | Characters related to Czech are used for creating a PDF file. |
| 223589 | The date could not be captured when Interpret was run as a service. | The correct language is used to derive the correct date format. |
| 220900 | The SaveExtractedImagesInBWTiff flag affected the values that were extracted. | OmniPage is upgraded to version to 22.1.0.2. |
| 167136 | The invoice date on some PDF files could not be interpreted correctly. | OmniPage is upgraded to version to 22.1.0.2. |
| 153425 | Values in the header and footer could not be interpreted. | The value of the PDFTextInput flag is set to 2. |
Feature added
From this fix pack onwards, the product version (fix pack version number) will be displayed instead of the build number in the About and Extensions dialog of the ReadSoft Invoices, as well as in the Control Panel.
Issue resolved
| ID | Issue | Solution |
|---|---|---|
| 166769 | Other values could not be extracted from the TIF image except the barcode value. | A new flag, OCRExtractionTimeOut, is added to the [Options] section in eiglobal.ini. Use this flag to set extra time for extraction. To resolve this issue, the flag value should be set to 20000 milliseconds (12000 milliseconds is the default value). |
Issues resolved
166153: The License reset file did not work for Invoices 6.2.
159293: Interpret did not work while using the last page identifiers.
157392: If the master data was used in creating an invoice definition in the Interpret module, the definition did not work after the invoices were transferred.