I’ve mentioned this before, but…
There isn’t true parity between form views and forms inside other view types. The issues with the form view, as expressed by users:
- Relationships and selects don’t keep their database and icon respectively.
- Cannot have filters applied to the select fields, allowing invalid selections (like assigning tasks to the wrong team—or worse, the admin account).
- There’s no “create and open” feature—you can only submit. Is this because forms can be shared externally?
As for the forms inside other views/entities:
- The default “new” behaviour is “compact” not “full”. I don’t think I’ve ever had a situation where I want the “compact” entity creation, and users really dislike how unpolished it feels.
- All forms are visible at all times. This is information overload. Similarly named forms cause confusion.
- If I don’t want a form view accessible directly—to only allow it using the ‘+ New’ button—I’ve had to implement a hack workaround by sending that form to a folder effectively called “DO NOT TOUCH” to strongly deter users from touching it. I can’t move the form into a hidden space because that then removes it from user access entirely. I still want it visible but ONLY when users click ‘+ New’.
These are just my gripes about how all this is unintuitive from both the architect and the user perspectives. Hopefully it starts a discussion about usability and consistency.
