# Dashboard Control

## Introduction

The **Wisej.NET Dashboard Control is** a modular framework for building interactive, data-driven dashboards within Wisej.NET applications. The control supports rapid composition of dashboard layouts with real-time data integration and extensible widget architecture.

## Technical Highlights

* **Modular Widget System**\
  Extensible toolbox architecture allowing custom dashboard items (e.g., charts, grids, gauges) via implementation of dashboard item classes. Widgets are automatically discovered and loaded at runtime.
* **Drag-and-Drop Layout Engine**\
  Client-side layout management enabling dynamic arrangement, resizing, and configuration of dashboard components without requiring code changes.
* **Event-Driven Data Integration**\
  Agnostic to data sources; supports integration with REST APIs, WebSockets, timers, and standard .NET event patterns for real-time updates.
* **Responsive and Adaptive UI**\
  Built-in support for responsive layouts and theming, aligned with modern UI requirements.

<figure><img src="/files/MU5HvqLfiQpLojuPlibF" alt=""><figcaption></figcaption></figure>

## Use Cases

* Business Intelligence (BI) dashboards for KPI visualization
* Operational monitoring (IT systems, logistics, manufacturing)
* IoT data visualization panels
* Custom analytics and reporting interfaces

{% hint style="info" %}
Dashboard Control is available for Technology Partners (TP) only. \
If you are a TP, please contact us at <support@wisej.com> to get access to the Dashboard Project Repository. \
If you are interested in becoming a TP, please reach out to <sales@wisej.com>
{% endhint %}


---

# Agent Instructions: 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:

```
GET https://docs.wisej.com/docs/whats-new-in-4.1/dashboard-control.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.