> For the complete documentation index, see [llms.txt](https://docs.userlane.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.userlane.com/changelog/2024/improvements-and-fixes-june-2024.md). # Improvements and fixes, June 2024 Improvements and bug fixes released in June 2024. *30 June 2024* ## Improved * **Portal:** Removed duplicate headers to streamline the design on certain Portal pages. * **Portal:** Added the option to repeat Announcements automatically at weekly and bi-weekly intervals. * **Portal:** Upgraded core analytics services to the latest versions to improve performance and resolve vulnerabilities. * **Portal:** Improved how HEART scores are calculated for the all-apps page so that scores are shown as long as there was activity in the past 90 days. * **Portal:** Improved how the Engagement page measures time spent on a page by adding additional checks. * **Editor:** Improved how Userlane interacts with Cookiebot. * **Other:** Improved how the new Userlane Browser Extension handles the SSO authentication process. ## Fixed * **Portal:** Fixed an issue where User Import would not complete if an attribute in the upload file was in an archived state. * **Portal:** Fixed an issue where users with the Contributor role could see the User Segments filter for analytics but not successfully filter with them. * **Editor:** Fixed an issue causing linked Guides to Tooltips to crash under specific circumstances. * **Other:** Enhanced data-deletion and anonymization process for greater GDPR compliance. * **Other:** Squashed security vulnerabilities to keep the platform robust and secure. * **Other:** Enhanced the URL Exceptions list logic to cover more specific scenarios. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.userlane.com/changelog/2024/improvements-and-fixes-june-2024.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.