> 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/2026/improvements-and-fixes-april-2026.md). # Improvements and fixes, April 2026 Improvements and bug fixes released in April 2026. *30 April 2026* ## Improved * **Portal:** Added auto-translation to the texts under Customize, with a progress bar while translations are created. * **Portal:** Added a case sensitivity option to segments, so you can choose whether attribute values must match upper and lower case exactly. * **Portal:** Added a "started from" table to Guide analytics that shows where users start each Guide. * **Portal:** Redesigned the chart on the Content overview page to make it more compact and easier to read. * **Portal:** Updated the attributes page so you can see where an attribute is used in a side panel. * **Portal:** Improved refining Message text with AI: you now see a preview, a loading state, and a confirmation before the text is replaced. * **Portal:** Renamed the Language and Texts items in the Customize menu to make clear which page holds text export and import and which holds default texts. * **Portal:** Postponed the deprecation of the Manage page to 1 June 2026. * **Other:** Improved the processing of step error data so that error alerts are sent with less delay. ## Fixed * **Portal:** Fixed multiple issues with segments and user attributes: segments could not be created after the case sensitivity update, attribute titles could not be added or edited, uploaded attribute values were not always shown, and attributes in the user side panel were incorrect. * **Portal:** Fixed issues on the File transfers page: files from manual uploads could not be downloaded, and Guide exports were missing for some properties. * **Portal:** Fixed an issue where the user activity page showed incorrect dates and did not load Guides. * **Portal:** Fixed an issue where the user import steps showed technical labels instead of readable text. * **Portal:** Fixed minor display issues, including a filter dropdown that stayed open after selecting All and a cut-off message in the App Discovery list. * **Editor:** Fixed an issue where the Editor stopped working when opening a Guide or Tooltip inside a pop-up in some applications. * **Editor:** Fixed an issue where the Editor jumped to the wrong step after a preview. * **Editor:** Fixed an issue where generating text with AI did not work in the Editor. * **Editor:** Fixed an issue where auto-translation in the Editor failed with a timeout error. * **Editor:** Fixed an issue where Guide links pointed to the EU server for properties hosted on the US server. * **Editor:** Fixed an issue where the Translate button was misaligned with the Language dropdown. * **Assistant:** Fixed an issue where a conflict error prevented the Assistant and the Editor from opening, or prevented content from being saved, for some customers. * **Assistant:** Fixed an issue where the Assistant kept opening while users navigated in Salesforce. * **Assistant:** Fixed an issue where a Guide showed two steps at once after navigating to an area of the application that uses an iframe. * **Assistant:** Fixed an issue where a Guide stopped working after the page reloaded. * **Other:** Fixed multiple backend stability issues, including errors when saving segments and loading content. --- # 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/2026/improvements-and-fixes-april-2026.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.