Available for testing on pre-live sites in the UK and Ireland on April 19, then going live on April 25. Released in the US on April 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
- Reporting: As part of a feature enhancement, a Hide deleted fields checkbox has been added to filter the data fields in global, process and PII mapping screens (Mapping UI and Mapping API). By default, the checkbox is selected and deleted fields are not shown on mapping screens.
- Citizen mobile app: We have updated the payments workflow on the app to match the desktop experience. When submitting a payment within the mobile app, users are now redirected back into the form to review a summary of the submission's details.
- Escalations: We have improved escalations to run quickly after being initiated. Before this release, when a large number were run at once, escalations could take hours to complete; now, they run much faster.
- Forms: We have removed the zoom-level limit that existed on our Google Maps form Integration and added the ability to use different map layers. A greater zoom level allows more specific markers to be dropped on the map, therefore reducing errors during issue reporting. For example, the exact location can be tagged when reporting a pothole or graffiti, allowing remote teams to quickly and easily locate the issue. Layers further reduce the chance of error by allowing reporters to identify familiar features of their surroundings when dropping a pin. See screenshots below for details.
Previous maximum zoom level:

New maximum zoom level:

New functionality to select map layer:
Bug Fixes
- Forms: We have fixed a bug that was preventing users of mobile devices from downloading documents from the upload field within a form.
A reminder of the planned component sunsets for 2022
Sunset Features/Products | Current Status | Date |
---|
Integrations V1*1 | Security only | 30-June-2022 |
Dashboard*2 | Security only | 30-June-2022 |
Old Saves*3 | Security only | 30-June-2022 |
Councillor Portal V1*4 | Security only | 30-June-2022 |
Data Dump*5 | Security only | 31-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.
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.
- Log onto the server that hosts your LIM application
- In Windows Explorer, search "lim.config"
- Open the file titled lim.config in Notepad.
- 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.