best practice
While extending your application and adding entities, attributes and associations you get to the point where you have to generate objects or associations to have a consistent data model and data. Here’s an example:
A lot of AppStore modules, and probably your own modules too, require configuration to run properly in your application. A simple example is the AppStore SMTP Email module which needs to know how to access your SMTP server otherwise it cannot do what it is supposed to do. In this module and many other modules this is solved by allowing you to store that configuration data in the database and you can adjust these settings while the application runs.
The Mendix Modeler has an advanced find function to find unused items. It is very helpful to remove obsolete microflows, pages, enumerations, etc from your model.