Field Properties
When a field is selected, the Field properties panel to the
right provides more detail about the data being stored. You can enter a
Label (which will show in forms) or a Comment (which
can be viewed here). The Required flag makes a field mandatory
in forms. The Use predefined field flag is discussed more
below.
The pencil tool next to the Name allows you to
rename the field. The new name must be unique within this data setup
file or, more precisely, the name must be unique within the namespace
URI defined when creating the data setup file. After renaming a field,
all references to that field within the current file will also be
automatically updated to use the new name.
Note that in Tag, by convention, each data setup file corresponds to
exactly one namespace URI. However, that does not always have to be the
case. At the end of the day files do not matter, but namespace URIs do.
In fact, data setup instructions can be stored in a database or other
medium (not a file) and still work in exactly the same way, but they
always have to define a valid and unique namespace URI.
The intent with Tag is to keep all this as simple as possible, and add
more complexity only when necessary. If you need more flexibility than
is available now, please let
us know .
The above screenshot also shows how to select a form control for a data
field. The Form control dropdown list provides options for the
most common data types. Once a few more fields are added to the example,
and the correct form controls are selected, the form preview now looks
like this.
Dropdown lists are very useful, as they define a fixed set of values
for a data field. In forms, users can fill out the field with two clicks
and no chance of typos.
Create dropdown values by adding strings to a list, and reordering them
them as needed. The following values could be used for a "direction"
field.
In forms, these values populate dropdown lists as follows.