Coresuite 7.90 - Changelog

Introduction

Below you can find a short description of the main changes delivered in Coresuite 7.90.
For all changes delivered in Coresuite 7.90, please see our Release Notes.

IMPORTANT: Due to the changes in the main Coresuite executable file and Framework the full Coresuite add-on needs to be upgraded!

ODBC Pooling - Performance Improvement on HANA

Following our Performance related article on HANA and performance improvements delivered for a preview of documents in Coresuite 7.85, we are improving now Coresuite to be able to use the Pooling mechanism of ODBC driver, which will improve the general performance of SAP Business One when using Coresuite on HANA installations.

In addition to the configuration related to PBKDF2 vs Password authentication mechanisms (described in the article from the link above), you can now open pooling on the HANA ODBC driver:
1. On every client machine, open the Windows Start menu and type ODBC → open ODBC Data Sources (64-bit).
2. Open tab Connection Pooling → Double click HDBODBC.
3. Click on Pool Connections to this driver and keep the default value of 60 seconds.
4. Click on OK → Apply → Start SAP Business One again.

This will allow using of connections from the pool, rather than opening a connection for each query executed, which improves the performance.

Log Level, Dynamic Path of Log Report, and License Check

Due to the terminal service configuration, the temp folder of each session might be cleaned once the user closes the session, leading to the loss of log files.
We are delivering an improvement that allows changing the log file folder, as well as the level of logging.
In addition to log report-related changes, we are bringing a new feature for OnDemand installations - License Settings. This new feature checks the validity of the license during the startup of Coresuite based on the expiration date and downloads the new license automatically based on the information on our portal. The value for license download is set by default to 30 days before the license expires.
You can find all the new improvements in the:
1. Administration → Add-Ons → coresuite administration → Administration → tab Settings.
- Please note that you need to click on the button Save Settings after changing Log Level or Log Path values to reflect changes.
- We suggest configuring maximum the "Info" level (recommended Error) to avoid the number of messages being written in the log, which might impact also the performance of Coresuite.

Batchprinting with Coresuite Service

Using Coresuite Service for batch printing can cause a conflict with users logged-in in the SAP Business One leading to the failure of printing or emailing based on the XML files.
Now you can configure Coresuite Designer in a way that Coresuite Service will take over exclusive rights to batch printing:
1. Administration → Add-Ons → coresuite designer → Configuration → tab Batchprint.
2. Select Coresuite Service from the dropdown in the value User.

 - For the Coresuite Service to take over batch printing tasks, it is sufficient to configure it on the Batchprint tab and start the Coresuite Service.

Parameter Resolving in Grid Configurator

After introducing the new feature where it is possible to use multiple values from CFL of Grid Configurator, this change brought issues for existing Grid Configurators due to queries used in it. After investigation, we found that we are not able to make old queries (which were designed for 1 value) working with the new multi-select functionality.
We are now bringing improvement, where you can decide if you want to use the old behavior with one value being selected, or you will adapt existing queries and use Allow multi-select parameters on tab 3. Query of each Grid Configurator.
 - Please see the sample queries for single parameter value vs multi-select in the attachment SampleQueries.sql.

Logging Improvements for Coresuite Service

Usually, it is not recommended to run rules in Coresuite Service very often (every 1-60 seconds) due to queries that might take longer to run, or other rules being executed at the same time leading to conflict/locking occurrences and delaying other tasks. However, even rules being triggered each minute could cause there will be many entries in the log table @COR_CUSTOM_SVCLOG. This improvement disables logging of the "Rule successfully executed: %RuleName% " messages by default and you decide if you want to log them or not by adding the following line of the code in the rule:
CoresuiteServiceAPI.DebugLog.Info(companyDatabase, "Rule successfully executed: SAMPLE: Print Open Sales Orders");

We are delivering this change in the sample rule "SAMPLE: Print Open Sales Orders" and also "SAMPLE: Print Open Sales Orders Load Balancing", however, as we are not overwriting our sample rules, these new improved sample rules will be deployed only on new databases (where Coresuite was not installed previously).
Both improved rules can be found also below in the attachment SampleRules.cocu.

Specific Directories for Custom DLLs

Currently, Coresuite Designer and Customize are loading dependencies from the base directory of the company DB folder. This causes unrelated DLLs to be loaded into memory, which has a cost in performance.

If the customer has many custom DLLs, it is now possible to increase the performance by placing their dependencies in the given directory. To allow the customer to adjust to the new feature, it is required to create the following directory in the company DB folder and place DLLs in the folders accordingly:
 - COR_Dependencies\Designer
 - COR_Dependencies\Customize