Breaking Changes in Jedox 2022.2

The conditional formatting rules have been changed to align with Microsoft Excel in the following situation: if a cell range contains both a zero value and an empty cell, the zero value is no longer marked as a duplicate value by the conditional format.

As announced in the Jedox 2021.2 Release Notes, the new, REST-based Macro Engine wrapper function for Integrator is now used by default when requiring the "integrator" library. The SOAP-based wrapper function can be used only when requiring the "integrator-soap" library.

Both the REST- and SOAP-based wrapper functions are functionally equivalent, but may return different error messages.

Security vulnerabilities

When TFilter in a stored subset passes an empty regular expression, the stored subset will now return all elements, thus behaving the same as a PALO.SUBSET formula. In prior versions, such a TFilter in a stored subset returned an empty result.

There is a change in behavior of the In-Memory DB (OLAP) during startup if the "System" database is damaged or missing.

If the System database is missing, the server will by default print an error message in the log and abort startup. The server will start only if a specific new key is defined in palo.ini, and a new System database will be generated with default users, groups, roles, and passwords.

If the System database exists, but is damaged and cannot be loaded, the server will abort startup in all cases. The System database then either has to be manually restored from a backup or removed; if removed, when setting the new configuration key defined above, the server will generate the default System database.

There has been a change in the handling of Standard and Parallel jobs where a variable is set with an empty value.

From 2021.1 and on: the empty value of the variable is used in the execution.
From 2019.3-20.4: the empty value is ignored and the global default value of the variable is use

The following configuration parameters have become obsolete and have been removed from config.php:

• CFG_ETL_LEGACY
• CFG_CURL_REUSE and its comment "// enable curl conn reuse"
• CFG_IE8_COMPAT_MODE and its comment "// enable IE8 compatibility mode"
• CFG_AHVIEWER_PATH and its comment "// ad hoc viewer"

In favor of reduced resource usage, improved average performance, and general reliability, the current implementation of multi-core rule processing within the DDE rules engine has been deprecated.

As of Jedox 2020.4, new installations (setups and managed/Cloud) will ship with the "engine-configuration 1" setting in palo.ini. The internal default configuration will be changed in a future version.

Note that multi-core aggregations are not affected by this change.

The handling of inputs on Web spreadsheet cells that are formatted as a percentage has been changed. On such cells, when a value is entered without specifying the "%" character, the value is still interpreted and set as a percentage value. This behavior is aligned with Microsoft Excel.

For example, entering "50" on such a cell will then show 50% in the cell (0.5 being the actual cell value). The result when actually specifying the percentage character is not changed.

Note: this change impacts OLAP writeback on base cells. When making a numeric input on such a percentage-formatted cell with a PALO.DATA function, the value sent to OLAP will be divided by 100. For example, imagine that an OLAP base cell contains the value 0.05, and this value is shown in a spreadsheet cell, formatted as a percentage. The shown value is "5%". If the user now enters "10" (without a percentage character) on this cell, the value 0.1 will be sent to the In-Memory DB (resulting in the cell then showing 10%). In previous versions, the value 10 would have been written.

A specific query can return many, many records in a result (e.g. for large dimensions), which would in turn create many rule instances. For performance reasons, queries are by default limited to a maximum of 1000 records.

Before Jedox 2020.3, the number of rule instances created was in fact limited to 1000, but did not result in an error message. As of 20.3, an error will instead be returned, and no rule instances will be created in this case.

Compare, which was a possible value in the dimension-file-format of the palo.ini, is obsolete as of 20.3. It will be removed from the list of possible values in version 20.4 of the OLAP server.

When you create a time dimension in Data-Driven Modeling (DDM), the hierarchy is similar to that in the Time Editor. The dimension will also be assigned the dimension type “Time”. Note: the <targetformat> parameter for column headers is no longer available.