I like the functionality of making fields (in-)visible via conditions - those however only work with boolean or enumerations - however in order to make a form user-friendly (display different part of the form by ticking chechbox) should not be hard-coded into the domain model. At the moment a checkbox can not be standalone but needs to refer to an attribute of an entity. It would be great if for presentation purposes there would be a different way to achieve this.
How about modeling an extra entity that contains all the display logic you require? That way you're separating the view logic from the domain model logic, which, as I gather, is your main concern.