Error handling for default value on branch action
Somehow make it clearer that the default value needs to be set and not take the "select a value" text. It looked as if it was setup when building it fast. Definitely user error; however the error message sent me on a wild goose chase. When the default is not set it throws an error - "no implicit conversion of String into Integer".
I knew it was failing near the branch, but couldn't figure it out until I pulled the actions from the branch and ran them sequentially without changing them....
Pretty obvious that it's necessary.
Error messaging has been updated and the ability to create an “Error” branch and set it as default option is available.
Adminrenai.bell (Admin, Nintex) commented
Thank you for your feedback! We have it in our backlog to improve error messaging so that these examples are much easier to troubleshoot and overcome. We will prioritize this against other feedback submissions as we continue to build out the platform.