What problem are you observing?
We have a requirement for a custom form to allow some data to be filled in. Based on the first field ‘actionRequired’, one or several fields should be kept hidden, so that data cannot be entered there. Example:
Action required equals:
- Hide-1and2 → hide fields One and Two
- Hide-2and3 → hide fields Two and Three
- Hide-3 → hide field Three
We have setup conditions to allow this behavior, with one primary block to hide all fields when no value has been selected yet. Depending on the order of the conditions, the form hides all, none or just one of the fields needed. If we change the action to disable instead of hide, the behaviour is the same, i.e. it only hides all, none or just one of the required fields, depending on the order we put the conditions in.
Please find the form example attached.
What is the correct behavior?
We expect the actions of each condition block to be executing all actions, not just one.
What product feature is this related to?
SailPoint ISC Forms
What are the steps to reproduce the issue?
Please find the attached form that can be used to replicate the issue.
Do you have any other information about your environment that may help?
This is happening in a partner tenant as well as a client tenant.
example-form.json (5.1 KB)