validate field condition dependencys when building app

Follow

Bob Schaefer

• June 03, 2021 16:13

Is there a way to validate the field conditions when building an app?

Ex: The choice of a drop-down is used to show or hide several fields in an app, on several separate pages. If the choices of the drop-down are modified, you have to manually go through the entire app to check & see if that particular text was used. (This seems to hold true for all field conditions.)

My idea solution would be a way to download a machine-generated intermediate textual format that could be programmatically (or manually) checked, even if the corrections must be made in the graphical editor, because a text format is easier for me to follow the logic; but a graphical dependency tree of some sort would work as well.

3

• 

  Nathan H

  • June 03, 2021 21:25

  Agreed.  That would be helpful.  Maybe even add a small "dependency" icon in the app builder for fields / screens that are dependent on other fields (maybe an "up arrow" type icon) and for fields / screens that have other fields / screens dependent on them (maybe a "down arrow" type icon).  Perhaps you could click that icon and it would show a small modal window with the field / screen name(s) that you could click to jump to the field(s) or screen(s).  (Kind of like the conditional logic icon that appears next to fields / screens that have conditions applied)

  2

  Comment actions Permalink
• 

  Lauren Sunday

  • June 08, 2021 21:37

  Hey ya'll,

  I can definitely identify with the issue that is presented when you change even a slight conditional value that conditions are based on. I think it would be interesting to see the logic branch on the settings modal so you can quickly identify what needs to be updated. This also could be helped with another recent request to Select multiple fields to update while designing. Upvoted and passed along to the product team!

  2

  Comment actions Permalink
• 

  Doug Borrowman

  • August 31, 2022 17:43

  Hoping to get this feature back into the light. Being able to see field & screen dependencies is of huge value to form development. We're looking at updating fields to new field types that have been released for better functionality. Unfortunately, doing so means re-coding many dependencies in fields & screens throughout our whole form layout. Being able to see what is linked together and how is critical to show a guiding map of conditions we need to recreate and errors that are happening when we are completing form development. 

  1

  Comment actions Permalink
• 

  Hazel Kral

  • September 01, 2022 13:56

  Hi Doug,

  Thank you so much for expressing your interest here again. Our product team is in the loop and we will update here if anything changes. If you haven't already be sure to upvote this post!

  Best,

  Hazel Kral

  Customer Engagement Manager

  0

  Comment actions Permalink

Please sign in to leave a comment.