Joget DX Preview Release Available for Download

Check out Joget DX, the next generation successor to Joget Workflow for faster, simpler digital transformation.

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Current »

Reserved IDs

 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

Figure 2: Create New Form - Advanced Options

NameDescription
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

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

DescriptionEntity description.
Duplicate form settings and elements fromWith the above information filled up, one can choose to clone the design from existing Form entity.

Table of Contents

  • No labels