Release Overview

Release L2024.3 provides a number of new features, improvements, and fixes to Sisense for Linux.

What's New

The following table lists the high-level impact (or potential impact, if any) of new features, and how to handle it if upgrading to version L2024.3 or newer. Continue reading the Release Notes below the table for a detailed explanation of these features, as well as improvements and fixes.

Feature	Issues and Actions to Consider
SRV Connection String Now Supported in MongoDB Connector	There are no specific actions to consider - this is an optional capability.

SRV Connection String Support in MongoDB Connector

The MongoDB connector for ElastiCubes now supports the SRV connection string (see https://www.mongodb.com/resources/products/fundamentals/mongodb-connection-string ). When the “Use Svr Connection” checkbox is marked, the input field for “Port“ is hidden and the provided SRV connection will be used.

The MongoDB connector has been updated and now supports MongoDB versions 5.0 & 7.0.

What's Improved

Audit Logs

The Audit logs are now always enabled. This is non-configurable.
Password changes will now be audited in the Audit logs.

Build

Now, in ElastiCubes with failed builds, the latest build logs are displayed each time a user opens such a data model. This simplifies accessing data required for fixing the issue by the user.
The build flow has been extended with additional validations to proactively inform users about potential issues and prevent usage of corrupted data in dependent assets.

The following validations have been added:
- "DataIndexingValidation" - Validates that all keys and values in dimension tables are unique
- "RelationDimTablesValidation" - Validates that all dimension tables that were created for relations between tables include all of the possible keys and values
- "IndexingDimTablesValidation" - Validates that all dimension tables that were created for indexing include all of the possible keys and values
All of the validations are included and enabled by default in the build flow and fail the build with corresponding messages displayed in the build logs. In most cases, rebuilding fixes the issue.

Database

Several database optimizations have been implemented, including: refining complex queries, adding new indexes, and removing unused indexes. These improvements have led to performance gains in API response times, particularly in Sisense instances with large numbers of users, dashboards, and widgets.

Data Models

It is now possible to easily access the OID of data models’ entities, such as Model OID, Dataset OID, and Table OID.

Export to Excel V2

When exporting a Pivot widget to Excel, you can now choose between repeating rows (displays repeating row values in each cell) and merging rows (merges cells with repeating row values).

Git

Previously, creating a Git project on an instance with a large number of users and assets may have been very slow. The performance of loading assets available to be added to the project by relevant users and the overall project creation flow have been improved.

Infra

Due to the deprecation of the component, the deployment of model-logspersistence has been removed from the application.

Mobile

Sisense Mobile App version 3.0.1 has been released, and includes the following improvements:

Implemented session inactivity support in the mobile app for all authentication types
Added direct login support for internal users in the mobile app when SSO is enabled. In order to login with Sisense credentials:
- In the server selection screen, enter the direct login URL: {your_server}/app/account/login – this opens the direct login screen
- In the login screen, enter your Sisense user name and password
Fixed SSO error handling and overall SSO stability
Many minor improvements

Important - Session inactivity flow:
- In case of activity in the mobile app, the session expiration timeout will be extended (only for activity with requests - menu, elements, dashboard, and filters menu will not take effect)
- Logout after the session expiration timeout will be performed only in case of re-rendering

What’s Fixed

Add-ons

Report Manager - Previously, CSV files generated by the Report Manager were limited to 50K rows. This has now been fixed, and will contain the same number of rows as when downloaded directly from a dashboard UI, even if more than 50k.

Data Models

Previously, if an .sdata file was renamed, attempting to import it failed with the following error: "java.lang.NullPointerException: Cannot read the array length because "dbs" is null". Importing .sdata files now works as expected.
Previously, when the same column of the data model was renamed in different tabs of the same browser, it returned the following error: "Validation error: Invalid table schema. The table contains duplicate column names.". Now, it works as expected, using the latest updated name of the column.
Previously, duplicated custom import queries would still point to the table ID of the original import query, which resulted in query errors and failed widgets. Now, logic for identifying tables works as expected.

Data Security

In earlier versions, you may have encountered dashboard loading errors in cases when no permitted values by data security rules were found for them. This has been amended, so that such dashboards are loaded as expected and display no results.

Email Reports

Previously, upon transferring ownership of a dashboard, the new owner was not able to modify and save the report schedule, since their changes would be lost after republishing. This has now been corrected, so that the reporting schedule configured by the user is saved after republishing.

Export to PDF

In earlier versions, the PDF formatting configuration in the PDF report settings was sometimes not being saved after a user had saved it successfully several times. This has now been fixed, so that the selected PDF format is saved upon every attempt.

Filters

Previously, setting a datetime filter with a level different from the level of a background filter led to filtering out some relevant periods' data or receiving no results. This has now been fixed, such that the data is displayed for all periods of any date level that are filtered by a user, as scoped by the background filter.

Git

Previously, the color palette of dashboards tracked in Git projects reverted to ‘Vivid’ and created unintended uncommitted changes. This has been fixed, and now works as expected.
Previously, pulling commits that included deletion of the asset from the project was not reflected in the target environment. Now, the asset is deleted from the list of tracked assets of the project. Note that in such cases the asset is not deleted from the actual DB, which is by design.
Previously, when the owner of a Git project was deleted from the system, the project was not accessible. Now, ownership automatically moves to the system admin, and the project's accessibility remains the same.

Multitenancy

Previously, white-labeled organization tenant logos were redirecting to the system tenant home page. This has now been fixed, such that clicking an organization tenant logo leads to the tenant's home page.
Previously, it was possible to assign a Tenant Admin role to a system tenant user by editing their role. The Tenant Admin role would then be locked without the possibility to revert the change. This has now been corrected, such that the Tenant Admin role cannot be assigned to users in the system tenant.

Notebooks

Previously, outdated Notebooks query results that were no longer used were not cleaned up properly, thus consuming storage space. As a result, some customers experienced disk space issues, for example not having enough space to back up data, etc. Now, the Notebooks files and folders that are not linked to existing Notebooks are cleaned up automatically on a regular basis, thus avoiding unnecessary storage consumption.

Perspectives

Previously, when there were a lot of tables in the perspective, or a table expanded to see all columns, the layout of the Apply/Cancel buttons got corrupted, making it hard to design such perspectives. Now, the layout of the buttons is correct regardless of the amount of tables or columns in the perspective.

Simply Ask (NLQ)

Simply Ask now displays an error message when a query fails to run.
Previously, table names were not hidden properly when the hide table name configuration was enabled. This has now been fixed and works as expected.

Usage Analytics

In earlier versions, exporting widget to image was not recorded in Usage Analytics. This has been fixed, and widget export to image now appears in the Usage Analytics data.

Web Access Token

Previously, when viewing Sisense assets via Web Access Token (WAT), the Notebooks tab was available to users. Since Notebooks are intended for writing ad-hoc queries and easily transforming them into visualizations, this tab is not relevant for the WAT end-users, and therefore it has now been removed from WAT.

Widgets

In earlier versions, after using the zoom bar on charts, the browser menu sometimes overlapped the right-click menu on value points. This has now been fixed.

Widget Script Customizations

In earlier versions, modifying a query limit via a widget script was ignored during query execution, thus having no effect on the widget results. The implementation has now been changed so that it is possible to override a query limit per widget by changing the 'query.count' property.

What's Coming

Among many other improvements and fixes, the following major feature is expected to be released in the next Service Update.

Connection Management (GA)

With the L2024.3 Service Update 1 release, Connection Management moves from Beta to General Availability (GA), becoming the unified solution for managing data source connections. This feature enhances governance, security, and efficiency in managing connections across assets such as ElastiCubes, Live Models, and Notebooks.

Key Use Cases

Reuse Across Multiple Assets: A single connection can be reused across multiple data models and asset types (ElastiCubes, Live Models, Notebooks), streamlining connection management.
Secure Sharing: Connections can be shared without the need to expose sensitive data, such as login credentials or passwords, ensuring security across teams and users.
Centralized Management: Centralized management and governance enable administrators to control and monitor all connections from a single location, simplifying oversight.
Instant Updates: Any changes made to a connection are instantly applied to all dependent assets, eliminating the need for manual updates and ensuring consistency across the system.
Encourages Connection Sharing: The system encourages the sharing of existing connections to reduce duplication and maintain a streamlined connection structure.
Visibility and Dependency Management: Gain visibility into all assets that depend on a connection, with the ability to manage dependencies, ensuring that any connection changes are carefully handled.

Migration Details

Conversion of Old Connections: All legacy connections are converted into the new managed connections format.
Setting “supportedModelTypes”: The connection type is determined by the asset it was converted from:
- NOTEBOOK: If the connection was converted from a Notebook
- EXTRACT/LIVE: If the connection was converted from a Data Model
Deduplication of Connections: Keeping only unique connections aiming to prevent duplicates. If there were multiple connections with identical connection details but owned by different users, they are converted into two separate managed connections.
Ensuring Backward Compatibility: All assets that previously used these connections will continue to function seamlessly, maintaining full backward compatibility.

When working with Git projects, the following actions should be taken into consideration:

Commit the Converted Connections: After migration, each converted connection is assigned a new OID, which appears in the Uncommitted section of your Git project. It is important for users to commit these changes rather than discard them, ensuring proper tracking of the converted connections and maintaining the consistency of the data models.
Handling Merge Conflicts Across Environments: Since migration occurs independently in each environment (e.g., Dev, Stage, Prod), the same data model may have different managed connection OIDs across environments. This will likely result in a merge conflict when pulling changes from one environment to another. Users must resolve this conflict one time by selecting the connection that should be used with the data model across all environments.

This migration process ensures a smooth transition to the new Connection Management system without disrupting existing workflows or assets.