0

Incorta Analytics Version 3.1 Release Notes

The following table includes a list of the features and main fixes in version 3.1. 

WARNING: If you are upgrading from a pre-2.9.2 release, system administrators MUST run the migration tool "migrateScheduledJobs.sh" in order for schemas with existing auto-refresh jobs to continue working. This tool is shipped with the Incorta Analytics package, in the "<INSTALLATION_PATH>/bin" directory. If the migration tool is not run, schemas will stop refreshing automatically. Learn more

Area Feature/Enhancement
Engine Incorta Analytics 3.1 includes a revamped Data Engine, featuring enhanced performance and stability. This change removes the 1.7 billion record-per-table loading limitation, allowing unlimited records to be loaded as long as there is sufficient machine, and Tomcat (heap), memory assigned.
In this release, there are a few changes in the admin UI (Engine) properties. These changes empower Admins to control the maximum number of groups that cannot be exceeded in an Insight. This prevents individual users from running very costly dashboards, and thus impacting the overall system performance. Learn more
Business Schemas This release includes a new enhancement in the Business Schemas area that allows creating folders to help organize business views. Grouping business views in logical folders helps users select the correct business views when choosing attributes for an Insight. Learn more
There is a new enhancement in the syntax parser affecting the creation of business schema columns that are defined using presentation variables. In order to create/edit such columns, you would need to follow a few steps. Learn more
Schemas Incorta Analytics 3.1 now offers the option to export scheduled jobs along when exporting schemas. At the time of exporting a schema, a prompt gives schema managers the option to export existing scheduled jobs. If this option is selected, the exported jobs from the source will overwrite the scheduled jobs existing in the target system. If this option is not selected, only the exported schema will overwrite the schema in the target system, leaving the scheduled jobs in the target system unchanged.
In this release, Incorta Analytics now supports Type 2 dimension joins using the primary key only. Learn more
Administration This release offers the option to configure the number of schemas and tables to be extracted in parallel per tenant. This can be done setting the pool size for loading tables and schemas in the admin UI, which can be accessed at "<IP_ADDRESS>:<PORT_NO>/incorta/admin". Learn more
Security Incorta Analytics now allows SSO users and internal Incorta users (i.e. users with Incorta username and password) to log in to the same Incorta instance. If you want to share an Incorta instance with your Employees and consultants, you can enable SSO for internal employees, and internal authentication for consultants or suppliers. Incorta Analytics allows you to sync both sets of users from an LDAP server.
T his release provides a solution for Active Directory setups containing referrals. Users now can search the global catalog when the scope of the search is not in the same domain/organizational unit as the contacted domain controller. Learn more
Data Sources and Data Files Incorta Analytics now supports Salesforce version 41. Existing users must update the Salesforce URL for the Salesforce definition in Incorta post upgrading to 3.1.
Analyzer Users with the "Analyzer" role can now group by timestamp columns. That is, in the Analyzer, a timestamp column can now be used in the grouping dimension field.
iOS Mobile Application This release avails Incorta Analytics as an application for iOS mobile devices. For the steps required to get the application and set it up, click here
UI Updates This release includes an enhanced design in the "Business Schemas" and "Analyzer" screens, changing the way users select columns in business views, formula builder, schema editor, and more.
Incorta Analytics will only show the parent tables of tableA that are in the same schema when defining a formula column on tableA. This is because formula columns are created at a row level, so it only makes sense to denormalize the data from a parent to child without changing the grain of tableA. If tableA has a parent table (tableB) in a different schema, that table will not be available to use when defining the formula column. Incorta only supports formula columns defined based on the same schema, to ensure that every data refresh is automatically carried out to the formula columns whenever it applies.
Reply Oldest first
  • Oldest first
  • Newest first
  • Active threads
  • Popular
Like Follow
  • 3 mths agoLast active
  • 17Views
  • 1 Following