Documentation
Main site
Search…
⌃K
Links

Step 1. Features requesting

Step duration ~18 min

Step 1.1. Create an app and set up basic data structures

6:05
First of all, we create an app. System name shave to be unique, because it has the URL-address SYSNAME.directual.app
​Database is the 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
Some 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
Okay, we want to add objects (features) via a Form. First and foremost, we need to create an API-endpoint. We go to API section and there click [ + New API-endpoint ] and choose the data structure — features, set the API-endpoint name and description and click [ + New layer ]
Pat attention to the layer conditions on the user's session. Default one — id isNotNull means that API-endpoint is NOT a public one, user have to authorise to get access to the data via this endpoint. We do not recommend to remove this condition if only you don't plan to provide an access to your data publicly.
Configuring an API-endpoint
Next, let's create a Page in Web-page builder. Click [ + New web-page ] and fill the form and click [ Save ].
Let's at once turn on Signing In and Signing UP for our app. Click [ Web-portal settings ], choose Security tab and turn on these options:
Then, we are dragging-and-dropping the Form component to the page, choose the API-endpoint and set up the fields, like this:
We should:
  • Turn ON quick search option for Tags — that will ad a dropdown;
  • Hide user_id from the form;
  • Turn ON automatic filling of user_id;
  • Change the field order and turn on requirement (if needed).
Superb! The form has been sвуet up. Try it out!

Step 1.3. Process new requests

5:50
New feature requests or bug reports are the objects. If we want to process those objects, we need a scenario, with a real-time trigger.
Step
Description
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
—
Previous
Step 0. Thinking over an app architecture
Next
Step 2. Features approving
Last modified 1yr ago