Possible values for the different types of URLs of formcycle. The following are currently available:
/formcycle
.dataquery_db
instead.Default or predefined data types for input fields. The following are currently available:
22.05.1990
.james@john.org
or θσερ@εχαμπλε.ψομ
.3
, 0
, or -21
.127.0.0.1
or 10.42.42.13
.2,00
, -3,95
, 0,00
or 897345,38
.0.03
, -99.2
, or 42
.0234995483
or +49 351 4459654
.02349
. Does not check whether such a code is actually registered within Germany.0
, 3
, oder 123
.0,00
or 2,34
.0,00
, 0
, 3,4
, or 3
.hh:mm
, e.g. 22:05
or 03:42
.http://example.com
or https://www.james.org
.Represents all data types that are valid JSON.
Represents all arrays that are valid JSON arrays..
Represents all objects that are valid JSON objects.
Legacy model for the file store with all binary files from upload elements.
The key is the ID of the form element, e.g. xi-tf-1
.
Legacy model with saved data of form field and the meta data of the form field.
The key can be one of the following
_0
or _1
. Then the value is the corresponding value of the form field, which
could be a string, an array, an object etc., depending on the type of form element.Possible types for the saved data of a form field
Legacy model that represents the data entered into a form, including values from repeated form fields as well as images.
The key can be any of the following:
_dyn_size
, e.g.
tf1_dyn_size
. Then the value is an array with the repetition IDs, e.g. ["0", "1", "2"]
.xi-tf-1
. The the value is an object with the
meta data and values for each form field.Represents a single value or an array of such values.
Possible request types for forms that indicate how the form was opened. To access the request type of the currently opened form, use
XFC_METADATA.requestType
zugegriffen. Some of these options are only for internal use and should not be used.