> 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/2025/improvements-and-fixes-april-2025.md). # Improvements and fixes, April 2025 Improvements and bug fixes released in April 2025. *30 April 2025* ## Improved * **Portal:** Introduced a custom color picker on the Customize page. * **Portal:** Enhanced the design system with improvements and resolved various bugs. * **Portal:** Updated the UI dropdown in the email notification settings with a new component. * **Other:** Upgraded one of the libraries used for AI services to prevent introducing a vulnerability and maintain security compliance. ## Fixed * **Editor:** Fixed an issue where refreshing the page while in the Validator Preview mode removed the previously added content and configuration details. * **Editor:** Fixed an issue where unpublishing a Validator did not also unpublish other languages for which the Validator had been active. * **Editor:** Fixed an issue where Moderators were not able to generate regular expressions for Validators or specific value input Guide Steps. * **Editor:** Fixed an issue where editing the Step Title in a Guide reverted recently saved changes to the same Guide. * **Other:** Updated the knowledge base integration API with KnowledgeOwl to fix an issue where not all documents were being returned as expected. --- # 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/2025/improvements-and-fixes-april-2025.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.