Extended logic and dependencies

Hey ​@Benjamin,

Thank you for the feedback. This is definitely feedback that we hear from time to time, can I ask what your specific use-case would be for it?

While we don’t have any immediate plans to uplift this part of the template, I can definitely reach back out when that changes.

Thank you,
Karen

Ugh.  I wrote a long reply to this and then Chrome decided that it had encountered an error and had to close.  Helpful!

In short...
Sometimes I don’t want the logic to appear immediately beneath a question - and would prefer to have it appear later in the flow of the form.  So for example… I have risk assessments that I’ve built out that contain mitigation strategies that a user has to select and/or respond to.  For…  bus transport, let’s say, I might want them to select that drivers will adhere to “rest, work and sleep requirements”, but I don’t necessarily want to disrupt the flow of selecting the mitigation strategies in order to insert information about those requirements and/or a link to the state transport web site.  I’d rather have that pop up after all of the risk strategies have been addressed.

That’s probably not a great example - but I’ve encountered a few occasions where I felt that using logic to make a field immediately appear wasn’t quite ideal.

You could alternatively have a combination of two functions - logic and dependencies.  Logic perhaps making an immediate secondary response, and dependencies allowing for something further down the page.

It may also be that I’d like something further down on the basis of something that was specified earlier - so for example one use case would be a multi-select in which I don’t want the selections’ logic to appear in the middle of that list, but rather, collate them all together further down.

Does that make sense?

This is also something that a lot of other form builders have as a standard option and would be super helpful.

For our use - imagine inspecting a playground.

an earlier question is what components are installed - and a multi select list appears with options like: slide, swingset, merry-go-round, teeter totter.

If they answer yes to Slide and Teeter Totter, then later in the form those products questions appear (but not the unrelated questions for swing set  and merry-go-round.

An early question can help streamline the # of pages and Forms the user needs to flip through to complete their inspection. 

Yep, not a bad example.
I’d also like to be able to have dependencies on another page entirely - so the first page might be your basic setup, with questions and multi-select etc.
….and then your later pages might contain all of the follow-up.

Hi ​@Benjamin soooo frustrating when that happens! Thanks for taking the time to write out your response again. Yes, that does make sense and ​@Keith J ‘s example helps to solidify the use cases.

Logic across pages is definitely one that we hear often, and extended dependencies definitely falls within that same project. I will reach back out once we start scoping this one out more, there’s a bit of work that needs to be done in the background before that happens.

Thanks again :)

Karen