Where is the "persistable" property of an entity defined?

The "persistable" property of an entity is defined in the domain model. In Mendix, the domain model represents the structure of your application data. Each entity is defined within this model, which includes attributes, relationships, and properties.

The "persistable" property specifically indicates whether instances of that entity can be saved to the database. By default, entities in Mendix are designed to be persistable, allowing you to store and manipulate data effectively. When working within the domain model, you have the ability to configure various properties, including whether an entity should be persistable or not, thereby directly influencing how the entity will behave in terms of data storage and lifecycle within the Mendix application.

Other areas such as action JavaScript, microflows, or the user interface do not define the persistence characteristics of an entity. Instead, they involve different aspects of application functionality and user interaction. For example, action JavaScript might handle logic or functionality, microflows orchestrate complex processes involving multiple operations, and the user interface focuses on how data is presented and interacted with by the user. Thus, understanding the central role of the domain model in establishing fundamental entity properties is essential for effective application design in Mendix.