2021.1 - DataClarity New Features and Enhancements

DataClarity 2021.1 brings the following new features and enhancements:

Data Preparation


Installation & Configuration



Save data connections without testing it

Previously, you could save a data connection only if it passed the connection test successfully. Starting from this release, you can save a data connection even if the connection cannot be established. This may be useful when you don’t have the proper credentials at that time or need to verify other connection details. However, to save a connection, you need to complete all the fields.




Load data incrementally in Table

Starting with this release, the Table widget can load data differently depending on your needs―load all the data at once or load the rows incrementally.

By default, all the data rows are loaded at once, limited by the value in the Maximum data rows field. If you have a large dataset with many rows, loading all of them at once may take some time and make your interaction with the Table inconvenient. In this case, you can choose to load data incrementally (server-side), where each set of data (increment) is queried separately. The number of rows to load is defined in the Incremental load field, set to 50 by default.

The incremental data loading improves performance but has some nuances:

  • The Totals row appears on each page, showing the sum of the data that is already loaded. For example, if the incremental load is 50 rows, you will see the total for the first 50 rows, then for 100, and so on.
  • The pagination bar shows the page total number after you load all the data.
  • Grouping and pivoting are not supported.



Filter published and embedded storyboards with query parameters

Now, you can filter the embedded and published storyboards by using query parameters. To do so, add a filter through the Filter widget and then specify a parameter name in the Parameter field.



After generating the URL for a storyboard, you can add the defined parameter name with one or multiple values to the URL as needed. For example, if you add “&store=Mall,Standalone&dep=Electronics” to the published storyboard URL, the visualization shows data only for the Mall and Standalone store types with the Electronics department.



When using query parameters, consider the following:

  • Values for the filter parameter should be the same as listed in the Filter widget.
  • If using multiple values, separate them by a comma. For example, “&city=London,New%20York”.
  • Each parameter starts with an “&” sign. For example, “&store=Mall&dep=Electronics”.
  • If the values have spaces or other special symbols, convert them appropriately for the URL encoding. For example, “&city=New%20York”, where the space character is specified as %20.
  • Filtering applies to all the widgets in a storyboard where filters use the same parameter name.



Upload TLS/SSL certificates for secure web connectors and data connections

When the applications need to communicate with other secure servers, it is required to import the third-party certificates into the Java certificate stores for the respective docker containers.

Now, administrators can upload and manage TLS/SSL certificates to secure connections for web connectors and any data connections right from Configuration Manager. In the TLS/SSL Certificates section, go to the Data Connectors page and click Upload certificate. After adding a valid and trusted certificate file (.crt or .cer), click Restart on the toolbar and proceed with the secure connectors in the platform.



Upload TLS/SSL certificates for secure LDAP connections

When Access Manager needs to communicate with a secure LDAP server to work with users' lists, it is required to import the third-party certificate into the Java certificate store for the “user access” docker container.

Administrators can now upload and manage TLS/SSL certificates for secure LDAP connections right from Configuration Manager. In the TLS/SSL Certificates section, go to the User Access page and click Upload certificate and select a valid and trusted certificate file (.crt or .cer). After adding a valid and trusted certificate file (.crt or .cer), click Restart on the toolbar and proceed with the secure LDAP connection in the platform.



Use Personal Token authentication for Tableau web connector

If Tableau is configured to use SAML authentication, it cannot authenticate users by credentials. In this case, you can use the Personal Access Token authentication―instead of the username and password, you specify the user’s token name and secret.

The Personal Access Token authentication option is now available in the Web Connectors section, under Tableau Software. If you choose the token authentication, enter the user’s token name and secret as generated in a user’s account settings in Tableau. For details, see Manage Your Account Settings (Tableau).

In the Token username field, you may enter the username or email address associated with the token. This way, when the token expires, you can easily find the user for whom you need to regenerate it. Depending on the personal access token usage, it expires in 15 days (if not used during this period) or in 1 year (if used regularly). You can also change the default refresh token expiry time span in Tableau. For details, see Personal Access Tokens (Tableau).



Configure revision history limit for a Portals application

Administrators can now control the number of portal revisions available as backups in Configuration Manager. In the Revision history limit field, specify the maximum number of portal revisions. By default, the revision history limit is set to 0. This means that the system does not keep any backups, and by saving a Portals application, you overwrite the current version. If the limit is 2, the system keeps two backup versions that you can restore.

To change the revision history limit, go to the Portals section, and open the Revision History page.



Manage authentication for Kubernetes during installation

The on-prem installation is now using the new Kubernetes version 1.19 MicroK8s. The installation script for Kubernetes allows users to choose whether to disable authentication for Kubernetes Dashboard. If the authentication is enabled, an administrator can use an existing token or generate a new one.

When running the installation script, for the Disable authentication for Kubernetes Dashboard option, enter one of the following:

  • y — To disable authentication for the Kubernetes Dashboard.
  • n — To enable authentication for the Kubernetes Dashboard.

If you decide to enable authentication, you will need to use a token to log into the Kubernetes Dashboard. In this case, for the Generate new access token for Kubernetes Dashboard option, enter one of the following:

  • — To generate a new token. You can use it to log into the Kubernetes Dashboard.
  • n — To use an existing token. To view the token, run the following command: kubectl config view –raw.


Release Notes (other formats)

Was this article helpful?
0 out of 0 found this helpful



Article is closed for comments.