> For the complete documentation index, see [llms.txt](https://help.watcherlink.online/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.watcherlink.online/release-notes/release-note-1.42.0.md).

# Release note 1.42.0

1. The **Clients** and **Bills** pages have been redesigned. We have updated the interface to make it more intuitive and performant. Working with lists and searching for required records now takes less time, and key financial metrics are more easily accessible for quick analysis.
2. For clients, we have added the ability to export data for both a single client and multiple clients. You can now obtain aggregated data across all key client parameters.
3. The task tooltip has been updated. It now allows you to quickly understand which task managers and status types contain tasks for a client’s devices or assets.
4. It is now possible to create tasks for clients. When creating a task, you can add all devices or all assets of a client in just a few clicks.
5. The **Bills** page now contains invoices for all clients. Using filters and search, you can quickly find the required invoice and process it.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.watcherlink.online/release-notes/release-note-1.42.0.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
