CYPEX supports GIS (Geographical Information Systems) data. However, in order to use GIS data in CYPEX, there are some things which have to be taken into consideration.

Let’s take a look at a sample table:

cypex=# CREATE EXTENSION postgis;
CREATE EXTENSION
cypex=# CREATE TABLE t_area (
    id 		serial 	PRIMARY KEY,
        name 		text,
        g 		geometry
);
CREATE TABLE

The keys to GIS data are the “geometry” and “geography” columns. These aren’t directly visible in a web frontend. Let’s take a look at how default queries are generated:

• Ability to drag&drop query into the query group.

• Application creation: query selection tree and query description.

• Demo data for CYPEX trial version.

• Enable/disable autocomplete element via custom expression.

• Fix current_user and current_role functions to work also in old PostgreSQL versions.

A workflow is a good start if you want to build an application. However, sometimes it’s still necessary to add control elements. In this section, you’ll learn to add buttons and to write server side code to make your application even more powerful. Starting with v1.9.0 CYPEX offers an approach to create database functions directly within its interface. The REST API behind the scenes executes these functions, providing a unified experience for managing both data and logic.

• Upgrade PostgreSQL database & postgREST docker images to the latest version

• App description as translated markdown text

• Implement permission assignment on default queries

• Trial version for the demo purpose

• Groups for queries - Admin panel

• Application Extension: support company internal repository urls

• Admin Panel: Added filter by query type

• Autogenerate Input Fields for the Form Element

CYBERTEC provides a set of extensions which can be used to simplify the process of building applications. In this section you’ll learn which extensions exist and what they are capable of doing.

Purpose:

Store telegram posts

ER model:

Description:

The extension consists of just one table. The content of the message is stored in the “payload” column.