Here is our scenario and we are not limiting this to this application:
We handle dual citizens and we would like to know if they have one or both NIN(UK) and SSN/TIN. We have 2 nationality fields by default, we would like to set it up so that whenever they answered UK for 1 of them, the NIN field would show up, and if they answered US it would show SSN. If they selected the US and UK regardless of order, it would show both fields.
The dilemma here is that if it’s only 1 field with logic then it’s easy to set up using the current method but since we are limited to calling properties once per form, we cannot apply the same logic to the second nationality field.
I agree, the ability to have a branching action (similar to workflows) would be useful in several similar use cases. In general, there needs to be more flexibility with the conditional logic on forms as well as follows:
The ability to reorder dependent fields, if you have multiple dependent fields for one field.
Let’s say the field with the conditional logic is a multi-select field, then each of the options selected would show 2 dependent fields each using “contains any of”. If there are 32 multi-select options, sometimes you might forget to add a dependent field for one of the options. But if you add the missed dependent fields at the end, it will show at the end, rather than in the order of the multi-select options (see screen shots). In order to fix this, you have to edit the dependent field where the missed field should go, AND ALSO edit every dependent field after it so they are in the correct order. A simple fix would be the ability to reorder the dependent fields.
The ability to use a property more than once in a form, especially if a branching action is allowed
The ability to format the dependent fields just like regular fields (up to 4 columns of fields next to each other).
This would be extremely helpful when you have SKU and related quantity and pricing fields.