Form

A form allows the grouping of properties to be displayed in a specific part of the UI page. It displays a list of properties that allied together and offers a wide range of selections to organize the information on the page.

The form component has the following structure:

"form": {
{
	"form": {
		"collapsible": "true | false",
		"sections": [{
			"title": "boilerplatekey",
			"sub-section": [{
				"title": "boilerplatekey",
				"subSectionResource": {

					"listResource": "{the name of the list property that is displayed by the tab}"
				},
				"region": {},
				"table": {}
			}]
		}]
	}
}

UI Specifications

The form allows different presentation styles to display data on the UI page in an efficient manner. The form data can be categorized into multiple sections, and each section can collapse and expand by setting collapsible to true.

Each section is divided into multiple sub-sections. A section of region or table display setting is permitted for each subsection. In this manner, every sub-section can be configured based on the nature of the data. With the anchor menu (drop-down), users can swiftly switch between sections and subsections.

The sub-section shows data either as a region or table. For tabular representation, the application supports users to configure list properties having a maximum of 10 rows within the form. Any list attribute having more than 10 rows should be defined as Tab.

The sub-section is an independent unit and can display the data from:

  • A top-level object

  • Any list property linked to the top-level object

  • Any resource linked to the top-level object

Top-level

When subSectionResource is not specified, all the properties within the region or table are considered relative to the top level.

List Property Linked to the Top-level

The subSectionResource setting may specify the listResource that must be shown in the sub-section. When specified, the anchor point, all other properties within the other components region, and the table are defined relative to it. The listResource setting must specify the name of the list property directly accessible from the top-level resource (on which the Form is based).