The name of the entry in the context that contains the value to use for this field. By default will use the field name and look in the context and if not found in the context then in a map called "fieldValues" (ie: "fieldValues.${name}"). With this convention when you do an entity find to get a recard to edit, use "fieldValues" for the value-field.
hide
boolean
optional
If false field will always be visible (at least the title if nothing else). If true will always be hidden regardless of title and widgets defined. If empty (default) will guess based on definition of field. Note that for form-list fields this governs the entire column for the field, and not just a single row.
name
xs:string
required
A unique name for this field. Used for the parameter name, referencing the field in other places, etc.
Only applicable to fields until a form-list element. Used to show a field to filter the results by (instead of a separate search form), and/or to show the order-by option in the header.
The widget/interaction part will be red if the date value is before-now (for thruDate), after-now (for fromDate), or by-name (if the field's name or entry-name or fromDate or thruDate the corresponding action will be done); only applicable when the field is a timestamp.
title
xs:string
optional
The name of this field that will be shown to the user; can use the ${} and map.key (dot) syntax to insert values from the context.
tooltip
xs:string
optional
The text to show on mouse over or help for more information; can use the ${} and map.key (dot) syntax to insert values from the context.
The widget/interaction part will be red if the date value is before-now (for thruDate), after-now (for fromDate), or by-name (if the field's name or entry-name or fromDate or thruDate the corresponding action will be done); only applicable when the field is a timestamp.
title
xs:string
optional
The name of this field that will be shown to the user; can use the ${} and map.key (dot) syntax to insert values from the context.
tooltip
xs:string
optional
The text to show on mouse over or help for more information; can use the ${} and map.key (dot) syntax to insert values from the context.
Fields in the field-row will be "floated" left so that they stack up on a single line as long as them will fit, and then will overflow to the next line, etc.
A list form is a list of individual forms in a table (could be called a tabular form), it has a list of sets of values and creates one form for each list element. A variation on the list form is the multi form (set the attribute multi=true). In the multi mode all list elements will be put into a single large form with suffixes on each field for each row, with a single submit button at the bottom instead of a submit button on each row.
The location and name (separated by a hash/pound sign) of the form to extend. If there is no location is a form in the current screen.
list
xs:string
optional
The name of the list in the context to iterate over.
list-entry
xs:string
optional
If specified each list entry will be put in the context with this name; otherwise the list entry must be a Map and the entries in the Map will be put into the context root directly.
multi
boolean
true
optional
name
xs:string
required
paginate
xs:string
true
optional
Indicate if this form should paginate or not. Defaults to true.
If true text will be encoded so that it does not interfere with markup of the target output. For example, if output is HTML then data presented will be HTML encoded so that all HTML-specific characters are escaped.
The text representing the key. Use the ${} syntax to insert entries from a Map in the list or from the context. If empty and the List contains EntityValue instances then will use the first primary key field name to lookup a value in the context, otherwise will use the name of the field to lookup a value in the context.
list
xs:string
required
The name of the list to iterate through to get values.
text
xs:string
optional
Actual text shown to the user. Use the ${} syntax to insert entries from a Map in the list or from the context. If empty defaults to the value of the key.
This is just like display but looks up a description using the Entity Facade; note that if also-hidden is true then it uses the key as the value, not the shown description.
Attributes
QName
Type
Fixed
Default
Use
Annotation
also-hidden
boolean
true
optional
encode
boolean
true
optional
If true text will be encoded so that it does not interfere with markup of the target output.