# Widget Dashboard

The **Widget Dashboard** is a configuration‑based tool used to create **basic charts and dashboards** within the ONEWEB platform.\
It is designed to help users visualize key metrics through predefined widgets without requiring custom UI development.

This dashboard approach is primarily intended for **simple analytics use cases** and is commonly found in legacy ONEWEB implementations.

***

### Overview of Widget Dashboard Architecture

ONEWEB provides both:

* The **database structure** required to store dashboard configurations, and
* The **runtime engine** that reads these configurations and renders the dashboard at runtime.

However, there is **no visual designer or drag‑and‑drop tool** available for creating or managing Widget Dashboards.

As a result:

* All dashboard definitions must be created **manually**
* Users are required to insert and manage configuration records directly in the relevant database tables

This section explains the **core components** involved and the role they play in rendering a Widget Dashboard.

***

### Main Dashboard Page Component

The **Main Dashboard Page** acts as the container for the dashboard layout.\
It defines the overall structure of the dashboard, including how individual widgets are positioned and rendered on the page.

<figure><img src="https://2015371994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMpDjHWFRUtZ5nJcSfVXd%2Fuploads%2FcxHqHJUWHTtsp1lgd4fW%2Fimage.png?alt=media&#x26;token=cd01bd4a-09bf-46d7-9a4a-651533aa02c0" alt=""><figcaption></figcaption></figure>

This component serves as the entry point for displaying one or more dashboard widgets at runtime.

***

### Widget Dashboard Component

The **Widget Dashboard Component** represents individual dashboard widgets such as charts or metric blocks.\
Each widget is defined by configuration values stored in the database, which control:

* Data source
* Chart or widget type
* Display behavior
* Layout positioning

<figure><img src="https://2015371994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMpDjHWFRUtZ5nJcSfVXd%2Fuploads%2FnukSMRLeTQj8kB4hoDVG%2Fimage.png?alt=media&#x26;token=659d38a2-ba2c-4abf-b7f5-4aede60d397a" alt=""><figcaption></figcaption></figure>

The runtime engine reads these configurations and renders the widget dynamically when the dashboard page is loaded.

***

### Key Characteristics and Limitations

The Widget Dashboard approach has the following characteristics:

* Configuration‑driven (database‑based)
* No visual editor or UI designer
* Requires manual configuration management
* Suitable for maintaining **existing dashboards**
* Limited flexibility compared to modern dashboard solutions

Because of these limitations, Widget Dashboards are considered a **legacy dashboard mechanism**.

***

### When to Use Widget Dashboard

Widget Dashboards are most appropriate in the following scenarios:

* Maintaining or supporting **existing legacy dashboards**
* Environments where dashboards are already configured using this model
* Simple visualization requirements that do not require frequent changes

For new dashboard development or advanced analytics use cases, ONEWEB recommends using the **Charts Extension in Page Designer** instead.

***

### Summary

The Widget Dashboard provides a basic, configuration‑based solution for dashboard creation in ONEWEB.\
While it is still fully supported to ensure backward compatibility, its manual setup process and limited flexibility make it less suitable for modern application requirements.

Developers are encouraged to evaluate newer dashboard approaches when building new applications.


---

# 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.onewebstack.com/building-apps/ui-page-designer/ux-ui-components/dashboard/widget-dashboard.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.