Conditional fields app idea is very good, but necessary update crucial things:
- Copy agent rules to end-user
Now it works only first time, when no other conditions are set. Usually forms are expanded with time, so it's crucial to have possibility to copy same rules for each different form.
- Allow to use field conditions more than 1 time
When field is used once, you can't set it up for second time. Why we have this limit? Should be normal practise to set fields conditions for second time. FOr example in one group you need always and another group need only when other specific fields are selected. (P.S. CloudSet conditions can do that). Also
- Two types for required fields: 1)on solving 2) on update
It's crucial update, because some fields for example on tickets creation you can't make mandatory and also it's impossible to use system required field, because field can be hidden under condition and agent gets error on submission.
- Conditional fields for end-user and organization
Should be great to have different conditions user and org profiles. For example 1 for agents and another for end-users would be extremely useful.
- Help Center conditional fields
Even if conditional fields in help center works on submission, but when you log as end-user conditions are not working so user can see all form fields.
- Deactivating fields issue
We lose all field conditions if one of set ticket fields gets deactivated. For example: If group A has 20 conditional fields and one of them gets deactivated you lose all other conditions and you have to setup them again.
Post is closed for comments.