I encountered some problems with LOV fields in formspider. We need to a validate LOV which uses lovField. There is a bindVarible which is set in the lovField so that it’s validated with list of values in the LOV.
If a user enters an invalid LOV field and moves to another component, the LOV is shown.
When the LOV is placed in a gird and the user moves the cursor from the LOV field to another component, the LOV is popped up if the value is incorrect. However, if the user presses cancel, the focus is lost from the LOV field while the wrong value entered by the user placed in the in the lovField. This value is not validated again until the focus is given to the lovField. I think the focus should be kept in the lovField if the user press the cancel provided that the lovField is invalid. It should also validate scenarios of empty lovField.
Is it possible to handle such situation with Text Fields used as LOVs. I'm using FocusGain and Focus lost events for validations. But the situation would be complicated with focus moving between multiple rows.
asked 19 Jul '13, 05:04
Formspider does not enforce required fields. In other words, Formspider allows users to get out of a required field even if its value is null. Developers should enforce required fields at the time that is appropriate (usually during a save operation. But sometimes leaving a screen, for example in a Wizard like navigation might be appropriate.) If you want to enforce users to enter a value before they leave a field, you can code that, too. But in general this is not the best way to enforce mandatory fields.
We did not understand what you mean by this. Could you give an example please?
This sounds like a bug. I created a ticket in our issue system.