Standard for User Error Messages?
It seems like there should be a standard for user error messages -- those generally beyond the user's control.
This is what should generally be supplied:
- A clear error message statement, including the system or subsystem that threw the error.
- Brief explanation of what the cause could have been the problem, to put the user at ease.
- What recovery is available? Is the system unavailable, or it fixable for that user?
- Error Details for capture (Including timestamp, SessionID, etc)
The authentication failure messages generally follow this pattern ("Connection Failed. Try again"), but not exactly -- leaving us customers to fill in the gaps here.
We are unable to customize those messages from the engine, unfortunately.
Can that be considered?
(or can we anticipate Pega getting errors cleaned up following some standard?)
To follow up on this request, there should also be a distinction between 'User Friendly' and 'Developer Friendly' messages. If the website is an external, public application (or even if it is used internally by front-line users), technical msgs do not provide a good end user experience. One option could be a user friendly message, with a collapsed section that contains more technical details.
Hi Jon,
Agreed to your points & want to echo the same that for the Errors/Exceptions which gets triggered from the Pega OOTB/Engine level, the Application Developers doesn't have any control nor can customize them. We should have a STANDARD to display the relevant UI Error Messages to the Users whenever any Exception happens.
Thanks
Hari