> 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-january-2024.md).

# Improvements and fixes, January 2024

Improvements and bug fixes released in January 2024.

*31 January 2024*

## Improved

* **Portal:** Updated the multi-app dashboard so that disabled applications are no longer shown.
* **Portal:** Updated the text to make the explanation for the Activate Userlane toggle clearer.
* **Portal:** Removed the info box on the API Token page explaining which applications have the API Token enabled, as this is now enabled for all by default.
* **Portal:** Increased the available space for Guide titles on the Manage page for better readability.
* **Portal:** Updated Announcement view calculations so that totals on the Performance page match the Content Analytics overview.
* **Portal:** Updated the logic for "is one of" and "is not one of" data connection types when creating user segments so that entered values are lowercased.
* **Portal:** Improved Guide behavior when consuming content located inside pop-ups and modals with scrollbars.
* **Portal:** Added additional logs to the Browser Extension Options page for easier debugging.
* **Editor:** Optimized handling of elements located inside cross-origin iFrames, including additional support for nested iFrames.
* **Editor:** Improved performance in underlying applications that rely on long URLs.

## Fixed

* **Portal:** Fixed an issue where unpublished Guides were available in the dropdown to link a Guide to an Announcement.
* **Portal:** Fixed an issue where users were directed to Announcements instead of Standard Surveys from the View Usage page for Languages.
* **Portal:** Fixed an issue where Moderators could see HEART scores of applications where they did not have access in the multi-app dashboard.
* **Editor:** Fixed an issue where Userlane was breaking a functionality available in the underlying application.
* **Editor:** Fixed an issue that was causing Guides to break on certain web pages.
* **Other:** Enhanced security by updating the NodeJS framework and tightening checks, along with implementing automated solutions to ensure the platform stays up-to-date.
* **Other:** Enhanced the verification process for setting up enterprise search integrations (Confluence, SharePoint, Zendesk, etc.) to ensure more reliable connections.


---

# 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-january-2024.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.