Single module description

System modules are registered and installed. Object module describe the installation state

• Module object – data model
• Related objects
  • Event Handlers
  • Object
  • Right
  • Translation
  • Enum – Counters

The purpose of the module definition is:

• Evidence what system modules are installed in the environment
• Documentation of the last installation process results (Modules could be reinstalled repeatedly when changed)
• Linkage to the module options

Module is master object for several other objects that described module settings for clients.

Module object – data model

Related objects

Event Handlers

Each module could defined handlers for events – both system events and events from related modules. More information about system events is here. Events are loaded during module installation

Object

Object describes each object supported by module. It stores attributes and data necessary for server automation.

Right

Rights are low-level system rights. They are not directly used to set up users' rights but they are linked via system roles

Complete right management is subject of the system module but rights available for management are defined by modules and objects.

Translation

Translation imported to the database are only those that are used by the server – back-end functionality. Front-end application does not uses them.

Back-end translations are used for back-end generated pages, email messages and automatically generated reminders. They are defined by the back-end translation modules m_Lang.json file

Enum – Counters

Imported counter are used mostly for report generation and for generation of the code during the development. The back-end code does not regularly use them because they work with internally defined counter constants. However, the constants are generated from this table.