Functionality

We have attempted to maintain standards, but due to the nature of the data and programming languages, this has not been achieved. We have tried to ensure that certain files or libraries contain the same functionality throughout the system, to the extent that the notation or capabilities of the language allow.

Although the files, objects, and functions retain the same name, the notation may vary. Thus, a call in a procedural language such as envGet("value"); would be equivalent to $env->envGet("value"); in an object-oriented language.

Due to the nature of the information and its functionality, it has not been possible to include examples of all the functionalities, which is why they are presented in summary form. There is no intention to create extensive documentation or support for external systems, since the system, being developed in open source, allows for code evaluation and modification, making it easier for programmers to understand.

I have arranged the processes and functions as closely as possible according to their "depth" or sequence in which they are executed for easier understanding.

The first are groups of functions that can function as standalone; that is, they can be used in another system without problem.
Secondly, there are the system's own functions. Although some, such as database, can be used independently, there is generally some interrelationship with other functions. It should be noted that the names of the latter may appear as sup_name in early versions of the system, and now as adm_name and usr_name, depending on whether they have specific configurations for administrators and users, respectively, with minor differences.