Available for testing on pre-live sites in the UK and Ireland on January 11, then going live on January 14. Released in the US on January 19. Please be advised that Release Updates will involve a short downtime period.
Special update to Release 467:
Following release 467, we identified two persisting issues. A fix will be applied overnight on January 24, 2021 for UK/Ireland and January 26, 2021 for US clients.
- We identified an issue affecting SharePoint integrations that was causing integrations to fail.
- Random CSS styling was appearing in email messages for some customers using Inbox.
Additionally, we are including a background change which will improve the reliability of submissions.
Case Viewer
Improvements
- Updated Welsh translation files so that the product can be fully translated into Welsh when required.
- Admin screen now displays correct Granicus branding.
Compliance Console
Improvements
- Added a new retention period of 365 days to enable the 'Unconfirmed User Retention Period' setting. This will allow unconfirmed user accounts to exist. This functionality is not yet enabled fully, and will require additional setting changes. We will let clients know as soon as this is available.
- Admin screen now displays correct Granicus branding.
Bug Fix
- Some clients were receiving error messages when they tried to view large audit logs. We have made improvements to performance to ensure large audit logs can be viewed.
govService Platform
Bug Fixes
- This change ensures SPS/Poller continues to poll, if on checking a third party application it is not available. SPS will now halt and retry at the next scheduled interval (there is no immediate retry, it reverts to the poller schedule). This should ensure that SPS no longer fails when a third party system is unavailable at the time of polling. If the Final integration that the poller is designed to run fails then there is no retry but the failure is logged in the usual way.
User Account Verification
Following an investigation into a Customer support ticket, we have identified that some customers are not using email verification by default for Self/Customer Portal Account creation/email changes. We would advise customers that we recommend switching this functionality on as best practice. Email verification by its nature ensures that the user signing up for a Customer account is a genuine user and of course has access to the email account that they are registering.
Why this is important:
- Reduces risk of spammed/fake accounts
- Potentially, without email verification, it is possible for a Bad Actor to create a user account and if they were able to guess a valid email address for an existing Service /Customer Service Hub Account holder they could view existing cases raised against that email address.
We therefore recommend switching on email verification for Self/Customer portal and other public facing portals where applicable.
To switch on email verification, visit yourselfsite.achieveservice.com/admin/self/SiteSettings/Registration and tick the enable Email verification option. You will also be able to create bespoke the content for the verification email if required.
We plan to mandate the use of email verification within the platform, in the mean time customers are advised to switch on locally.
