Change log 1.38.0

Change log 1.38.0

Release Date: 12.12.2023
DB Version: 1.38.0.0

Enhancements

Website

  1. An optional payment processor can now be selected on import configurations, transaction match rules, settlement match rules and posting rules
  2. Extended the organizational structure export with a new column for the parent OU name
  3. Acquirer has been renamed to Payment processor.
    A payment processor is an entity that processes transactions for a merchant, and pays out the moneys to the merchant, almost always for a fee.
    For ReconHub, generally the entity that provides the settlement file with the settlement transactions.
    This includes:
    1. Acquirer
    2. PayFac
    3. Market Place
    4. Delivery Service
    5. PSP
    6. Cash Handlers
  4. Job executions now display their original planned execution date. The duration of an execution is now the sum of the duration of its tries. Job execution results now track their own start dates and durations.
  5. A new option Create empty files has been added to the export rules. This option can be used to prevent the creation and upload of empty export files.
  6. Added new payment processor overview and details pages.

Modules

  1. Extended the HTTP and SOAP upload module with the ability to check for errors in the response message using a regular expression

Processing

  1. Introducing exact and tolerant transaction matching: During matching, ReconHub will prioritize Exact Rules, followed by Tolerant Rules. This prioritization strategy streamlines the process, minimizing tolerance-dependent matches and increasing overall efficiency. Rule priorities remain, but with a twist: they're now assessed separately during Exact and Tolerant matching, ensuring a more organized and efficient workflow.
    1. Exact matching: Matching based on a match key hash. No toleranes or multimatching are allowed.
    2. Tolerant matching: Works like the existing transaction matching. Tolerances and multimatching is possible.

Security

  1. Added new settings "Encrypted" (enabled by default) and "TrustServerCertificate" (disabled by default) to the Database section in the environment configuration which allows more control over the database connection security.
  2. Important: The SQL server connection has already been encrypted before, but the certificate (incl. trust chain) of the encrypted database connection is now verified if not configured differently (secure by default). If a self-signed certificate is used on the SQL Server, the certificate validation and DB connection might fail after installing this release. In this case, TrustServerCertificate can be enabled via environment configuration which allows encrypted cnnections even if the certificate validation fails.

Bug fixes

Website

  • The accounting view showed accounts multiple times in a multi-mandator environment
  • Fixed a bug where DST switch was not taken into account when calculating the date range for top metrics on the dashboard
  • For the roles Export administration and Export viewer an incorrect name was displayed in German and French

Modules

  • The generic import modules now accept a normal character instead of an ASCII code for the fill character in fixed length file configurations
  • Transactions can now be marked with the transaction type Fee on import
  • The HTTP collector module now supports to provide an additional body on OAuth2 client credentials request
  • The posting processing did not work as expected when the settlement matching was disabled
  • Fixed a bug where State settlement matching was not validate properly on creating new Posting rule template

Processing

  • The booking date of the bank payments is now always transferred to the transactions during the settlement matching if the booking date is unique
  • Fixed a bug when multiple similar accounts were returned that leads to an error in Post bank payment

Installation

  1. The default security settings of the SQL database connection have changed. Please check the SQL server certificate used for the database connection before installing this release. For details see "Enhancements" -> "Security" above.
  2. The SQL script bin/DS/Database/Migration/1.38.0.0/PreMigration/PreMigration_1.38.0.0.sql can be run beforehand without the need to stop the ReconHub services. This will speed up the actual deployment of the release and reduce downtime but will also mean, that the verify-upgradepath step will fail.
    Important: This script requires ReconHub 1.36.0.0 or higher.

Notes

Changes in Database Support: Discontinuing Support for SQL Server 2014

As part of our ongoing commitment to deliver a product that meets the evolving needs of our customers and stays in line with current technology standards, we are making an important update in our database support strategy. We'll drop support for the following modules:
  1. Deployment:
    Starting with this release (1.38.0), the deployment is not supported for SQL Server 2014 anymore. For customers operation ReconHub on SQL Server 2014, Abrantix can provide support for the database migration
  2. Application:
    Starting with release 1.41, ReconHub can no longer gurantee support for SQL Server 2014.
This decision is guided by the following considerations:
  1. End of Microsoft Support: Microsoft has officially ended mainstream support for SQL Server 2014, limiting the availability of updates, security patches, and technical assistance. Continuing to support an outdated version could expose our users to unaddressed security vulnerabilities and stability issues.
  2. Enhanced Performance and Features: Newer versions of SQL Server offer significant improvements in performance, security, and functionality. By focusing our efforts on these versions, we can leverage these advancements to provide a better, more efficient, and secure experience for our users.
  3. Resource Allocation: Concentrating our resources on newer technologies allows us to be more efficient and innovative, ensuring that our product remains at the forefront of industry developments and standards.
If you are currently using SQL Server 2014, we strongly recommend planning for an upgrade to a newer version of SQL Server. This will not only ensure compatibility with our product but also provide you with improved performance, security, and support.

    • Related Articles

    • Change log 1.42.0

      Release Date: 23.05.2024 DB Version: 1.42.0.0 New features Exception list view showing all unmatched transactions Simplified one-to-one matching of transactions Balance matching, with which several ECR transactions can be matched with several EFT ...

    • Change log 1.33.0

      Release Date: 31.05.2023 DB Version: 1.33.0.0 Enhancements Website The look of the application has been updated When creating a tenant, it is now possible to select from a default set of custom fields to be available for the tenant When creating a ...

    • Change log 1.33.1

      Release Date: 08.06.2023 DB Version: 1.33.0.0 Enhancements Modules The generic export module now supports json format Bug fixes Website Two default currency filters were incorrectly added to the posting rule, when the accounts of the posting rule ...

    • Change log 1.36.0

      Release Date: 28.09.2023 DB Version: 1.36.0.0 Enhancements Website Default dashboard items are added for new users based on the new user's roles When relocating a terminal, a note has been added to indicate that it may be necessary to reset the ...

    • Change log 1.35.0

      Release Date: 21.08.2023 DB Version: 1.35.0.0 Enhancements Website A new action Delete export has been added in the export detail view to delete failed exports It is now possible to filter the import list view by folder In the accounting view, ...