In OutSystems, each Email Web Screen is counted as an Application Object (AO), and AOs directly impact licensing cost. In many enterprise applications, we create multiple Email-related Web Screens (for templates, preview, configuration, triggers, admin panels, etc.), which can significantly increase the AO count.
My idea is to replace most Email Web Screens with an Extension-based approach.
Instead of building multiple Web Screens for email management, we can:
Handle email generation, templates, and logic inside an Extension
Store email templates and configurations in the database
Trigger emails via server actions or APIs without requiring dedicated UI screens
How this helps customers:
✅ Reduces AO consumption by eliminating multiple Email Web Screens
✅ Lowers licensing cost for large-scale applications
✅ Centralized email logic in one reusable Extension
✅ Better performance and maintainability for complex email workflows
✅ Reusable across multiple modules and applications
Example Use Cases:
Transactional emails (OTP, notifications, approvals)
Bulk marketing or system alerts
Multi-tenant email templates per client
Configurable email rules without UI-heavy admin screens
This approach can help enterprises optimize licensing cost while still keeping email functionality flexible and scalable.