Step 1: Requesting Features

Step duration ~18 min

Step 1.1: Create an App and Configure Basic Data Structures

6:05

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.

Field system name	Field name	Field type
id	id	default id field
title	Title	string
description	Description	markdown (string)
date_requested	Date requested	date
user_id	Who requested	link to App users (WebUser)
tags	Tags	arrayLink to Tags (tags)
request_status	Request status	link to Request status (req_status)
development_status	Development status	link to Development status (dev_status)
type	Type	link to Type (type)

Configuring data structure fields

Additional directory data structures:

Tags (tags)

Field system name	Field name	Field type
id	id	default id field

Type (type)

Field system name	Field name	Field type
id	id	default id field

Request Status (req_status)

Field system name	Field name	Field type
id	id	default id field

Development Status (dev_status)

Field system name	Field name	Field type
id	id	default id field

Add Objects:

Structure	Object IDs
Type	bug, feature
Development status	planned, under development, released
Request status	new, approved, declined
Tags	design, integrations, product, etc.

Step 1.2: Create a Request Form

5:29

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 ].

Pay attention to the layer conditions related to the user's session. The default condition, 'id isNotNull,' indicates that the API endpoint is not public. Users need to authorize themselves to access data via this endpoint. We do not recommend removing this condition unless you plan to make your data publicly accessible.

Configuring an API-endpoint

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

5:50

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

Step	Description	Coding mode
Edit object // Save the date	Saves to {{date_requested}} current time, using now expression	🟢ON
Edit object // Set the status to new	Saves to {{request_status}} string new	🔴OFF
Send email	Alerts admin that new request has been created. Integration with email has to be established	—