# Approach

## Design Approach&#x20;

The Workbench design introduces dynamically generated user interface screens for system users to perform key implementation tasks that typically require software code to be written by engineers.&#x20;

#### Generic Concept of Workbench v1&#x20;

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

The Master Data Management Service contains the standardised schemas defining the structure of data models to be used by the applications. The schemas ensure that master data management conforms to a unified data model offering consistent formats for data input.&#x20;

Based on the defined schemas, dynamic forms are generated in the user interface. The forms contain embedded validation rules for data input ensuring data complies with the required formats. Once the data is validated and the entry is complete, the forms are pushed to the corresponding API endpoints. The master data is saved in the backend database.&#x20;

## Pre-requisites & Constraints&#x20;

1. Individual master data management services are available and contain JSON schemas that define the structure of the data model.&#x20;
2. The UI library for v1 is built based on the current master data structure for Health Campaign Management. Hence, the components available in this version will only address the master data types included in HCM masters.

## Scope

The illustration below offers a glimpse into the features presently in the scope of the Workbench solution design. Follow the colour legend at the bottom of the visual for details of the design elements.

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

| In Scope                                                                                                                                                                                                                                                                                                                                                                                                   | Out Of Scope                                                                                                                                                                                                                                                                                                                              |
| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| <ol><li>Tenant management through UI<br>Edit Tenant Data</li><li>UI for masters managed by MDMS service<br>Dynamically rendered Add, Search, View and Update master data pages </li><li>UI components for fields to “Add” master data</li><li>Link to Other master-data Services(Employees, localization, boundary, projects etc) </li><li>Master specific fields for search and view all pages </li></ol> | <ol><li>Tenant <br>Master tenant creation <br>Child tenant creation</li><li>Generate localization key and add to localization service while “Adding” data </li><li>Link to add localization data while adding new master data</li><li>Custom UI for a master </li><li>Upload files </li><li>Add master data in bulk </li></ol><p><br></p> |


---

# 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://workbench.digit.org/understanding-workbench/approach.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.
