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 had an overview of how BPTs and Light BPTs work, as well as how to implement each of these models.

We also saw the functioning of Timers and their implementation.

Furthermore, we realized that all of these three models are asynchronous activities, that is, they do not occur at runtime; rather, each of them requires a trigger to run.

We detailed the main differences between them and what their purposes are, and got a brief idea of some scenarios in which each one of them should be used.

In the final part, we saw how we can monitor Processes and Timers in Service Center and what information is available to us.

The purpose of this chapter is to highlight that we do not need to process all the information in real time if this is not necessary, thus improving our control of Timers and Processes life cycles, performance, and data robustness.

The asynchronous capabilities of the platform were left to the end of this book because it is a more complex...