You are viewing limited content. For full access, please sign in.

Question

Question

Reset selections on fields when another field is changed

asked on June 14, 2022 Show version history

History of Situation:

We are trying to deploy a customer ID validation into one of our processes. We are using a view that tracks customer folders in the repository. We are using that view as a look-up to match customer input of First/Last Name. Since this process can be used for brand new customers we had to create a way to allow for customers with no folder in our repository to go through. Also want to mention I am using a custom submit button so I can hide it when no match is found. 

 

Here is where I need help.

With the validation I have two questions :

1. Does the look-up search match the customer input? (yes/no radio)

  • Yes - will show submit button and No will hide it.
  • Question 1 appears (by Field Rules) when the look up using the ID returns values

2. Is this a new customer with a new customer ID? (yes/no radio)

  • Yes - will show submit button and No will hide it.
  • Question 2 appears (by Field Rules) when the look up using the ID does not return values (in other words the look up First/Last name fields are blank)

 

If I answer question 2(New customer) as Yes and the submit button shows up, but also go back and change the customer ID to a value that returns a value I get question 1 (Does the validation name match customer input). If I say No, I should expect the submit button to remain hidden. But since my previous response to question 2 (New customer) still says yes , even though, it is hidden, the submit button will show even if I select No to the now showing Question 1. 

Is it possible to have the choices for question 1 & question 2 reset upon the change of the customer ID?

 

 

I have attached a document detailing the scenario we are trying to solve for (Scenario 3)

0 0

Answer

SELECTED ANSWER
replied on June 14, 2022

If I'm right about those two situations in my last comment...

Then you could probably make it work with two separate rules if you changed them to hide the submit button when any of the three items are not true.  It'll warn you about unexpected behavior with two rules on the same field, but it might still work.

Or, and maybe this is a better option.  Could you have two custom submit buttons instead?  One that shows when the first group of three items are all true, and the second that shows when the second group of three items are all true.

1 0

Replies

replied on June 14, 2022

You could probably get some Javascript together to handle the field resets you are requesting.  But that may not be possible.  I'm guessing you might be able to achieve what you want with a tweak of the field rules.  It sounds like you probably have your field rules that the show/hide of the submit button is triggered from the second question where you probably want it triggering from valid responses on both question 1 and question 2, along with some of the inputs that triggers lookups for those questions, so that there has to be valid information throughout all of the values in order for that button to be shown, so that hiding one of the questions due to a change in another question would result in the submit button being hidden as well.

Would you mind sharing your field rules for review?

0 0
replied on June 14, 2022
0 0
replied on June 14, 2022 Show version history

Okay, am I understanding this correctly?

 

Show the Submit Button when:

 

  1. Found First Name is not blank
    and
  2. Found Last Name is not blank
    and
  3. Does the name match the... is Yes

    or

 

  1. Found First Name is blank
    and
  2. Found Last Name is blank
    and
  3. Is this a new client with a... is Yes

 

Do I have that right?

0 0
SELECTED ANSWER
replied on June 14, 2022

If I'm right about those two situations in my last comment...

Then you could probably make it work with two separate rules if you changed them to hide the submit button when any of the three items are not true.  It'll warn you about unexpected behavior with two rules on the same field, but it might still work.

Or, and maybe this is a better option.  Could you have two custom submit buttons instead?  One that shows when the first group of three items are all true, and the second that shows when the second group of three items are all true.

1 0
replied on June 15, 2022

I actually considered both of those options after I provided the rules. I went ahead and created two rules for the submit button using both scenarios. I crossed my fingers after getting the little warning. It does seem to work at the moment. We will be taking it through approval testing (the same course that found the illogical scenario I am solving for) so hopefully it withstands the break efforts by our testing team. 

1 0
replied on June 15, 2022

That's great!  I'm keep my fingers crossed for you.

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.