> 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-july-2025.md).

# Improvements and fixes, July 2025

Improvements and bug fixes released in July 2025.

*31 July 2025*

## Improved

* **Portal:** Updated segment table sorting so that lists are now filtered by last updated by default.
* **Portal:** Removed the App Discovery section from the Applications page to avoid metrics duplication.
* **Portal:** Updated the UI of the card design for main metrics in HEART.
* **Portal:** Deprecated the additional hint (arrow) from settings and customize options.
* **Portal:** Minor enhancements to the new Application Overview page.
* **Assistant:** Removed the additional hint (arrow) functionality from Guide steps.

## Fixed

* **Portal:** Fixed routing for Guides so the navigation re-click opens the correct chapter instead of unsorted Guides.
* **Portal:** Fixed comments-only filter for Surveys and NPS.
* **Portal:** Fixed missing Survey scores in NPS and Standard survey details pages.
* **Portal:** Fixed Announcement link issue to allow URLs containing commas.
* **Portal:** Fixed incorrect toast message position in Edge browser.
* **Editor:** Fixed an issue where the Pause Recording mode was not reset when exiting and then re-entering the recording mode.
* **Editor:** Fixed an issue where attempting to publish a Validator before saving it would not actually publish the Validator.
* **Editor:** Fixed an issue where Vimeo videos with a hash query were not able to be properly added to Guide steps.
* **Assistant:** Fixed an issue where clicks on the underlying app would cause the Userlane Assistant to open.


---

# 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-july-2025.md?ask=<question>&goal=<user_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.