Jump to release notes for a specific product:
Legislate
- We have fixed issues that prevented non-PDF attachments from Legistar from opening correctly in Legislate.
Legistar and Insite
- We have addressed a bug that prevented jurisdictions who use SSO from obtaining the Device ID of the user attempting to log in. Some users rely on this Device ID info as part of their SSO flow. If your SSO requires Device ID to be passed, you can reach out to Granicus Support, who will enable Device ID passing for you. For those who have already reached out with concerns about this issue, this capability is enabled on release.
- We have fixed an issue in which attachments that were marked as not viewable on Insite were accessible via the API without an authentication key or token. Any users who wish to pull attachments via API that are not viewable on Insite will need to start using an API key or token moving forward. If you do not yet have an API key, you can request one from Granicus Support. Adding a key to API calls is very simple; it can be added as a parameter at the end of the URL of the call, like so: https://webapi.legistar.com/v1/{CLIENT_NAME}/matters?{key=API_KEY_VALUE_HERE}
Alternatively, you can ensure that an attachment is accessible without an API key or token by making the attachment viewable on Insite. To do so, simply make sure that the Not Viewable via Insite checkbox is unselected for the attachment in Legistar (this checkbox may be labelled differently for some jurisdictions; contact your Legistar administrator if you cannot identify the checkbox). - We have removed Social Media Sharing buttons from Insite pages. This includes the buttons that resided at the top right corner of the page for Facebook, Twitter, and Share with links to other social media services. RSS and Alerts buttons are still present. Users can continue to share Insite pages on social media services by copying the URL from Insite and pasting it into their social media service of choice.
- We have fixed an issue in which users received an error message when attempting to access the RSS feed from Events pages via the API, saying that the page was removed. Users can now access the RSS feed as expected.
Peak
- We have fixed issues wherein editing a meeting series updated the day and time for previous meetings, rather than for upcoming meetings only.
