Domain Model Flashcards
What alternative to drawing an association between two entities can you use to connect two entities, each located in a separate domain model?
By right-clicking in an entity and selecting Add>Association.
What is an easy way to limit access rights for a given role to a specific functionality within an app?
By adding a separate module.
Why don’t we use entities from the Administration module?
Because it is a Marketplace module, so it’s best not to alter the module itself. They can be updated at anytime, and all your changes to this module will be replaced.
Why don’t we use entities from the System module?
Because the access rights of the System module can’t be changed.
How can we use the Entities from the Administration and System modules?
By creating specialized entities inside of our App Domain Model using generalization .
Can a user have more than 1 UserRole?
By default, yes.
What is a good reason to choose to use an Information Entity instead of multiple associations?
- You want it to be clear that only one object can have a specific qualification.
2.You want clear Entity names.
3.You want to optimize the app’s performance. - You want to display additional information about an association.
- You want to display additional information about an association
Can be Non-persistable entities be saved in the database?
No, non-persistable entities can’t be saved inside of the database.
What happens when you commit non-persistable entities?
The current attribute values and association values get stored in memory, not in the database.
What happens to values saved in memory at the end of the session(person stops using the application)?
All of it will be deleted
What is a transient object?
An object that only exists in memory and not in the database
Associations between persistable and non-persistable entities.
On which side should the ownership be?
The ownership (the side with the dot) should always lie on the side of the non-persistable entity.
You can use validation rules with non-persistable entities
true
false
false
You can use indexes with non-persistable entities
true
false
false
Why would you use non-persistable entities in Mendix applications?
Non-persistable entities are used in Mendix applications for data that should not be stored in the database. This can be because the data is related to a specific transaction (process data) or contains sensitive information that, by law, cannot be stored in the database. Non-persistable entities ensure that such data cannot be committed to the database.
