The same combinations for configuring field state on roles and stages are also available when making a field mandatory. Mandatory field checking is often better handled by the Check Mandatory behavior command rather than the field state management options. See Checking for Mandatory Fields.
The reason for this is that the Mandatory Answer property is checked only when the app is submitted. You will often want to perform mandatory field checking when the user moves to another page rather than at app submission. You may also want to perform validations that are conditional upon field values. Conditional mandatory field checking is not supported as a part of field state management.
 |
The Check Mandatory command does not check read-only, hidden or disabled app objects. |
See also: Overriding Persisted Field State
Return to: Limiting User Access to App Fields, Designing an App
