Salesforce

govService Release 485: September 23, 2021

« Go Back
Information
govService Release 485: September 23, 2021
govService-Release-485-September-23-2021
Article Details
Available for testing on pre-live sites in the UK and Ireland on September 17, then going live on September 23. Released in the US on September 28.

Generally the release is timed to commence at 21:00 UK/Ireland Release and 10:00 US release (UK times) and usually there is no loss in service as part of this Scheduled Engineering work. If we expect a transient loss in Service to occur this will be be within the opening 1 hour window of the release, and we would advise in the release notes.

govService Platform

Improvements

  • Realtime Reporting: We have added a comment field on the IP Allowlist tab so users can annotate a brief description of what the IP address is. Please note: If you've already added IP addresses and want to add a comment, you will need to remove the IP address and add it back in.
  • A link to the Reporting Profile page (in which users can manage their reporting profile details) is now available within Self as well as Dash.
  • Help text added to form fields will now be read out by screen-readers.
  • To improve accessibility, we have removed the "user-scalable=no" tag from our code. The tag was preventing users from zooming in to read small text.
  • We have optimised the way Integrations handle files, making it more efficient.
  • To improve security, it will now be possible only to redirect users back to the platform upon logout. This prevents users being unknowingly redirected to third party sites.
  • Security updates have been made to Payments Admin.

Bug Fixes

  • A bug causing duplicate submission to appear in the reporting database has been fixed.
  • We have fixed an issue where Welsh and other special characters from FTP upload are not stored correctly in the LLPG database.
  • A bug has been fixed with the Subform disable edit and disable delete settings.
  • A bug causing process version to not update correctly within Caseviewer upon republishing has been fixed.

Powered by