modules
This is an old revision of the document!
Introduction:
The Modules table is used to store information about different modules available in the system. Each entry represents a module, including its unique identifier, associated client, hierarchy, appearance, and status. This table plays a crucial role in organizing and managing modules in the system, ensuring that they are displayed and function correctly in both the backend and front-end application.
| Sr. No. | Name | Type | Comments |
|---|---|---|---|
| 1 | id | Primary | ID of the module (auto-incremented). |
| 2 | clientid | Index | ID of the client associated with the module. |
| 3 | modulename | varchar(50) | Name of the module. |
| parentmoduleid | int | ID of the parent module, if this module is a submodule of another module. | |
| defaultmodule | int | Indicates if this is the default module. 1=default, 0=not default. | |
| dependentmodules | varchar(200) | Comma-separated list of module IDs that are dependent on this module to form the overall module. | |
| ord | int | The order in which the module should appear, typically used for sorting modules. | |
| modulelogo | blob | Stores the logo of the module, in binary format (image). | |
| appiconname | varchar(250) | Stores the image name used to display the module's icon on the app's module screen. | |
| status | int | Indicates the module's status. 1=active, 0=inactive. |
modules.1741590506.txt.gz · Last modified: 2025/03/10 07:08 by gloria
