Client Apps

Impact Changes Details On Client Apps

Overview

The DIGIT UI framework requires updates to support handling multiple tenants and integrate seamlessly with Sandbox environments. This involves modifications to the global configuration, core UI components, and various modules to ensure smooth functionality.

Impact Areas

1. Global Configuration

Current State:

The global configuration is designed to handle single-tenant information from the base application.

Required Changes:

Update Configuration: Modify the global configuration to support multiple tenants.
Configuration Structure: Redesign the configuration structure to include tenant-specific settings.
Dynamic Loading: Implement logic to dynamically load tenant configurations based on the tenant information received from the base application.

Impact:

Ensures the application can handle requests from multiple tenants simultaneously.
Improves scalability and flexibility of the Digit UI framework.

2. Core UI Components

Current State:

Core UI components are designed to fetch and display data for a single tenant.
Access control logic is based on single-tenant information.

Required Changes:

Fetch Logic: Update the core UI components to fetch data based on the tenant context.
Tenant Context: Introduce a mechanism to pass tenant context to UI components.
Access Control: Revise the access control logic to consider multiple tenants.
Role-Based Access: Ensure role-based access control supports multiple tenants by updating the roles and permissions structure.
User Service: Integrate with the new User Service.

Impact:

Enhances the core UI components to be tenant-aware.
Ensures accurate data fetching and access control across multiple tenants.
Maintains security and proper access management in a multi-tenant environment.

3. All Modules (Urban, Works, Sanitation)

Current State: Modules need to fetch the module tenant configuration and operate accordingly, either at the tenant or subtenant level. The same applies to boundary hierarchies, as the system will contain multiple boundary hierarchy definitions and datasets. Thus, the module should determine which hierarchy and level it should function within.

Required Changes:

Tenant Awareness: Make all modules tenant-aware by updating their internal logic to handle multiple tenants.
Module Initialization: Ensure modules initialize correctly with tenant-specific data.
Data Handling: Adapt data handling processes within modules to support multiple tenants.