Page History

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

Classification by purpose

By 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 against modification from changes by the end-userusers 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 used created by users in the process of operation of the SimpleOne systemthe end-users with the admin role and used to solve their business tasks. 

Classification by the type of processed data

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

• Configuration
• Reference
• Transactional
• Journal

Configuration tables

Configuration The configuration tables contain records with the information on the current configuration on a SimpleOne platform instance of an instance and are used as the primary source of the input parameters , determining the operation and functionality of that determine how the platform itself and applications developed on its base. For work and their functionalities. For example, the Tables Table (sys_db_table) table contains records with configuration information on configurations of all tables of on an instance, including itself, as well as on the Table itself and the virtual root table for all tables.

These tables are normally versioned, i.e. they 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 , constitute and are an integral part of a platform engine, and . They contain records with directive information for that determines these engines or for and the implemented business logic implemented using the platform capabilities. These tables and their columns are protected from modification with special policies (дать ссылку)  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 directive information for that determines the business logic implemented using the platform capabilities within the limits of an application. The application configuration tables supplied by the vendor are protected by special policies as the system configuration tablesa special security policy. The application configuration tables created and modified by the users or business solution developers for their purposes can be unprotected.
  Examples: Event Rules (itsm_event_rule), Monitoring Rules (itsm_monitoring_rule).

Reference tables

The reference tables contain master data which that define the business entities information objects an enterprise organization is dealing with. Such business entitiesinformation objects, depending on the area of activitiesindustry, may include clients, suppliers, products, services, contracts, invoices, patients, etc. In addition to the information directly describing a business entityand 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 entities and hierarchiesobjects and their hierarchy.

The reference tables also contain specific parameters that are used for performing business transactions. For example, for the purposes of finding additional sales opportunities, it may be important to identify explicit and implicit relations between persons time zones, countries, languages, and others. These data seldom change.

Examples: 

• Employees (sys_employee)

• Company (org_company

• )

The data of the reference table contain reference data, which determine values of specific entities, used when performing transactions within the limits of the whole enterprise. These entities include timezones, countries, languages, etc. The reference data seldom change.

• 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. For example, for 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 it is providing provides services, registering registers and processing processes requests, planning plans and approving approves work, notification of final an end-user and responsible person, etc. The transactional systems make a wide use of reference tables when carrying out transactions.. Reference tables are commonly used when when the business transactions are performed.

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

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

Journal tables

The journal tables contain data that include historical transaction related to the system operation and the processing of transactional and reference datatables. They are can be used to 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)