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

Using Service Center logs to support troubleshooting

We can often get errors and we don't quite know where they occur or where to start investigating.

A very interesting way to have something to start with and be more effective and quicker to find out where the errors are is through the logs generated automatically by the platform.

Remember in Chapter 7, Exceptions Handling, we talked about exception handlers? Well, it is at this point that we thank them for their existence, as if they have the option of Log Error as Yes it will allow us to obtain the error information.

Tip

These errors are caught in the debugger when the flow enters the exception handler and exits the predicted flow. By default, these errors enter the most appropriate exception handler with their context. For example, an error caused by writing to the database is caught in the exception handler dedicated to database exceptions. If it does not exist explicitly, the error is handled by all exceptions...