> For the complete documentation index, see [llms.txt](https://tmediadocs.telcobridges.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://tmediadocs.telcobridges.com/other-pages/overview-and-conventions/status-menus-screen-conventions.md).

# Status Menus:Screen Conventions

#### ***Applies to version(s): v2.5, v2.6.***

Most of the status screens are designed by default to provide the most relevant information in the general view. This general view may be extended to provide more information. In addition, status information can either be displayed once upon accessing a status screen or it can be refreshed on demand, or on a periodic basis. The choice is up to the user and this feature is common to every status screen. Another feature common to most screens is the ability to reset the values of displayed counters. This feature is key in enabling the user to verify whether certain conditions persist.

### Extended Status

To display extended status, do the following:

From a status screen, check the **Extended status** check box. The extended view will displayed.

![Toolpack v2.5 Extended Status](https://docs.telcobridges.com/w/images/6/6a/Toolpack_v2.5_Extended_Status.png)

### Refresh Status

To refresh the current status display, do the following:

From a status screen, either click the **Now** button or select a refresh interval.

An updated status screen is displayed.

![Toolpack v2.5 Refresh](https://docs.telcobridges.com/w/images/5/5a/Toolpack_v2.5_Refresh.png)

### Reset Status

To reset the counters of a current screen, do the following:

* Select the **Reset status** check box
* Click **Now**

![Toolpack v2.5 Reset Status](https://docs.telcobridges.com/w/images/6/6f/Toolpack_v2.5_Reset_Status.png)


---

# 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://tmediadocs.telcobridges.com/other-pages/overview-and-conventions/status-menus-screen-conventions.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.