Tungsten Automation

Kofax ReadSoft Collector 6.5.0 Fix Pack 23

Build date: April 23, 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 Collector 6.5.0.23.

Note: To install Kofax ReadSoft Collector 6.5.0.23 successfully, an existing full installation of Kofax ReadSoft Collector 6.5.0 is required.

If you need to perform a full product installation, see the Kofax ReadSoft Collector Installation Guide for instructions.

Issues resolved in this fix pack

ID Issue Solution
252613 When the XML invoices included a PDF file with parentheses in the name, the PDF was ignored, and a blank image was generated.

The file names with valid special characters are now recognized.

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 Invoices, and it is compatible with Invoices 6.2.0 Fix Pack 6 and higher.

Features added in previous fix packs

Fix pack 22

249026: The field order in the invoice fields for XML invoices can be changed as per preference.

Fix pack 21

229996: Only one amount summary table is created now, as in the XML invoice. In earlier versions, the amount summary table was created twice with the same values.

232784: A new XMLInvoiceFieldOrderConfiguration.xml is added to the GlobalPath folder for XML invoices to change the order of fields in the Buyer and Supplier sections as per preference.

Note:

Fix pack 20

226837: A new flag, OFDTypeID, is added under a new section [OFD2.0] in collector.ini to specify the identifiers for the new format of OFD.

Flag value:

OFDTypeID = eInvoice,root (default)

Note: Irrespective of flag values in collector.ini, empty string("") will always be considered to determine the new OFD type.

Fix pack 19

164736: Collector supports the OFD file format.

Note: Collector only supports one page and one line-item extraction for the OFD file format.

Fix pack 18

161356: Upgrading from Azure Active Directory Authentication Library (ADAL) to Microsoft Authentication Library (MSAL) while using EWS with OAuth.

A new flag, UseMSALContextInEWS, is added to the [General] section in collector.ini. You can use this flag to choose ADAL or MSAL.

Flag values:

Note: After installing this fix pack, re-authenticate any services that use EWS with an OAuth input source; otherwise, set the flag value to 0.

150844: Use a value outside the LineItem part for a column in the LineItem table.

Fix pack 17

123704: Regardless of whether the AllPagesAreInvoicePagesInterpret flag is enabled or disabled, the invoice appendix is created while processing the XML invoices.

122515: Office 365 and EWS with OAuth input sources bypass Microsoft security to process digitally signed emails.

122509: XML invoices support the VAT table.

117773: XML Maintenance can be run from the Command Prompt or scheduled in the Windows Task Scheduler to automatically start and stop.

112831: While converting an email to PDF, the CC field of the email is included in the converted PDF.

112304: Limilabs supports the following date format while processing emails from Gmail:

"Date: Tue, 31 Aug 2021 14:22:31 +0870"

112152: ReadSoft Collector supports Windows Server 2022.

109143: ReadSoft Collector settings can be exported into a .sxprof file. Also, the ReadSoft Collector settings saved in a .sxprof file can be imported into the application.

101104: ReadSoft Collector can be configured to send automatic notification emails when an error occurs.

99273: While processing the emails, only the email attachments can be saved skipping the other information in the email, such as logo, title, and signature.

Fix pack 16

122362: Office 365 and EWS with OAuth input sources skip verification of email attachment names while processing digitally signed emails.

Fix pack 15

112580: While converting an email to PDF, the CC field of the email is included in the converted PDF.

Fix pack 13

112044: Emails with an invalid date format are moved to the configured error folder.

Fix pack 12

103857, 14808: ZUGFeRD version 2.1.1 standard is supported.

100569, 14775: Impersonation with OAuth is supported.

Fix pack 11

100986: A new input source type, OFD Files, is added to process OFD files.

73111: A complete list of email attachments is displayed in ReadSoft Collector whether or not they are supported by ReadSoft Collector.

72766: The attachment folder can be set to a specific particular job in the Job configuration > Email settings tab. In earlier versions, the attachment folder was set at the global level in ReadSoft Collector General settings, which was common to all the jobs.

50534: ReadSoft Invoices can process digitally signed emails. The How to handle digitally signed emails option is added to the Email settings tab in the Job configuration dialog box in ReadSoft Collector. Select this option to move emails to the error folder if the digital signature validation fails.

Fix pack 8

26179093, 13194, 98635: The database name and username in collector.ini can be encrypted.

New flags, UseEncryptedDB and EncryptedDatabase, are added to the [General] section in collector.ini.

26157426, 13041, 96515: A ZURGFeRD file larger than 64 KB can be processed.

26095307, 12721, 73025: The ReadSoft Collector email folder can be added to the job description. A new option has been added to the Email settings tab to select the email folder.

Fix pack 7

26068897, 12506, 71259: It is now possible to process email in order when using EWS and Office365.

65863: It is now possible to connect to Gmail using OAuth with IMAP in Collector. Now, all the OAuth input sources such as Gmail, Office 365, and EWS are added in a separate list under source type OAuth.

Fix pack 6

63972: Previously, if ReadSoft Collector maintenance was not performed frequently, the size of the database potentially grew large enough to cause connection time or command timeout errors, and the sync operation would fail as a result. This has been redesigned and a "Run maintenance" button is added so that both sync and delete are performed with a single click.

58478: Support is added for the ZUGFeRD 2.0 XML standard.

58477: Support is added for invoices in XML.p7m format.

57108: Support is added for XSLT 2.0.

54825: Database maintenance is simplified with a “Run maintenance” button.

53386: It is now possible to configure Microsoft Office 365 and EWS with Oauth as input sources.

Fix pack 5

58388: To connect to Microsoft Cloud resources (Office 365), Microsoft Graph REST API can be used .

54550, 10362: ReadSoft Collector database maintenance is simplified with the addition of the Run Maintenance option.

52564, 28387, 10108: A custom value can be added when importing XML invoices.

Fix pack 4

51940: The perceptive document filter is upgraded to version 11.4.0.2822.

49322, 9670: It is now possible to use a value outside of the line items as a condition to be able to extract them.

48591, 9551: It is now possible to process XML invoices even though they contain text/XML embedded as a file.

48335, 9512: It is now possible to use different images for XML invoices depending on the situation (that is, embedded, from email, or newly created automatically).

46373: The Finvoices 3.0 XML profile is now supported.

45038: Supplier numbers are no longer duplicated when using SmartXML.

44759: TLS 1.2 is added as a SecurityProtocolType option for Exchange server communication in the [General] section of collector.ini.

41473: It is now possible to separate email attachments into multiple invoices if the invoices are separated by blank pages.

41284: PDFSharp is replaced by Atalasoft for PDF creation.

41031: Support is added for Microsoft SQL 2017.

39811: If a namespace is present, working with child notes is possible while using XSL.

28387: Email from specific senders or entire domains can now be blocked.

Fix pack 3

48234: Emails with broken PDFs are now moved to the error folder instead of causing Interpret to fail.

43458: It is possible to have all the pages in an invoice be numbered using AllPagesAreInvoicePagesInterpret in connection with Kofax ReadSoft Collector.

42569: The OAuth 2.0 protocol is supported for Exchange Online Web Services.

Fix pack 2

40473: Fields in the XML Mapper can be filtered.

39811: If a namespace is present, working with child notes is possible while using XSL.

Fix pack 1

Kofax ReadSoft Invoices 6.0.1 is supported for use with Kofax ReadSoft Collector.

Issues resolved in previous fix packs

Fix pack 22

ID Issue Solution
252619 When processing a Chinese OFD invoice with ReadSoft Collector 6.5.0.21,

the Amount Summary table was not created in the output PDF.

 The Summary table is displayed even if the invoice does not have line items.
250910 When UsePdfTableForLineItemDataForXML was set to 1 in the collector.ini file,

incorrect data was created for line items in the generated image files.

 A proper initialization of the local variable is executed.

Fix pack 20

223432: Images were downloaded from the email, even though the "Do not download images referenced in the email body" option was selected.

Fix pack 19

166996: The field order was changed in the "Supplier" and "Buyer" sections of the newly created PDF for POL XML invoices.

165392: The field label name "Tax code" was changed to "Supplier Tax Reg No" in the autogenerated XML invoice image.

163944: A single image from the PDF was used for all the XML files, even though each XML file had a distinct image in its respective PDF.

161844: The content of one field overlapped with the content of the other field in the newly created PDF from an email.

159284: The product version for Collector is now reflected in the Manager module and the Control Panel (this works only with 6.1.0.8, 6.2.0.3, and later versions).

Fix pack 18

163025: The newly created invoice image for the updated XML field did not have any value.

161018: System decimal setting affected importing an XML file.

160752: Some PDF files generated error messages during interpretation.

Fix pack 16

122863: The field labels in the XML invoices PDF incorrectly displayed Polish special characters.

Fix pack 14

26430313, 16576, 113600: When attempting to reconnect to an Office365 input source, the remote server connection failed.

113573: The Office365 input source connection failed when TLS 1.2 protocol was used.

Fix pack 13

110580: The email processing failed if the P7M file attachments were not ignored while processing email using the EWS and EWS with OAuth input methods.

Fix pack 11

107011, 104756: The emails were not processed when IMAP Limilabs and Gmail with OAuth input configurations were used.

106436: The PDF conversion was not successful using Collector and Import.

100659: The Hebrew characters in an email image were not similar to the characters in the actual email.

99441, 97266: The PDF was not processed when the OmniPage engine was used.

65147: In the XML Maintenance plug-in, the custom fields added from the XML Maintenance > Layouts tab were not copied when the XML invoice profiles or XML invoice definitions were exported.

Fix pack 10

26255252, 14856, 104833: When Limilabs API was changed to support OAuth, the group mail address was not supported.

26234483, 102854, 14708: While processing an email using the EWS input source, if a faulty attachment was detected, incorrect attachments were moved to the error folder instead of the error attachment.

Fix pack 9

26200718, 100314: An email remained in the Working folder and was not processed when the application was unable to retrieve the sender details.

Note: Due to the SDK changes made to Atalasoft, Kofax ReadSoft Collector 6.5.0.9 supports Kofax ReadSoft Invoices 6.0.3.4 and higher.

Fix pack 7

26138042, 94833, 12779: A newly created file name included part of the original file name if an extra dot was included.

Fix pack 6

64853: The image layout was not correct on the image created for XML invoices. Lines overlapped at the end of the page.

Fix pack 5

63149, 10809: The PDF files were interpreted multiple times if a .eml file was included as an attachment in the same email.

57396, 10507: The latest XML definitions could not be selected during the import if there were more definitions than could fit on the current screen.

57379, 10492: Attachment folder information was not updated in the log.

55734, 10450: Only one of the multiple emails that had an attachment with the same name could be processed if SaveMailContentToFile=1.

55680, 10451: It took considerable time to show the supplier list in the XML mapper.

55635, 10445: Emails were processed out of order.

54562, 10330: The output dimensions for the PDF body in Collector were incorrect for a sample PDF.

Fix pack 4

53248, 10169: Job name was not updated after rerouting an XML invoice to another profile.

50654, 9868: It was not possible to process digitally signed emails using EWS.

48234: Emails with broken PDFs are now moved to the error folder instead of causing Interpret to fail.

41931, 8740: In the XML maintenance plugin, XML invoices with "invoice object missing" status could not be deleted.

40473: It was not possible to filter fields in the XML Mapper.

29800, 8993: Changes to an XML definition in the XML mapper affected all XML invoices belonging to the parent XML profile.

Fix pack 2

43897, 43458, 8886: The AllPagesAreInvoicePagesInterpret setting was overridden in Kofax ReadSoft Collector.

41931, 8740: In the XML maintenance plugin, XML invoices with “invoice object missing” status could not be deleted.

29800, 8993: Changes to an XML definition in the XML mapper affected all XML invoices belonging to the parent XML profile.

Fix pack build numbers

Fix pack Build number Fix pack Build number
23 6.50.24114 11 6.50.21131
22 6.50.24075 10 6.50.21061
21 6.50.23335 9 6.50.20329
20 6.50.23251 8 6.50.20295
19 6.50.23167 7 6.50.20195
18 6.50.23082 6 6.50.20090
17 6.50.22311 5 6.50.19346
16 6.50.22237 4 6.50.19217
15 6.50.22066 3 6.50.18355
14 6.50.21347 2 6.50.18267
13 6.50.21279 1 6.50.18164
12 6.50.21215

Changes in behavior

Fix pack 6

Previously, help files were installed separately in CHM format on each computer where Kofax ReadSoft Collector was installed, and context-sensitive help calls were done locally. The help is now located on an online Kofax documentation server to which context-sensitive help calls are directed when you click a help button or press F1 in the program. In this case, Internet access is necessary.

Note: Context-sensitive help is available when ReadSoft Collector 6.5.0.6 or higher is installed with ReadSoft Invoices 6.0.3 or higher.

Fix pack 4

The following flags are added to the [Settings] section in COLLECTOR.ini file:

A new flag, SecurityProtocolType, is added to the [General] section in the COLLECTOR.ini file.

Applies to

This fix pack is cumulative and includes the resolved issues released in previous Kofax ReadSoft Collector 6.5.0 fix packs.

Apply this fix pack to update any of the following versions.

Compatibility

Kofax ReadSoft Collector 6.5.0.23 can only be used with Kofax ReadSoft Invoices 6.1.0.5 and 6.2 or higher.

Files included

This fix pack includes the following files:

File name Version
KofaxReadSoftCollector-6.5.0.23.zip N/A
ReadMe-KofaxReadSoftCollector-6.5.0.23.htm N/A

Install this fix pack

Refer to the Kofax ReadSoft Collector Installation Guide for instructions on installing ReadSoft Collector.

Remove this fix pack

Use the following procedure to remove this fix pack.

  1. Verify that the following applications/services are not running.

    2. Note: For best results, remove the fix pack during off-peak processing hours.

  2. In Control Panel, select Programs > Programs and Features > Uninstall or change a program.
  3. From the list of programs, in the Name column, select the item that corresponds to Kofax ReadSoft Collector 6.5.0.23.
  4. Right-click and select Uninstall.
  5. Restart any applications/services that were stopped before removing this fix pack.