Since our last update we have been focusing on adding some simple customisation options to our bar and column charts, and we’ve been improving the output from our journey completion statements in order to support Waves as part of the ecosystem first approach that the Product team as a whole is trying to live by. Much of the feedback we continue to receive from clients and within the business is around simplifying the product and improving the performance, so many of the features you see over the next few months will have this mind.
Chart Data Labels
What it is:
For both the Bar and Column chart visualisations we have added a toggle in the options menu that allows you to show the data labels on the bar or column. Switching the toggle on will simply show the respective counts providing there is a sensible amount of space to do so. An example of this is shown below.
Why we have done this:
We received feedback from a number of customers who had wanted to be able to see what the actual value was without the need to hover over each element in the chart. This was designed to try and make it easy to glance at a chart and get the counts without having to waste time getting the accurate numbers.
We felt that there would still be scenarios where someone might not want this so the toggle appeared to be a sensible choice to avoid changing existing charts already in place, allowing customers the freedom to make the decision without us dictating it.
How it works:
A short video explaining how the new feature works can be found here:
Persona names for journey completions
What it is:
This is an update to an existing feature for journey completion statements. Before if you added the setting and chose a store you would get a completion statement, but the Persona name was not pulled through. The update now correctly adds the Persona name to all of the statements.
Why we have done this
This one has two main benefits. The first is to make the data easier to read for anyone looking to make use of journey completion statements in their reporting, adding the Persona name makes it clear who has completed the journey, so the overall UX is much better.
The second reason is to support the Waves platform available as part of the suite of products we have at Learning Pool. Waves uses the Persona name when creating emails to learners so by adding this feature we have avoided the need to create workarounds.
How it works
A short video explaining the new feature and a refresher on how to use this part of journeys can be found here: https://www.loom.com/share/4d5098acec134448af23886271bac4c3
We are continuing to work on rebuilding the way we handle aggregations in Learning Locker. There won’t be anything you have to do when we release this in about a month's time, but you will notice some changes which will be outlined in documentation and videos that we make available in advance.
See more on our roadmap https://learningpool.com/roadmaps/learning-locker-roadmap/
- Dashboard widgets: Minimum height has been fixed to allow a user more flexibility with the size of the visualisations.
- Personas Import: Fixed issue where large persona imports were affecting the performance of the worker jobs.
We are also currently improving our feature request process across all Learning Pool products. We will
soon release some info on how our feature request and product design process works so that you can
see how we go about identifying the core of the problem and then deciding on the best solution to solve
In the meantime, we have removed the feature requests form from the help centre website and you
should now contact your Learning Consultant who will manage the feature request for you. Partners,
please contact email@example.com