Improve/Customise Error messages
Currently the error messages are user unfriendly and full of unhelpful jargon. It would be a great improvement to translate the error messages into lament terms so Admins and Users can benefit alike.
Anonymous
shared this idea
-
Thomas J Routhouska
commented
Applicable to better error messaging ...
As a higher-ed institution that uses SalesForce as an application system, we get a lot of protected documents included with an application - a common example being transcripts. When we create a PDF of the application via Loop, the DDP includes all attached files and if one is protected, will fail the loop process.
Any given application could have multiple attached documents so what staff have to do is run the DDP manually and exclude one of the attached documents until they figure out which is the problematic one (keep in mind some applications could have up to 20 files attached). This takes an enormous amount of time and I've asked in the past if there is a way to surface which one of the documents its failing on in the actual error message. Knowing which file is protected/causing issues will shave off a ton of time diagnosing the problem for staff. This seems to be a bigger problem each year.
-
Anonymous
commented
Or can Nintex add ability to customize the error message? For example, in one of my packages I have a DocuSign delivery option's recipient set as Static Name-Email and we want to be able to give a more user-friendly error message when the value is missing.
Thanks!