<--
<element name="events" type="F:EventsType" minOccurs="0"
maxOccurs="1">
<annotation>
<documentation>
Form-wide event handlers. This element is
deprecated since version 6.0 - use event
attributes instead.
</documentation>
</annotation>
</element>
-->
<--
<choice>
<element name="events" type="F:EventsType" minOccurs="0" maxOccurs="1">
<annotation>
<documentation>
Property holds an instance of the Events class which contains all available events. This element is deprecated since version 6.0 - use event attributes instead.
</documentation>
</annotation>
</element>
</choice>
-->
Control which allows selecting location coordinates. The defaultValue attribute can be set to "current" which indicates
that the control should attempt to automatically find and set the user's location when the form is loaded.
A DateTime control brings up a calendar or digital clock interface allowing the user to enter a time or date.
For DateTime controls, setting <pre> defaultValue="NOW"</pre> will pre-fill the control with the current time
or date.
A Dropdown control contains a list of options which appears when the control is tapped or clicked,
allowing the user to make a selection from a limited number of options
A Checkbox control changes binary state when tapped or clicked between checked and unchecked.
It is useful for allowing users to answer 'yes or no', 'true or false' questions.
A Masterdetail control contains detail pages, which can each contain a large quantity and variety of user
input gathered from multiple controls. The masterdetail enables users to view a summary of existing details,
create new details, and select and edit details.
A List View appears like a text field, but as the user inputs text, the List View locates and displays matching entries from
a resource list of possible entries, which can be selected to populate the field.
A page is a single section of the form containing meaningfully related controls.
Pages can be navigated between, displaying different groups of controls.
A Detail element is contained within a Master Detail,
and can contain a large quantity and variety of user
input gathered from multiple controls. Each detail
appears as a separate page which is displayed by
selecting the detail in the Master Detail control.
A JavaScript regular expression that will be used to validate the contents of the control.
If the pattern is mismatched, an error will be displayed: formatErrorText will be displayed if specified,
otherwise mandatoryText. If neither attribute is specified, a default will be displayed.
Called when the form is first displayed, after all the controls have been created by the system.
This allows specific initialisation code to be executed e.g. loading reference data, prior to initial validation of the form.
This event is fired on the form first, and subsequently on each individual control.
(Deprecated - use the <description> tag with bindings instead.)
Called by the system when it draws the list which is used to navigate the entries of a Master-Detail control.
Use this event if you need more control of what is displayed in this list, beyond the functionality provided by
the description's descriptionid element.
Called on the page to be presented (and its controls) when a new page is selected by the user, before the changing process commences.
Making the page visible or invisible during this handler can block or allow the page swap.
Called when the form engine has finished initialising and it is ready for user interaction.
This occurs after onInit and immediately after the form has been first validated.
This event is fired on the form first, and subsequently on each individual control.
Controls the output data format of the signature control.
image encodes the signature in PNG format (Larger data size).
svgbase64 is svg compressed as base64 (Smaller data size).
A datasource encapsulates a list of data that is
available in controls. The data may be specified inline,
by the options element, or loaded from a JSON, OData,
TSV or CSV resource file, using the resource and
dataFormat attributes. The datasource can be used by
controls to supply their options, for instance the
options in a Dropdown.
The XML Instance Representation table above shows the schema component's content as an XML instance.
The minimum and maximum occurrence of elements and attributes are provided in square brackets, e.g. [0..1].
Model group information are shown in gray, e.g. Start Choice ... End Choice.
For type derivations, the elements and attributes that have been added to or changed from the base type's content are shown in bold.
If an element/attribute has a fixed value, the fixed value is shown in green, e.g. country="Australia".
Otherwise, the type of the element/attribute is displayed.
If the element/attribute's type is in the schema, a link is provided to it.
For local simple type definitions, the constraints are displayed in angle brackets, e.g. <<pattern = [1-9][0-9]{3}>>.
If a local element/attribute has documentation, it will be displayed in a window that pops up when the question mark inside the attribute or next to the element is clicked, e.g. <postcode>.
Abstract(Applies to complex type definitions and element declarations). An abstract element or complex type cannot used to validate an element instance. If there is a reference to an abstract element, only element declarations that can substitute the abstract element can be used to validate the instance. For references to abstract type definitions, only derived types can be used.
Collapse Whitespace PolicyReplace tab, line feed, and carriage return characters with space character (Unicode character 32). Then, collapse contiguous sequences of space characters into single space character, and remove leading and trailing space characters.
Disallowed Substitutions(Applies to element declarations). If substitution is specified, then substitution group members cannot be used in place of the given element declaration to validate element instances. If derivation methods, e.g. extension, restriction, are specified, then the given element declaration will not validate element instances that have types derived from the element declaration's type using the specified derivation methods. Normally, element instances can override their declaration's type by specifying an xsi:type attribute.
Nillable(Applies to element declarations). If an element declaration is nillable, instances can use the xsi:nil attribute. The xsi:nil attribute is the boolean attribute, nil, from the http://www.w3.org/2001/XMLSchema-instance namespace. If an element instance has an xsi:nil attribute set to true, it can be left empty, even though its element declaration may have required content.
Prohibited Derivations(Applies to type definitions). Derivation methods that cannot be used to create sub-types from a given type definition.
Prohibited Substitutions(Applies to complex type definitions). Prevents sub-types that have been derived using the specified derivation methods from validating element instances in place of the given type definition.
Replace Whitespace PolicyReplace tab, line feed, and carriage return characters with space character (Unicode character 32).
Substitution GroupElements that are members of a substitution group can be used wherever the head element of the substitution group is referenced.
Substitution Group Exclusions(Applies to element declarations). Prohibits element declarations from nominating themselves as being able to substitute a given element declaration, if they have types that are derived from the original element's type using the specified derivation methods.
Target NamespaceThe target namespace identifies the namespace that components in this schema belongs to. If no target namespace is provided, then the schema components do not belong to any namespace.