Figure 1: Create New Form
Figure 2: Create New Form - Advanced Options
Name | Description |
---|---|
Form ID | Unique ID to represent this entity. Naming convention A standard naming convention is highly recommended to be used across the development of your App to maintain consistency and ease maintenance works. Camel case naming convention is recommended for this field. Example: leaveApplicationForm Reserved IDs Do not use the following reserved IDs as ID of Form, Section and Field. "appId, appVersion, version, userviewId, menuId, key, embed". |
Form Name | Name to represent this entity. Example Leave Application Form |
Table Name | Table name to store form data to. Naming convention As the table name is related to the database, we highly recommend the use of database naming conventions, e.g. leave_applications |
Description | Entity description. |
Duplicate form settings and elements from | With the above information filled up, one can choose to clone the design from existing Form entity. |
Table of Contents
- Form Builder
- Form Element
- Hidden Field
- Text Field
- Password Field
- Text Area
- Select Box
- Check Box
- Radio
- Date Picker
- File Upload
- Subform
- Grid
- Custom HTML
- ID Generator Field
- Multi Paged Form
- Multi Select Box
- Popup Select Box
- Calculation Field
- Signature
- Time Picker
- AJAX Subform
- Image Upload
- Rich Text Editor
- Advanced Grid
- Form Grid
- List Grid
- Section
- Form Column
- Captcha
- Form Validator
- Form Binder
- Form Options Binder
- Form Properties
- Generate App
- Form Element