Change log 1.34.0

Change log 1.34.0


Release Date: 12.07.2023
DB Version: 1.34.0.0

Enhancements

Website

  • Introduction of Data Analytics
  • For missing terminals which were detected when importing transactions, there is now a list of proposed terminals to simplify the creation of the missing terminals. The list is located in the navigation menu under Organization.
  • Links will now open in a new tab when holding down the control key while clicking
  • The reprocessing of posting rule has been enhanced with possibilities to:
    • Reprocess entities already processed by the selected rules
    • Delete unexported postings of the selected rules (only available for elevated users)
  • The field UniqueTerminalId was removed from the organizational structure import/export, because it always has the same value as the field ExternalTerminalId
  • A comment can now be set when creating an adjustments manually
  • For match rules tolerances the same tolerance will be applied to both sides of match key definitions of a rule. The tolerance from definition 1 (ECR, transaction) is equal to the tolerance from definition 2 (EFT, bank payment). Therefore there is now only one tolerance field per definition.
  • The username cannot be updated by tenant user admins anymore
  • A new action Reset posting processing is introduced for:
    • Bank payments
    • Transactions
    • ECR transactions
    • EFT transactions
    • Adjustments
    With this action, the posting processing of the selected entities can be reset. Additionally it is possible to also delete the unexported postings of the entites (for privileged users only).
  • The title of the page is now displayed in list view exports
  • The uploads of ReconHub to external systems can now be viewed in the Monitoring section
  • Searching for a file name in the file list view now works the same as all other text filters in the list views: The file name does not have to start with entered text, but the entered text just has to be included somewhere in the file name

API

  • By default, it is now not possible anymore to submit products or acquirers which are unknown to ReconHub. For product it is either necessary to submit a valid BrandId or ApplicationId. If the product or acquirer is unknown, the client can submit either not submit the value, leave it blank or set the value to "Unknown". For a complete list, please check developers.reconhub.cloud.

Modules

  • In the EFT RAF import module the automatic creation of terminals based on the merchant ID is now possible
  • For the EFT PAYONE EPA import module it is now possible to define RefNumberSe values to be ignored for fee records. By default, the RefNumberSe value 88888888 is ignored.
  • The UID in the EFT Elavon EPA import module has been improved
  • DCC (Dynamic Currency Conversion) information is now saved by the EFT MRX import module
  • The UID of the EFT Adyen SDR import module has been improved.
  • In the EFT Adyen SDR import module, transactions of type BalancePlatformTransfer are also now handled.
  • The EFT MRX import module now maps the acquirer based on the first 6 digits of the field mercNoticeUniqueID. For existing import configurations, the acquirer is mapped to Worldline. This can be adjusted in the import configuration.
  • The Amazon S3 collector module can now filter objects to download
  • The Upload module now supports sending the files per email

Processing

  • Bulk operations on the database now use the same timeout as other SQL commands

Bug fixes

Website

  • Fixed a bug which allowed the user to create an invalid settlement match rule
  • When duplicating a skip rule, a wrong organizational unit was selected under certain circumstances
  • Removing the values of custom fields did not work when importing organizational structures
  • The number of decimal digits is now based on the currency when displaying the balance in the accounting view
  • For settlement match rules it is now not possible anymore to set a tolerance for the match date, because that tolerance did not have any effect
  • Fixed a bug which prevented some authenticator apps (IOS, 2FAS) to read the QR code correctly when registering a user for multi factor autentication
  • Fixed a bug which prevented manual posting of multiple bank payments
  • Fixed a bug which occurred when saving a new organizational unit. When saving a new organizational unit, custom fields were not saved.
  • Fixed a bug which lead to an error when selecting Parent OU ID as a match key in match rule editors
  • Fixed various breadcrumb paths and links

API

  • To prevent reading files while they are being written, the Sales API transaction upload endpoint now writes the file to the Temp-Directory first before moving it to the filestore

Modules

  • The generic import modules have been adjusted regarding the behavior of nullable decimals when a field or value is not supplied in a file
  • Fixed a bug in the Bank CAMT.053 import module which occurred when importing bank payments with remittance informations longer than 1000 characters
  • Fixed a bug in the generic XML writer, which caused the default namespace to be written incorrectly in an XML file
  • Fixed a bug in the Posting export module which prevented dots from being supported in placeholder formats
  • Fixed a bug in the EFT GRRCN import module, which caused reimport of transactions, by improving the UID

Processing

  • The posting export now uses the file store as the temporary folder instead of a local temporary folder, since interrupted posting exports can be continued by another worker instance
  • The file store cleanup now checks the last write time next to the creation time when deleting files