a single form is a simple single form with values from a single set of values 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 multi form is like a list/tabular form, but it creates a single form to submit all list item forms at once; the field names in the resulting form have an appendage attached to make them unique according to the pattern used for the multi-service event handler that will call one service for each list element for list type and other multiple data/form types this is the name of the list in the context to iterate over 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 by name The form-title-area-style specifies the style to use in the header or title area for the form in a multi-form widget with all form fields rendered in one area. The form-widget-area-style specifies the style to use in the main or widget area for the form in a multi-form widget with all form fields rendered in one area. Target location for the [Previous] and [Next] buttons in a form with pagination. Accepts ${} notation. Target anchor for the [Previous] and [Next] buttons in a form with pagination. The name of the parameter that specifies the number of rows to display for each page in a list form with multiple pages. The default is VIEW_SIZE. Accepts ${} notation. The name of the parameter that specifies what the current page is in a list form with multiple pages. The default is VIEW_INDEX Accepts ${} notation. The total number of rows in the original list (used for pagination). If not specified, the size of the list will be used. Accepts ${} notation. Text to display for the [Previous] button in a form with pagination. Defaults to "Previous". Accepts ${} notation. Text to display for the [Next] button in a form with pagination. Defaults to "Next". Accepts ${} notation. CSS style to use for the [Previous] button in a form with pagination. Defaults to "buttontext". CSS style to use for the [Next] button in a form with pagination. Defaults to "buttontext". The odd-row-style specifies the style to use in the table content odd rows. The even-row-style specifies the style to use in the table content even rows. The header-row-style specifies the style to use in the header of table. The default-table-style specifies the style to use in the table. A unique name for this field. The name (or location) of the map that contains the data for this field in the form context. Used along with the field-name to look up the entity field definition for any information that might be helpful when rendering the form field. See the description of entity-name. Used along with the attribute-name to look up the service attribute definition for any information that might be helpful when rendering the form field. See the description of service-name. Defaults to the value of the name attribute; is used to specify the name of the entry in the map that contains the value to populate. Defaults to the value of the name attribute; is the name of the parameter to use for this field (the request parameter in a web application). The name of this field that will be shown to the user; can use the ${} and foo.bar (dot) syntax to insert values from the context for parameterization or internationalization. A link for this field in the header of a list form. Useful for sorting a list form by different columns. The CSS style for a header-link. The text to show on mouse over or help for more information; can use the ${} and foo.bar (dot) syntax to insert values from the context for parameterization or internationalization. The name of a style (like a CSS class) to apply to the area around the title of this field. The name of a style (like a CSS class) to apply to the area around the widget that the user will interact with for this field. The name of a style (like a CSS class) to apply to the title of this field. The name of a style (like a CSS class) to apply to the widget that the user will interact with for this field. The name of a style (like a CSS class) to apply to the tooltip of this field. For row oriented forms (single type) can specify that the field should be put a column other than the first; for column oriented forms (list type) specifies the row the field should be put in. 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. Used to specify a condition that must be true to use this field; the condition should be written using the Java syntax and can operate on values in the form context; if this is used the field will only be put on the field list, and not in the field map meaning that values for this field cannot be overridden. Used to specify javascript events that should be attached to fields. Used to specify javascript actions that should be run based on events. The name of a style (like a CSS class) to apply to the title of this field if required. Will default to form's default-required-field-style. If field is required, but required-field-style is empty, an '*' will be placed to the right of text, textarea and password fields. A special entry for date-time fields; may just have a default size text entry box and some sort of widget to make date entry/selection easier. Specifies the string to display, can use the ${} syntax to insert context values; if empty the value of the field will be printed for a default. Specifies the currency uom ID used to format context value, should generally use the ${} syntax to retrieve value. This is just like display but looks up a description using the Entity Engine; note that if also-hidden is true then it uses the key as the value, not the shown description. The key to mark as selected when there is no current entry value. If non-zero, a text field will conditionally show next to the select control to implement a crude "combo box". In order for this to work there must be a option in the select as: <option key="_OTHER_" description="Specify other"/> - with '_OTHER_' being required and any 'description' allowed. In order to use this feature, the javascript code contained in the file: images/webapp/images/combobox.js must be included in the page. The target location of the hyperlink; can use the ${} syntax to substitute values from the context. Specifies the string to display, can use the ${} syntax to insert context values; if empty the value of the field will be printed for a default. The name of a field whose value is passed in as a parameter to the lookup target form. Can be a comma separated list. This will enable the html editor on this text area from www.unverse.net (more info there), only one textarea can be used on one page In here you can specify which buttons you want to see and in which order separated by blanks. Available buttons are:formatblock fontname fontsize newline bold italic underline left center right number bullet indent outdent undo redo color hilite rule link image table clean html spellcheck |(separator) Default is that all buttons are shown entity-options will look up options for the field in the given entity The name of the field in the looked up entity that will be used for the key value; if empty defaults to the entry-name of the field this is in. Will be presented to the user with field values substituted using the ${} syntax. list-options will create options based on data in a list The name of the list to iterate through to get values. If specified the list entry will be placed in the local context, otherwise each list entry must be a Map that will be expanded into the local context. The value of the key-name will be the value passed to the server; this should be the full name of the location of the key value in the context, given the list-entry-name or expanded list-entry Map as the options you would most likely use. Will be presented to the user with field values substituted using the ${} syntax. What the user will see in the widget; defaults to the value of the key attribute. This can be "true", "false" or the name of a Map in the context to use as the source Map for the service context. Should resolve into a non-negative integer. Should resolve into a non-negative integer. Should resolve into a non-negative integer. Should resolve into a positive integer.