Hi All,
In onboarding process, I set up NEXT to be activated when a specific conditions is met as per the screenshots:
What have I missed or done wrong in the second step?
Oh, and I’ve also had them as 2 separate workflows and it was the same problem.
The popup showing action is not throttled by any condition. It will always execute as long as the whole workflow is executed.
The condition you say isn’t working is only preventing the last action to execute (the Go to page action). The condition is also mutually exclusive with the workflow condition, so it’s expected that will always evaluate to false.
Erm, I absolutely have no idea what you just said. Disclaimer - non-Developer here 
I need both toggles to be toggled for NEXT to be activate and move the user to the next page. So in laymans terms, what do I change to make this work?
I’ll put it in other words.
You are writing your conditionals based on two values:
toggle_bank statement's isToggledtoggle_loan agreement's isToggledThe click on Text next won’t do anything unless both values are no, because that’s how you have defined the conditional for your workflow to trigger.
I guess both values are set to no because the workflow is executing.
If the workflow executes, the popup Popup_hold up will inevitably show, because Step 1 will always execute (there’s no conditional on that step).
Step 2 will never execute. Why? Because there is a conditional preventing it from executing. Why? Because it needs above mentioned values to be yes, and they will never be, just because the whole workflow need them to be no to execute.
Just guessing here, but I think you either want the popup to show or the user to be moved to next page. Then you need to move the workflow conditional to Step 1, and let the workflow execute always.
Yes, I need the user to be moved to the next page but only after
toggle_bank statement's isToggled is yestoggle_loan agreement's isToggled is yesIf either are no, they pop shows.
May be I’m missing something here but which values needs to be yes?
I’ve tried moving the conditions, it doesn’t work. And I’ve switched step 1 and 2 around with the condition in step 1, it still doesn’t work.
I’m seeing different names for things. You said users should move to next page when “toggle_bank statement” and “toggle_loan agreement” are “yes” … your screenshot shows references to differently named toggles. That might be the new issue.
Also, navigation actions that take the user away from the page should be the last action. This is obviously a conditional scenario where they may not always leave the page, but good to get in that habit.
Your last screenshot is almost there with the opposing conditions on each action, but I think (possibly) you’re just referencing the wrong toggles now.
My bad on the name confusion, I’d switched to another page but the conditions that need to be met are exactly the same.
I assumed that the correct steps were:
But Ademiguel’s suggested this was incorrect, or at least that’s what I understand.
Switching back to the original conditional statement
Use your debugger to confirm the values of the toggles. It’s possible that they’re not actually changing to “yes.” In your preview, click “inspect” and then search for the toggle elements by name and see what value they’re outputting. If they’re still “no,” then that’s what you need to troubleshoot.
Maybe they’re being reset too early? Maybe they’re not visible and other toggles are visible instead by mistake? Maybe you have conditions that define default values for them?
This isn’t the original setup you posted (neither conditional redaction nor its placement)…
BUT it’s the exact setup you need, according to what you have last explained! Don’t change it for now!
If you are using the correct toggles and they are properly valued at execution time, you should see what you look for.
If not, you’ll need to check why they aren’t valued the way you want. You can use the debugger for that, just as @romanmg has proposed.
Right, this is what the debugger shows
For step 1:
For step 2:
Unless I’m mistaken, both steps are outputting the correct value.
Then problem solved?
I have a hunch that it’s not. I see both toggles in your last screenshot and both are “on”.
Remember, non-Developer here 
When you say both toggles are on, do you mean ‘isToggled is yes’?, the condition for moving to the next page or something.
What change do I need to make?
I am wondering why those two toggles in your UI are “on” (a.k.a switched right/activated), but you are getting the condition below to be false.
I mean, if both are activated in the UI you should be getting the below right?
toggle_bank statement's isToggled is yestoggle_loan agreement's isToggled is yesI think your problem is somewhere in the process of giving a value to those isToggled custom states.
Are the toggles inputs or icons? I’m assuming they’re icons because you’re using a custom state to track the values and have a workflow when “group_toggle” is clicked to set the values to “yes.” I’m also assuming you have a condition on the icons to change their appearance (off position vs on position) based on the custom states.
However, if they’re actually inputs, then you may confusing the input values with the custom state values. Where, if the input is changed, but not the state, then your conditions to show popup vs navigate will not behave how you want. If they’re inputs, I’d ONLY go off the input values for everything and remove the states completely.
Yes, it’s the toggles are icons that I designed with custom states.
I added an opacity condition to NEXT - 25% when either toggle are ‘no’. When I click the toggles to yes (which works) NEXT’s opacity doesn’t change. I have the same opacity setting elsewhere and it works fine.
So, am I correct in thinking the toggles aren’t working or when isToggled is ‘yes’ that is? If so, what might cause that?
This topic was automatically closed after 14 days. New replies are no longer allowed.
