Release notes – OrgVue version 2.24

Documentation release date:2nd February 2017

In addition to usability enhancements, the OrgVue version 2.24 release includes an interactive gantt chart (Gantt View), which is specifically designed to support complex workforce planning scenarios and two new dashboards.

Note: a link to a downloadable version of this article can be found at the bottom of the page.

New features

New dashboard landing page

The release of 2.24 introduces 2 new dashboards, making a total of 25 analytics dashboards to choose from in the tool. To help users find the right analytics within seconds, we’ve created a new dashboard landing page, which organises the dashboards into five categories:

  • Core
  • Org Analytics
  • Time Series
  • Processes
  • Competencies


Hovering over a dashboard allows users to read a short description of the dashboard's use case and requirements.The example below shows the tool-tip for Changes Report:

Users also have the option to show/hide the dashboard collection by category.

NB: Some dashboards are listed only when an appropriate type of data exists in the data set. For example, if there is no Date property in your dataset, 'Time Series' category of dashboards are not listed.

Gantt View

The Gantt View is the primary new feature of OrgVue 2.24. It is an evolution of the Gantt chart available within dashboards. The Gantt View is accessible as an additional component to the worksheet and allows for fully interactive editing.

While Gantt charts are common in project planning, it hasn't been widely used for workforce planning. OrgVue's Gantt View can support complex operational workforce planning - allowing users to do capacity planning over short, medium, and long-term horizons.

The Gantt View may be used within any dataset type. It can be used to represent joiners and leavers with a People dataset, a capacity plan with a Roles dataset, or a traditional project plan within Processes or Objectives.

To be able to use the Gantt View, there must be two properties, Type > Date, in the dataset to indicate start date and end date.

Any type of Date properties in the dataset can be chosen to enable the Gantt View functionality but either the properties' alias must be set, using only keywords startand end, or the properties are explicitly named Start Date and End Date. The example below shows how the property 'Leave Date' has been given the alias end.

Once OrgVue detects the date properties with their associated startand end aliases (or property names), a new panel is added to the Property selector for the Worksheet.

The panel allows for:

  • Optional display of the Gantt Chart itself, its time range (for scaling), and granularity
  • Optional display of a Footer to summarise a chosen metric over a time period


Dragging a gantt bar shifts it on the timeline and always snaps it to the chosen time unit. This interactivity can simplify planning activity, e.g. if planning occurs at a month level, the start and end times can be fixed to that unit.

Dragging the left end of the bar will shift only the start date, while dragging the right end of the bar will shift only the end date. Dragging the bar itself will shift both the start and end dates. In all cases, holding the Ctrl key down when dragging will directly set the date without raising the Set Property Value dialog.

For any given node, the gantt bars have four different display modes, dependent upon the values of the properties associated with the start and end date states.

  • If both start and end properties have values set, the bar has handles on both ends. If any of the two handles extends beyond the timeline, an arrow is shown at the origin to jump to that date.
  • If neither start date nor end date properties have values set, then a + button is provided to set the dates.
  • If no end date property value is set, then the bar logically extends for ever. The bar is represented as dashed lines at the maximum date in the data (or today, if that is greater).
  • Finally, if there is only an end date value set, or the end date is set earlier than the start date, then a diamond is used to represent a milestone.



The Gantt Footer option allows users to add a bar chart below the Gantt Chart. This is useful to visualise aggregates of a selected measure over the full time period. Typically, this will be the total FTE by month.

The bar chart is stacked according to the color by (in this example, by 'Gender'), and each bar is interactive (holding all the nodes which contribute to that bar).

The data from the Footer chart can be exported to Excel by clicking on the Copy icon from the panel.

NB: The condition to be met for a node to contribute to the aggregate for that period is that it exists at the end of the period under analysis: if that condition is met, it will contribute for the whole period. In other words, when working with month (30 days) as our period:

  • If an employee starts and ends within the same month, the employee will make no contribution to FTE at all, unless they leave on the last day of the month, in which instance they will contribute 1 full FTE to that month
  • If an employee starts and ends during two consecutive months, the employee will make 1 full FTE to the first month only, unless they leave on the last day of the second month, in which instance they will contribute 1 full FTE to the first month, and also 1 full FTE to the second month

2.24 represents only the early stage of the Gantt View. In the future, users will be able to display and interact with links so they can make resource allocations and visualise them in a single view.



Pivot tables

While data visualisation in OrgVue is very powerful, customer feedback has shown that there are occasions where tables remain more practical than graphical representation. This is why we introduced a new dashboard called Pivot Table, which follows a conventional tabular layout, but empowers users to slice and dice numerical data by up to four dimensions. There are currently four tables to choose from:

  • Single Measure
  • Multiple Measures
  • Gender Pay Gap
  • Total Headcount

The first two tables (Single Measure and Multiple Measures) are general-purpose tables allowing users to pivot over one or multiple measures. The tables share dashboard controls to select table type and split-by properties:

Each table has its own set of controls specific to it, which can be accessed by clicking on the cog symbol next to the metrics list. For instance, it is easy now to display different payroll costs by regions:

Furthermore, users can also export the dashboard directly to Excel by clicking on the clipboard next to the dashboard title. All tables have the option to show column aggregates - min, max, mean, count and sum - for any level of nesting.

Meanwhile, the Gender Pay Gap table is a specifically targeted report on pay inequality. The table calculates the following metrics:

  • Mean and median pay gaps;
  • Mean bonus gap;
  • Proportion of employees who received bonus;
  • Salary quartiles

Finally, the Total Headcount table is a preset single measure table for quick report on headcounts.

A vs B Survey

NB: This new dashboard is only available upon request. If you cannot see it and wish to find out more, please get in touch.

Organisational data is a goldmine, yet most clients find it challenging to identify and prioritise questions that are most aligned to their goals. Running A vs B survey in OrgVue is a powerful way to gamify and crowd source the prioritisation process, from business objectives to organisation design criteria to what office perks motivate people most. Over the last six months, we have conducted a great number of A vs B surveys with our clients and found that they delivered significant value, enabling faster and fairer decision-making. 2.24 introduces a more sophisticated and visual way to analyse the A vs B Survey through an in-built dashboard.

The figure below shows how visual and easy it is to derive insights from the dashboard. These are the results of running an internal 'A vs B' survey where participants had to rank which OrgVue dashboards they find most valuable. As shown, users can colour by heat map to quickly identify patterns, such as the highest to the lowest ranking dashboards, while breaking down the overall results based on demographic categories, in this case 'Consulting' and 'Development' teams.

The results show significant variation in opinion, but both teams share the same view that rank 'Data Types and Patterns' and 'Box Grid' as the most valuable visualisations.


Core feature enhancements

Compact Card

The new Compact Card allows users to display more information on screen when creating org charts. The card is equivalent to the Summary Card, but reduces the white space around the text.

Fixing the height of cards

Both the new Compact Card and the Summary Card now provide a height setting. This height sets the minimum height of the card and can be used to guarantee all cards are the same size so that the org chart will align at all levels.

Cloning node(s) multiple times

When modelling a future organisation, it is common to want to create multiple copies of a role. By dragging and dropping one or more nodes onto the Add button, users will now be prompted with a dialog to set the number of copies to create. The copied nodes will preserve their parent, and will be appended to end of the child list.

Expand to Level now relative, not absolute

Prior to 2.24, the Expand to Level control acted as a filter on depth. For example, setting 'Level 3' would hide any node at depth of greater than 3. This is inconvenient, especially when wanting to create paginated outputs of the org chart for all Managers. In 2.24, the selector is now relative to the first node in the paginated hierarchy. This means paginated outputs can be created to a fixed depth from each manager.

Support for bulk updates in Set Property dialog

Making bulk updates to data has always been easy in OrgVue (splash commands, drag and drop in filter control, in charts and in pivot view). However, prior to 2.24, users cannot make a common edit across multiple nodes in a quick way.

In 2.24, having opened the Set Property Value dialog, more nodes can be dropped on the dialog to add them to the list of nodes to be updated. Moreover, by dragging a property to the dialog, multiple properties may be set at once.

Users can open the Set Property Value dialog by dragging and dropping in the filter control, in charts, in the pivot view or by double clicking on a property value in cards. Holding down the Ctrl key when dropping, allows users to suppress the dialog and apply the update immediately.

Filtering measures by '(Blank)' and '(NA)'

Prior to 2.24, measures within the filter control hid any nodes for which the value was empty or was not a number. The '(Blank)' and '(NA)' buckets are now available in the filter respectively.

Prior to 2.24, although link values and properties from the Target dataset were available to be used in the filter control, it wasn't possible to filter across links, i.e. filtering nodes in a dataset wouldn't extend the filtering criteria either to the links values or to the nodes in the dataset to which it has been linked.

In version 2.24, filter control applies and combines filter criteria across linked datasets. It is not only dynamically responsive to properties in the Source dataset, but also to link values and to properties in the Target dataset.

This icon is now available in the filter control and it can be used to drag all the filtered nodes in the Source dataset for further actions, e.g. cleansing, assigning new values or linking to many nodes in the Target dataset.

Filtering flexibility has also been extended to the level that the user can even control in which dataset the filter will have effect. There are four possible options:

Fully linked: Filtering by properties of any dataset will have effect in Source dataset, Link values and Target dataset.

Right linked: Filtering by properties in Target dataset will have effect on Target dataset properties and Link values. No effect in Source dataset.

Not linked: No filtering across links. Filters apply only to properties in the same dataset.

Left linked: Filtering by properties in Source dataset will have effect on Source dataset properties and Link values. No effect in Target dataset.

Y-axis on charts

By popular demand, 2.24 now provides a y-axis on Column and Line charts.

The axes can also be formatted over a greater range, rather than fixed from 0 to Max. However, it currently remains impossible to set the origin to be greater than 0. The secondary axis is not yet available on Horizontal bar charts.

Additional currency formatters

To provide users with more flexibility in chart formatting, users can now pick a currency formatter in fixed units of K (thousands) or M (millions).


Have more questions? Submit a request