Low Code configuration
By configuring your Low Code, you define the logical data structure and its representation. This page focuses on the most important aspects of the configuration process. If you wish to learn more about a specific topic, refer to the subsections under .
Namespaces
Before we can configure anything, we need to create a new namespace.
A namespace encapsulates all of the data that is specific to some area (such as a CRM). The namespace also defines how the data is structured, any relations between the data, and how the data is displayed.
|
A namespace can not directly access data from another namespace. If this is needed, consider implementing this using workflows or automation scripts. |
-
navigate to the Corteza Low Code,
-
click on the Create namespace button at the bottom of the page,
-
provide all the requested data,
-
press the Save or the Save and close button.
When you enter the newly created namespace, you will see that there is nothing there. Let us change this.
Modules
We now need to create a few modules to define the data’s shape and any relations (for example, a contact is related to an account). A module consists of two parts; the module itself and a series of module fields.
|
Think of this as a table in a relational database. |
Enter the subpage and click on the New Module button.
Define the name and the handle for the module. The handle defines a unique identifier that you can use instead of the system generated ID. We recommend you define a handle for all modules as it simplifies any automation.
Next, you need to define a set of module fields. Click on the + Add new field button on the bottom of the page to add a new field. A module field is fairly complicated, so let’s break it down:
A field name defines how the system stores the corresponding value internally. Module field names are mostly used within automation scripts and workflows, so we recommend that a field name is short, descriptive and consistent. Use the value of the name field when accessing records of the The name field must:
|
|||
A field title defines how the field is shown to the user. You can write field titles in any format and any language; they do not affect the internals. We recommend that the title is short, descriptive and consistent with the handle. If a title is not provided, the name is displayed instead. A title is limited to 64 characters; no other constraints apply. |
|||
A field type defines what type of data the field will contain.
For example, if we wish to store the users' email, the field type will be Refer to the Module field types section for more details regarding field types. |
|||
The base field settings control the general behaviour of the module field. You can view base field settings directly under the "Attributes" column of the module field list.
|
|||
Type-specific field setting control the behavior of the module field based on the field type. To access type-specific settings, click on the settings icon next to the field type and navigate to the second tab (the one with the same name as the field type). |
|||
A field expression allows you to implement a formula (calculated) field. When you define an expression, you can no longer directly manipulate the field; the value only changes when the expressions' result changes. Click on the settings icon next to the field type and navigate to the "General" tab. Check the "Field value expression" checkbox and insert the formula into the new input box. Refer to the Field expressions for more details. |
|||
Custom field validation allows you to implement custom user-provided value validation and sanitisation. Click on the settings icon next to the field type and navigate to the "Validation" tab. You will see two sections:
Refer to the Field expressions for more details. |
Pages
The next step is to define how the data is displayed. To do this, we need to define some pages. There are two types of pages:
- Record pages
-
A record page allows you to define how your users will interact with the given module. The record page is used when you want to create or edit records. A record page is created directly from the module list by clicking on the Create record page or on the Page builder if the record page already exists.
|
If a module does not have a record page defined, you are unable to create or update its records through the user interface. Workflows and automation scripts can still interact with such modules. |
- List pages
-
A list page allows you to display aggregated data from different sources (e.g. modules and external websites). You can use list pages to implement simple record lists for a single module or a complex dashboard showing multiple record lists and charts. A list page is created in the section.
Page builder
The page builder allows you to define your page’s shape using page blocks and an intuitive drag and drop interface. Refer to the Page block reference section for details regarding specific page blocks. Each page defines a grid of 12 columns that page blocks can populate.
To add a new page block, click on the + Add block button on the bottom of the page. A new popup opens up where you can select what page block you wish to use. Each page block has its specific purpose, from showing records to showing charts and attached files.
Existing page blocks can be edited, moved, resized, or removed.
Navigation
The navigation on the Corteza Low Code changes dynamically based on the defined pages, their visibility, and their hierarchy. We call this a page tree, and it’s accessible directly in the section.
You can easily change the order of the pages by dragging them around.
To create a subpage (a dropdown menu), nest the page by dropping it into another page.
Charts
The last major component of the Low Code configuration are charts. Charts allow you to visualise your data and create beautiful dashboards.
Go to the subsection, click on the New Chart button, and select one of the available categories (let’s start by making a generic chart)
Insert the initial parameters that define the chart; name, handle, and colour scheme. The rest of the configuration depends on the selected category and are discussed in the following sub-sections.
|
Ensure that the selected colour scheme provides enough colours for your dataset (the number of colours is written next to the colour scheme name). |
Generic chart configuration
-
bar chart,
-
line chart,
-
pie chart,
-
doughnut chart.
The chart module specifies the data source (the records) for the chart. |
|||
The filter allows you to filter over the data source to include only specific entries. For example, we wish to aggregate the leads that you created in the last month. The dropdown menu provides you with a selection of the most common filters. If you wish to write something completely custom, tick on the customise filter checkbox and write your filter. Refer to the QL reference for details regarding filter definition. |
|||
The y-axis section allows you to configure the axis’s position (left or right), the label, and min-max values. |
|||
The dimensions section allows you to specify what field will be used to plot the dimension; the x-axis.
You may only use "simple", single-value fields as dimension fields:
Field of type |
|||
The metric section allows you to specify what field will be used to determine each dimension’s value and how it will be plotted. You may only use numeric fields as dimension fields.
A special |
Funnel chart configuration
A funnel chart is constructed from a series of reports where each report may define its dimension and metric. This allows you to piece together reports from different modules, allowing you to visualise the data between multiple modules.
The report module specifies the data source (the records) for the given report. |
|
The filter allows you to filter over the data source to include only specific entries. For example, we wish only to use leads that are in a specific stage. The dropdown menu provides you with a selection of the most common filters. If you wish to write something completely custom, tick on the customise filter checkbox and write your filter. Refer to the QL reference for details regarding filter definition. |
|
The dimensions section allows you to specify what field will be used to plot the dimension. Only fields of type |
|
The metric section allows you to specify what field will be used to determine each dimension’s value. You may only use numeric fields as dimension fields.
A special |
Gauge chart configuration
The report module specifies the data source (the records) for the given report. |
|
The filter allows you to filter over the data source to include only specific entries. For example, we wish only to use leads that are in a specific stage. The dropdown menu provides you with a selection of the most common filters. If you wish to write something completely custom, tick on the customise filter checkbox and write your filter. Refer to the QL reference for details regarding filter definition. |
|
The dimensions section allows you to specify what field will be represented on the gauge.
Only fields of type Each dimension has a series of steps that can be added by clicking on the + Add button. Each step defines a label and the maximum value for the step. The colours are defined based on the colour scheme. |
|
The metric section allows you to specify how the value of the gauge is calculated. You may only use numeric fields as dimension fields.
A special |
Configuring permissions
Our flexible access control system (RBAC) allows you to allow or deny access to all resources except for records (we will add this in the future).
Namespaces
-
go to Corteza Low Code,
-
click on the Permissions button.
-
go to Corteza Low Code,
-
click on the edit icon button on the namespace,
-
click on the lock icon in the top right.
Modules and module fields
Enter the namespace you wish to manage.
-
go to ,
-
click on the Permissions button.
-
go to ,
-
click on the lock icon next to the module,
-
go to ,
-
click on a module to open the editor,
-
click on the lock icon next to the module field.