Page Properties |
---|
|
Product Version |
|
---|
Report Note | presentable, review (move stuff into tutorials) |
---|
Assignee |
|
---|
Resources & Remarks - There is already good text available in the tutorial section - it needs to be split into concept article and tutorial.
- The app schemata article, originally located in the Tutorials section, has been moved into this article. The REST endpoint overview around the application schemata topic should probably be moved back into the tutorials and linked here.
- v2.2 - Inga: "floating" secondary object type infos added
- Antje: add Content Stream Properties as a new section in the hidden part.
- Antje: move Content Stream Properties to the public section "System Properties"
- Antje: contentStreamAllowed attribute added for SOTs
Modification History Name | Date | Product Version | Action |
---|
Antje | 08 FEB 2021 | 2020 Winter | New page properties macro. | Agnieszka | 02 JUNE 2021 | 2021 Summer | rLANG (partial) |
|
...
Attribute | Type | Required | Description |
---|
seconaryObjectTypeIdsecondaryObjectTypeId | 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 (static="true" ) or can be added at runtime (static="false" ). >> Secondary Object Type Definition Info |
---|
In contrast to the CMIS specification (Content Management Interoperability Services), in which the secondary object types can be determined freely for each object instance, the schema specifies which secondary object types an object instance must have. |
|
...
Attribute | Type | Required | Description |
---|
contentStreamAllowed (As of product version 2020 Autumn)
| Enum | no | Can substantiate the contentStreamAllowed attribute of document type definitions. Possible values are analogous to document object type definitions: required , notallowed , allowed . For the final document, content will be allowed if only allowed values occur in the document type definition and included secondary object type definitions for this attribute. For the final document, content will be required (notallowed ) if the value is required (notallowed ) in at least one object type definition – either document type definition or included secondary object type definition. Conflict situation leading to invalid documents: any combination of at least once required and at least once notallowed in included secondary object type definitions or the document object type definition itself. - If the conflict occurs between the document object type definition and a secondary object type definition, the whole schema is invalid.
- If the conflict occurs between secondary object type definitions with at least one of them referenced as static, the schema is valid but the document validation will fail (instantiated documents will be invalid).
If the conflict occurs exclusively between secondary object type definitions referenced as floating, a document cannot have conflicting secondary object types at the same time. If a secondary object type with the value required (notallowed) is added to the document, all secondary object types with the value notallowed (required) must be removed by means of the keyword "remove": .
If contentStreamAllowed is specified in a secondary object type definition, this secondary object type cannot be referenced in folder object type definitions. The schema would be invalid. |
...
The app schema endpoints are:
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}.
...
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
Section |
---|
Column |
---|
| Insert excerpt |
---|
| Managing the Schema |
---|
| Managing the Schema |
---|
nopanel | true |
---|
| Keep reading
|
Column |
---|
| Insert excerpt |
---|
| Importing Documents via Core API |
---|
| Importing Documents via Core API |
---|
nopanel | true |
---|
| Keep reading
|
Column |
---|
| Insert excerpt |
---|
| Changing Schema Structures ("Schema Flow") |
---|
| Changing Schema Structures ("Schema Flow") |
---|
nopanel | true |
---|
| Keep reading
|
|
|
...