|
How to handle required fields when doing a Create on an object depends on what you want your users to experience. I'm assuming you generated your business objects with Verification turned "on" and its sub-option to generate verifiers. The "Generate predefined verifiers" options means (in effect) that you want DevForce to inscribe "Required" verifiers for every non-null property it generates.
The verifiers are generated with Preset triggers, which means they lock up the UI when the user sets the value to null (more precisely, they throw an exception which causes Data Binding to lock up the UI).
This is appropriate most of the time and is the safest thing to do. That is, it is safest to assume that the user should not be able to leave a required field blank once she has started entering data into it.
However if you decide that it is OK to allow blank strings temporarily (you should run Verification before the save to catch errors), there are a couple options you can do:
1. You could turn off auto-generation of verifiers (but leave generation of BeforeSetValue and AfterSetValue) and add the verifiers you want in the business logic of the entity.
2. Alternatively, you can programmatically discover the generated required verifiers and change the triggering from Preset to Postset. Postset means the verifier is evaluated after the property is set (no exception is thrown and the user can move out of the control).
Hope this helps.
|