Global settings

This table shows the global settings of GT. Many properties relate to different limits, such as the number of possible portfolios per client. Changing the properties is reserved for the administrator.

Edit global settings

Only the administrator can edit these, and only the property value of the existing settings can be changed.

Properties and table columns

The properties are self-explanatory and are not explained further.

Special settings

The meaning of certain settings is described elsewhere in this document. Only those settings are mentioned here that are more extensive or are not explained elsewhere in this documentation.

Password setting (gt.password.regex.properties)

This property can be used to set a specific password strength for the user password. This setting has an expandable table row in the view, from which the current setting can be taken. A regular expression can be used to define a specific minimum requirement for a valid password. Here are some examples:

  • “^(?=.[A-Za-z])(?=.\d)[A-Za-z\d]{8,}$”: At least eight characters, at least one letter and one number.
  • “^(?=.[A-Za-z])(?=.\d)(?=.[@$!%#?&])[A-Za-z\d@$!%*#?&]{8,}$”: At least eight characters, at least one letter, one number and one special character.
  • “^(?=.[a-z])(?=.[A-Z])(?=.\d)(?=.[@$!%?&])[A-Za-z\d@$!%?&]{8,}$”: At least eight characters, at least one upper case letter, one lower case letter, one number and one special character.
  • “^(?=.[a-z])(?=.[A-Z])(?=.\d)(?=.[@$!%?&])[A-Za-z\d@$!%?&]{8,10}$”: At least eight and at most 10 characters, at least one uppercase letter, one lowercase letter, one number and one special character.

By default, the first example is set in GT. Users are not prompted to enter a new password.

Parameters for the password setting

The following parameters must be available for the password setting:

  • regex: Assign the regular expression here.
  • forceRegex: If a password no longer meets the requirements of the regular expression, the user can be forced to enter a new password that meets the requirements. If “forceRegex” is set to “true”, the dialog for changing the password is opened after logging in if the password strength is not met. After successfully entering the new password, the user must log in again. If “forceRegex” is set to “false”, the existing passwords are still accepted and the regular expression is only used when the password is changed.
  • de and en: GT currently supports these two languages. Therefore, a hint or error text must be available for the corresponding language and the regular expression. The user must be able to understand the requirements of the regular expression from this text.

Validation of input rules for global parameters

To prevent invalid entries, there is validation for some property values. This also serves as an indication of which input values are accepted.

Supported rules

RuleSyntaxDescriptionApplies to
minmin:NMinimum allowed valuepropertyInt
maxmax:NMaximum allowed valuepropertyInt
enumenum:N1,N2,N3,…Value must be one of the specified valuespropertyInt
patternpattern:REGEXValue must match the regex patternpropertyString

Syntax

Rules are separated by commas: rule1:value1,rule2:value2

Note: For enum, the values are also separated by commas, but the parser handles this correctly by only splitting at , when a rule name and : follow.

Examples

inputRuleDescriptionValid valuesInvalid values
min:1,max:99Value between 1 and 991, 50, 990, 100, -5
min:0,max:100Percentage value0, 50, 100-1, 101
enum:1,7,30,365Specific day intervals1, 7, 30, 3652, 14, 60
enum:0,1Boolean-like integer0, 12, -1
min:1At least 1 (no upper limit)1, 100, 99990, -1
max:10At most 10 (no lower limit)-5, 0, 1011, 100
pattern:^[A-Z]{2,3}$2-3 uppercase letters“CH”, “USD”“ch”, “EURO”
pattern:^[a-z0-9.]+$Lowercase letters, digits and dots“gt.test”“GT.Test”

Combined rules

Multiple rules can be combined:

inputRuleDescription
min:1,max:99Range validation
min:0,max:100,enum:0,25,50,75,100Range + specific allowed values (enum takes precedence)