The application works in demo mode. Data change is blocked.

Create app metadata

The Studio module creates metadata describing domain entities and relationships between them.
For example, the Blog app consists of the Article, Category, Comment, and others classes.

The created entities are located in a separate store. Export them to your app metadata folder to start using.

Class attribute

Class attribute describes a single class element.
For example, the Article class consists of the Title, Content, Date and other attributes.

Each attribute has a specific type depending on the stored data.
For example, the Title attribute is of type String, the Content attribute is of type Text.

Class relation

The Reference and Back Reference attribute types define the relationship between classes. Link settings are located on the Relation tab.
The Reference type keeps a link directly in an instance of the class. For example, a comment has a link to the article it refers to.

The Back Reference type retrieves the link data from the referenced class object.
For example, comments on an article are retrieved from the back reference, because each comment stores an article ID. Articles do not store any data about comments.

The linking can be multiple or single.
An article link in a comment is an example of a single link. Linking to comments in an article is an example of a multiple link.

Class view

Views override class parameters for specific use cases.
For example, when displaying objects in a list, only selected attributes can be shown.

The codename "list" is used to represent objects in a list.
The codename "create" is used to represent an object when it is created.
The codename "edit" is used to represent an object when edited.
The codename "eager" is used to represent an object when eagerly loaded.


The Office module sidebar menu is created from the navigation section codenamed "main".