definition of Model Data
Model Data step allows you to define where all the process data will be stored and any lookup tables.
The main process entity can be any name you like, it's not limited to the process itself.
an example of naming the process entity
The Data Modeller allows you to create child tables for all entities and the relationship is managed by the system. You don't have to worry about Id's or making sure the data is inserted or updated, it's all managed for you. When we look at the forms you will see how easy it is to actually create the user interface to edit the main and child items, without having to worry about any kind of relationship mechanism.
an example of creating child tables
There are items called parameter entities that are simple look-ups.
an example of entity values
One major advantage of these is that you can edit the values both in the modeller,
an example of editing values in the browser
and in the browser (client).
an example of managing system entities
If you use system entities, such as Users, these are also managed for you and you just have to apply the User Id, and everything is sorted out for you. You have full access to all the data within there, without having to worry where the data is and how it's stored.