Emojot 9.7.3 – What’s new?

Sensors

Improvements to file upload capability

Emojot recently introduced file uploading capability from sensors. If a respondent has selected a file(s) and not uploaded, it is highlighted and the respondent cannot proceed to the next page. This will ensure respondent will always upload the selected file(s) when response is submitted.

Forward Enterprise Hierarchy values (context data) in sensor chaining

This enables Enterprise Hierarchy (EH) based survey intelligence for all the sensors in sensor chaining. Previously it was only for the first sensor loaded in the chain.

Case Management

Incident Management renamed to “Case Management”

With this release, we have renamed “Incident Management” to “Case Management”. If you are using Emojot dashboard you will find “Case Management” in the menu instead of “Incident Management”.

Sort option for Case Management table

Case Management table is provided with a sorting option for each column, making it more convenient to find the cases.

Assignee filter in Case Management and reports

With the help of this filter, in both Case Management table and reports, admins can filter out the cases that are assigned to a particular team member. This will improve the efficiency of the project management particularly for large scale compliance/audit management projects.

Assignee breakdowns in Case reports

This can be used to monitor workload of team members in real time which will again lead to efficient project management.

Introducing “Last updated” field to the Case Management table

Last updated date/time column can be used to see the recent active cases.

Respondent Journey

Option to sort journeys by sensor name

Respondent Journey is sorted by the response time by default. In this release, a new option has been introduced to sort the respondent journey by sensor name. This option is particularly helpful in compliance management use cases where the auditors have to continuously scan the responses given for a set of checklists.

Option to show only the last response

This reduces the clutter of the journey and admins can easily navigate and find responses for a specific sensor/touchpoint.

Platform security enhancements

Bug fixes and usability improvements

Leave a Reply

Leave a Reply