TECHNICAL Sign up Sign in EN
Database configurator

Database configurator.

Each account in the ERP Platform is freely configurable and can be configured for the individual processes of the company. The configurator consists of 4 parts:
  • Database Configurator
  • Interface configurator
  • Menu configurator
  • Report Configurator
Database configurator allows :
  • make arbitrary modification of the database structure, create and modify tables;
  • has a built-in PL \ SQL editor, you can create procedures and triggers of any complexity;
The Database Configurator ( hereinafter DB Configurator ) is available to the Account Administrator (the one who created the account), as well as to all users to whom the Administrator assigns administrative rights, or individually as a user will indicate that he can use the DB Configurator ...

The DB configurator is a rather complex tool and is not intended for ordinary users.
Its purpose:
  • allows ERP-Platform programmers to quickly and quickly change the database configuration at the request of the client;
  • to the client - if desired, independently, make any changes to the database structure and data processing algorithms, in accordance with the requirements of their own business processes;

Database Programming

The built-in ERP-Script programming language gives organizations unlimited flexibility in database localization. ERP-Platform allows its clients to independently create and edit any data structures, customize any actions for events occurring in the system.


The programming system allows you to create or update any tables in the database.

Web-oriented PLSQL Procedures and Triggers

The creation of data processing procedures of any complexity is supported. You can customize the execution of the procedure by commands from the interface (for example, by pressing a button), upon a modification event in the database (in a trigger), or generate an execution plan according to a given schedule.


BlockChain is a standard ERP-Script function and allows one-click connection to tables to calculate the checksum of records or a chain of record blocks. Checking the consistency of a block chain is built into procedures or triggers with one click. BlockChain functions are very convenient for reliable logging, or other functions where it is necessary to guarantee the accuracy of the information entered.

And also

built-in CRUD (procedure creation automation), Snapshot procedures, data transfer to the API system, ... and much more.


The DB configurator allows you to make arbitrary editing of tables. You can create new tables, or add fields to existing ones.

The database structure supports all standard field types + an additional Image field. Image type - allows you to store images and work with them as with ordinary data in the database.

You can change the order and name of the fields. You can customize the relationship of key fields to other tables. Set up links with directories. Also, each field can be canceled, use it in the reporting system or not.

Each table can include a detailed log entry. The system will write logs on adding, changing and deleting data. What values ​​were in which fields before modification and what became after modification.
This data is written to a separate database and does not clutter up the company's working base. Viewing these logs is available through a special interface in the "Settings-Logs" section.


Procedures are the most flexible tool for receiving and processing data.
The procedures support full PL \ SQL. You can make queries, loops, conditions, string operations, data modification operations, etc. Lots of built-in system functions. There are also unusual structures. For example, you can embed API structures directly into a procedure / trigger. Those. directly from the trigger to the database (by event), transfer information somewhere outside. The user configures the API structure himself, and he configures the addresses where to transfer. You can embed procedures in procedures of any nesting. There is a task scheduler where you can put procedures in a scheduled launch on schedule.

The procedure can include the following types of blocks:
  1. Condition
  2. SQL Query data
  3. String
  4. Adding data (Insert)
  5. Data change (Update)
  6. Deleting data (Delete)
  7. Procedures (other procedures can be embedded in procedures)
  8. API (you can send data to external systems directly from the procedure)
  9. ... and various derivatives of these blocks
Case structures (output conditions) are supported in SQL query. Of course, join (joining tables) is supported, any conditions, any sorting and grouping of data.

The procedure supports a wide variety of functions. Functions are grouped into thematic blocks: System, Data type conversion, String processing, Operations with dates. Functions can be used in any query fields, strings, modification operations, etc.

You can take a Snapshot of the procedure and roll back to its previous states in case of errors.

The procedures are fast thanks to compilation. Modern databases are quite a perfect tool, and there is no point in neglecting them. The procedure written by the user via the web interface is compiled.
The system works knowing the structure of the procedure and executing the necessary requests to an already compiled, fast working element.


A trigger is a procedure of a special type, which the user does not call directly, but whose execution is conditioned by the action of modifying the data: adding INSERT, deleting DELETE rows in a specified table, or changing UPDATE data in a specific column of a specified table.

The DB configurator allows you to create triggers for any type of modification or their combination.
Triggers use full procedure functionality, including API blocks. Those. by event in the database, you can transfer information to external systems.

The main purpose of triggers is to configure the system's response to events. For example, when a letter arrives via a postal channel - analyze the letter, calculate the client, create an application. Or, when adding a user to a task, write a notification to this user in the mailing system. And much, much more, the trigger is a very versatile mechanism for customizing reactions.

Triggers allow you to work with field values ​​before and after modification. Those. if a data change event has occurred, the trigger can work both with the data values ​​that existed before the modification, and with the newly assigned values.


BlockChain is a built-in ERP-Script function. BlockChain or checksum calculation can be connected in any table of the system with one button.

Calculating BlockChain and Checksum

Checksum calculation only monitors the record within the data line. Any changes to the data will invalidate the old checksum.

BlockChain in the checksum also includes the checksum of the previous data line. This recording technology guarantees that when:
  1. Delete any data line
  2. Any change to the data of the current row
  3. Forgery of the previous line with other data
The system will show that the record has been changed and the checksum is incorrect

BlockChain and Checksum Validation Functions

The BlockChain record checking system is a standard feature, and can be built into any procedure or trigger with one click. Any output of information about checksums to the system interface can be organized in them.