• option_<n>=<value>,<name> — List definition for the 'pulldown' field-type.
    Example:
    option_1=Fruit,Apple
    option_2=Vegetable,Broccoli
    The pulldown will display Apple and Broccoli, selecting Apple will return a value of 'Fruit' into the database.
  • option_default=<id> — Which option will be displayed by default.
  • REQVALTOLOG — Required value to login, set to a value that will be required to allow user to login.
  • required=y — the field cannot be left blank during registration.
  • readonly=y — the field is read-only.
  • monetIze=y — the field is converted to Currency or Money format when displayed or presented to users.
  • verifyDisabled=yes — the field will not be checked even if the field type requires it.
  • emailVerified=yes — the account will have the email verified field set as true technically enabling and activating the account.
  • session_ids=<list> — List of session Ids that will be accepted for this field. List of sessions here.
  • preset_key=y — the field will used as reference for retrieving preset information. This is used with third-party website sending pre-populated fields back to this website..
  • registerGroups=<list> — the list of groups that the user will become a member of upon registration.
    Example:
    registerGroups=5
    - Group ID can be viewed from AM::GM, click a group and the Group ID info will appear at the right panel.
  • forceCase=<value> — This option forces the data entered on this field to take the case indicated by the <value>.
    Valid values are UPPERCASE, LOWERCASE, UPPERCASEFIRST, and LOWERCASEFIRST.
    Example:
    forceCase=UPPERCASE
    - Data entered will be saved in upper case even if the data entered is lower case or mixed case.
  • copyField=<field name> — the value of the specified field name will be copied to this field. Make sure the specified field name is placed before this field to copy the value.
    Example:
    copyField=LOGIN
    - Data from field LOGIN will be copied to this field containing the copyField option.
  • copyBase=<base field name> — the value of this field will be copied to the base field specified by base field name.
    Example:
    copyBase=name
    - Data from this field will be copied to base field 'name'.
  • ref_field=<field name> — assign the specified field name as the reference pair field.
    Example:
    ref_field=UID
    - UID is the reference field if this field containing the option is a REFERRER ID type field.
  • job=<command> — The job that will be sent to PSM queue management. Format of command is:
    <job>,<field>::self
    Example: job=REG1,UID::self
    Where REG1 is the job name, list of jobs here.
    UID is the field name, list of fields here.
  • crrm=<command> — The task that will be sent to CRRM queue management. Format of command is:
    <crrm>,<cmd>:<val>
    Example: crrm=prod_id:1
    This will process a product purchase with ID 1
    CRRM Products can be found here.
  • uuid=<version> — The field auto-generate a UUID. The following versions are accepted:
    ver1 = Used for MAC Address and Timestamps
    ver3 = MD5 Hash and Namespace (better performance than ver5, best for large data)
    ver4 = Random
    ver5 = SHA1 and Namespace (better randomness than ver3, best for small data)
    See Universally unique identifier on Wikipedia for more details.
    NOTE: LOGIN and USER ID type fields cannot accomodate the uuid due to 16 character limitation to login names
    Examples:
    • uuid=ver1 — will produce UUID based on time.
    • uuid=ver3 — will produce MD5 Hashed UUID based Client ID affixed with UUID_Suffix.
    • uuid=ver4 — will produce random UUID.
    • uuid=ver5 — will produce SHA1 UUID based Client ID affixed with uuid_suffix.
  • uuid_suffix=<suffix> — Optional suffix used by uuid ver3 and ver5 to affix the Client ID as namespace. Example:
    uuid_suffix=88
    This will place 88 after the Client ID before passing into the UUID generator.