Further Explanation and Onboarding

Sign-In to our Free Trial and visit the Backend Graph in Generato. Click the the Show Backend Features Button in the Menu on top to run through our detailed Onboarding.

The Backend-Graph

As the first out of two layers, the Backend defines all the data of your project.
You can create entities and enumerations, specify their properties and define relationships between them. Every unit conceptualized on Generato's Backend-Graph will be transformed into your selection of templates.

By clicking on the buttons in the top left corner of the application, you can create new entities or enumerations.


Basically the entity is related to an independent existence of your solution-domain which can be uniquely identified. E.g. the "Passenger" that uses your App or the "Flight" that you'll observe within your "Space-Harbour-Onboarding"-System.
Creating new Entities by specifying its name and a description in the overview tab. 

In the next step you can add the properties to your entity. All entities will be created with an ID (which can't be changed) and a preset "Name" property by default. In order to add further properties, navigate to the Property tab, click on the Add Property button and new dialogue window will be triggered. You may also reorder the properties by dragging them around in their list. For each property you can specify its name, a description and its type. Overall, there are two types of properties: Data-Properties and Relations.

The "Standard" Properties can take the following form:

  • id
  • number
  • text
  • timestamp
  • yes-no
  • floating-number
  • long-text (soon)
  • file (soon)
  • geopoint (soon)
  • object (soon)
  • list (soon)
  • image (soon)


Relation-Types are differentiating in main-types and different cardinalities. On the one side, there are foreign relations which represent the classical ID-ForeignKey-Relation between two entities/classes. On the other side there are Embed-Relations. These represent object-references, which means the "child" will be documented in the "parent"-entity as a whole, which appears, for example in NoSQL-Databases with Collections, Documents and Sub-Documents/-Collections.

Root and Embedded

Depending on their relationship-environment Entities will be categorized into two Types. Root-Entities are Entities which are standing for their own, which means they are not embedded into other Entities. Embedded Entities are included into other Entities. You can see their status in the header of the entity detail window.

The related Cardinalities of the Relations are the following:  


  • ForeignKeyZeroOrOne - optional single foreign-key
  • ForeignKeyZeroToMany - mandatory single foreign-key
  • ForeignKeyOne - optional multiple foreign-key(s) 
  • ForeignKeyOneToMany - mandatory multiple foreign-key(s) 


  • EmbedZeroOrOne - optional single object 
  • EmbedZeroToMany - mandatory single object 
  • EmbedOne - optional multiple object(s)
  • EmbedOneToMany - mandatory multiple object(s) 

If a relation is created using the "Add Property > DataType: Relation" dialogue, the visual relationship (arrow) will be created automatically. In order for you to have a better user experience, we highly recommend creating relationships by using the drag and drop functionality.


Enumerations describe opinionated optionalities with different values (shapings). To create them just click on the New Enum Button on the top let corner to add a new Enum, enter your name and create the values. To connect them with the existing entities these relations will always be defined with the "Embed"-Relations.

Did this answer your question?