In many client projects, Pega applications call external services to access external data.
But sometimes service calls can fail and return a bulk of complex error details. The problem is that users are often non-technical and do not want to see those technical details in UI.
On the other hand, IT wants to capture those details on UI to quickly identify the root cause and start troubleshooting. Note that pulling those error/exception details by IT from a very large log file in production (which often have multiple JVMs that make it even more difficult to find) can often take many hours and delay the resolution process.
How can we balance the need between business and IT?
How can we come up with a reusable solution that can ensure consistent user experience and easier maintenance for future changes?
= = =
See attached for a solution that we designed and implemented at a client who wants to adopt it as a standard across their enterprise.
Appreciate if anyone can share any feedback or other alternative to design this common use case.