Hoping someone can provide a bit of an explanation on why fallbacks act a certain way when a wizard is initiated via the API or (I assume) the Nintex Console.
It seems that if, for example, an object fails to be detected and the fallback for that is set to raise an error, that an error isn’t actually raised. Instead, the wizard just fails and closes. I assumed that one of 2 things would happen, neither of which did.
- The wizard would pop up with a box indicating what it was trying to find, similar to the “Do It” version of running a wizard.
- The wizard would move to the Wizard end unsuccessfully section, since it is apparently going to end with a fail, which seems to be an unsuccessful end.
However, since neither of these option happen, I’m a bit unsure what the point of the default “raise error” fallback is when it comes to these unattended wizards.
Thanks!