Coresuite 8.20 - Changelog

Introduction

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

Following on our SAP Business One 10.0 SP2402 - Coresuite Fails to Start article, Coresuite 8.20 is compatible with both old and new SAP Business One installations as we compiled it with the latest SAPBusinessOneSDK.dll library. In addition to the compilation, we modified also the config.exe file which defines when to use which DLL version.
The benefit of compatibility is, that you do not need to know which Coresuite version to install on which SAP Business One patch level, however, the drawback is that the Coresuite installer needs to be replaced (full addon upgrade is required) as the installer contains the reference to SAP Business One libraries and also the config file. For the Coresuite Administration Assistant (CAA) this change allows selection of Microsoft SQL Server 2019 in the configuration.

If you need only a Designer 8.20, Accounting 8.20, Customize 8.20, or SwissPayment 8.20 due to some specific bug fix or improvement, it is possible to upgrade only the mentioned modules.

If you need/want any of the functionalities mentioned below (excluding SwissPayment as it is a standalone module), you need to upgrade full add-on as those features are delivered via Coresuite Framework or the installer.

For all changes delivered in Coresuite 8.20, 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.15 yet, the full Coresuite add-on needs to be upgraded!

Enterprise Search: New Functionality “Exact Match”

Following improvements delivered in Coresuite Enterprise Search version 8.05, we are now delivering an additional new feature with the name "Exact Match" to allow more control over search results.
This new functionality concludes the overall searching experience and it is up to users to decide what they want to search for.

The logic behind all the improvements of the search functionalities works as follows:
- When the "Same search behavior on Enter and Search" is not activated, key Enter acts as an equals ("=") operator with regards to the underlying value from the autocomplete (suggest list) control, and the Search button acts as a LIKE operator.
- When the "Same search behavior on Enter and Search" is activated, you get results from the LIKE operator.
- The new functionality "Exact Match" (in combination with the previously introduced "Same search behavior on Enter and Search") will get you all LIKE results, but only those that equal the exact searched term. This means, no difference between clicking on Search or hitting Enter, but results for the specific searched term.

Enterprise Search: Characters To Show in Search Results

In the search results of Enterprise Search, we were displaying 50 characters.

With Enterprise Search 8.20, we are bringing the improvement that allows you to set the length of search results between 30 - 100 characters according to your needs. If you do not perform any change, 50 characters will be displayed by default.

You can change this setting in the field named "Characters to show" in SAP Business One via Tools → User-Defined Windows → COR_SEARCH_CONF.

Close SAP Business One Fast on Exit

When you close the SAP Business One client and any add-on is/was connected, it takes 30-40 seconds for the SAP Business One client to be closed.
According to SAP note 3368860 it is an expected behavior because SAP Business One client needs time to unload DLLs related to DI-API from the memory.

With Coresuite 8.20, we are bringing a feature named "SBO Fast Close on Exit", that terminates the SAP Business One process once Coresuite is closed.

Please note that this feature is experimental and by using it you agree to use it at your own risk. We are not responsible for any problems caused by the termination of the SAP Business One client process through this feature.

Swiss Payment: Improvement of the Cleanup of The Old Payment Files Functionality

Following on the functionality "Purge Posted Wizard Runs" delivered in SwissPayment 8.15, we are now adding in the configuration a day parameter so you can set how old payment files should be purged from the database.

When the day value is saved, the purging occurs during the startup of SwissPayment when any user logs in and the add-on starts.

Swiss Payment: Reload Saved Payment Runs

When you attempt to post a payment run with some missing reference number and later correct the document, the saved payment run can't be executed because it does not refresh the information.

The new functionality enables you to post such payment runs again as it will refresh the data on a payment run.

When the functionality "Reload Saved Payment Runs" is active and the user selects a saved payment run from the drop-down list, data will be reloaded based on the saved parameters.

This functionality is deactivated by default.

[E-Bill] Default billing/contact data used

When Uploading an invoice with a billing address and contact person that is different from the standard address and contact person, SwissPayment uses the default information from the business partner instead of the data in the document. 

With this improvement, invoice contact will be used by default. If invoice contact is not filled, default business partner contact will be used as a fallback. If a bill-to-address has been selected on the invoice, this will be used. Note that this is not the free text address, but the detailed fields you get when clicking the "..." button next to the bill-to address on the logistics tab. Here a check exists to see if the city field has been populated. If it is, it is considered a success and the invoice bill-to-address will be used. If not, the business partner bill-to-address will be used (as was the case before this implementation).