Sometimes a field shouldn't always be required — it depends on what the user said earlier. ActiveManage lets you mark a field as conditionally required using the same rule-builder you use for show/hide.
How It Works
On any field, change Required from “Always” / “Never” to Conditionally. A rule editor appears. Add one or more conditions; if any are met the field becomes required.
Validation Behaviour
- If the field is visible and required, the user sees the usual asterisk and a validation error if they skip it.
- If the field is hidden by another rule, the required status is suppressed automatically (you can't be required to fill in a field you can't see).
- If the field is visible but not required by current conditions, the validation passes even when empty.
Worked Examples
- International delivery: Customs declaration is required only when shipping outside the EU.
- Refund flow: Original order number is required only when the “Type of issue” is “Refund request”.
- Health declaration: Medication list is required only when the user has ticked “I have pre-existing conditions”.
- Employment application: Notice period is required only when the user enters a current employer.
Warning: Server-side validation must mirror the client-side rule. The platform handles this automatically when you use the rule builder. If you write custom validation, replicate the same condition check or you'll either block valid submissions or accept incomplete ones.