Release 3.7

Ajay Khanna Updated by Ajay Khanna

Released in Nov 2021

We are thrilled to announce our newest release, 3.7. This release is full of several key enhancements to improve user's experience and ability. Read more below!

Admin

Usage Data Model BV Built

Operating a scalable Augmented BI platform for large number of users in the enterprise requires understanding how resources are consumed and how the users are engaging with the functionality in the application. In order to help administrators and users understand their usage, Tinace is introducing new Usage Business Views (UBVs). The UBVs offer transactional details across both the infrastructure and application usage.

UBVs comprise of the Usage Statistics, Job Statistics and Infrastructure Metrics business views. These BVs get updated continuously with information on the types of objects and datasets the users interacts with most, the jobs that get submitted on the infrastructure metrics consumed by the instances of Tinace. The BVs can be used in a flexible manner to perform search as well as build bespoke vizpads, with the views and KPIs of choice for the purposed of the admins. For a detailed description of the UBVs and what they track, please see the Usage Business Views article.

Support to add role to user group

The roles for users will be adjusted based on the highest role assigned to them within a group. This becomes the user's "effective" role.

Scenario: Suppose a User has ExplorerRole and Admin add the user to AdminRole user group. In this case, user’s access will be updated to the Admin role from ExplorerRole. If the admin removes the user from the AdminRole group, Users access is returned back to ExplorerRole (i.e. previous role of user) or ViewRole if not defined by admin or no previous role existed.

SSO Improvements

In Tinace 3.7, admins can enables SSO methods including LDAP, OIDC or Azure AD. When SSO using LDAP or Azure AD is enabled, by default the users will get a message at login to use the respective credential instead of a Tinace credential. The users can still opt to use the Tinace native login with the Tinace credentials, even if other SSO options are enabled by default.

Settings Menu:

Login screen:

Mobile App Updates: Search and Feeds

In Tinace 3.7, we have updated the Tinace Mobile iOS and Android native apps. We have added two new exciting features for search and feeds. This will enable users to perform a search against their Tinace instance while on the move. Additionally, users will have access to the latest Feeds of the KPIs of interest directly into the mobile app. With the Tinace Mobile app, users can get explore and access their business insights on the GO.

Search in Tinace App:

Feed in Tinace App:

Data

Display Name for Business Layer across all Tinace

In Tinace 3.7 we complete the integration of Display Names across the entire Tinace application. The Display Names is a concept that allows business users to add business names on top of the variables in the datasets and Business Views. This is the preferred method of changing the names for variables (as opposed to renaming columns) as it assures that there is no disruption in terms of refreshing the data in Tinace.

Display Names now have been integrated in the following areas of the application: Discover, Predict, Prepare Data and Business Views. For more detail please review the Display Names article.

Auto Partition Discovery for JDBC Sources

In Tinace 3.7, the auto-partition discovery was added for JDBC Sources as an option that is turned on by default. This helps speed up and scale the way data is loaded into the application. Tinace has added automated calculations and suggestions to guide the user through the partition process. Once datasource is configured, the following steps are followed:

  1. User selects the Partition column for a drop down
  2. Tinace will load a subset of data, analyze data and recommend the partitions to user along with the logic of Partitioning and an explanation of how to provide a partition column
  3. Tinace will automatically partition for datasources like MySQL, Oracle, MSSQL when data is imported from JDBC sources.

SQL scripting support across multiple datasets

One of the exciting features in Tinace 3.7 is related to the flexibility added to support SQL scripting using multiple SQL tables as input and one SQL table as output. In addition to writing code from scratch, this feature is tremendously valuable for data engineers who have already existing code they can just move and run into Tinace with minimum edits. The scripting feature in Prepare Data allows users to engage in the following steps:

  1. Select one of the Input tables and then select Scripting from the view tab
  2. Select all the Input Tables, Name the Output Table and Create the Script
  3. Insert the Script, Run Validation and Create the Dataset
  4. View the Output table, go Back and edit the script

For more information please see details in Multiple Datasets Scripting article.

Comparison using "Contains" Operator

In Tinace 3.7, the search experience is enhanced from using the "=" operator to being able to use "contains" operator. This is particularly valuable when users are interested in querying dimension values like names of products (example: Movie Title contains Avengers).

Keyword free typing in Search queries

In Tinace 3.7, the user can now select a highlighted Entity in a previous search query and freely delete it or edit it with a basic type function without needed the drop down of suggestions. This is valuable if the users know exactly what the value they are interested in querying.

Did we help you?

Release 3.8

Release 3.6

Contact