What's new in Version 5.9.5
Group Based Ranking in Leader Board
With the new grouping feature inside Leaderboards that is coming in version 5.9.5 of Performio, you no longer have to create a separate leader board for each group, for example, one leaderboard for all participants in Location A, another one for participants in Location B.
There is a new option in the Leader Board config screen. See screenshot below:
Grouping can be based on 4 options:
- Job Title
As soon as an option is selected for 'Group By', you will see three other fields -Group Rank, Group Size, Group Name. As the name suggests, these will store the rank of the participant within his group, total size of the group and also the name of the group. These PVALs need to be created in the PVAL schema first.
As soon as you configure the leader board, assign participants to it and run leader board calculation, these PVALs will be populated in the PVAL tree in the path specified in the schema.
As always you can then create a leader board report for the leader board. In the leader board report config page, you will see a new option as shown in below screenshot:
This allows data to be filtered by the grouping selected in the Leader Board configuration. If this option is selected, this report will display filtered data in all the places in which it can be accessed. Example: in the HTML Report module, in the report generated from the Reports module and in a report generated from the Participant Console.
Participants who are on the leader board get a filtered leader board report with details of all participants in his/her group. Participants who are not on the leader board get a drop down to filter by any group or get the unfiltered global leader board.
For example, in the below example, in the HTML report module, Daenerys Targaryen will see all the participants in her Leader Board who are in her Location - Westeros.
But for someone else on the same leaderboard, in a different location will have the records filtered for their location. Example Joey Tribbiani is on the same leaderboard, but his location is New York. He will see participants who are in New York location
And for someone who does not belong to this leaderboard, he/she gets to filter data with the help of a drop down option that appears on the HTML report module:
If a participant who does not belong to a leader board tries to download that leader board report from the Reports module, a group option will be shown to filter reports per group.
Additionally, these reports if generated from Participant Console will also do the data filtering per group for participants who belong to the leader board. For others, it generates the whole report, when generating from participant console
All these additional filter options on leader board report download/view are controlled by the check box for 'Filter data by group' in leader board report config.
Note: If a participant has multiple plans/job titles/sips, the grouping will be done based on the first plan/job title/sip that he is assigned to.
Product Enhancements & Bug Fixes
Duplicate Transform Enhancements
1-1 copy of records
Duplicate transform can now be used to copy the records in one table to another, without having to write an SQL script. Simply select the Input table and the Output table, select one input field and one output field each. This means that the input field selected from the input table gets copied to the output field selected from the output table. The rest of the fields can be copied as it is to output table by choosing 'No operation' in the Formula or you can do some basic mathematical operations on them before copying to the output table.
Turn on/off delete before duplicate transform
You will see a checkbox towards the bottom of the page in the duplicate transform configuration. If this checkbox is ticked, it will delete data for the target period on the output table before running the transformation.
Formula component can handle values greater than a million
There was a limitation in the library that we used for the formula component. We have fixed this issue in this release.