Page History

A drop-down list with a predefined and fixed set of possible values.

Note. The type in the database can also be numeric, in which case the entire set of values must be numeric

A drop-down list where you can enter arbitrary values. The logic is similar to the C format, but it allows you to manually fill the field with text if necessary. It is used if the full list of possible values is too large, but there are few most frequently used options (they are predefined)

A drop-down list with predefined values and option to generate events on saving. It is used if changes in key user parameters need to be logged in the database or “intercepted” by an event dispatcher/script. It is recommended to make this field mandatory.

Note. The event is generated if the given user was saved after changing the field, and the event is not generated when new users are currently created. The event that was edited is generated for the Access Manager module object. To see this event in the Event Viewer or use it in the Event Manager, add these events to the Access Manager object in the DDI file of the Access Manager module

{CCI%Descr1(EVENT1)|Descr2(EVENT2)|...||DescrN(EVENTN)}
Example: {CCI%Issued(CARD_ISSUED)|Lost(CARD_LOST)|Broken(CARD_BROKEN)}

A numeric field with increment/decrement and manual input option.

Note. If a numeric data type is selected for a field in the database, then it is necessary to take into account the minimum and maximum values in accordance with the ranges in the syntax

Example 1: {S%0}—range of values: min -2147483648, max 2147483647
Example 2: {S%100|999}—range of values: min 100, max 999

This format is internal and cannot be used to generate additional fields

Unique text with validation (checking for compliance with certain requirements) using a regular expression template. It is a convenient customization tool, but it requires technical knowledge in writing regular expressions. The text entered by the operator is checked against the template, and only if it matches the template—the field value can be changed. Also, when saving a user, the uniqueness of the entered value is checked: there cannot be two users with the same value for this field

{UT%pattern_base64}
Example:
{UT%XlvQkNCS0JXQmtCc0J3QntCg0KHQotCj0KVdXGR7M31b0JDQktCV0JrQnNCd0J7QoNCh0KLQo9ClXXsyfVxkezIsM30k}

The text packed in Base64 format contains the following template (for the English version of the product):
^[A-Z]\d{3}-\d{3}-\d{2}-\d{3}-\d$.
This template allows you to check the entry of a car license plate in the state of Florida:

• F031-469-45-999-5—matches the template,
• F 31-469 45-A99-5—does not match the template

Unique text. When saving a user, the uniqueness of the entered value is checked: there cannot be two users with the same value for this field. If another user tries to enter the same value into a field, a warning message is displayed that this value is already set for another user

Non-unique text that contains predefined values, with the option to add new values. It allows you to supplement the set of text values as necessary and re-select values from the list. It may have a fixed set of predefined values.

Note. Before you edit a field, you should collect all variants of the value of this field from all users, eliminate the duplicates and add values to the list of predefined values, if any. Therefore:

1) If you want to remove a certain cached value from this list, you need to clear or change it for all users who have this value set in their fields.

2) If you save a value with an error, it will be cached along with other values. That is, the options “bucket”, “buc ket”, “bUcket” or “buket” will end up in the cache and can appear in the list of available values

Text with limited length.

Note. It is necessary to make sure that the field type in the database does not exceed the allowed length. The example above requires TEXT or CHAR, 10 (or more)

An arbitrary readonly field. It is used, for example, to display data when importing users from an external system or if this field is filled in with a script when manual input by the operator is prohibited.

Note. This format is similar to the normal default test field, which is marked as "Read Only" in the Access Manager settings. The difference is that this field remains non-editable even if it is marked as editable. It also has a default value