> For the complete documentation index, see [llms.txt](https://help.solink.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.solink.com/docs/release-notes/web/2025/release-15-22-zone-tracking-events-event-flow-audits.md).

# Release 15.22 - Zone Tracking Events + Event Flow Audits

Feb 19, 2025

See the following updates to the Solink platform for **Feb 19, 2025**.

***

## New Features

* Added [**Zone Tracking Events**](/docs/understand-your-business/ai-features/vision-analytics/zone-tracking-events.md) for users subscribed to Solink's **AI Package**. Automatically create an event whenever an individual in the camera view remains or leaves a zone for a certain period of time

***

## Enhancements

* Added [Audit Logs to Event Flow](/docs/review-events-and-save-evidence/events/event-flow.md#see-event-flow-history-audit-logs). Audit Logs provide information on who reviewed the event, including user name, time and response provided for the event.
* Added the ability to [undo/reset an Event Flow](/docs/review-events-and-save-evidence/events/event-flow.md#undo-reviewed-event).
* Added a **Locations** and **Groups** tab on the Video page for a cleaner user interface (previously, Camera Groups and Locations were displayed together in the same area):

***

## Bug Fixes

* Fixed an issue with 360 cameras incorrectly displaying in [pinhole view](/docs/watch-and-find-video/manage-cameras/360-cameras-in-solink.md#pinhole-view) when viewing multiple cameras at once and expanding a 360 camera to full screen.

| Before | After |
| ------ | ----- |
|        |       |

* Fixed an issue that occurred when viewing event footage from a widget (double-click on a data point in the widget > find an event in the list > view event) that caused the Dashboard timeframe filter to automatically change to "Day" and therefore alter the displayed data in the widget.


---

# 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://help.solink.com/docs/release-notes/web/2025/release-15-22-zone-tracking-events-event-flow-audits.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.