Coresuite 8.25 - Changelog

Introduction

Below you can find a short description of the main changes delivered in Coresuite 8.25.

For all changes delivered in Coresuite 8.25, please see our Release Notes.

IMPORTANT: Due to the changes and performance improvements delivered in Coresuite 7.90, if you have not upgraded to Coresuite 7.90 - Coresuite 8.20 yet, the full Coresuite add-on needs to be upgraded!

Coresuite: Don't Close SBO When Changing Company DB with "SBO Fast Close on Exit"

Following on the "SBO Fast Close on Exit" functionality delivered in Coresuite 8.20, we are now improving this experimental feature so that SAP Business One is not closed when changing the company DB.

Coresuite: Connection String Length

The Coresuite connection string to the database is constructed based on the hostname, DB connection user, and password. The field storing the connection string allowed a string with a length of up to 254 characters. In case the hostname, password, or username had more characters leading to the construction of a connection string longer than 254 characters, Coresuite failed to connect.

With Coresuite 8.25, we are now delivering also a new field of a memo data type, that theoretically supports up to 65535 characters on HANA and on SQL up to 2GB of data.

Coresuite Enterprise Search: Option to Deactivate the "Exact Match" Functionality

Following on the "Exact Match" functionality delivered in Coresuite 8.20, this improvement allows you to deactivate the functionality.

You can deactivate it via the field named "Enable Exact Match" in SAP Business One via Tools → User-Defined Windows → COR_SEARCH_CONF.

Swiss Payment: Block Save/Post On Error

We implemented a new validation functionality "Block Save/Post On Error" that blocks the booking of documents in specific cases.

The following scenarios are controlled by this functionality:
 - If a credit note is higher than the issued invoice, the validation stops booking/saving if any selected document will prompt an error.
 - If address details are too long for example street name is longer than allowed.
 - If a user creates a payment run with normal IBAN and the reference number is entered instead of a customer ref number (user filled details under the accounting tab in the ref field).
 - If a user has created an invoice with a QR bank connection, without entering the ref number on the invoice.

Note: Users must first click on "Create File" for the system to run validation and should any errors mentioned above exist then the user will not be able to make a posting before the errors are fixed i.e if the user clicks on the "Post" directly and errors exist in the selected rows for posting then the addon cannot stop the user.

The functionality can be activated by ticking a check-box "Block Save/Post On Error" on the Payment wizard swiss tab in the swissPayment configuration.