OneVu 2.10

This release provides a couple of enhancements which are listed below:

Completed Forms

Until now when a form was submitted in OneVu it would only be obvious this had happened if it subsequently kicked off a process in OpenProcess, which they tracked. This is because within the Submit a Request function you could access In Progress forms but not forms that had been submitted.

So now, within a new Completed forms tab, a user can see any form they've submitted as soon as they've submitted it:

This is literally to show them when they started it and completed it.

Importantly, these will, after the period of time you've set your policy states, be cleared down from here. I.e. if a person submits a form on 01/10/2019 and your policy for deleting completed forms from our cloud is 30 days. The form will no longer appear in here on 31/10/2019.

OneVu Data Extracts

We have built two new extracts that provide:

1) the ability to take an extract of all customers that are in OneVu

2) the ability to see all of the accounts with personalised data

To provide an example of 1) see below:

 Obviously, the above shows a single row but in practice for every person there would be a row.

To provide an example of 2) see below for personalised benefit accounts. Where we can see in the 2nd to 6th columns the data fields used when the person personalised their account:

These extracts could be used for mail shots etc. however it's important to note that you need to ensure that you take into consideration GDPR rules.

Currently, you will need to request these via the helpdesk but in future we will enable you to do this.

Custom API Security Headers

To enable councils to use their own adhoc security models when retrieving sensitive back office data we have added the ability to support custom security headers when retrieving data from back office systems.