Form rules, hide and show fields based on other field values
I tried MobiDB and I think it's awesome for its price. The fact that you can go out in the field and work offline is an amazig feature that (as far as I know)only Alpha 5 has, which is much more expensive. So far, all is good. But you know there is going to be a "however"... so,
However, I miss one feature that is crucial to my organization and that is that the forms need to have to have some flexibility that I haven't seen yet. What I mean is that the appearance of a field or a nested table can be determined by a value entered in another field.
Let me give you an example of something that happens to us once in a while. We are a chemical plant and we sometimes have to deal with incidents, and we need to log them. Now, an incident can be many things but i will give you two options: one with and one without someone getting hurt. If someone creates a new record in the Incidents table the first field on the form should be a dropdown or radiobuttons that says: Person(s) Hurt Yes/No. If there are any people hurt we need to enter a lot more data than when the incident is something less harmful, like a leak or a spill. So in that case I don't need any victim-related fields in my form. And because we have about 20 types of incidents that can happen on our plant I don't want 20 different tables, I want one table that can handle all 20 scenarios, based on clever filtering of the form fields. We can handle the backend, no problem, but we need to have this on the frontend.
Is this something, these form rules, that you might develop for a future version of MobiDB? It would make the product so much better.
Thanks for reading,