Consistent behavior for relevant field between web and field app

[bowlincd]

Currently there is a distinct difference in how survey 123 web app and the field app handles a field with a relevancy. On an update of a record, the field app will clear out existing data of a field that does not meet the relevant criteria. The web app will not change any data in  field with a relevant criteria. It only makes the field not visible. See note

 The idea suggestion is to make the web app clear out a field that is not relevant on a record update like the field app does.  Since the inception of the visible field, there is no point to cause the relevant field to work identical to the visible field. One should clear data (on both platforms) and the other just act as visibility only.