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

Modules and application naming convention

To better identify the modules and applications we create, there is a convention advised by OutSystems for their names. This convention involves the use of suffixes, and although the suggestion is not mandatory (each one can follow its own normalization, as long as it is adequate), it is heavily used in the OutSystems world.

This convention is based on two attributes of modules and applications: their layer and their sub layer.

The following table explains the convention used today:

Figure 4.5 – Module naming conventions in OutSystems

* Nowadays, in frontend modules, suffixes are no longer used, because it is presented in the URL and is unfriendly if it has one.

** If they are modules dedicated to mobile, add an M before, such as _MCS or _MPat.

Based on the suffixes shown, the platform can correctly infer (in most cases) which layer and sub layer each module/application belongs to. This makes...