Release Notes - 2021.08.25

Introducing a new Data Destination - Azure Data Lake Storage Gen 2. You may recall that we recently added a new Data Destination for Azure Blog Storage and in this release it is now possible to send data from One Model to the Data Lake Storage Gen 2 storage in your Azure instance. For configuration details, please refer to our guide to Configure an Azure Data Destination (ref 9101)

Introducing a new Data Destination - Snowflake. It's now possible to send data from One Model to your Snowflake instance. For details on how to configure a Snowflake Data Destination, please refer to our guide to Configure a Snowflake Data Destination (ref 9340)

We made some subtle formatting changes to the csv files you can download from the user upload screen so that they more closely match the upload file format in case a user wanted to copy this content for re-use in an upload file. Most notable changing boolean true/false columns to be shown as Y/N. (ref 9149)

To make it easier to manage a large list of Company role mappings when using either the SSO or file upload automated role assignment capabilities we have sorted the tables in the Company Admin screen to display Company Roles. (ref 9361)

We've run into some cases where Oracle doesn't always send through the full list of Workers when their API is queried, so we don't always have the full list of workers to query. We now track Worker IDs that were returned from previous runs, and will continue to query the history of those workers even if Oracle doesn't send us their ID on a given run. (ref 9038)

We've enhanced the stability of our SFTP Data Source during One Model product release updates. The job will now restart reliably if it was running when One Model was updated. (ref 9066).

We are continually tuning and optimizing One Model’s product and operating environment to improve performance and over the course of the last month have delivered a number of major enhancements to some core platform capabilities and our query engine, notably increasing the number of concurrent queries that can be run in the production environment, caching enhancements and improvements to handling very large dimensions.

We have Application Access Role permissions that control which roles are able to perform actions such as create, edit or delete Storyboards. Users without the specific permissions could previously see the Delete Storyboard menu option and while they could not perform the action due to the underlying Application Access Role permissions we cleaned this up so that they now can’t see the delete option. (ref 9279)

In some rare scenarios an error in a single tile within a Storyboard could cause the entire Storyboard to not load for a user. We have enhanced the framework so that there will be an error message displayed in the specific tile, while allowing the rest of the Storyboard to load. We have also retained the ability for a user to use the tile action menu to review the data query for that tile via Explore if it is something that could be corrected by changing the query definition. (ref 9257)