Salesforce

govService Release 509: September 21, 2022

« Go Back
Information
govService Release 509: September 21, 2022
govService-Release-509-September-21-2022
Article Details

Available for testing on pre-live sites in the UK and Ireland on September 16, then going live on September 21. Released in the US on September 27.

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

  • General: We have improved the way we release new changes to the govService platform. The new method (blue/green deployment) reduces risks associated with the deployment process, ensuring customer sites aren't disturbed by the process of releasing.

Bug Fixes

  • We have addressed an issue with LexisNexis postbacks by returning a text sting "success=true" in the body of LexisNexis payment connector's postback response.
  • Reporting: We have fixed a bug that was preventing weekly data anonymisation from running within the reporting database. Reporting data is now anonymised on a weekly basis.
  • Customer Service Hub: We have fixed an issue with misaligned labels on the side menu within the Customer Service Hub. Labels now correctly appear within their respective tabs.
User-added image
  • Reporting: We have increased the character limit of custom text field data within Reporting from 255 to 3000 characters. Characters above 3000 in number are truncated. This change allows data such as addresses to be viewed within Reporting.
  • Reporting: We have updated Redshift to truncate custom text field data after the character limit of 3000 characters.

New terminology

We are in the process of updating the terminology for our govService products. Below is a list of terminology changes, so that you can learn the new terminology and avoid confusion.

  • Dash is now known as the Staff Portal.
  • Self is now known as the Customer Portal.
  • Service is now known as the Customer Service Hub.
  • Forms is now known as the Service Designer.
  • The Shared Digital Workspace is now known as Shared Service Portals.

Ideas Portal

You can now request up to 5 non-voting team members be added to the Ideas Portal. To make this request, please submit a Support ticket with the subject "Ideas Portal".

A reminder of the planned component sunsets for 2022

Sunset Features/ProductsCurrent StatusDate
Integrations V1*1Security onlyEOL (End of Life)
Dashboard*2Security only30-Sep-2022
Old Saves*3Security onlyEOL (End of Life)
Councillor Portal V1*4Security only30-June-2022
Data Dump*5Security only30-Sep-2023

Security only: Only fixes which are causing security issues and assessed by Granicus security team as high or medium.

*1 Integrations V1 should be migrated to Integrations V2.

*2 Dashboard will not be fully sunset until performance improvements to Caseviewer are completed, resolving intermittent issues for our largest customers. However in this quarter we will begin removing Dashboard for customers unaffected by performance issues - more detail will be shared in release notes for version 510.

*3 Old Saves is replaced by new saves and requires V2 integrations.

*4 Councillor Portal V1 is replaced by Councillor Portal V2.

*5 Data Dump is replaced by Realtime Reporting.

Please note that the sunset date for Dashboard has been postponed to accommodate clients already in progress of migrating but requiring a little more time. We have previously listed the sunset date as June 30th, 2022; it has been changed to September 30th, 2022. Note that from this date, Dashboard will be removed entirely and replaced with Caseviewer.


Microsoft has announced that they have officially ended support for Internet Explorer 11. Any govService features that use Internet Explorer 11 are now in Security only status.

For a full list of planned sunsetting products and deprecated products, please see Sunset/Deprecated govService Products

Reminder: LIM Security Update

Granicus will soon be releasing a LIM security update for govService, which will impact a subset of govService customers that use the Inbox functionality with Office 365 as their email provider.

Please have your IT team complete the steps below to determine if you are impacted by this update.

  1. Log onto the server that hosts your LIM application
  2. In Windows Explorer, search "lim.config"
  3. Open the file titled lim.config in Notepad.
  4. Check for the following line in the file. If the line is present and identical to the text below, you will be impacted by the update:
    <add key="IMAP.Server" value="outlook.office365.com"/>

If the steps above determine that you will be impacted by the update, please reach out to Granicus Customer Support via support@granicus.com or submit a ticket via our Support site.

Further details about the update are provided below.

What is Granicus releasing for govService?

Microsoft is deprecating their Basic Authentication (Basic Auth) and the end of Basic Auth will impact all govService customers using Office 365 for Inbox. We are building out a new LIM which will authenticate using the OAuth2 protocol, which Microsoft will still support.

Reference here for the full press release from Microsoft.

What should I expect from this update?

This update will include a new authentication interface and enhanced security update. As a customer, if you are impacted (see steps above), you will need to reach out to Granicus Customer Support, who will help you re-authenticate your credentials to ensure that this will not impact your experience with the Inbox functionality.

When will this take effect?

Microsoft has not been explicit in their communication as to when they will disable Basic Auth on Office 365 accounts. Out of caution, we recommend reaching out to Granicus Customer Support and completing the steps for re-authentication as soon as possible if you are impacted. We will be providing impacted customers with a detailed user guide, which will walk through how to re-authenticate and the steps for proper set-up. If you wait to reach out, you risk potential loss of inbox files, all relevant data, and access to your inbox when Microsoft implements the change on their end.


Powered by