Should I use Contains or Is Equal To in my conditions?

  • Profile Image
    PriscillaC
    Asked on January 03, 2018 at 01:46 PM

    We have a form (https://www.jotform.com/build/73528302984159?iak=67d45559377211927e9b7fb4748d5446-2c3eb5c1323065fc)

    This form has two fields. based on the input of those two fields, the form will direct them to specific pages. Field #1 is Type of Request and Field #2 is Target Audience. 

    I am using the "is equal to" option for them to enter their requests' target audience but I don't want users to be denied access to a specific form if they don't enter the target audiences exactly as I have them in the conditional wizard.  

    For example, if the user selects Field #1: Member Communication as their request and selects  Field #2: Members, they should be directed to Member Comm page. However, if the user selects Field #2: Members & ProvidersI'd still like them to be directed to the Member Communication page since Members was also included. 

    Would Contains work better for this function?

    When I tried using the ANY option, it would cause errors within the rest of my conditions for some reason. 


  • Profile Image
    Jim_R
    Answered on January 03, 2018 at 03:46 PM

    To answer your question, using CONTAINS is better than IS EQUAL TO seeing that you're using the Multiple Selection Widget. If you're using a field that allows one selection only (e.g. a dropdown field or a radio button), then always use IS EQUAL TO.

    And to address your comment about using ANY, I'm afraid it won't work with your current setup. For example, your first condition (shown below) will always be TRUE as soon as a user selects "Ad Request". This means that you won't be able to distinguish the difference on the Target Audience field regardless (since the first IF statement will always be TRUE and will always trigger the condition).

    I think what you're trying to accomplish is to redirect users to different pages based on the combination of answers they select on the Target Audience field. We can help you for as long as we understand what your end goal is. As of now, I'm confused with the number of conditions and combinations you have for the redirects.

    I recommend you break down your IF statements into separate conditions. For example, the 2 conditions below would fulfill your end goal for the first condition above:

    The 2 conditions above will cover all these scenarios:

    🔘 Request = Ad Request AND Audience = Public

    🔘 Request = Ad Request AND Audience = Members

    🔘 Request = Ad Request AND Audience = Public, Members

    🔘 Request = Ad Request AND Audience = Members, Public

    One good way to test conditions out is to test them one by one. Here are my recommendations:

    1. Disable ALL your conditions first.

    2. Setup those 2 conditions above. This should always redirect your users to http://www.lacare.org/Content/Podio/forms/Ad_Request.html if it meets any of the 4 combinations above. And if none of those 4 were met, they should see a regular Thank You page.

    3. If that worked, add another condition for a different redirect URL that fulfills a different set of condition.

    4. Make sure to follow the same principle and separate your conditions if you're targeting multiple audiences (e.g. combination of just Members, just Providers or both Members/Providers).

    5. Rinse and repeat.

  • Profile Image
    PriscillaC
    Answered on January 11, 2018 at 03:43 PM
    Hello,
    Thank you for your feedback. I did what you said and my conditions worked.
    However, I noticed when I came back from the weekend, my conditions were not there anymore. They had somehow reverted back to my old conditions. I was curious if there was a way to lock these conditions so they can’t be altered with? Also, do you know if JotForm does some sort of sweep occasionally that might explain this?
    Thanks,
    Priscilla
    ...
  • Profile Image
    aubreybourke
    Answered on January 11, 2018 at 04:30 PM

    You can revert your form to a previous state using the form revision history:

    How-to-View-Form-Revision-History