(v12.0.8874.35714 started 2024-04-18 18:00:37 on VM2)
Updating the Groups Table via web interface:
To enable the web interface the keyword GRPUPD must be defined at the corresponding manage or status routing entry. New groups can be created using the link New Group Existing groups can be updated, renamed or deleted using the links provided in the ID field of the Groups list.
To upload and load a completely new groups table via web, click here.
Notes for update via status links: - Only update of existing groups is allowed. The comment and eMail fields are not allowed to be updated. - The user must be logged on or identified via a client certificate (keyword CCR). - Hint: *@* in SourceIP of the routing table forces logon checking. - The email address of the user must match the email address in the field eMail (groups and wildcards are supported). - In the Groups list the links for update are shown dependent on the privilege of the user.
Keyword MCHK:list ... within the comment field of the group (optional): to check email syntax during web update or creation of groups - list is a list of allowed emails with wildcards separated by |, e.g. MCHK:*@x.com|*abc*@y.com - If MCHK:* is specified, all emails are allowed if the email syntax is correct. - If the entered email contains *, the general syntax check is disabled but the checks against the list will be done. - The keyword is ignored for all special groups such as StyleColors and groups where the name starts with "A_", "B_", "H_", "P_" or "X_".
Notes: - The original group table file will be backed up (with timestamp within the file name). - After the update the group table file will be written. - The field lengths (column widths) are derived from the header line of the group tabe. - Comments are accumulated in the first line of a group entry. - The special groups License, Notify and Title are stored at the top, all other groups are stored in ascending order. - Any comment lines (lines starting with #) or empty lines are removed. - Simultaneous access to the groups table via web interface and by any editor should be avoided to prohibit access conflicts.
