Formula Rules for Decision-Tree Script

  • 0
  • 1
  • Question
  • Updated 2 months ago
  • In Progress
I am trying to create a call-script using QuickBase as the interactive decision-tree (not familiar with the software? I want to develop something like ZingTree or Yonyx). It seems to be going well, but I'm having trouble with some of the formula rules, beyond that - the form page is giving me a hard time. So here are a few questions:

A. Has anyone built a decision-tree in QuickBase?
B. Why can't I have multiple tabs and fields within those tabs, but when I set the rules - I cannot hide all of the tabs? I always end up having either my first or my last tab show even if all of my rules are correct. I have even collapsed all of the other fields.
C. How can I get my text to align with my fields and be a larger size? For example, I add a text besides of a drop-drown menu.

I want it to look exactly as so:  "Hello my name is <user field>."

Are these jobs for add-ons?  Or custom coding?

I've tried looking in the community and even checking out the pre-built apps, but there aren't any that resemble this at all! All recommendations are welcome. Thanks!
Photo of Jessica

Jessica

  • 142 Points 100 badge 2x thumb

Posted 2 months ago

  • 0
  • 1
Photo of QuickBaseCoach App Dev./Training

QuickBaseCoach App Dev./Training, Champion

  • 51,346 Points 50k badge 2x thumb
Lots of questions.

A. I have not built a decision tree.

B. I was able to have form rules which hid all my tabs. in my case the first tab was not at the very top of the form. Note that you need to be sure that you do not have any pink warning messages at the top of your form when editing the form - ie if you have conflicting form rules you will get warning messages.  You need to set 1 rule to control if a tab shows, for example, and not multiple rules.


C. If you want to have text beside a field to aid the user with some explanation and the "text elements"  on a form are not good enough (I know that all the format control you get there is basically bold), then you can make a real field and use all the html that you like.  That would be a formula Rich Text field type.

Photo of Jessica

Jessica

  • 142 Points 100 badge 2x thumb
B. Okay - so maybe tabs are not a good option for the form rules I have to set up. I will have to create a field for each option I'm assuming? Because some fields can be used multiple times based on the decision.

C. Thank you!
Photo of Jessica

Jessica

  • 142 Points 100 badge 2x thumb
Wait -- having problems with the Rich Text Formula field now. It's not understanding html? I'm getting a formula error when I begin with <html>
Photo of QuickBaseCoach App Dev./Training

QuickBaseCoach App Dev./Training, Champion

  • 51,346 Points 50k badge 2x thumb
I don't claim to be an html expert, but you use it like

"<font color=blue><b>My blue text goes here" 

btw, QuickBase is quite tolerant on not closing your tags.
Photo of Jessica

Jessica

  • 142 Points 100 badge 2x thumb
Got it - so I need to put the HTML in "   "'s?
Photo of QuickBaseCoach App Dev./Training

QuickBaseCoach App Dev./Training, Champion

  • 51,256 Points 50k badge 2x thumb
You are creating a text string, so it needs to be in quotes at the beginning and the end.

Like

"Hello - my name is Jessica"

or you can write

"<font color=red><b>My name is Jessica"
Photo of QuickBaseCoach App Dev./Training

QuickBaseCoach App Dev./Training, Champion

  • 51,346 Points 50k badge 2x thumb
If you have a field or a tab that is used in more than one "situation", then you will need a single rule to control that field or tab.