1.7
Product | Kaizen |
Release Number | 1.7 |
Release Date | Jan 25, 2017 |
Â
New Features
CCF Feedback
This is to allow anonymous feedback to be collected and collectively returned to an event in Kaizen. One single URL can be distributed to people wishing to provide feedback and accessed online at any point whilst the original event is open.
Information on the responses will be displayed on the event to show the number of responses received and how many are awaiting administrator approval. Administrators can also upload feedback manually through a CSV if this has been received as a hard copy.
Once the event is closed then a report is produced and displayed by default whenever the event is viewed again. It can be re-opened (with correct permissions) in order to accept further responses if necessary.
Improvements & Fixes
New tree style layout for tags. This allows the levels to be expanded in place rather than navigating down and up through the individual levels.
Re-styled widget on the dashboard to allow quick creation of new events. If you have permissions to create for other people then you will see the option to search for the person you wish to create for directly on the dashboard itself. This saves having to navigate to the users list and add a new event from there.
Start date and end date selectors when creating new events are now separate again.
User fields can now be set to be locked. This prevents users from changing the value assigned in that field even if they can edit their own profile.
User fields can now be set to appear on the users list against each record and are all searchable.
Speed improvements to using advanced search.
New option to select 'anonymous external user' within event types to gather feedback anonymously.Â
New administration area for approving/rejecting anonymous responses.
New import CSV option for uploading anonymous responses.
Improvements to event type searching on timelines. All event types will now be displayed in the resulting pop up if searching within a timeline category so that you know which events are contained there.
When creating Likert fields in event types the values can now be left empty if you wish to exclude that response from reporting.
Â