The Studio module creates metadata describing application entities and relationships between them.
For example, the Blog application consists of the Article, Category, Comment, and others classes.
The created entities are in a separate store. Export them to metadata/app folder to load into the application.
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 stored data.
For example, the Title attribute is of type String, the Content attribute is of type Text.
Attribute types Reference and Back reference define relationship between classes.
Link settings are on the Relation tab.
The Reference type stores the link directly in the class instance. For example, a comment has a link to the article it refers to.
The Back reference type retrieves the link data from the object of the referenced class.
For example, comments for an article are retrieved from a back reference, because each comment stores an article ID. The article itself does 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. A link to comments in an article is an examples of a multiple link.
The view overrides 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 the list.
The codename "create" is used to represent the object when it is created.
The codename "edit" is used to represent the object when editing.
The codename "eager" is used to represent the eager load object.
The Office module sidebar menu is created from the navigation section codenamed "main".