Overview
Entity field parameters
- Type
-
Possible value types:
| Type | Description | Examples — Empty value |
|---|---|---|
|
Identifier |
|
|
String |
|
|
Integer |
|
|
fractional number |
|
|
Date in RFC3339 |
|
|
JSON-object |
|
|
JSON-type array str |
|
|
JSON-type array int |
|
|
JSON-type array object |
|
|
JSON-type array <T> |
|
|
JSON-value (object, array, quoted string, number, null) |
|
|
Any value |
|
- Mention
-
Default values:
-
required– field is mandatory to be specified when creating a resource. -
generated– is generated by the system when the resource is created; in some cases it may be specified at creation, then the specified value is applied. -
empty– empty value of the corresponding type. -
str_empty– blank line.
-
Sections
Categories
Configuration structure - the value of the "content" field of the entity configurations.
Configuration categories are the root elements of the configuration structure.
Configuration can be generated immediately as a JSON-structure, or you can use the "Configuration Editor" application".
The articles listed below provide a description of the categories and examples of their values in a JSON structure.
Logical roles (A-Z)
Logical role - a service that implements some isolated functionality of the system. A role instance runs as an application in one of the nodes on one of the servers and has a unique name throughout the system. The role name begins with a lowercase Latin letter and may consist of Latin letters and numbers.