Another big month of changes! To many to list in but a simple intro paragraph! You can read about the lot of them below:
(Currently active, updates coming Friday 3rd of March)
The New KPI Module in Donesafe allows team leaders to set KPIs and keep track of those KPIs for Audits, Observations and Consultations.
To illustrate exactly how it works, you could create a KPI that says:
All workers in MY TEAM whose ROLE is “Worker” in LOCATION “Sydney” must complete TWO AUDITS using the TEMPLATE “WHS checklist” PER QUARTER. The screenshot of the form to administer this is below:
This module’s functionality in Donesafe will expand over time (in fact, some more upgrades are coming this Friday 3rd of March ‘17). Already though, it allows a great deal more oversight from team leaders for their subordinate’s activities in Donesafe in regards to repeating audit templates. This is particularly useful when dealing with larger teams.
One important caveat:
KPIs are created to view data from the creator’s organisational hierarchy. So if a team leader creates a KPI, it will apply to their direct team, whereas if a company CEO creates one they could potentially view data from their entire company depending on the setup.
It is important to understand that for a team leader to only see their subordinate’s records, they themselves must create the KPI to do this; it cannot be done by somebody else.
There are plans to allow site admins to be able to create these on behalf of specific people or automatically in future, however, that is some time off. The reason that this approach was taken is that in larger businesses, individual managers have individual requirements and KPIs for their teams. It was because of the granularity needed that a granular delivery method was developed; at least in the short term.
Enabling the KPI module
The KPI module is hidden by default, both at the module and role level.
This change addresses a few issues:
This new update resolves these issues and a handful of others in a simple, clean way and we’re all really excited about it.
For a full description of this update and how to administer it, make sure you check out the release blog here: https://donesafe.com/2017/02/pre-release-update-workflow-ui-update/
This one has been a common request for a while. Previously, actions defaulted to show all actions that were due within the next 7 days; including actions that had already been closed. Many users found this difficult to work with as it often made it unclear what actions needed to still be completed. Furthermore if an action was missed, it would disappear from the default view often resulting in actions being unfinished.
Now the default action view will show by default: All OPEN or OVERDUE actions due from the beginning of time to seven days time. This makes it considerably easier to go through and quickly close out your actions without any uncertainty around whether they’ve been completed or not. To facilitate this an additional filter was added so that users could filter the state at the parent level.
Adding new contact users is done by clicking on the add new user button next to people selectors as shown below.
Donesafe’s permissions system is extremely configurable and powerful; which is great, but it does make it one of the trickiest parts of the platform to configure for more advanced, enterprise level systems with thousands of users.
To account for this, documentation has been put together to explain the relationships between Role Permissions, Organisational Hierarchy, Locations and Workflow Restrictions. If you’re interested it’s a great read!
Plain English Documentation: https://donesafe.kayako.com/article/146-how-access-rights-work-in-donesafe
System Description of Roles: https://donesafe.kayako.com/article/147-role-permissions-in-depth
The report builder was already awesome. Now it’s a bit more awesome.
You can now chose a secondary grouping. For example, you might like to see incidents, grouped by quarter AND locations. You can now do this with ease (see below). You can see here we now have incidents by quarter grouped by location. Ta-da!
Global Search has received some much needed TLC. There’s been some significant changes, which are listed below:
Related to was also upgraded to use the same search code that Global Search uses. This means that relating records is now also; super fast. It also removes any risk of users seeing record names that they shouldn’t be able to. Furthermore, search results will also show up with the module name to which that record relates. This makes it significantly easier to identify the record you wish to relate.
Finally, we updated the ID numbers for all records to be be shown as unique between modules. This may seem like a minor change, but it makes it significantly easier for the user to now search for a specific record. Where before an Incident’s ID might have been 0354, it now displays as INC0354. This ID can by typed into the global search bar at the top of the page to return a search result for that specific record making it significantly easier, particularly for administrative staff, to find and reference records easily.