logologo
Get Started
Guide
Development
Plugins
API
English
简体中文
Get Started
Guide
Development
Plugins
API
English
简体中文
logologo
Overview

Data sources

Data source manager
Main data source

External data sources (Databases)

Overview
External MySQL
External MariaDB
External PostgreSQL
External MSSQL
External Oracle
Main vs External Databases
REST API data source
KingbaseES data source

Collections

Overview
General collection
Inheritance collection
File collection
Tree collection
Calendar collection
Comment collection
Expression collection
SQL collection
View collection

Collection fields

Overview
Field Validation

Basic

Single text
Long text
Phone
Email
URL
Integer
Number
Percent
Password
Color
Icon

Choices

Checkbox
Select
Multiple select
Radio group
Checkbox group

Media

Markdown
Markdown (Vditor)
Rich text
Attachment (Relationship)
Attachment (URL)

Date & Time

Overview
Date & time (with timezone)
Date & time (without timezone)
Unix timestamp
Date (without time)
Time

Geometry

Point
Line
Circle
Polygon

Advanced

UUID
Nano ID
Sort
Formula
Sequence
JSON
Collection select
Encryption

System info

Created at
Updated at
Created by
Last updated by
Space
Table OID

Associations

Overview
One to one
One to many
Many to one
Many to many
Many to many (array)

Development

Overview
Previous PageComment collection
Next PageSQL collection

#Expression Collection

#Creating an "Expression" Template Collection

Before using dynamic expression operation nodes within a workflow, it's essential to first create an "Expression" template collection using the collection management tool. This collection serves as a repository for various expressions:

Creating an Expression Collection

#Entering Expression Data

Following this, you can set up a table block and input several formula entries into the template collection. Each row in the "Expression" template collection can be viewed as a calculation rule designed for a specific data model within the collection. You can use fields from the data models of various collections as variables, crafting unique expressions as calculation rules. Moreover, you can leverage different calculation engines as needed.

Entering Expression Data

Tip

Once the formulas are established, they need to be linked to the business data. Directly associating each row of business data with formula data can be tedious, so a common approach is to use a metadata collection, similar to a classification collection, to create a many-to-one (or one-to-one) relationship with the formula collection. Then, the business data is associated with the classified metadata in a many-to-one relationship. This approach allows you to simply specify the relevant classified metadata when creating business data, making it easy to locate and use the corresponding formula data through the established association path.

#Loading Relevant Data in the Workflow

As an example, consider creating a workflow triggered by a collection event. When an order is created, the trigger should preload the associated product data along with the product-related expression data:

Collection Event_Trigger Configuration