Form Types

Experience the ease and flexibility of creating a myriad of forms in various business context. Leverage the capabilities of creating Admin Form or Transaction Form specifically to meet the various requirements.

Form Designer empowers you to create a wide range of forms, classified as follows: 

1. Admin Form
   • Mandatory Forms
   • Non-Mandatory Forms
2. Transaction Form
   • Main Form
   • Sub Form
   • Popover Form

Admin Form

Admin forms are used to manage the master data and are accessible only to an Administrator. You can also group multiple Admin Forms under the same group based on the similar operations. The Admin Form can be configured as a mandatory or non-mandatory form based on the requirement. The Administrator can easily access a list of designed Admin Forms under Design Studio > Configurations. A sample screenshot is shown below:

Figure: Configurations

While configuring an Admin form, at least one field must be unique and mandatory. For Example - For an Admin Form such as Priority, let's say Priority field must be mandatory and unique. 

Admin Forms are further categorized into the following types:

• Mandatory Form
• Non-Mandatory Form

Mandatory Form

A mandatory Admin Form will be mandatory to configure to operate the respective module. For a module to be fully functional, the Application Administrator must complete the configuration of these forms. It provides the structured interface to configure the essential settings.

Enable the Mandatory Configuration under Form Type on the Form Designer details page to make an Admin Form as mandatory form. A sample screenshot is shown below:

Figure: Form Designer - Admin Form - Mandatory

Non-Mandatory Form

A non-mandatory Admin Form will be optional to configure for to operate the respective module. For a module to be functional, the non-mandatory Admin Form may or may not be configured. It provides the flexible interface to configure the additional customizable options. 

Do not enable the Mandatory Configuration under Form Type on Form Designer details page to make an Admin Form as non-mandatory form. A sample screenshot is shown below:

Figure: Form Designer - Admin Form - Non-Mandatory

Transaction Form

The transaction forms are primarily used to systematically capture and to process the data. These sorts of forms are consumed by End-User or Analyst to perform various operations effectively. These forms will be available on main menu bar independently or inter-dependently.

Transaction form is further categorized into the following three types:

• Main Form
• Sub Form
• Popover Form

Main Form

Main Forms are independent forms and will be available on the main menu to perform a task. It refers to the main screen of the application or dashboard, which functions as the primary interaction platform for the End User.
For Example: My Service Request

A sample screenshot is shown below:

Figure: Main Form - My Service Requests

Sub Form

A Sub Form is not an independent form and will be linked to the parent form (Main Form) to input or capture the additional information related to specific data or actions on the main form . The Sub Form is not visible directly on the main interface of the application. The End User has to navigate through Main Forms to access the Sub Forms.
For Example: My Service Requests - Shared Folder Access

A sample screenshot is shown below:

Figure: Sub Form - Shared Folder Access

Popover Form

A Popover Form is a transient view that displays on the parent form when a user clicks on any defined option or button. It stays on the screen until you close it. Popover allows the user to enter or to collect the information connected to the Main form. It appears on the same parent form and can be closed by clicking anywhere on the parent form. Popover Forms are used for mainly single-action user interactions like Submit, Delete, and so on.

For Example: Update Service Request

Figure: Popover Form - Actions Panel

Figure: Popover Form - Update Service Request

Let's explore the following use case.