Modeling the Data Structure¶
One of the first steps of creating an app is to define the data model.
We recommend you to start with an entity-relationship diagram, considering all the information you will need to store in your app.
For example, let’s think on a Procurement app. You can come out with a diagram like this:

You can implement the relationships among the tables:
items
would be atable
field in thepurchaseRequest
table.product
would be arelationship
field in theitems
table.quotes
would be atable
field in thepurchaseRequest
table.selectedQuote
would be arelationship
field in thepurchaseRequest
table.vendor
would be arelationship
field in thequotes
table.
After implementing the tables for storing the data, the next step would be:
define the processes to implement.
define the main table for each one of your processes.
This is covered in the process modeling documentation.