Several organisations work in shifts, where people use the Zenya Search app during the shift. This is often done on shared devices that are handed over to another colleague at the end of the shift.
Failure to log out of the Zenya Search app at the end of the service could result in the Zenya Search app being used under the wrong account.
To prevent improper use of the Zenya Search app, we are introducing a personal access code!

As there may be both personal and shared devices in an organisation, we have made it possible to set in Zenya which users (groups) the personal access code should apply to.
Has the personal access code been set for you? The first time you open the Zenya Search app, after the update, you will be asked to set this personal access code.
If you have not accessed the Zenya Search app for a while and you open it again, it will ask for the access code to unlock the app. If the device has since changed users, the user has to log in to confirm who is currently using the device.

To use this functionality, an update to Zenya 6.1.2 is required.

Bug fixes:

  • If a user logged out and another user logged in afterwards you could still see a document in the favourites or recent list
  • The notification for missing or wrong data during login was not clear enough
  • While synchronising the app, the display of target groups was aborted
  • The 'mark as unread' button on a notification was not always displayed properly
  • Opening Vilans documents could sometimes cause an error message

Several organisations work in shifts, where people use the Zenya Capture app during the shift. This is often done on shared devices that are handed over to another colleague at the end of the shift.
Failure to log out of the Zenya Capture app at the end of the service could result in the Zeny Capture app being used under the wrong account.
To prevent improper use of the Zenya Capture app, we are introducing a personal access code!

As there may be both personal and shared devices in an organisation, we have made it possible to set in Zenya which users (groups) the personal access code should apply to.
Has the personal access code been set for you? The first time you open the Zenya Capture app, after the update, you will be asked to set this personal access code.
If you have not accessed the Zenya Capture app for a while and you open it again, it will ask for the access code to unlock the app. If the device has since changed users, the user will need to log in to confirm who is currently using the device.

To use this functionality, an update to Zenya 6.1.2 is required.

Bug fixes:

  • Long names of report forms were not shown in full
  • The notification for missing or wrong data during login was not clear enough

Several organisations work in shifts, where people use the Zenya Assist app during the shift. This is often done on shared devices that are handed over to another colleague at the end of the shift.
Failure to log out of the Zenya Assist app at the end of the service could result in the Zenya Assist app being used under the wrong account.
To prevent improper use of the Zenya Assist app, we are introducing a personal access code!

As there may be both personal and shared devices in an organisation, we have made it possible to set in Zenya which users (groups) the personal access code should apply to.
Is personal access code set for you? The first time you open the Zenya Assist app, after the update, you will be asked to set this personal access code.
If you have not accessed the Zenya Assist app for a while and you open it again, it will ask for the access code to unlock the app. If the device has since changed users, the user has to log in to confirm who is currently using the device.

To use this functionality, an update to Zenya 6.1.2 is required.

Bug fixes:

  • The notification for missing or wrong data during login was not clear enough

In this patchpack update, for the search engine used in document management, we have applied the semantic search technique and built in support for the Vilans content type background information and, as usual, we have fixed some bugs. Hopefully you haven't been bothered by any or very few of them!

In this patchpack update, we have built in support for the Vilans content type background information and, as usual, we have fixed some bugs. Hopefully you haven't been affected by them at all or very little!