Hi Scott,
While hiding elements on the form is confined to form rules you can use custom data rules to help make a field required or not available for edit when certain conditions are met. You can use our formula language to write out your own conditions under which a record will prevent a save and even put in your own error message for guidance. These rules then apply across data imports, API, Pipelines, and manual entry channels to help assure data meets those standards. It won't help you easily transition all your form rules but can help you simplify some of them so they aren't going to need to be repeated on every form.
For example you can set it up to do something simple like require a field not be empty when another field has a certain value. In my example below if a company is marked inactive and the Date Cancelled is blank or the Reason for Cancellation is blank I prevent a save, this makes sure no records are saved without this important information.
If([Active?]=false and ([Date Cancelled]=null or [Reason for Cancellation]=""), "All companies must have a date cancelled and reason for cancellation before they can be closed")
You can then get more complex if needed for your logic and it is all stored in one central place. It doesn't solve for everything form rules does but it can remove some of your rules from needing to be repeated and protect more than just form entry.
------------------------------
Evan Martinez
------------------------------
