Skip Logic applied to next instrument

[tobadia]

Hi everyone,
I'm using FRSL v3.3.4 to conditionnaly skip instruments, whan a patient reports no exposure to say, [exp_1] and [exp_2]. Upgrading is not an option at the moment although I don't think it is related to the issue at hand
I'm in the following scenario:
instrument_1 contains demographics, as well as [exp_1] and [exp_2], both being radio buttons (1, Yes | 0, No)
instrument_2 contains several items that are only relevant when [exp_1] = '1'
instrument_3 contains several items that are only relevant when [exp_2] = '1'

My understanding is that FRSL does its hook magic when loading instrument_1. However, this means that instrument_2 and instrument_3 aren't available by default (and for whatever reason, setting default/fallback value to 1 does not seem to change anything, even with the Advanced logic and piping in the content of [exp_1] and [exp_2]). Is there any way to fix that ?

My understanding of hooks makes me fear there's no way out: there would need to be at least another instrument right after instrument_1, so that the updated content of [exp_1] and [exp_2] triggers the hook again and makes instrument_2 and instrument_3 available.

Any hint ?
Thanks and all the best!

[pbchase]

@tobadia, it would be helpful if you could provide an example project that implements the sequence of forms you want to talk about. The easier it is for us to reproduce the problem you are having, the easier it is for us to help you. We need a small reproducible example.

You don't say it explicitly say it, but it sounds like you are saying that "Save and go to next form" will skip both instruments 2 and 3 and proceed to instrument 4 because instrument 1 thinks 2 and 3 are off limits when it loads. Thus, instrument 4 is the next form the first time instrument 1 loads? Do I have that right?

[tobadia]

@pbchase I had for some reason missed the notification of reply here. Apologies about that.

You had it right about skipping instruments 2 and 3. Basically, if FRSL triggers are on a given form N, they can't be used to conditionnally show/hide form N+1. At least in my test cases. That can very well be a limitation by design and if so, doesn't need to be adressed further.

I guess my question was rather "is it possible to use fields from an instrument to conditionnally show/hide the next instrument in order, i.e. the one that would come directly after hitting 'Save and go to next form' ?"
About reproducibility, I can set up a small test project to highlight that particular setting but this could be unnecessary if the answer to the question just above if no (meaning it's a limitation by design).