Separate Exception Messages from Error Log messages

By Justin James on 9 Jun

The discussion around the "string truncated" error brought this up... we need to be able to throw an exception in a manner where there are two messages: one that gets logged in Error Log, and one that goes onto the stack as Exception Message. Reason is that sometimes we need to throw something where the proper message for debugging purposes may contain sensitive or in-depth technical information (like database details) that should only go to the error log and never go to the screen, but we want a friendly message to go to the screen.