This site uses cookies and similar technologies related to personal data to offer you a better browsing experience and analyse traffic. By clicking "I Accept" on this banner, or using this site, you consent to this.
Project Infrastructure
The package not only includes the interface editor itself and the interface engine but a number of infrastructure modules, which can be beneficial for any project as well. While older, long-running applications are most likely to have their own infrastructure, these solutions might come in handy to new projects or startups. The infrastructure elements listed below are optional for any project.
  • Users
    User registration by the system administrator. Password changing by the administrator, or by the user — optionally or forced (on the first use and/or as scheduled). Temporary user blocking.
  • Access control
    Editable dictionary of types of objects to which rights management can be applied. Defining various types of rights (view, change, run, etc.) for each type of objects. Supervising user groups, creating a code, which would apply in case of adding or excluding a member. Granting explicit rights for various objects to user groups. Revising existing rights and their conditions.
  • Audit
    Editable dictionary of types of audit records. Auditing user connections/disconnections, user actions, and data changing (inserting, updating, deleting) in the database table.
  • Multilanguage support
    Editable dictionary of languages, indication of kin languages. Setting current language for all/a number of users as well as for a number of operating modes. Language changing by the user during the session. Ability to enter a different value for every language supported by the application.
  • Alphabets
    Editable dictionary of rules for checking and autocorrecting the inputted texts.
  • Messages
    Editable dictionary of error, warning, and info multilingual messages. The messages can be explicitly activated by the code with passing parameters. The error messages can be linked to the database constraint or to the exceptions of procedural language and can activate automatically.
  • Parameters
    Tagged values categorized as follows:
By storage type
Real parameter
Has a default value and keeps the defined value between different sessions.
Virtual parameter
Value is set and stored for a current session only.
By type of change
Read only
Once the value is set the parameter can not be changed by the application.
Modifiable parameter
Can change value during a session even if it is a global one. The new value is stored till the end of the current session.
By place of use
Global parameter
Has only one value set for the entire application. If the parameter is changed, the new value is applied in every place where it is used.
Local parameter
Has different values depending on given conditions. E.g. set for each user individually.
By the method of setting the initial value
Static parameter
Has a constant value set either by default of during the application work.
Dynamic parameter
A declarative algorithm for calculating the value, which runs when the parameter is newly accessed. The algorithm can base upon other parameters, either static or dynamic, real and virtual, read only and modifiable ones.
  • Special dates
    The interface has a calendar where you can select values for the Time/Date fields. It has two default values — business days and weekends. The user can make amends by setting the type of any day to be a weekend, a public holiday or a business day. The set of possible day types can be extended. These changes will be displayed on the calendar. The application logic can refer to these values afterward.