I have a branched path where the next step depends on the path the user took to get to this point. These past path options include one path where a particular variable (Variable A) is set, and one path where the user never encountered Variable A. The value of Variable A is irrelevant, and if the user came from the path that doesn't use the variable, then Variable A itself is irrelevant.
To create the new paths, I used a pair of conditions that test whether Variable A "has value" or "has no value (empty)." In testing, however, if Variable A is not set then the next step is the question that sets Variable A.
I understand that this is the default behavior if the bot needs to evaluate a variable that hasn't been set. However, I don't need to access the value. I just need to know if it's there or not. Setting Variable A at this point is inappropriate for the user (it's out of context and serves no purpose--that's why it's not set in the first place).
Is there a way around the default behavior? (Note that my team can't upgrade to the Preview version of PVA of this time because of other functionality issues.)
Romain The Low-Code...
76
Pablo Roldan
61
stampcoin
10