RELATED IDEAS
Improved wording and explaination in error messages
It would be fantastic if there were a variety of error messages instead of the generic "Whoops that wasn't meant to happen" and "Contact your Promaster" error messages.
Current when users come across those error messages they will contact the Promaster and provide a screenshot, however the message is so vague that it can be incredible difficult for the Promaster to trouble shoot before determining whether it needs to be escalated to Nintex Promapp as a bug. It would be great if the error message included a description of the type of error or a code of some sort etc.
Current when users come across those error messages they will contact the Promaster and provide a screenshot, however the message is so vague that it can be incredible difficult for the Promaster to trouble shoot before determining whether it needs to be escalated to Nintex Promapp as a bug. It would be great if the error message included a description of the type of error or a code of some sort etc.
I do agree that error codes would also help in these situations. We don't have this on our near-term roadmap so we'll monitor interest in this idea for now.