Search icon CANCEL
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Rapid Application Development with OutSystems

You're reading from   Rapid Application Development with OutSystems Create applications with OutSystems up to seven times faster than with traditional technologies

Arrow left icon
Product type Paperback
Published in Jan 2022
Publisher Packt
ISBN-13 9781800208759
Length 402 pages
Edition 1st Edition
Arrow right icon
Author (1):
Arrow left icon
Ricardo Pereira Ricardo Pereira
Author Profile Icon Ricardo Pereira
Ricardo Pereira
Arrow right icon
View More author details
Toc

Table of Contents (21) Chapters Close

Preface 1. Section 1: OutSystems 101
2. Chapter 1: Exploring the OutSystems Platform FREE CHAPTER 3. Chapter 2: Components, Tools, and Capabilities 4. Chapter 3: Starting Work with OutSystems 5. Section 2: The Magical Path of the Backend
6. Chapter 4: Using Your Modules to Simplify and Encapsulate Your Code 7. Chapter 5: Modeling Data by Using Entities 8. Chapter 6: Server-Side Logic 9. Chapter 7: Exceptions Handling 10. Section 3: Create Value and Innovate with the Frontend
11. Chapter 8: Reactive UI Development 12. Chapter 9: Using Mobile Patterns for Fast Mobile UI Development 13. Chapter 10: Client-Side Logic 14. Chapter 11: Local Storage and Data Synchronization 15. Chapter 12: Debugging and Troubleshooting Mobile and Reactive Web Apps 16. Section 4: Extensibility and Complexity of the OutSystems Platform
17. Chapter 13: Designing the Architecture of Your OutSystems Applications 18. Chapter 14: Integrating OutSystems with Your Ecosystem 19. Chapter 15: BPT Processes and Timers – Asynchronous Tools in OutSystems 20. Other Books You May Enjoy

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...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at €18.99/month. Cancel anytime