Field Dependencies for Contact Properties

I agree with the others that have said having the conditional logic check for only being “equal to” is very limiting. It’s a great start but should mimic the behaviors of the other logical checks you have already available in workflows, reports, etc. i.e. “is known”, 'is any of…[multi-select] value", and other options would be more along the lines of what I would need for my use-case.

For instance, if my users populate X-field (regardless of value) require that Y-field is populated.