Welcome to the latest One Model product release update. This article provides an overview of the product innovations and improvements to be delivered on 10 March 2021. You can see the full 2021 release schedule here: https://help.onemodel.co/en/articles/3134972-one-model-product-release-calendar.

User Experience

Export Storyboards to PowerPoint slides

The world works online, but in most business meetings everything invariably gets distilled into a slide-based presentation of some sort. To help customers more easily leverage content from One Model for these presentations we have developed an ability to export a Storyboard to PowerPoint slides. We chose this format because it is also readily read by other platforms such as Google Slides.

To use the new capability open the settings panel in a Storyboard and navigate to the Export tab. There are a few options to select, such as the export quality, number of tiles per slide, whether you would like to include the tile header, or just the charts/tables etc. or if you would like to convert the tile headers to text. Then just press the Export button. While the export is running you won’t be able to navigate to other areas of the application, but you are able to cancel the export at any time. Your presentation will automatically download in the browser.

We are excited to release this much requested product feature and have barely scratched the surface, so we welcome your suggestions and ideas for the next set of enhancements to this new capability.

New Data Visualization Design Capability

Over the last few releases we have been beta testing our new charting capability and releasing new Storyboard design features such as duplicating tiles and improved saving workflow. We have since had many customers starting to use the new capability and wanting to make it available for their broader company user base, so in this release we have made the new charting framework available to be turned on for your entire company instance.

This option is in the Company Setting page. This is a non-destructive switch so if you turn on the new charting and find some issues with any of your data visualizations it can easily be turned off again. This is our final phase of developing the new charting framework before we push the framework as a default for all customers; replacing the older charting. (If you don’t want to turn on the new charting for your entire company yet and want to do some smaller scale testing the One Model team can enable it for a small number of named users, or a test user account.)

So, what’s in the new Data Visualization Design Capability

The new charting provides us with a powerful new platform to extend One Model’s visualization library for customers to deliver tailored insights. In the first instance we are delivering all the capability you have in Storyboards today, but we have also taken the opportunity to add some finesse to the visualizations and a range of new features, such as:

  • a significant increase in the range of configurability options for charts that can all be applied directly from within the Storyboard edit page without the need to return to Explore.

  • Changes made in the design panel happen instantly making it a much faster intuitive experience. As well as all current settings from Explore we have included some new options and will be adding more based on customer input. Notable new features include the ability to control chart axis scaling and min/max, data label formatting & positioning, legend positioning, metric styling (lines, columns, bars, area etc.) bar width & padding. We have also improved the interactivity and hover/highlighting experience.

  • Since the beta release first started we have now included all existing Storyboard charts. The Pie Charts and Scatterplot Charts are the most recently ones charts and these still have a little refinement to go, but this is mostly minor aesthetic items such as label formatting.

  • As mentioned in 2020.02.20 release notes, forecasting is now included with the new charting capability and has improvements to how we display the forecast periods, i.e. as +1, +2, +3 etc. Forecasting now also supports dimensional breakdowns in Line Charts per the example below.

General User Experience Updates

We made some improvements to the display of filter search results, including the ability to expand a large breadcrumb if you want to see the full hierarchy for a particular result. (ref 7387)

We also improved the size of the ‘Saved Filters’ drop-down selector to expand wider to cater for longer names in the list. (ref 7435)

When editing a Storyboard the tile design settings panel would sometimes get unruly, so we added some usability improvements. The design panel button now works as a toggle to open and close the panel and the keyboard ESC key will also close the panel. You can also resize the panel by dragging the bottom right corner. (ref 7711 & 7712)

Improvements to Data Pipeline Processing

  • We've added support for the DATE_TRUNC function from Redshift to be available in our Pipeline script. This allows users to truncate the date and time value to the nearest Year, Month, Week, Day, Hour, Minute, or Second.. (ref 5434)

Improvements to Data Ingestion

  • Added a Prefix configuration for the Workday Custom Reports connector. This prefix will be added onto the table names that are created so that they can be differentiated if the same report is loaded multiple times (and therefore the same table names are re-used). This allows a report to be re-used with different parameters, which is particularly useful for complex Workday reports. (ref 7139)

  • We've improved the ability to retry API Runs that error when a task is almost complete. Historically, the data that was created by the first attempt would cause the second attempt to error when it tried to write the same data. (ref 7137)

  • We now automatically include closed positions in data requested from the Get_Positions endpoint Workday, by always setting the "Include_Closed_Positions" Response Group to "True". (ref 7446)

  • Improved the stability of the Greenhouse connector in case of temporal errors in Greenhouse. (ref 7569)

General Platform Improvements

  • In the 2020.12.09 product release we delivered an enhancement to the Create/Edit Metric page providing the ability for users to rename the metric categories. In this release we have extended this to allow you to also now edit the metric cub-categories. (ref 7473)

  • We are now sorting Data Destinations in Alphabetical Order in the Explore and Data Destinations pages. (ref 7803)

  • Added the ability to Cancel Data Destinations while they are running. (ref 7377)

  • We made a change to how PGP keys are named, when generated by One Model, as we found some customers are using their company name as the name of PGP keys for other products, which could cause confusion. Until this change, One Model used the Company ID as the PGP Key name and this is often the same as the Company name, so now we will use the full URL including the onemodel.co extension, e.g. [company name].onemodel.co. (ref 7805)

Bugs Squashed

  • We made some improvements to how role based permissions are being applied to some drill-through queries. In some rare scenarios, if a metric (such as Terminations) had different Role-Based Security to another metric that referenced the same metric (e.g. Termination Rate, which has Terminations as part of it's calculation), the Drillthrough engine would simply restrict all results for the Termination Rate metric. This issue didn’t represent a security concern, but rather was too strict in applying security, so we have improved this to appropriately resolve all the metric permissions for the user. (ref 7437)

  • Improved the stability of queries in cases where Role Based Security is configured to restrict on a very large number of dimension nodes, which would increase the query complexity to unmanageable levels.(ref 7218)

  • Fixed an issue where the Oracle V2 connector could error trying to create a duplicate table name when loading Absence data. (ref 7474)

  • Fixed an issue where Data Destination Pipeline Scripts wouldn't run without having a "create model", "create fact", or "create dimension" statement. As these statements are no longer required to run a Pipeline Data Destination script, it shouldn't error in the future. (ref 7433)

  • Fixed an issue where SFTP Data Sources would not ask for confirmation before they were deleted. (ref 7752)

  • Improved the stability of queries in cases where Role Based Security is configured to restrict on a very large number of dimension nodes, which would increase the query size to unmanageable levels. (ref 7218)

  • Fixed an issue where Data Destinations based on an Explore query could error if a row or column (such as the slice of a Dimension) had some values, but not values for all cells in the row or column. (ref 7493)

  • Fixed an issue where some of the expandable panes in the Data Destinations run page would automatically collapse within seconds of being expanded. Now they will stay expanded until the user collapses them. (ref 6870)

  • Fixed an issue where the SuccessFactors connector could error for some unexpected configurations of the Recruiting module within SuccessFactors. (ref 7296)

  • Fixed an issue where the Data Access Roles "Columns" page would error if some tables that had been enabled were deleted from the role. (ref 7434)

Did this answer your question?