Architecture

Preface

On the low-level, SimpleOne stores its data and business logic configuration in tables,

Tables consists out of columns; they are interconnected in many ways.

Tables are divided into two sets: system tables and functional tables.

The system tables are used for business logic implementation. They store the inner mechanisms developed on top of the platform.

Tables are protected from structural changes, to prevent system disruption or business logic disruption. 

The purpose of functional tables is to store the data models used in the business logic implementation.

System Tables

System tables, in turn, are divided into several groups, called "layers." In these layers, tables are grouped functionally.

Structure layer

On this layer, tables keep information about the system structure (tables relationships and dependencies, fields relationships, access rights allocation, and so on). Most of them are write-protected.

Tables

This table group contains information about the table structure of the system. 

Fields

This table group contains information about the structure of the fields in the tables.

System Properties

This table group contains specific parameters reliable for the system behavior as a whole, or the specified modules, for example, the system locale or the timezone,

ACL group

This table group contains information about access control lists (ACLs). Notably, the structure of roles and groups is specified.

Applications

This is the dictionary of the applications implemented on the SimpleOne base and installed on the current instance. All the dependencies and components constituting the application are stored here.

Schedules group

This table group contains information about system schedules. This information is needed for the tasks sensitive to the time spent (for example, it may be SLA indicators).

Business Logic Layer

On this layer, tables keep the information necessary for the business logic implementation. Most of them are write-protected.

Scripts

This table group contains information about the scripts, how they interact with the tables, and how it realizes the business logic.

Business Rules

This table group contains information about business rules.

Clients Scripts

This table group contains information about the client-side scripts and how they interact within the system.

Notifications

In there, all necessary information about notifications can be found.

UI Actions group

This table group contains information about UI actions.

Events group

This table group contains information about Events.

Workflows

This table group contains information about workflows and state models,

URL Actions group

This table group contains information about URL actions.

Interface and Navigation Layer

On this layer, the tables are mostly not write-protected. They are responsible for the interface view.

Navigator

This table group contains information about the Navigator, that is located on the left. Information about the categories and items is stored.

Forms

This table group contains information about the forms and lists, their configuration, and position on the page.

Layouts

This table contains information about the form layouts.

Portals

This table contains information about the end-user and agent portals.

Widgets

This table group contains information about different widgets (for example, comments widget).

Dashboards

This table group contains information about dashboards.

Interaction Layer

On this layer, the tables keep the information necessary for the interaction between the system and the user.

Logs

This table group contains system logs that are produced while the system is functioning, and the tasks are handled.

Emails

This table group contains emails (incoming and outgoing), also it contains inbound email actions and default email account. This table group is necessary for email processing.

Attachments

This table group contains all attachments (to emails, to tasks. and so on).

Imports

This table group purpose is to store information about different export and import tasks (for example, updatesets export and import).

API group

This big group contains the server-side, the client-side, and the REST SimpleOne API.

Functional Tables

Functional tables are also divided into layers. In these layers, they are also grouped functionally.

MasterData Layer

Organization Data Layer

On this layer, the purpose of the tables is to store and manage master data for their further processing.

Tasks

This big table group, also known as "ITSM Tasks," contains information related to the different types of ITSM tasks (Incident tasks, Requests Tasks, and so on).

Approvals

This table group contains information related to the approvals (approval rules, approval texts, and so on).

Events group

This table group contains events and alerts produced by the system.

Timesheets

This table group contains information related to the timesheets for their further processing (time sheets and time cards for every employee).

Costs

This table group contains information related to costs and expenses. For example, it can be business trip expenses or representation expenses.

Record Storage Layer

On this layer, the purpose of the table groups is to store records for further processing following the established business logic,

CMDB

CMDB is the Configuration Management Database; this is the ITIL term. So this table group contains configurations of IT-services. For example, it stores configuration records that describe CI (configuration items) through their lifecycle. CMDB is one of the key points of Service Asset and Configuration Management process.

Assets

This table group contains information about all assets and their relationships with other components of the system.

Knowledge Base

This table group contains information related to the Knowledge Base (articles, categories, relationships, and so on).

Contracts

This table group contains information related to the Contracts and Contract Management (contract types, categories, and so on).

No-code Tuning Layer

On this layer, functional tables related to the no-code system and interface configuration tuning are located.

Request Templates

This table group is needed to store Request Templates and keep their creation logic.

Data Lookup Definition

This table group contains the data lookup definition rules used in the escalation process.

Indicators

This table group contains SLA indicators, their relationships with contracts, breach rules, and other related information.

State Models

This table group contains the state models of the processes. Particularly, the transition rules between the states is one of the examples of information stored there.

Assignment Rules

This table group contains the assignment rules. The provided information is necessary for assignment logic (how this or that kind of task (an Incident, or a Change Request, or a Problem, also Service Type and Related CI must be taken into account) will be assigned to the relevant person or group).

Presentation Layer

On this layer, the table groups are related to visualization. They store the settings, including user settings, necessary for data visualization. It is a more visual way of representing transaction data.

Reports

This table group contains information related to the reports. 

Timelines

This table group contains user timelines, including dates, events, and their relationships, depending on the current user.

Taskboards

This table group contains user task boards (such as scrum boards, kanban boards), representing the progress of the team during the period (usually it's a sprint).