Even the code of the best OutSystems developers isn’t always perfect and might have a glitch. For any developer, in whatever technology they’re working, it’s not easy to write code that captures all possible exception cases. And we’re not only taking about access errors, network issues, … but also invalid inputs, incomplete or corrupt data, … Fortunately, OutSystems already covers the basic error handling out of the box but a solid application needs more.

Duarte explained how to implement error handling for the different use cases. He showed that building a robust application that on the one hand give the developer enough information to find the root cause of an issue, and at the same time, alert the end user with a readable, non technical error message does require some thinking and coding.