- 22 Apr 2024
- 1 Minute to read
- Print
- PDF
Mapping
- Updated on 22 Apr 2024
- 1 Minute to read
- Print
- PDF
The Platform Topology map visually depicts how the different components of the Platform foundation relate to each other. It offers a comprehensive and up-to-date view of how Domains, Sub Domains, and Departments are interconnected with their corresponding Applications and Modules. This mapping also enables you to associate configured Modules with specific Departments.
User Persona: Super Admin
Use Cases
Let us consider scenario-based use cases that help in understanding the Mapping of Modules to the Department in the context of Domain and Sub Domain.
Scenario - I
For Example, ACME has multiple Department requirements as described in the following table:
TENANT | REQUIREMENT |
---|---|
OPERATIONS | Should be able to perform activities related to recruitment, onboarding, payroll, and leaves. |
QUALITY | Should be able to perform activities related to payroll and leaves. |
FACILITY | Should be able to perform activities related to payroll and leaves. |
To do so, the Super Admin should define the mapping between Tenants and Modules as described in the following image:
Figure: Module mapping scenario
Scenario - II
For Example, the ACME domain has the following Sub Domains and relevant Departments. ACME requires that OPERATIONS Tenant which is common among three Sub Domains (ACME OPERATIONS SERVICES, ACME MOTORS SERVICES, ACME MOTORS SERVICES) should reuse the required modules.
Sub Domain | Contains Tenants |
---|---|
ACME Operations Services | Operations, Quality, Facility |
ACME Motors Services | Motors, Operations, Design |
ACME Healthcare Services | Healthcare, Operations, Inventory |
To do so, the platform designer should define the mapping between Departments and Modules as described in the following image:
Figure: Module Mapping scenario
The following graphic represents mapping on Platform Topology:
To Map the Application to Departments and Modules, click here.