DIGIT Workbench
PlatformDomainsAcademyDesign SystemFeedback
  • đź‘‹Introducing DIGIT Workbench
    • Release Notes
      • Service Build Updates
      • MDMS & Configuration Updates
      • Test cases
      • Schema Collection
  • Understanding Workbench
    • Workbench Concept Note
    • Approach
  • Specifications
    • Master Data Management Process Flow
    • User Stories
  • Platform
    • Architecture
      • High Level Design
      • Low Level Design
    • Source Code
  • Setup
    • Configurations
      • Services
        • MDMS V2 (Master Data Management Service)
          • Adopt New MDMS - Steps
      • Workbench UI
        • Configurations
          • MDMS Configurations
          • DevOps Configuration
          • FAQ :: On Localisation Screens
        • Manage Master Data
          • Search Master Data
          • Add Master Data
          • View Master Data
          • Update Master Data
        • Manage Localisation Data
          • Search Localisation Data
            • Add Localisation Data
          • Edit Localization Messages
          • FAQ :: Add localisation if screens are not localised.
        • Create New Master
      • MDMS V2 Migration Guide
  • Community
    • Issues
Powered by GitBook

All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.

On this page
  • Design Approach
  • Pre-requisites & Constraints
  • Scope

Was this helpful?

Export as PDF
  1. Understanding Workbench

Approach

PreviousWorkbench Concept NoteNextMaster Data Management Process Flow

Last updated 7 months ago

Was this helpful?

Design Approach

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.

Generic Concept of Workbench v1

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.

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.

Pre-requisites & Constraints

  1. Individual master data management services are available and contain JSON schemas that define the structure of the data model.

  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.

In Scope
Out Of Scope
  1. Tenant management through UI Edit Tenant Data

  2. UI for masters managed by MDMS service Dynamically rendered Add, Search, View and Update master data pages

  3. UI components for fields to “Add” master data

  4. Link to Other master-data Services(Employees, localization, boundary, projects etc)

  5. Master specific fields for search and view all pages

  1. Tenant Master tenant creation Child tenant creation

  2. Generate localization key and add to localization service while “Adding” data

  3. Link to add localization data while adding new master data

  4. Custom UI for a master

  5. Upload files

  6. Add master data in bulk