CS

NET Genium settings

Home / Documentation / Administrator guide /

NET Genium settings

CS

1. NET Genium settings

  • NET Genium settings are available to all users with administrator privileges.

2. List of tabs in the settings dialog NET Genium

  • General – Setting general properties of NET Genium
  • Emails – Email settings
  • Print templates – Setting up print templates
  • Permissions – Permission settings
  • Passwords – Password settings
  • Colors – Color settings
  • Other – Setting other properties

2.1. “General” tab

2.1.1. Name

  • The name NET Genium displayed in the web browser tab.
  • The NET Genium name is stored in the server variable “#portal#”.

2.1.2. Version

  • The NET Genium version displayed in the header of the web browser and in the subject of all outgoing e-mail messages.

2.1.3. Portal address

  • Intranet address – the Enter-separated list of these addresses will be used when initializing NET Genium in multiple instances.
  • Internet address – the Enter-separated list of these addresses will be used in e-mail messages sent by the script and will ensure that the user can be redirected to NET Genium for specific records.
  • In NET Genium Online neither field is displayed – the address of the instance is given by its identifier (“identifier.netgenium.online”) and NET Genium inserts it into outgoing e-mail messages by itself.

2.1.4. Time zone

  • The NET Genium time zone is automatically set to the time zone of the server on which NET Genium is hosted.
  • By selecting a specific time zone from the drop-down list, this setting can be changed to the desired value.
  • In NET Genium Online the time zone is chosen when the instance is registered.
  • The time zone applies to the date values that the platform itself writes, and to the way they are displayed — for example to the values of the “#now#” and “#today#” variables, to the default values of date controls, and to the highlighting of today in the calendar. The date and time filled in by the buttons of date and time fields and by the “Now” and “Now2” JavaScript functions correspond to the time zone in which the user sees the times (see below).
  • Changing the time zone does not recalculate the values already stored, it only changes their meaning. It is therefore advisable to set it when the instance is being deployed, not while it is in use.
  • Individual users can have the times displayed in their own time zone — the Time zone and Show times in my time zone fields in their user account are there for that. The conversion only affects what is displayed: the value is always stored in the time zone of the instance, so the conditions of database queries, the values of the “#now#” and “#today#” variables in scripts and statistical queries are unaffected. Only the values that carry a time are converted — a date without a time (a due date, for example) is not a moment and stays unchanged.
    • The Time zone and Show times in my time zone fields exist only in newly created NET Genium installations; they are not added to older installations yet.
    • Values are displayed and entered in the user's time zone in the edit form, in the view table, in the calendar, in the planners, and in the data export and import of the view table. Filters and search in the view table, on the other hand, are entered in the time zone of the instance, as are the values of the “#ng_...:value#” variables.
  • Print templates and exports follow the time zone of the user who prints or exports; the e-mails composed by the “Send e-mail” script step follow the time zone of the user whose action started the script.

2.1.5. Date format

  • The date format determines the order of the day and month in the short date across the entire application – when displaying as well as when entering and reading dates in forms, filters and scripts – regardless of the user's language. The separator (period or slash) and the decimal separator of numbers follow the user's language.
  • The drop-down list contains the following options:
    • dd/mm/yyyy – day month year
    • mm/dd/yyyy – month, day, year

2.1.6. Default map

  • The default map defines the default geographical center of all map data that does not contain any points on the map in the currently displayed data visualization. In other cases, the geographic center is calculated automatically from all points displayed on the map.
  • The default map controls the search for addresses stored in “TextBox” controls called “Find on map”, “Find on map” or “Find on map”.
  • The drop-down list contains the following options:
    • Czech Republic – address search offers map portals “maps.google.cz” and “www.mapy.cz”.
    • Slovakia – address search is offered by the map portal “maps.google.sk”.
  • In NET Genium Online the field is not displayed and the drop-down list offers no country – the setting stays empty and NET Genium behaves the same way as with the “Czech Republic” option.

2.1.7. Fulltext catalog

  • Catalog for the full-text file attachment search function.
  • The drop-down list contains the following options:
    • None – File attachments are never searched while searching for values in view tables.
    • Windows Search – while searching for values in the view tables, file attachments are searched using the “Windows Search” full-text catalog. A detailed description of the configuration of the “Windows Search” full-text catalog is provided in the separate guide Installing NET Genium on the web server.
    • Indexing Service – while searching for values in view tables, file attachments are searched using the “Indexing Service” in the catalog, the name of which is entered in the text field below the drop-down list of the full-text catalog. The “Indexing Service” was last available in the “Windows Server 2008” operating system, so we recommend replacing its use with the full-text catalog “Windows Search”. A detailed description of the configuration of the “Windows Search” full-text catalog is provided in the separate guide Installing NET Genium on the web server.
  • In NET Genium Online neither the drop-down list nor the text field with the catalog name is displayed – full-text searching of file attachments is not available in the cloud.

2.2. “Emails” tab

2.2.1. Default sender of all messages

  • An email address that will be set as the default sender of all messages. Emails that have senders from another domain will be sent using the default sender of all messages. In this case, the original sender of the message is preserved in the “Reply-To” header of the message, so any replies are delivered to the original sender. If the message has its own reply address, that address is kept.
  • In NET Genium Online the address is fixed to “identifier@netgenium.online” according to the identifier of the instance and the field cannot be edited – no instance can therefore send messages under the address of another instance.

2.2.2. System warnings

2.2.2.1. Service e-mail address

  • Administrator's email address for sending system messages. If the address is empty, no system messages will be sent.
    • E-mail messages without any recipient (NG NO-RCPT: will be inserted in the subject of the message)
    • Reports of exceeding the maximum number of logged in users
    • Error messages in applications or when synchronizing records

2.2.2.2. Sender of system warnings

  • An email address that will be set as the sender of system messages.
  • If the address is empty, the address filled in as the “Default sender of all messages” is used. If that one is empty as well, messages about licences are sent from “license@netgenium.com” and reports of errors in applications or during record synchronisation from “error@netgenium.com”.
  • In NET Genium Online the field is not displayed and system messages are always sent from the default sender address of the instance. The sender of other messages (the “Send email” script step, server functions, the “New email” form) is likewise always replaced by the default sender address of the instance in the cloud; if the message has no reply-to address, the original sender address is used as one.

2.2.3. Outgoing mail server

2.2.3.1. SMTP Server 1

  • The name or Internet address of the SMTP mail server used to send e-mail messages.
  • SMTP Server 1 is used to send e-mail messages through the following commands:
    • View page – New e-mail message
    • Button – Open the form for entering a new e-mail message
    • Script – Send email
    • Script – SENDMAILMESSAGE()
    • Script – SENDMAILINVITATION()
    • Script – SENDMAILINVITATION2()
    • Script – SCHEDULEMAILMESSAGE()
  • In NET Genium Online the whole “Outgoing mail server” section is not displayed and cannot be configured – SMTP Server 1 is fixed to “localhost”, so all instances send mail through the mail service of the cloud server. The “SMTP TEST 1” button is not displayed either.

2.2.3.2. SMTP Server 2

  • The name or Internet address of the SMTP mail server used to send e-mail messages.
  • SMTP Server 2 is used to send e-mail messages through the following commands:
    • Backup SMTP Server – all e-mail messages that fail to be sent the first time using SMTP Server 1 are forwarded for sending using SMTP Server 2. If SMTP Server 2 is not defined, or fails when sending a message using SMTP Server 2, the e-mail message is saved in the “SMTP” directory as an “eml” file, and “ResendEmlFiles.exe” tries to resend it. Which is typically run every 30 minutes using a scheduled task.
    • Script – SENDMAILMESSAGE2()
  • In NET Genium Online SMTP Server 2 is not displayed and cannot be filled in – a backup mail server is not available in the cloud.
  • If neither SMTP Server 1 nor SMTP Server 2 is defined, all e-mail messages are stored in the “SMTP” directory in the form of “eml” files. The name of the “eml” file consists of the date and time of its creation and a unique GUID identifier (e.g. “2026-06-09 10-20-20 8925b488-b4a8-4192-a503-60b74b853186.eml”). The “ResendEmlFiles.exe” program, which typically runs every 30 minutes with a scheduled task, attempts to resubmit them. Messages successfully sent by “ResendEmlFiles.exe” are deleted from the “SMTP” directory, unsuccessful messages sent by “ResendEmlFiles.exe” will be sent a total of 48 times (the scheduled task created by “Setup.exe” runs from 6:00 to 24:00 every 30 minutes, so 48 attempts take about a day and a half), and then ignores these files in the “SMTP” directory. The list of unsuccessfully sent or already ignored messages is stored in the configuration file “SMTP/ResendEmlFiles.errors”.

2.3. “Print templates” tab

  • List of print templates stored in the “Templates” directory with the option to add or remove templates from this directory.
  • Print templates from this list are offered in “File” and “Button” controls.
  • Unused print templates are shown in italics.
  • A detailed description of print templates is provided in the separate guide Print templates.

2.3.1. Statistics

  • Statistics display aggregated information about the use of printing templates across the entire application.
  • The “Statistics” link displays a detailed report of all controls that use this template, including the ability to open the settings for this control.

2.3.2. Add template

  • Button for inserting a new print template in the “Templates” directory.

2.4. “Permissions” tab

2.4.1. User account administrator

  • List of user groups or users who:
    • they can set a new password for other users (except for users who have administrator privileges). As with user groups, the administrator of user accounts needs the right to edit the user record to save the new password.
    • they can add and remove user groups of other users; only the user “Administrator” may add or remove the “Administrators” group. To save changes in a user record, the administrator of user accounts additionally needs the right to edit the record, typically as a co-owner of the “User” form.
    • they can set up new user groups for each rights group.
    • they can send a chat message to all users of the application (as well as users with administrator privileges).
    • sees all sessions in the list of online users (as well as users with administrator privileges). Other users see only one record for each user online, in terms of time the one with the latest user login date.
    • they can log out sessions of other users in the list of online users; sessions of users with administrator privileges can be logged out only by a user with administrator privileges.

2.4.2. Administrators with access to the MCP server

  • List of users who are allowed to work with the integrated MCP server of the instance. Only users with administrator rights, i.e. members of the “Administrators” group, can be selected; the “Administrator” user is not among them, because they always have access.
  • If the list is empty, the MCP server can be used by any user with administrator rights who has generated a personal MCP token.
  • If the list contains at least one record, the MCP server can be used only by the “Administrator” user, i.e. the user with database ID 1, and by the users listed. For all other users the request is refused with a 403 response and the reason is written into the “Auth” log.
  • The restriction applies to all tools of the MCP server, i.e. to reading and writing data, to the implementation model and to the framework documentation.
  • The restriction applies to connecting an AI tool by signing in as well – an administrator who is not on the list is shown a message that their account is not allowed to access the MCP server instead of the consent screen.
  • The “Access via a custom API” permission of the personal token is not restricted by the list — a custom API handles authorization on its own.
  • An administrator who is not on the list is not offered the “Reading all data and the model via the MCP server” and “Writing all data and the model via the MCP server” token permissions on the “MCP token” tab.
  • A detailed description of the MCP server is provided in the separate guide The integrated MCP server.

2.4.3. IP addresses allowed

  • List of allowed IP addresses from which it is possible to log in to the application if the user is a member of the selected user group.
  • The list of allowed IP addresses is used to set restrictions for users who are in the “Administrators” group and therefore have administrator privileges, including the administrator mode option. Administrator mode is then enabled only if the user accesses the application from specific IP addresses. An administrator who is also a member of another user group and accesses from another IP address logs in – if the restrictions of their other groups allow it – without administrator rights. An administrator who is only in the “Administrators” group, and the built-in Administrator account, cannot log in from another IP address at all.
  • The list of allowed IP addresses is used to set restrictions for users who are not in the “Administrators” group. If the user accesses from another IP address, the option to log in to the application is removed. A user none of whose user groups is in the list is not restricted. A user who is a member of several user groups in the list needs to match the IP addresses of any one of them. When working in the web browser, the IP address is checked only at login; the MCP server checks it with every request. The restriction does not apply on the server desktop (IP address “127.0.0.1”).
  • The allowed IP address can take the following values:
    • 1.2.3.4 – access is allowed only for this specific IP address
    • 1.2.3 – access is allowed for all IP addresses where the first three parts agree, the value of the fourth part can be arbitrary
    • 1.2 – access is allowed for all IP addresses where the first two parts agree, the value of the third and fourth part can be arbitrary
    • 1 – access is allowed for all IP addresses where the first part agrees, the following three parts can be arbitrary

2.4.4. Public external functions

  • List of public external functions that a client may call without prior authorization by the server. For each function a user group to which it is accessible is selected: without a restriction the function is accessible to anyone including users who are not logged in, otherwise only to users with administrator privileges, or to members of the selected user group. A function cannot be restricted to an individual user.
  • The definition of a public external function must contain only the identifier of the external function, ie the value of the “string id” parameter. A detailed description of external functions is provided in the separate guide External functions, and also for the function “string ngef” in the separate guide Server functions.
  • In NET Genium Online the list of public external functions is not displayed – external functions are not available in the cloud.

2.4.5. Add IP address

  • Button for entering a new record of the allowed IP address.

2.4.6. Add external function

  • Button for inserting a new record of a public external function.
  • In NET Genium Online the button is not displayed.

2.5. “Passwords” tab

2.5.1. Password strength required

  • The password strength setting determines how complex passwords must be when changing old passwords to new ones.
    • None – The password may be blank.
    • Weak – The password must be at least 5 characters long. The password expires every 12 months, and the new password may be the same as the previous one.
    • Fair – The password must be at least 8 characters long, and must contain at least 3 characters from the set {lowercase, uppercase, numbers, special characters}. The password expires every 12 months, and the new password cannot be the same as the previous one.
    • Strong – The password must be at least 12 characters long (administrator password at least 17 characters), and must contain all characters from the set {lowercase, uppercase, numbers, special characters}. The password expires every 12 months, and the new password cannot be the same as any of the previous passwords.
  • Special characters: - _ , . : ; ! @ # $ % ^ & * = + ( ) { } [ ] < > / ? ' ` " | § and space
  • Only letters without diacritics count as lowercase and uppercase letters; letters with diacritics and characters outside the listed special characters do not count toward any group.
  • Previous passwords are looked up in the user's change history, so deleting the history shortens their list. The “User” edit form allows keeping a password identical to the current one; with the “Strong” password strength, however, no other previous password can be set there either.
  • When a password strength is set, the password must not contain any four consecutive characters of the login name (case-insensitive).
  • When a password strength is set, a user who has never changed their password themselves must enter a new password at the next login with a user name and password. Only the user's own password change counts – a password set by an administrator is not taken into account and does not change the expiration period. A user who has changed their password themselves, even before the password strength was set, enters a new password only after it expires, that is 12 months after their last own change.

2.5.2. Print templates

  • Password required when editing print templates by a user who does not have administrator privileges. If the password is blank, print templates cannot be edited.
  • The website for editing print templates is located at “url-netgenium/templates”.
  • The password is available only in full installations of NET Genium – in NET Genium Online the field is not displayed.

2.5.3. Restart

  • Password required when restarting NET Genium by a user who does not have administrator privileges. If the password is blank, NET Genium will not be restartable.
  • The NET Genium restart website is located at “url-netgenium/restart”.
  • The password is available only in full installations of NET Genium – in NET Genium Online the field is not displayed and NET Genium is restarted by the service provider.

2.5.4. Synchronisation

  • If the password is blank, it will not be possible to synchronize data from the remote server with your NET Genium.
  • The password is available only in full installations of NET Genium – in NET Genium Online the field is not displayed and data synchronisation between instances is not supported.

[[Kotva:ai-model-password]]

2.5.5. AI model

  • Password required when downloading the [[ai-models AI model]] automatically using web services. If the password is blank, the model cannot be downloaded automatically.
  • The website for downloading the model with this password is located at “url-netgenium/ai”.
  • The tool that downloads the model authenticates itself with this password – in the “ai-model.json” configuration file it is the value of the “ngPassword” key. After changing the password, that configuration file must be updated as well.
  • The password is stored in the database only as an irreversible hash, so it is never displayed in the settings – a forgotten password cannot be retrieved, only replaced with a new one.
  • Besides the password, the IP address the download comes from is verified as well – it must be listed in “IP addresses allowed” on the “Permissions” tab.
  • The password is available only in full installations of NET Genium. In NET Genium Online the field is not displayed at all and the model can neither be downloaded nor uploaded automatically – in the cloud the AI assistant connects to the [[mcp-data-server integrated MCP server]] of the instance, which serves the model directly.

2.5.6. Generate password

  • The button generates a random password in the form of a GUID identifier and writes it into the dialog together with an icon for copying it to the clipboard.
  • The generated password is not stored anywhere – it only serves as a source of a random value that can be pasted into any of the passwords above. It is displayed only once, so copy it and store it safely.

[[Kotva:colors]]

2.6. “Colors” tab

  • List of colors offered by the color designer when editing a value in “TextBox” controls with the “Show color designer in edit form” option checked.
  • If the color list is empty, the color designer offers a default color palette.

2.6.1. Add color

  • Button for inserting a new color record.

2.7. “Other” tab

2.7.1. Navigator

  • The navigator type setting determines how the navigation area lists the applications.
    • Type A – displays a list of all applications in the navigator, including the options for editing them.
    • Type B – speeds up the work with NET Genium in admin mode, but it is not as comfortable as type A.
  • The option is offered only in the old design (up to 2016); in the current appearance of NET Genium it is not displayed in the settings.

2.7.2. E-Learning

  • The e-learning style setting determines what appearance will be used to visualize e-learning courses.
    • Style A – displays e-learning courses in pleasant blue and orange colors and contains pictorial navigation buttons.
    • Style B – is rather conservative and respects the color settings of NET Genium.
  • In NET Genium Online the style option is not displayed.

[[Kotva:performance-logging]]

2.7.3. Logging

  • Logging is used to measure the processing time of database queries, scripts, view pages, edit forms and external functions.
    • Off – Server-side processing times are not measured.
    • To database – Processing times for database queries, scripts, view pages, edit forms and external functions are stored in the database. From this data it is possible to display aggregated statistics using the “Logging” button directly in the settings of the given control element, resp. its database query, as well as in the settings of the script, view page or edit form. Another option is to display these statistics on the reports page, where statistics of measurements of external functions are also available. A detailed description of the reports is provided in the separate guide [[reports Reports]].
    • To disk – Processing times for database queries, scripts, view pages, edit forms and external functions are stored on disk in the “Logs” directory.
    • To database and disk – Server-side processing times are stored in the database and on disk at the same time.
    • Logging to console – Processing times for view pages and client-side edit forms are displayed in the console at the bottom of the web browser.
      • Data Transferring Time – communication time between client and server
      • Page Processing Time – server-side page processing time
      • Page Rendering Time – time of page rendering in the web browser
      • Total Waiting Time – total waiting time for the page to be viewed
    • Measure memory consumption – Monitoring the memory consumption of each database query that retrieves data.
      • Memory consumption is calculated as the difference of the allocated memory of the “w3wp.exe” process before and after the data is successfully retrieved from the database.
      • The “w3wp.exe” process serves the requests of all users of the web application, so the calculated value may be inaccurate and may also include the memory consumption of other requests.
      • The calculated value can also be negative if memory was freed by the Garbage Collector during data loading.
      • The measured value of memory consumption is available in reports when database logging is enabled, and on disk in the log file “Logs\Data-yyyy-MM.log” for those database queries whose memory consumption exceeds 1GB (the word “LastMemoryConsumption”).
    • Delete old logs in the database – Deletes all measured data from the database, regardless of its age.
    • Delete old logs on the disk – Deletes log files with a date in their name older than 7 days from the “Logs” directory, together with the contents of all dated user subdirectories. Files without a date in their name, such as “System.log”, are kept.
  • In NET Genium Online the drop-down list offers only the “Off” and “To database” options – logging to disk is not available. The “Measure memory consumption” option is not displayed either.

[[Kotva:options]]

2.7.4. Options

  • Enable automatic error reporting to NetGenium
    • Checking this box determines whether each error should be automatically sent to NetGenium Technical Support.
    • For each error in NET Genium, an error message will be displayed on a separate page, where it is possible to send the error manually to NetGenium Technical Support.
  • Log usage of view pages
    • Checking this box determines whether the use of individual view pages in the database should be logged in the “Settings” application:
      • Logging into the “Settings/Statistics” table – Visited view page, User, Date
      • Logging into the table “Settings/Statistics 2” – Visited view page, Number of visits
      • Logging into the table “Settings/Statistics 3” – Visited view page, User, Number of visits
    • View page logging is used to detect underused or unused view pages by users.
    • The opening of the same page by the same user is logged in the database only once an hour.
    • In NET Genium Online this field is not displayed.
  • Enable sending lost passwords on the login page
    • Checking this box determines whether the “Forgot Password” button should be displayed on the login page next to the “Login” button, which is used to send password recovery instructions to the user's email address.
    • When the “Portal address” is filled in, the e-mail contains a link for setting a new password; the link is single-use and valid for 1 hour. When no portal address is available, a temporary password with the same validity is sent instead, with which the user logs in and changes the password right away.
    • In NET Genium Online the portal address is derived from the identifier of the instance, so the link works with no further configuration.
    • Password recovery can be requested at most five times in 24 hours for each user, and at most three times in five minutes from a single IP address.
    • The login page always answers the same way, regardless of whether the entered user exists and has an email address filled in — valid user names therefore cannot be probed. When the entered user does not exist or has no valid e-mail address, this is written to the “Warnings” log; the result of sending the e-mail is not evaluated.
    • Once the password change through the link or the temporary password is complete, the user receives a notification at their email address with the date, the IP address and the browser the change was made from.
    • In NET Genium Online both e-mails — the one with the link and the change notification — are sent in the visual style of the other cloud messages, with a button instead of a bare link and with an overview of the request details. A classic installation sends the e-mails unchanged.
  • Send emails with tips on getting the instance going
    • The field is displayed only in NET Genium Online. Checking this box determines whether NET Genium sends e-mails with tips on getting started with the instance in the first weeks after registration. Each e-mail points out a step that is still missing in the instance: the first work in the instance (no earlier than the 3rd day after registration), an application built by AI (no earlier than the 7th day) and connecting an AI agent through the MCP server (no earlier than the 14th day). Each e-mail is sent at most once, only within 30 days of registration and only on working days.

3. Application “Settings”

3.1. Core application

  • NET Genium contains a default set of edit forms and their corresponding view pages, which are essential for the correct functioning of the entire application. These edit forms are located in the “Settings” application.
  • The “Settings” application cannot be deleted or moved to another application group.
  • Modifications to edit forms and view pages in this application can be performed only by a single user with the highest permission level — the “Administrator” user with database ID 1.
  • The “Settings” application contains the following edit forms and their corresponding view pages:
    • User – database table “susers” with the list of users
      • Full name – the user’s full name
      • Surname – the user’s surname
      • First name – the user’s first name
      • Title – the user’s title
      • Login name – the user's login name
      • Password – the user’s password
      • Language – the user’s language setting (cs, de, en, fr, sk)
      • Windows account – the domain account name of the user in Active Directory, used to enable automatic login to NET Genium without entering a username and password
      • E-mail – the user’s email address
      • M-Password – password for the user’s Android mobile - device account
      • Rights group – foreign key to the rights group directory, defining the list of user groups of which the user is a member. Assigning a user to a rights group is the preferred method of granting permissions, though manual assignment of user groups is possible via the next control “User groups”.
      • User groups – list of user groups in which the user is a member. Manual assignment of user groups for each user individually is not the preferred method of permission assignment; the recommended method is selecting a rights group as described above.
    • User group – database table “susergroups” with the list of user groups
      • User group – name of the user group
      • Description – description of the user group
    • Rights group – database table “srightsgroups” with the list of rights groups
      • Rights group – name of the rights group
      • Description – description
      • User groups – list of user groups defining the rights group
    • Public holiday – database table “sholiday” listing current public holidays. Content is generated automatically according to the language settings of NET Genium.
      • Holiday name – name of the public holiday
      • Date – date of the public holiday
      • Half-day – checkbox for marking half - day public holidays (used mainly in Germany)
    • Layout – database table “slayout” with the list of graphic themes of NET Genium
      • Name – name of the layout
      • Save as active layout – checkbox for marking the layout as active and regenerating CSS
      • Font name
      • Text size
      • Font color
      • Header – Logo
      • Header – Background image
      • ...
    • Invalid login – database table “sinvalidlogins” with invalid login attempts
      • Date – date of the invalid login
      • IP address – IP address from which the login attempt was made
      • Login name – login name that was used
      • Password – always the value “*****”; the entered password is not stored
    • Statistics – database table “sstatistics” with view page usage statistics
      • View page – visited view page
      • User – login name of the user who visited
      • Date – date of visit
    • Statistics 2 – database table “sstatistics2”
      • View page – visited view page
      • Session – number of visits
    • Statistics 3 – database table “sstatistics3”
      • View page – the visited view page
      • User – the login name of the user who visited the page
      • Session – the number of visits
    • Synchronization – database table “ssynchro” with synchronization errors
      • Error date
      • Edit form – name of the form where the error occurred
      • Record ID – ID of the record involved
      • Error – error description

3.2. Optional applications

  • The “Install” directory contains a set of optional applications that can be imported into NET Genium.
  • Available optional applications:
    • API – management of API keys for external system access and SQL - query records available for download via API.
    • Applications – overview and management of applications installed in NET Genium. The edit forms use views defined in their settings; these views must be created afterwards on the “Administration” tab using the “CREATE VIEW” command.
    • Business Logins – management of credentials and tokens for communicating with the Google, Facebook and Microsoft APIs.
    • DataGrid Settings – saving/loading individual datagrid settings. The application uses the “SAVEDATAGRIDSETTINGS” and “LOADDATAGRIDSETTINGS” server functions and includes an example of their use.
    • E-learning – e-learning courses and materials.
    • E-mail – management of email templates and sent emails.
    • FileUpload – management of files uploaded to the server (used by FileUpload.exe).
    • Licenses – monitoring license usage over time.
    • Maps – map backgrounds and geographic data visualization. The application demonstrates working with maps and the use of the “PLACESONMAP” server function.
    • Practical information – a list of public holidays and foreign words.
    • Reset password – mass password reset and email delivery.
    • RUIAN – address lookup in the Czech territorial registry.
    • Services – monitoring services running via Windows Scheduler or console apps.
    • SMS – sending and receiving SMS. The application is required for the “SMSService” service to run.
    • Stats – edit forms for reading logs recorded by NET Genium while database logging is enabled. The edit forms use views defined in their settings; these views must be created afterwards on the “Administration” tab using the “CREATE VIEW” command.
    • UNION – examples of the SQL UNION operation using views. The edit forms use views defined in their settings; these views must be created afterwards on the “Administration” tab using the “CREATE VIEW” command.
    • Web – management of content published via NET Genium.

4. Configuration files

  • Configuration files contain data required for the correct operation of the web application but are not part of the database. They are located in “NETGenium\Config” as text files.
  • ActiveLayout.txt – database ID of the layout that will be used as the default, regardless of the active-layout setting in the database records of configured NET Genium layouts in the “Settings” application.
  • BlindFriendly.txt – when this file exists, view tables use a static toolbar displayed permanently under the view-table title instead of a dynamically displayed one.
  • ConnectionString.txt – the connection string to the NET Genium database.
  • Copyright.txt – placeholder HTML code for the copyright displayed in the navigation area. If the file does not exist, the text “© 20xx NetGenium” is shown. A second option for modifying the copyright is via the NETGenium.Copyright external function, see the [[external-functions#netgenium-copyright External functions]] guide.
  • CustomIcons.txt – a list of custom icons replacing default icons used in the application. Each line defines one icon in the format: “Images/Picker.gif:Images/Custom/Picker.svg”
  • DefaultLanguage.txt – two-letter code of the default language in which the “Settings” application is localized and which is assigned to users “Administrator” and “Anonymous” upon creation (“cs”, “de”, “en”, “fr”, “sk”).
  • Demo.txt – when this file exists, saving or deleting anything in the web application is disabled. The file may optionally contain a list of database tables (one per line) in which changes remain allowed. For example, “susers_vf” enables user customization of view tables. Where changes are disabled, scripts do not send e-mails either – neither the “Send email” step nor the server functions sending e-mails are performed. In tables in which changes are allowed, e-mails are sent as usual.
  • DenyContextMenu.txt – when this file exists, right-clicking selected text in the “RichTextBox” control and in the “TextArea” control with the “Wiki” or “Markdown” data type displays the default context menu of the web browser instead of the formatting context menu. Text is then formatted with the tools in the toolbar above the control.
  • DenyCookieless.txt – when this file exists, the web application requires cookies on the client side. It takes effect only after an update of NET Genium rewrites the “Web.config” file. Consequently:
    • SessionID will not be inserted into page URLs (“.../netgenium/(S(33cipeb0js15bo1t1xhkupr4))/default.aspx”)
    • it will not be possible to log in within a single web browser under different user accounts in different tabs — the web browser merges individual sessions.
  • DenyExport.txt – when this file exists, exporting applications is disabled.
  • DenyInvalidLogins.txt – when this file exists, account blocking after repeated invalid logins does not apply to logins with a user name and password in a web browser from IP addresses listed in “IP addresses allowed” for the “Administrators” group; the exception applies to any login name entered from such an address, but not to connections via the web services of the “NETGeniumConnection” library.
  • DenyLogin.txt – when this file exists, login with a user name and password is possible only on the server desktop or from the IP address “127.0.0.1”. From anywhere else the login window is not displayed and a login with a user name and password is refused; users can log in from there only by other means (login ticket, Microsoft sign-in, Windows authentication). Connections via the web services of the “NETGeniumConnection” library are not restricted by the file, whereas the integrated MCP server is disabled while the file exists. The file may optionally contain a URL for redirecting unauthorized login attempts.
  • DenyStartSynchro.txt – when this file exists, the web application does not send the synchronization queue itself; the queue is then sent only by the “StartSynchro.exe” program run by a scheduled task.
  • DenySynchro.txt – when this file exists, changes are neither queued for synchronization nor sent to linked servers; receiving synchronization from other installations is not disabled by it (an empty synchronization password disables it).
  • Developer.txt – when this file exists, application errors are displayed in their raw form instead of user-friendly messages.
  • EncryptionKey.txt – encryption key used for encrypting “TextArea” and “RichTextBox” columns. If the file does not exist, a default encryption key is used.
  • ExecutionTimeout.txt – maximum request-processing time (in hours) used to extend the default limit of 5 hours, typically for long-running scripts. This influences the “executionTimeout” attribute in “Web.config”, which is updated automatically by “FinishUpdate.exe”.
  • Framework.txt – automatically generated file containing the detected .NET Framework version configured in the IIS application pool.
  • Framework4.txt – when this file exists, the update program “Update.exe” downloads NET Genium builds intended for .NET Framework version 4.
  • GoogleTranslationApiKey.txt – API key for Google Translation API used for translating texts in the “RichTextBox” and “TextArea” controls with the “Wiki” or “Markdown” data type in an edit form, in the preview window of the “RichTextBox” control, and in the “Details” panel of a datagrid. If the file does not exist, the translation icon is not displayed at all.
  • GoogleTranslationLanguages.txt – semicolon-separated list of two-letter language codes offered for translating texts. If the file does not exist, all languages installed in NET Genium are offered.
  • Holidays.txt – condition used to filter public-holiday records loaded into date pickers and into functions such as “ADDWORKDAYS”, “MEASUREWORKDAYS”, “MEASUREWORKHOURS”, or “jsMeasureWorkDays”. Example: “ng_country = 'USERDETAILS(ng_countryforholidays)'”
  • License.txt – NET Genium license key.
  • LoginByIdentity.txt – the presence of this file ensures that the NET Genium login window includes a checkbox enabling automatic user login through Windows Integrated Authentication, without the need to manually enter a username and password.
    • For this purpose, the user must exist in Active Directory, and the user’s domain account name must be filled in within NET Genium in the users table (“susers”) in the “Windows account” column (“account”).
    • The automatic login process performs only authentication, while authorization is handled by NET Genium — each user has an assigned list of user groups to which the user belongs.
    • Along with creating the “LoginByIdentity.txt” file, it is necessary to configure the “LoginByIdentity.aspx” page in IIS so that it supports Windows Integrated Authentication; more details are provided in the separate guide [[installing-netgenium-web-server Installing NET Genium on the web server]].
  • LoginByMicrosoft.txt – the presence of this file ensures that the NET Genium login window includes a checkbox enabling automatic user login through Microsoft Integrated Authentication, without the need to manually enter a username and password. For this purpose, the user must exist in Azure Active Directory (Microsoft Entra ID), and the user’s email address must be filled in within NET Genium in the users table (“susers”) in the “E-mail” column (“email”). The automatic login process performs only user authentication, while authorization is handled by NET Genium — each user has an assigned list of user groups to which they belong. Along with creating the “LoginByMicrosoft.txt” file, NET Genium must be configured in the portal at “https://portal.azure.com”; more details are provided in the separate guide [[configuring-user-login-via-ms-entra Configuring user login via MS Entra]].
  • MaxRequestCount.txt – maximum number of requests per second from a single user and IP address. Increasing the default limit of 100 is relevant for anonymous web forms where all visitors share a single anonymous session.
  • MaxRequestLength.txt – maximum request size (in MB) used to increase the default limit of 50 MB, typically required for uploading large files using “File” and “Image” controls. This affects “maxRequestLength” and “maxAllowedContentLength” in “Web.config”, set by “FinishUpdate.exe”.
  • MaxSyncCount.txt – maximum number of records for one-time synchronization of all data in an edit form database table, used to increase the default limit of 10,000 records. A detailed description of one-time synchronization is provided in the separate guide [[edit-form Edit form]].
  • MetaTags.txt – list of HTML tags inserted into every edit form inside the <head> section.
  • NoFrames.txt – when this file exists, NET Genium runs in frameless mode — the header and navigation area become part of each page’s HTML.
  • NoScript.txt – text message inserted inside <noscript> in every edit form, displayed to users with JavaScript disabled. Example:
    “Dear users,
    Your browser unfortunately does not support JavaScript, which is required to display these pages correctly.
    Please enable it.
    Thank you.”
  • OCRServer.txt – URL of a remote NET Genium instance providing OCR services used with the “#ocrserver#” variable and functions “OCR2TEXT” or “OCR2FILE”.
  • ResponseHeaders.txt – list of HTTP headers (one per line, format “key: value”) added automatically to every response.
  • SecureCookies.txt – when this file exists, every cookie is assigned the “Secure” attribute. Use this only when SSL termination happens on a firewall (e.g., F5). When SSL is terminated in IIS, this file is not needed.
  • SessionTimeout.txt – session timeout in minutes after which inactive users are automatically logged out (default 480 minutes); it takes effect only after an update of NET Genium rewrites the “Web.config” file.
  • SingleLogin.txt – when this file exists, a user may have only one active session; older sessions are automatically logged out.
  • SimpleClick.txt – when this file exists, records in view tables open with a single click instead of the default double click.
  • SSL.txt – when this file exists, all HTTP requests are automatically redirected to HTTPS. The file may optionally contain a custom redirect URL.
  • SysLog.txt – IP addresses of SysLog servers (separated by semicolons) to which all log messages will be sent.
  • Tester.txt – when this file exists, “Update.exe” downloads testing versions of NET Genium intended for partners and developers. These versions may contain bugs or be unstable. See the [[#logging Logging]] chapter.
  • UnderConstruction.txt – when this file exists, the web application becomes unavailable, and all requests are redirected to “UnderConstruction.aspx”. The file may optionally contain a custom message.
  • UnderConstruction2.txt – similar to the above, but only users with administrator rights can log in; all other users, including those already logged in, are redirected to “UnderConstruction2.aspx”. A custom message may be included.
  • Version.txt – the current version number of NET Genium.
  • XFrameOptions.txt – value of the “X-Frame-Options” header inserted into every response. This header controls whether pages may be displayed in frames. Setting “*” allows framing from external domains.

5. File attachments

  • File attachments are stored on disk in the “Files” directory. Each file attachment has its original filename stored in the database in the “sfiles” table, while the actual file on disk is saved under a modified filename. The filename on disk (without extension) is defined as the ID of the file - attachment record in the “sfiles” table, and the file extension is preserved. For example, the first file attachment stored in NET Genium may appear as “1.pdf”.
  • File attachments are created by uploading a file using the “File” or “Image” controls in an edit form, by creating a file attachment through a server function in a script, and similar mechanisms.
  • The file-attachments directory can be redirected to a different location on disk using a configuration file named “Files” (without extension), which is stored directly inside the “Files” directory in the same way as other file attachments. The content of the “Files” configuration file defines the disk path to the alternative directory where file attachments should be stored.

[[Kotva:logging]]

6. Logging

6.1. Incident logging

  • Incident logging is handled by two primary operations:
    • Saving log messages to files on disk in the “NETGenium\Logs” directory
    • Simultaneously sending the same log messages to a “SysLog” server

6.1.1. Log files

  • Log messages are stored in the “NETGenium\Logs” directory in the following files:
    • Auth-year-month.log – List of successful and unsuccessful logins and logouts
    • Download-year-month.log – List of downloaded files
    • Errors.log – List of errors that occurred during user activity
    • Export-year-month.log – List of user-exported data
    • FinishUpdate.log – List of errors that occurred during application updates
    • Fulltext-year-month.log – List of errors during full-text searching of file attachments
    • ResendEmlFiles-year-month.log – List of SMTP communication commands executed when attempting to resend email messages queued on disk (in the “NETGenium\SMTP” directory)
    • RunScript-year-month.log – List of scripts executed through the “RunScript.exe” application
    • Scripts60sec-year-month.log – List of scripts that ran for more than 60 seconds
    • SMTP-year-month.log – List of successfully and unsuccessfully sent emails
    • System.log – List of informational messages related to application startup (often associated with application-pool starts or restarts)
    • Version.log – List of database - structure changes related to new application versions
    • Warnings.log – List of warnings
  • The log-file directory can be redirected to another location on disk using a configuration file named “Logs” (without extension), which is stored directly inside the directory of the same name, in the same way as other log files. The content of the “Logs” file defines the disk path to the alternative directory where log files should be stored.

6.1.2. SysLog

  • Sending log messages can be configured for multiple SysLog servers simultaneously. The configuration is done using the “SysLog.txt” file located in the “NETGenium\Config” directory.
  • If the “SysLog.txt” configuration file exists and contains one SysLog server IP address or several SysLog server IP addresses separated by semicolons, all log messages will be automatically sent to the specified SysLog servers and stored in the “NETGenium\Logs” directory.
  • If the “SysLog.txt” configuration file is not present, logging is performed only into the files located in the “NETGenium\Logs” directory.
  • Messages sent to a SysLog server use the following format, with space as the separator between values: “date time server_domain_name application category event_type user_login_name user_ip_address message”
    • Category – Auth, Download, Errors, etc.
    • Event type – VERBOSE, NOTICE, WARNING, ERROR, FATAL

6.2. Web application performance logging

  • NET Genium logs the following events into the database:
    • Loading speed of edit forms – into the database table “stables_stats”
    • Loading speed of view pages – into the database table “sviewpages_stats”
    • Database query performance – into the database table “squerybuilder_stats”
    • External function performance – into the database table “sngef_stats”
    • Script performance – into the database table “sngscript_stats”
  • Enabling or disabling logging is done in a dedicated dialog under “Modify NET Genium” on the “Other” tab:
    • Off – logging is turned off
    • To database – logging is performed only into the database
    • To disk – logging is performed only to disk in the “Logs” directory
    • To database and disk – logging is performed both into the database and to disk in the “Logs” directory
  • Aggregated statistics generated from database-logged events can be viewed using reports. More details are provided in the separate guide [[reports Reports]].
  • The log tables keep growing until old records are deleted from them. The deletion is performed by the “SqlBackup.exe” program run with the “/deletelogs” parameter – for regular cleanup as a scheduled Windows task, see the [[utilities Utilities]] guide. In addition, the “BackupServer.exe” program deletes records older than 1 month before backing up each database, see the [[server-backup-and-restore Server backup and restore]] guide.