ER: In Designer, change the 'Hidden' field value to be 'Visible' instead. This would make it easier to configure fields that need to be both visible and mandatory. If a field needs to be set to both mandatory and visible when a checkbox is selected, then you need to create 2 rules instead of 1. However, if the 'Hidden' condition was actually a 'Visible' condition you would only need 1. Alternatively (and this may be the safer dummy-proof option) design the system so that if a field is hidden it cannot be mandatory. ---------- Information from client: Required can be set on rules; and Field visibility can be based on rules. I would imagine that it is quite common to want to have the field required when it is made visible. This however requires two rules to be created. Had the function been for Visible (with default set to Yes) instead of Hidden then the same rule could have been applied to both properties. For example I have a tickbox that when ticked in displays a few fields. These fields are then mandatory. So I need create rule 1 If Tickbox = False and Rule 2 Tickbox = True Per field I then set Hidden to Rule 1 And Required to Rule 2 I can see no downside of having the property as Visible instead of Hidden but as mentioned, always need to duplicate rules with reverse conditions if both required and hidden should be active at the same time.