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:

• 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 these tables.
• User tables are created by the end-users with administrator rights (admin role) and used to perform 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 a SimpleOne platform instance and are used as the primary source of input parameters, determining the operation and functionality of the platform and developed applications. For example, the Table (sys_db_table) table contains records with configuration information on all tables of an instance, including itself, as well as on the virtual root table for all tables.

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 constitute 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 from modification 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 which define the business entities an enterprise is dealing with. Such business entities, depending on the area of activities, may include clients, suppliers, products, services, invoices, etc. The reference tables are used in various business processes of on organization automated with the use of the platform. In addition to the information directly describing a business entity, the reference tables describe relations between these entities and their hierarchy.

Besides master data, the reference tables contain specific parameters, used when performing business transaction, such as time zones, countries, languages, etc. 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 enterprise. Business transactions are actions or sets of actions reflected in the system and are a part of a business process. For example, for the service department of a company it is providing services, registering and processing requests, planning and approving work, notification of final user and responsible person, etc. Reference tables are extensively used when performing business transactions.

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

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

Journal tables

The journal tables contain data related to the system operation and to 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).