You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Relevance of repeat instances is evaluated in unexpected way
Steps to reproduce the problem
Start with this form. Instead of the nested veg group, put the relevance condition on the repeat itself. If you try to select any choice but the first one, no repeat instance exists. If you first select 'Beans' (the first choice), then the form works as expected with the first two choices. If you select the first two choices, then the form works with the first three choices, etc.
Expected behavior
I think relevance should be computed independently on every repeat instance?
The text was updated successfully, but these errors were encountered:
It's like the repeat instances have to be explicitly traversed to be created before their relevance is evaluated or something. Consider this variation which adds a count-selected(${tf_local_veg}) = 0 case to the relevance condition. In Collect, if you go to the hierarchy view and see the repeat there, then the form works as expected. Or if you jump to swipe through repeat instances without selecting vegetables, that also works. However, linear traversal doesn't work.
Software versions
JavaRosa v3.1.0
Problem description
Relevance of repeat instances is evaluated in unexpected way
Steps to reproduce the problem
Start with this form. Instead of the nested
veg
group, put the relevance condition on the repeat itself. If you try to select any choice but the first one, no repeat instance exists. If you first select 'Beans' (the first choice), then the form works as expected with the first two choices. If you select the first two choices, then the form works with the first three choices, etc.Expected behavior
I think relevance should be computed independently on every repeat instance?
The text was updated successfully, but these errors were encountered: