Verne Forms provide views into the business services and allow a user to create and edit information. Visually they are what the user sees on the screen when they start a business service.
In Verne a form relates to the static XML configuration that defines the data and structure that can be acted upon when performing a business service. These forms are what configurators compose.
The static form configuration is closely related to the service form, as it’s the static form configuration along with the static business service configuration the service form’s data structure is based on. This means the form is also closely related to the view tree, as the service form contains the structure to use when building out the view tree.
A form is defined using the following structure:
<serviceFormItems>
<record ...>
...
</record>
</serviceFormItems>serviceFormItems is the wrapper for holding one or more forms and can only be a child of a top-level configuration element. It can only contain exactly one of the following:
- record – contains the root record used as the domain tree root. This relates to the registry data being created or edited. In almost all cases a record is used as the form root element
- box – in rare cases the form doesn’t relate to any registry data/domain tree data, then a box can be used instead of a record. This would then require the configuration to handle any data retrieval used to populate the form
Service Form Items
Service form items is the umbrella term that relates to any element within form configuration.
Service form items are contained within the form’s root element which reflect the structures that may be available to a business service when it is being processed by Verne as the view tree and its view nodes.
Certain service form items can contain other service form items (which may in turn contain others, and so on and so on) which can result in complex, nested, hierarchical structures of elements to support numerous views.
