Joget DX 8 Stable Released
The stable release for Joget DX 8 is now available, with a focus on UX and Governance.
Previous step
Make sure that you have first completed the previous tutorial - Designing a New App
Key in the details of the new form.
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: travelRequestForm 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 Travel Request Form |
Table Name | The database table name to store the form data. Naming convention As the table name is related to the database, we highly recommend the use of database naming conventions, e.g. travel_requests Note that different forms can share data by pointing to the same table name. |
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. |