Exploring form design perspective The gadget spec URL could not be found
At this point, you have deployed the template application, explored the application and reviewed its data model implementation. In this section, we will explore the form design perspective by reviewing the form design implementation of the template application.
|

|
Creating/deleting forms
|
|
"New", "Delete" and "MakeDefault" option can be used to create a new form, delete a form and set a form as the default form respectively.
|
|
|
|
"Layout" and "preview" tabs can be used to toggle between form design and form preview.
|
|
|
|
Each form is displayed in a separate tab, just as worksheets are displayed in an Excel. |
|
|
|
Designing page layouts
|
|
|
|
"Insert" and "Delete" options can be used to work (insert/delete) with rows, columns and grids.
|
|
|
|
"Cell Styles" can be used to apply styles to a cell/row; "Alignment" options can be used to position contents in a cell.
|
|
|
|
How to define styles?
How do I apply those styles in forms?
|
|
|
|
Click here to learn more.
|
|
|
|
"Clipboard" options can be used to copy and paste a cell contents. Grids can also be copied.
|
|
|
|
|
|
|
|
Form fields and validations
|
|
|
|
"Named Cell" widget displays the list of public cells in the current data model and controls to add check box, radio button, label, text box, text area and combo box. The controls available for a cell depends on the format and type of a cell.
Check box/radio button is available for cells that has boolean format.
Combo box is available for cells which has reference look-up connection or which uses static list. E.g. "Sex" public cell.
Only labels are available for cells with formula or functions defined in the public cell. E.g. "FullName" public cell.
How do I add form fields in the form?
Select a cell and click on the controls in the "Named Cell" widget to add controls (Input fields) in the form.
|
|
|
|
"Validation" option can be used to add validations to be performed on form input fields. In addition, this option can also be used to define informational messages, warning messages and error messages.
|
|
|
|
Click here to learn more.
|
|
|
|
Specifying permissions
|
|
|
|
"Permission" can be used to configure visibility, editability, authorization at granular field level for the forms depending on the workflow activities, user and data model references.
|
|
|
|
Click here to learn more.
|
|
|
|
Adding buttons to forms
|
|
|
|
"Actions" widget displays the list of available actions that can be added to the form as buttons.
|
|
|
|
What are these actions?
Do we have to create them?
|
|
|
|
Click here to learn more.
|
|
|
|
"Save", "Cancel", "Delete", "Activate" and "Deactivate" buttons have been added to the customer form using the actions widget.
|
|
|
|
|
|
|
|
Parent-child forms, Reusing forms
|
|
|
|
"One-Many" widget can be used to add child model fields in the forms. Thus, a single form can be used to maintain data in both the parent and child models. E.g. Customer details and customer address can be maintained using a single customer form.
|
|
|
|
Customer address model fields have been inserted in the customer form using the "One-Many" widget.
|
|
|
|
"Many-One" widget can be used to add parent model fields in the forms.
"Forms" widget can be used to include other forms in the current model.
|
|
|
|
|
|