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)
1
Section 1: The Basics
6
Section 2: Building Your First App
11
Section 3: Leveling Up Your App

Seeing it – developer pages

It's often important to have a complete and unobstructed view of the data within your application. This statement sounds simple and obvious, but sometimes, it isn't quite that easy. Many times, the core pages and data grids you will be asked to add to your application will constrain your data over certain criteria. Perhaps an XPath over a certain attribute or combination of attributes, for example. And, depending on that data and application, it could become difficult to get a complete picture of your entire dataset. The concept of a "developer page" is just that complete, unobstructed view of a particular dataset. Think of a data grid without any XPath applied to it where all (or almost all) attributes are visible.

Sounds like a great idea, right? In many scenarios it is, yes. But, like all things, it's important to always keep the context in mind. For example, what data are you making available to be viewed? Is it personal...