> For the complete documentation index, see [llms.txt](https://docs.insuraviews.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.insuraviews.com/releases/release-notes/cycle-1.md).

# Cycle 1

### Features

* Added SERFF Tracking Number, Company Name, and Line of Business to the header of search results to better summarize key filing information.

### Improvements

* Ensure that the enter SERFF Tracking Number is visible whenever a tracking number appears within the Insuraviews product.
* SERFF Tracking Number is now visible when viewing the details of a filing.
* Converted Insuraviews logo to SVG.
* Added horizontal and vertical scrollbars to improve the Custom Query option when results return rows and columns that extend beyond the browser window.
* Fixed alignment of arrow between date inputs.

### Bug Fixes

* Fixed an issue that prevented filters from being cleared.
* Display "No related filings found" if there are no related filings in the related filings table.
* Fixed an issue that prevented scrolling in the Company filter drop-down menu.
* Removed invalid options from the DOI reviewer selection drop-down menu.
* Fixed an issue that prevented Effective and Renewal Dates from being displayed in the DOI View.
* Fixed an issue that prevented Record Counts from being displayed in the Single Carrier View.
* Fixed broken Support, Feedback, and Contact links.
* Fixed an issue that prevented the Selected Reviewer from being cleared upon refresh.


---

# 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.insuraviews.com/releases/release-notes/cycle-1.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.
