As a part of continuing enhancements to improve function, prevent issues and mitigate user error, we have carried outa few changes to OneVu in this release v2.4. These are documented below.
Enhancements
The following are the functional and non-functional enhancements that have been done in this release:
1) Don't auto-reload tabs when viewing a trackable request
Prior to this release every time a user moved from the steps tab to the notes tab or the notes tab to the steps tab and vice versa we would invoke a call to OpenProcess to retrieve any updates. What this meant is that when a user moved from one tab to another there was a delay of between 2-3 seconds.
We've updated this so now the first time they access each tab there is still the 2-3 seconds. But after that it won't try and fetch updates automatically. Because:
a) the odds of an update being done whilst they're in their account is negligible
b) they will be sent an email telling them a new note is added which if clicked on (the URL in the email) will then refresh the info
c) it means performance is better for a person switching between tabs
The following screen is what we are talking about:
What this means is that when a user is navigating between the tabs the performance is much, much faster with 0.5 seconds vs 2-3 seconds.
Now should a user get a note whilst viewing their request or a customer services officer want to refresh the info to do a subsequent fetch there is also a refresh button shown in the bottom right of the above screenshot.
2) Information message when an email is changed
Now, when a user changes their email address they will see an information message after they've changed their email. Essentially this is saying that until the new email has been confirmed (by clicking the link in the email sent upon change) the old details will remain in place. Only once this has happened will the message go away.
3) Information message when an address is changed
Now, when a user changes their address AND that change is in the future it will tell them that this address will start being on the date in the future that they have specified. On the following account they reported that they were moving out of one address to another on the 7th of February:
The point of doing this is that a user may be perplexed as to why their address does not immediately show their new address following a change that is in the future.
4) Ability to use Customer Service Vu address change without having the COA form
Prior to this release you could only change a customer's address using the 'Profile only' function in Customer Service Vu if the Council had the COA form enabled.
Now this is available irrespective of whether the COA form is enabled or not. Meaning Council staff can quickly and easily change customer's addresses without the IEG4 Change of Address form.
5) Improved handling of user creation/permission based functions
To mitigate user error and to prevent a spinning loop where it is not clear what is happening we have made a variety of changes.
a) A single Add user button
Prior to this release there were two buttons when in the user screen:
Now this has been made into a single function called 'Add a user'. When the user clicks on this it will automatically determine whether they already existed. If they do already exist and can be linked i.e. it is not a citizen user then it will associate them automatically with their existing details. If it is detected they do not exist then it will function as the previous 'Add a new user' function worked.
b) Where a person tries to add a user with an email that has already been used they will now be told that this email is unavailable to be linked per below:
c) If trying to access Customer Service Vu with a user that does not have permission to access this area you will no longer face a never ending spinning circle but instead will be presented within the following:
d) Some Groups (i.e. where permissions are connected) are fixed and part of OneVu upon install. These are not editable but this was not obvious previously. We have now enhanced this screen to:
- Be read only
- Have an explanatory note telling the user this is the case
Amendments
The following updates have been made:
1) Quick Search will automatically show email/address updates
If an email/address has just been changed the quick search will now automatically show the new details.
2) Quick Search improvements
Several amendments have been made to improve the robustness of this to handle changes to queries without the first query having returned a response yet and where no results are found.
3) Account Management Results
For consistency of UX with other applications now at the bottom of Account Management results there is a load more button rather than paginated results:
4) Social Media - Email Change
If someone changes the email address associated with their Facebook account etc. then it will now pick up this change for the purposes of pre-population of this into online forms.
5) Wee bits
a) Better error handling if unable to load the recently viewed customers list in Customer Service Vu
b) Show an onscreen message (not a browser based error pop up with gobbledegook in it) if trying to read notes, docs, steps from OpenProcess whilst looking at the Track My Requests screens.
c) Better handling when a customer attempts to log in where their account has been disabled via account management. I.e. no more never ending spinning circle.
The following are the release versioning details: