As an Solution developer/End User Experience Nerd
I want the error messages which MooD outputs to the web to be more "human readable" and (if possible) even accessible to me as a developer (so that I can translate them into whatever format my user base is most likely to understand). Example:
Current format of error message from a synchronizer group running and failing over the web:
Upload file and execute SAT panel: Type 'Salamander.Core.UI.Forms.ExceptionList'1[[System Exception, mscorlib, Version=126.96.36.199, Culture=Neutral, PublicKeyToken=b77a5c561934e089]]' in Assembly 'Salamander.Core, Version=188.8.131.52, Culture=neutral, PublicKeyToken=9a07d7c46ab16203' is not marked as serializable.
Preferred output format (example):
Error in executing synchronizer group "Import project reports" - failed to run synchronizer "Import project report": Missing information on Element Name on cell A113
Error in executing synchronizer group "Import project reports" - failed to run synchronizer "Import project reports": Unable to write new elements of type "project reports" due to lack of user rights.
So That deployed solutions give the end users useful feedback on which things they have missed vs things we as solution developers vs things "sys admin" have missed.
Benefits Less time spent in "undirected" trouble shooting, better ability to educate end user base, higher experience of "control" for the end user base.
- Improved "human readable" error handling when throwing errors to web solution.
- (OPTIONAL) Ability to edit error messages (preferrably through tokenised input) so that they can be put in a language adapted to the user base.
Customer / Originator LFV
Priority Mid, optional feature of editable error messages - low.
Please sign in to leave a comment.