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

Modeling data

In data modeling, we deal with the relationships between Entities. As an example, a support ticket request from a help desk application (already setting the tone for the application that we are going to develop in the exercise) will have several fields, and not all of them will be in the same Entity. The Entity that supports the ticket must have its primary key, description, who created it, when it was created, who updated it, when it was updated, and its status. If we analyze it carefully, we can model this data through relationships with other Entities. For example, who created and who updated the record in the Entity can be foreign keys that refer to a user Entity (which the platform already makes available automatically, synchronized with the user provider). The state can be a foreign key that references a Static Entity where we will have all the states. These are examples of one-to-many relationships:

Figure 5.3 – One-to-many view in...