> 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/2023-and-older/2023/improvements-and-fixes-april-2023.md). # Improvements and fixes, April 2023 Improvements and bug fixes released in April 2023. *30 April 2023* ## Improved * **Portal:** Removed the "show 200 rows" option from tables to avoid performance impact. Added pagination to Announcement and Guide analytics tables. * **Portal:** Added the Announcement ID to the CSV download. Improved Welcome Slide buttons. * **Editor:** Added a maximum width for Tooltips. Improved Tooltips analytics to only track those in the main viewport. * **Editor:** Reviewed and improved the Editor UI of the Regular Expression tab in the Specific Value Step type. * **Other:** Under-the-hood improvements for faster Userlane loading. Userlane now requires fewer resources (MBs of data) to run. * **Other:** Added additional property configuration information to the Browser Extension troubleshooting page. ## Fixed * **Portal:** Fixed loading issue on the Retention page, cache issues, NPS response export, NPS builder timezone issue, Platform analytics not loading with user segment, wrong Announcement publish date, hint color display, and language deletion. * **Editor:** Page segments list now correctly shown in Tags on smaller screen resolution. Editor no longer crashes when editing the Code Selector. * **Other:** NPS no longer animated while user types in the text box. Fixed registration of new Manager users. Fixed SSO SAML authentication issue. --- # 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/2023-and-older/2023/improvements-and-fixes-april-2023.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.