edit: sorry- now i realized that we discuss ACTION here… so, all the input parameters have to be entered at once; Your requirement sort of makes sense in this case!
I haven’t used more complex cases in action myself. Maybe you could change the “big action” into separate actions without parent choice statement to simplify parameters for user?
what i wrote down below applies co choice statements when working with normal configuration, and is bit different for action invocation of course…
— original response (effective for config, not 100% for action’s
So, my group2 has 3 case statements(that are mutually exclusive among each other).
If I set g2 (one of case leaves from group2) and I still see the group1 leaves in possible completions
yes, so far as expected
and I set g1 (one of the leaves from group1)
yes, normal use-case when working with
choice statement elements (switching between groups)
then it throws error: “g2” is an invalid value.
no, it will set g1 leaf, and drop/delete all the data that belongs to cases other than g1
[I can successfully set g2 individually though, i.e without any other leaf ]
yes, any elements in all the cases should be visible
Whereas, if I set g1 then I don’t see any leaf from group2 in the possible completions.
after g1 is set, all the other case leaves should be visible in completion hints…