I'm a bit afraid that this makes debugging harder in case a user hit different error cases and they all result in the same error. And we don't have a good automated error reporting system right now..
But I agree on the "irritate" part, so I'd suggest:
For all the errors we know ("Abbruch" for example), map their string content to our own error message, which we can also translate to English as well.
For all others strip the SecurityLayer Error: [6001] part in all cases, maybe extract the error number and append it instead like (Error code: 6001)
I agree that it would be harder to debug. But i think, if we want to do everything "correctly" from the usx point of view, the user should not see any error codes, especially not with something as simple as canceling the signature.
Maybe we can print the error code seperatly and hide them with some css tricks?
They do end up in the "Failed document" list when the process gets aborted atm, so we have to show some reason imho so the user knows why they ended up there (like "The signature process was manually aborted.")
Unless we do some string matching and don't treat this case as an error and instead of putting the PDF in the "failed list" add it back to the "todo list" as if the user clicked the "X" in the top right corner. What about this solution?
@987FCF504483CBC8 i've added a new function which parse three common error messages(6000,6001,6002) and added language support for them. Parsed the messages to user friendly messages.