Easy electronic forms with versatility beyond expectation

Hi Elton, thanks very much for the response. Re conditional logic: 1. Would be helpful to be able to combine different types of actions in one condition when they apply to the same fields under the same conditions, e.g. if the type of product I choose is a shirt, then the colour and size fields should be both visible and mandatory. Currently I would have to crate two separate rules for this. 2. Combined AND / OR rules would allow for similar reduction in rules needed + clarity of how they apply, e.g. if the vacancy I open is in the Finance department AND it's at either Site A OR Site B, then set a specific salary range. Currently have to make two rules, one for site A and one for site B or keep the AND function and go with 'site not equal' all sites except for A and B - this is a way to only have one rule but can be an issue when we have 60 sites. These are the main two ones that would help significantly, but will comment later if I remember any others that I was thinking about.

Some more suggestions for the conditional logic: 3. Ability to group several conditions together: sometimes more than one rule is needed to make a certain function work, it would help to be able to collapse these related rules in a group and give it a name 4. There is currently no way to detect conflicts in rules other than manual review, maybe a primitive debug tool could help with this? look for rules affecting the same field that will apply at the same time and give a warning

5. Maybe add a rule that allows to clear fields' values; in some cases the 'calculate field' rule can be used for that but it does not allow an empty value, and it can only apply to one field at a time. A rule that would clear a whole section of a form is currently not possible. There are ways to work around it, e.g. using the calculate option or copy value from another blank field, but those are not optimal

6. Any rules that could apply to options of a multiple-choice field, e.g. hide or deactivate options based on another field. Currently, if I need to make inter-dependent choices, I have to either create additional fields, or disable Submit button if a 'forbidden combination' is picked, or create a list of all possible combinations to pick from. All these have their own downsides. Example: in the first selection a user picks a business unit, then in the next they need to pick a team within that unit. This means that I need to create a different list of options for teams and hide/show them based on the first selection, or I need to make one list that has all options as "business-unit - team". There is a multi-level list field which can be used for cases like this, however, it also gets tricky when the combinations are more complex than described before, e.g. picking type of shirt in field 1, then size in field 2. Some shirts will come in all sizes and some will not, etc.