Model Designer

The model designer is a core component of the Oinone platform, providing users with the ability to quickly design models through visual configuration. To meet the needs of users with different R & D backgrounds, the model designer supports switching between operation modes, including the no - code mode and the expert mode:

The no - code mode contains basic functions, is simple to operate, and easy to understand, making it suitable for non - R & D users.
The expert mode has more comprehensive functions, including all the functions in the no - code mode and additional extended functions, making it suitable for users with basic R & D knowledge.

Note

When switching to the "no - code mode", you cannot view or operate models, fields, data dictionaries, and data encodings designed with low - code.
When switching to the "expert mode", you can view all models, fields, data dictionaries, and data encodings.

The model designer also supports the management of both no - code models and low - code models.

Tip

Regardless of whether it is the no - code mode or the expert mode, models designed through no - code designers (such as the model designer and the interface designer) are called no - code models.
Models written through the low - code R & D framework or automatically generated by the system during no - code design are called low - code models.
Fields designed through no - code designers are called no - code fields.
Fields written through the low - code R & D framework or automatically generated by the system during no - code design are called low - code fields.

Note

You cannot create or modify low - code models and low - code fields in the model designer.
You can add fields to low - code models in the model designer, and the added fields are no - code fields.

The model designer consists of three parts: models, data dictionaries, and data encodings.

Model: In Oinone, everything starts from the model. A model is a carrier of data and behavior. It is a simplified representation of an entity that needs to be described in an application, using appropriate forms or rules to describe its main features.

Tip

A model consists of metadata, fields, data managers, and custom functions.

Data Dictionary: It is a collection of fixed dictionary items that can be used as multi - select or single - select options.
Data Encoding: When there are certain encoding rules for the field data in a model, you can design the data encoding in the data encoding section of the model designer.

The following will provide a detailed explanation of these three parts.