All tables in the SimpleOne system can be classified according to the type of data processed and their purpose.

Classification by purpose

According to the purpose, the tables can be divided into three groups:

• System tables support the operation of the SimpleOne platform and its tools. They are supplied by the vendor and are protected from changes by the end-users and system administrators. These tables can be distinguished by the sys_ prefix in their system name.
• Application tables are created by the vendor or business solution developer within an application and implement its business logic. These tables can be distinguished by the application prefix in their system names. For example, the itsm_ prefix is used for all tables related to the ITSM application. It is not recommended to change the configurations of these tables.
• User tables are created by the end-users with the admin role and used to solve their business tasks. 

Classification by the type of processed data

According to the type of processed data, the tables can be divided into:

• Configuration
• Reference
• Transactional
• Journal

Configuration tables

The configuration tables contain records with the information on the current configuration of an instance and are used as the primary source of the input parameters that determine how the platform and applications work and their functionalities. For example, the Table (sys_db_table) table contains records with configurations of all tables on an instance, including the Table itself and the virtual root table.

These tables are always processed by the version control system.

The configuration tables can be further subdivided into the following subclasses:

• System configuration tables are supplied by the vendor and are an integral part of a platform engine. They contain records with information that determines these engines and the implemented business logic. These tables and their columns are protected by a special security policy to prevent users from changing the platform behavior.
  Examples: Business Rules (sys_busines_rule), Columns (sys_db_column), Access Control List (ACL) (sys_security_acl).
  
• Application configuration tables contain records with information that determines the business logic implemented within an application. The application tables supplied by the vendor are protected by a special security policy. The application tables created by the users or business solution developers can be unprotected.
  Examples: Event Rules (itsm_event_rule), Monitoring Rules (itsm_monitoring_rule).

Reference tables

The reference tables contain master data that define the information objects an organization is dealing with. Such information objects, depending on the industry, may include clients, suppliers, products, services, invoices, and others. The reference tables are used in various business processes of an organization that are automated with the means of the platform. Besides the information that describes a certain information objects, the reference tables describe the relations between these objects and their hierarchy.

The reference tables also contain specific parameters that are used for performing business transactions. For example, time zones, countries, languages, and others. These data seldom change.

Examples:

• Employees (sys_employee)
• Company (org_company)
• Timezone (sys_timezome)
• Language (sys_language)

Transactional tables

The transactional tables contain the data generated as a result of business transactions carried out by an organization. Business transactions are actions or sets of actions that are displayed in the system and are a part of a business process. For example, the service department of a company provides services, registers and processes requests, plans and approves work, notification of an end-user and responsible person. Reference tables are commonly used when when the business transactions are performed.

The CRUD (create, read, update, and delete) transactions are performed on the records of the transactional tables within the automated business processes and procedures.

Examples: Tasks (task), Approval (sys_approval).

Journal tables

The journal tables contain data related to the system operation and the processing of transactional and reference tables. They can be used for solving various analytical tasks and making management decisions.

Examples:

• History (sys_history)
• Activity Feed Item (sys_activity_feed_item)
• Main Log (sys_log)
• Email (sys_email)