Spanish Version
For a long time, my go-to solution for error handling was probably the same one most of us use: Send a notification with the input JSON and the corresponding exception. Functional? Yes. User-friendly? Not at all. 😬
Instead of solving the issue, it often sparked a new conversation just to translate what had gone wrong.
I decided to break that cycle. I realized my technical solution wasn’t solving the human problem. The end user shouldn’t need to be a JSON expert to understand what failed.
So I rolled up my sleeves. With the help of my trusted AI LLM (you can call it Gemini, Copilot, ChatGPT…), I challenged myself to find a better way.
I built the logic using Groovy, and what happened next felt like magic: That messy, cryptic JSON was transformed into a clean, beautiful HTML report ✨.
Now, instead of a wall of technical text, the user receives an email with a clear list of fields and a well-organized table. They can instantly see the data they submitted and the exact error message — no translator needed. 🧠📬
The benefits were immediate:
✅ Crystal-clear communication: Users instantly identify the issue (wrong data, app error in JDE, etc.)
✅ Fewer “What does this error mean?” questions
✅ A more professional image: Shows you care about user experience, even in tough moments
✅ Super easy to implement!
And because good things are meant to be shared, I’ve prepared a free package with the Groovy code and a sample Orchestrator so you can plug it into your projects today.
📥 Download it for free here
You only need add the orchestrator to the Error Handling put the input JSON, Exception Message and Notification Subject
Now instead of this
Get this
Let’s stop thinking only about whether automation works, and start thinking about how users experience it — that’s what truly makes the difference.
Now I want to hear from you: 👉 What’s the most “creative” or funny complaint you’ve received from a user about an automatic error message?