| Warning |
|---|
|
Do not use the following reserved IDs as ID of Form, Section and Field. "appId, appVersion, version, userviewId, menuId, key, embed". |
Figure 1: Create New Form
...
| Name | Description |
|---|
| Form ID | Unique ID to represent this entity. | Info |
|---|
| 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 |
| Warning |
|---|
| 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. | Info |
|---|
| Leave Application Form |
|
| Table Name | Table name to store form data to. | Info |
|---|
| 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. |
...