Step 1: Requesting Features

Step 1.1: Create an App and Configure Basic Data Structures

First, we create an app. The system name must be unique because it determines the URL address (SYSNAME.directual.app).

The Database is a fundamental part of any app. For our Development Pipeline app, we create the following data structures:

Features (system name Features), main system structure.

Additional directory data structures:

Tags (tags)

Type (type)

Request Status (req_status)

Development Status (dev_status)

Add Objects:

Step 1.2: Create a Request Form

Alright, to add objects (features) via a Form, the first step is to create an API endpoint. Head to the API section and click on [ + New API Endpoint ]. Choose the data structure - in this case, 'features.' Set the API endpoint name and description, then click on [ + New Layer ].

Next, let's create a page in the Web Page Builder. Click on [ + New Web Page ], complete the form, and then click [ Save ].

Let's enable both Sign-In and Sign-Up for our app. Click on [ Web Portal Settings ], go to the Security tab, and activate these options:

"Next, drag and drop the Form component onto the page, select the API endpoint, and configure the fields as follows:

Here are the steps you should follow:

1. Enable the quick search option for Tags, which will add a dropdown.

2. Hide the user_id field from the form.

3. Enable automatic filling of the user_id.

4. Rearrange the field order and activate requirements as needed.

Your form is now set up and ready to use. Give it a try!

Step 1.3: Process New Requests

New feature requests or bug reports are considered as objects. To handle these objects, we require a scenario with a real-time trigger.