L2022.4 Release Notes
  • 18 Sep 2022
  • 3 Minutes to read
  • Dark
    Light

L2022.4 Release Notes

  • Dark
    Light

L2022.4

For a list of release dates and Sisense's end of support schedule, see Sisense Life Cycle.

You can download the latest Sisense version from here.

Note:
  • If you need to upgrade to an older version, see that version’s Release Notes and contact your Sisense Customer Success Manager for the version package.
  • IMPORTANT: Sisense recommends running a system backup before upgrading. See Backing up and Restoring Sisense.

BREAKING CHANGES - WARNING!

  • L2021.12: Server side add-ons break following L2021.12 installation. 
  • Grafana Dashboards
    When performing a Sisense Provisioner or RKE installation, the installation supports Kubernetes 1.22. Therefore, the Prometheus stack was changed from prometheus-operator to kube-prometheus-stack. This means that any private customizations done on Grafana need to be manually migrated (see Upgrading Sisense on Linux). Out of the box, Grafana dashboards will be created on the new stack.
    The RKE upgrade from Kubernetes 1.21 to 1.22 is only supported for RKE or RKE Provisioner installations and occurs if update_k8s_version is set to true in the YAML configuration file. Customizations affected are Grafana dashboards, alerts, notifications, etc., revert to the default state.

Release Overview

Release L2022.4 provides a number of new features and significant improvements to Sisense for Linux.

What's New

This release includes the following new features:

New Sisense Filters

  • Sisense introduces new filters that provide additional filtering capabilities, as well as a more streamlined and flexible filtering experience.
  • The new filters feature is OFF by default. To try the new interface, an Admin must first enable it via the base configuration (under "FiltersModal"). Any active filter sets that you currently have in your dashboards remain active in the new filters interface. Note: Before enabling, take note that any add-ons that rely on the current filters interface may stop working.

See Creating and Editing Dashboard Filters with the New User Interface.

OIDC SSO acr_values for Embed SDK/IFrame Support

  • Sisense introduces support for 'acr_values' for OpenID Connect (OIDC) SSO protocol. 
  • This protocol is compatible with all types of embedding and can be passed via the 'ssoparams' embedding solution constructor parameter.
  • 'acr_values' are used to specify the Authentication Context Class Values within the Authentication Request. 
  • The parameter should be provided in base64 encoding format.
  • For example:  https://example.com/js/sisense.js?ssoparams={params in base64}

Web Access Token - Data Security Per Data Source

  • We have enhanced utilizing data security in the Web Access Token environment, by enabling you to apply data security rules per data source.
  • To correctly apply data security include the new "dataSourceTitle" parameter (containing the title of the queried data source) to each "acl" claim object. 
  • With this new improvement the "dataSourceId" parameter is deprecated and should be excluded from the payload. >> Read More  

Example:

"grants": {
	"acl": [
		{
			"dataSourceTitle": "Sample ECommerce",
			"table": "Commerce",
			"column": "Gender",
			"allMembers": null,
			"datatype": "text",
			"members": [
				"Male"
			],
			"exclusionary": false
		},
		{
			"dataSourceTitle": "Sample Lead Generation",
			"table": "Lead Generation",
			"column": "Country",
			"allMembers": null,
			"datatype": "text",
			"members": [
				"United States"
			],
			"exclusionary": true	
		}
	]
}

Web Access Token - Public Endpoint 'Create WAT'

  • Sisense introduces the capability of generating Web Access Tokens directly from within the application. 
  • Ability to generate Web Access Tokens directly from Sisense can assist users lacking their own developed token generation tool, or simply for generating tokens outside of a programmatic flow. 
  • Structure and logic validations are executed towards the token’s header and payload, with descriptive human-readable error messages. 
  • Previously-created secrets should be regenerated as strings (without break-lines) to pass API requirements.

Example:

What's Improved

Helm 3.8.1 Supported

  • Sisense now supports Helm version 3.8.1 The new Helm version can be used in addition to older versions.

Kubernetes 1.22 Supported

  • Kubernetes 1.22 is only supported for RKE or Provisioner installations. See Upgrading Sisense on Linux.

What's Fixed

BloX

  • Fixed UI displaying escaped special characters
  • Fixed editing BloX custom actions

Embedded Mode

  • Fixed displacement of filters panel on iPad.

SisenseJS

  • CSS rules that are loaded in the scope of Sisense.js are isolated and do not affect the host application.

Web Access Token

  • The format of the generated secret (public key) was changed to string, without line breaks, in order to meet the Web Access Token - Public Endpoint 'Create WAT' API validation requirements. Previously generated secrets should be regenerated if you wish to use Sisense Implementation when creating new tokens.
  • The ability to utilize pivot widgets in the Web Access Token based Sisense.js environment has been fixed.

Video

Watch this video for an overview of selected features from this release:



Was this article helpful?