Page Properties | ||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||
Resources & Remarks
Modification History
|
...
In every property definition and every object type definition the id attribute is required. It is used to identify the object type or property. An ID is a string with a maximum of 63 characters and it must match the regular expression
([a...zA...-zA-Z][a...zA...Z0...-zA-Z0-9]*:)?[a...zA...-zA-Z][a...zA...Z0...-zA-Z0-9]*.
Type IDs are also used as the name of the type, e.g., in query operations. Hence, it is recommended to choose meaningful values for type IDs.
...
As of 2021 Winter, it is possible to use the -
character as an additional separator within prefixes for tenant-specific IDs if matching the following regular expression:
(([a...zA...-zA-Z][a...zA...Z0...9]*-)?([a...zA...Z][a...zA...Z0...9-zA-Z0-9-]*:))?[a...zA...-zA-Z][a...zA...Z0...-zA-Z0-9]*
An exception are column names in Table Property Definitions, where prefixes are prohibited as of version 2020 Winter.
...
Attribute | Type | Required | Description | ||||||
---|---|---|---|---|---|---|---|---|---|
id | String | yes | The type ID of the property. It uniquely identifies the property in the schema. | ||||||
localNamespace | URI | no | By using namespaces, it is possible to form groups of properties and object types. | ||||||
description | String | no | Describes the property. | ||||||
propertyType
| Enum | yes | Specifies the type of this property. The following types are supported:
| ||||||
cardinality
| Enum | yes | Defines whether the property can have a maximum of one or an arbitrary number of values. Possible values are single and multi. | ||||||
required | Boolean | yes | If true, the object must have at least one value of this property. If a property is required and has no This attribute can be overwritten in the property references of object type definitions. Hence, the same property can be required in one object type and not required in another object type. | ||||||
queryable
| Boolean | no | Specifies whether or not the property may appear in the WHERE clause of a query statement. Default is true. false is only allowed for table properties. | ||||||
classification | String | no | Declares the classifications this property belongs to. There is no validation or use in the system itself. For example, string properties can be classified as 'email' or 'url' and a client can use this classification to present the property's content in an appropriate manner. This tag can be used several times and the corresponding values are delivered in an array. Note: Make sure to validate the strings you set for the classification tags, so that your application will not fail if the string does not match the expected syntax. | ||||||
defaultValue | depending on thepropertyType | no | The value that the system sets for the property if no value is provided during object creation. If the |
...
As of version 2020 Winter, the column names specified via <id>examplecolumn</id>
must not contain a prefix. They have to follow the convention [a...zA...-zA-Z][a...zA...Z0...-zA-Z0-9]*. Otherwise, the schema containing the corresponding property definition will not pass the validation.
...
As of version 2021 Summer, yuuvis® Momentum offers a property type for the storage of structured data in JSON format. Thus, it is possible to store interleaved data structures in a queryable way without defining each single sub-property in the schema. An example definition is shown in the code block below. The schema validation checks if the ID follows the convention. Only the value single
is allowed as cardinality
.
...
There are different groups of object type definitions:
Info |
---|
In a schema, all object type definitions must appear in this order. First all document object type definitions, then all folder object type definitions and so on. |
...
Attribut | Type | Required | Description | ||
---|---|---|---|---|---|
contentStreamAllowed | Enum | yes | Specifies whether objects of this type must, must not, or may have content. Possible values are:
Note: The attribute is also available for secondary object type definitions. If a secondary object type with a specified | ||
secondaryObjectTypeId | String | no | References to secondary object types (if there are several secondary object types, they are listed one below the other). Determines which secondary object types an instance of this object type receives upon creation (
|
...
Attribute | Type | Required | Description | ||
---|---|---|---|---|---|
secondaryObjectTypeId | String | no | References to secondary object types (if there are several secondary object types, they are listed one below the other). Determines which secondary object types an instance of this object type receives upon creation (
|
...
Attribute | Type | Required | Description |
---|---|---|---|
| Enum | no | Can substantiate the For the final document, content will be For the final document, content will be Conflict situation leading to invalid documents: any combination of at least once
If |
...
The app schema endpoints are:
- POST /api/system/apps/{app}/schema - Introduces provided schema as app within tenant schema, overwrites previous app schema
- GET /api/system/apps/{app}/schema - Retrieves the specified app portion of the tenant schema
- POST /api/system/apps/{app}/schema/validate - Validates a schema based on app schema rules
When uploading an app schema, all properties that do not specify a prefix will have that prefix generated as app<app name> where <app name> is equal to the path parameter {app}.
...
- GET /api/admin/schema - Retrieve the tenant's schema
- POST /api/admin/schema - Update the tenant's schema
- POST /api/admin/schema/validate - Validate the tenant's schema
Each object type ID and property type ID has the prefix t
en
+ <tenant name>
. Thus, the same object type name can occur in multiple tenant schemata.
...
Info | |||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||||||||||||||||
Read on
|
...