Book Image

Building Low-Code Applications with Mendix

By : Bryan Kenneweg, Imran Kasam, Micah McMullen
Book Image

Building Low-Code Applications with Mendix

By: Bryan Kenneweg, Imran Kasam, Micah McMullen

Overview of this book

Low-code is a visual approach to application development. It enables developers of varying experience levels to create web and mobile apps using drag-and-drop components and model-driven logic through a graphic user interface. Mendix is among the fastest-growing platforms that enable low-code enthusiasts to put their software ideas into practice without having to write much code, and Building Low-Code Applications with Mendix will help you get up and running with the process using examples and practice projects. The book starts with an introduction to Mendix, along with the reasons for using this platform and its tools for creating your first app. As you progress, you’ll explore Mendix Studio Pro, the visual environment that will help you learn Mendix app creation. Once you have your working app ready, you’ll understand how to enhance it with custom business logic and rules. Next, you’ll find out how to defend your app against bad data, troubleshoot and debug it, and finally, connect it with real-world business platforms. You’ll build practical skills as the book is filled with examples, real-world scenarios, and explanations of the tools needed to help you build low-code apps successfully. By the end of this book, you’ll have understood the concept of low-code development, learned how to use Mendix effectively, and developed a working app.
Table of Contents (18 chapters)
Section 1: The Basics
Section 2: Building Your First App
Section 3: Leveling Up Your App

Getting a handle on those errors – error handling

Even with your best efforts of trying to be predictive and defensive in your application, errors and issues will still arise – it's inevitable. And that's okay! There will always be situations and scenarios that you just are not able to account or plan for. You can try, but you will never release a single piece of functionality… ever. Generally, it's best to account for the most likely scenarios and then weigh up the likelihood of other possibilities, even perhaps performing some level of risk analysis. Ultimately, however you end up determining your functionality, you'll want some level of error handling on the most important or sensitive parts of your logic.

If you're not entirely sure of ALL the possible scenarios where something may go wrong in a particular process, you can always set the error handling on an entire process when it is called from a sub-microflow. That way, if an...