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

User Experience

WalkMe integration

  • To support high touch digital adoption for people analytics and provide additional support with guided training for users, some One Model customers have started reviewing the WalkMe Digital Adoption Platform. One Model has been collaborating with customers and the WalkMe team to build a product level integration. (This nicely complements the feature we delivered in the last product release allowing customers to customize the help link in One Model.)

  • From this release, One Model supports the embedding of the WalkMe product into a One Model customer's instance, which supports the delivery of custom user help and guided step-by-step interactive tutorials for using product features as people work.

  • On a technical level, each One Model & WalkMe customer has their own dedicated piece of code (known as a "snippet”) that connects the products together. The WalkMe team can help you understand how this works and once you have your WalkMe snippet, the One Model team embeds this into your specific instance configuration.

Bugs Squashed

  • Fixed an issue where a null Dimension Node ID being referenced in a metric would break the Edit Metric page. (ref 8619)

  • Fixed an issue where the Cache Warming job could error on queries with large datasets. This was reducing the performance of the application by preventing any subsequent query from being cached by the cache warm job. Depending on how early in the process the Cache Warm job came upon a query that caused the error, this could be a large number of the queries. (ref 8627)

  • Added some validation to the Processing Script to check that a GROUP BY clause has all required columns for the SQL to run. (ref 8444)

  • Fixed an issue where column calculations in the Processing Script that weren't given an alias would show a non-descript validation error that was hard to track down. (ref 8560)

Did this answer your question?