Book Image

Rapid Application Development with OutSystems

By : Ricardo Pereira
Book Image

Rapid Application Development with OutSystems

By: Ricardo Pereira

Overview of this book

OutSystems is a software development platform that speeds up the build phase by abstracting code and making almost everything visual. This means replacing textual language with visual artifacts that avoid lexical errors and speed up code composition using accelerators and predefined templates. The book begins by walking you through the fundamentals of the technology, along with a general overview of end-to-end web and mobile software development. You'll learn how to configure your personal area in the cloud and use the OutSystems IDE to connect with it. The book then shows you how to build a web application based on the best architectural and developmental practices in the market, and takes the same approach for the mobile paradigm. As you advance, you'll find out how to develop the same application, and the great potential of reusing code from one paradigm in another and the symbiosis between them is showcased.The only application that'll differ from the application in the exercise is the one used in business process technology (BPT), with a focus on a common market use case. By the end of this OutSystems book, you'll be able to develop enterprise-level applications on the web and mobile, integrating them with third parties and other systems on the market. You'll also understand the concepts of performance, security, and software construction and be able to apply them effectively.
Table of Contents (21 chapters)
1
Section 1: OutSystems 101
5
Section 2: The Magical Path of the Backend
10
Section 3: Create Value and Innovate with the Frontend
16
Section 4: Extensibility and Complexity of the OutSystems Platform

Summary

In this chapter, we learned how client-side logic works, about the available artifacts, and how to combine them to obtain the behaviors intended by our actions in our frontend.

We learned what screen actions, Client Actions and data actions are and looked at the concept of variables in the context of Client Actions how to create logic in Client Actions and the properties of the action attributes.

We should never forget the following: screen actions are defined at the screen level, Client Actions are defined at the module level and run on the client side, and server actions are defined at the module level and run on the server side!

Something very important to remember is this: whenever possible, abstract and isolate the manipulation of our data in data actions or aggregates so that we can better control their integrity (since these calls are asynchronous).

As we can see, we were able to develop code in a super-intuitive way, with little scope for errors (the typical...