I feel like currently forms are undermined as a concept by a very poor search functionality. Yes they can work well when acting as simple forms, but when it comes time to connect them to entities (which is Fibery’s strong point) forms fail miserably.
Here is a simple example of logging work via an entity, vs via a form.
In the entity view, I can search by a Task ID and get the matching result.
When I search in a form for the same Task ID I get no results, because forms use the old “search by name” functionality.
Given that Forms are generally meant to be more public / guest facing (not always, but generally), wouldn’t allowing search via an ID be added and unexpected complexity that most users (especially public ones) wouldn’t intend to search for?
In general, I agree, but it’s also straightforward to keep the form simple, isn’t it? For a public-facing form, I would simply not include a field that is related to internal working databases. This would allow for complexity for internal forms and for simplicity of public forms. Or is there a use-case I’m missing?
In our case, we are using forms internally.
Imagine people are coming from tools like Jira and for things like worklogs forms are one of the more welcoming approaches.
For external forms I assume those would not be linked to entities to begin with, but my expectation as a user is if the form allows me to link to entities, then it should provide a useful way to search through them.
