Salesforce

govService Release 507: August 24, 2022

« Go Back
Information
govService Release 507: August 24, 2022
govService-Release-507-August-24-2022
Article Details

Available for testing on pre-live sites in the UK and Ireland on August 22, then going live on August 24. Released in the US on August 30.

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

  • Forms: We have improved the speed of large HTTP lookup integrations.
  • We have added Systems in use and Systems not in use tabs to the Process-Scanner under Integrations. These tabs show Systems that are both in use and not in use and their associated integrations. This information was previously missing and is useful to find Systems that could cause a high impact if changed or Systems that may need cleaning up.
User-added image

Bug Fixes

  • Forms: We have fixed a bug that prevented Save redirect URLs from working as expected under certain conditions. If a process is set to take users to a different URL after saving, then that redirect now happens successfully.
  • Forms: We have fixed a bug that took users to a 'Page not found' screen after saving a form. Now, unless a Save redirect is configured, users can continue completing their form after saving progress.
  • Forms: We now allow tokens to be used within escalation Integrations to set the assigned user or group of the stage on which the integration is run.
  • Customer Service Hub: Results are now returned quickly when searching for a full Case Reference (e.g. ABC12345) in the Case reference section of the Customer Service Hub's search feature.
User-added image

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.

New documentation

Two new FAQ documents, on Realtime Reporting and the govService Data gateway, are now available on support.granicus.com.

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 only30-June-2022
Dashboard*2Security only30-Sep-2022
Old Saves*3Security only30-June-2022
Councillor Portal V1*4Security only30-June-2022
Data Dump*5Security only31-Dec-2022

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 is replaced by CaseViewer.

*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