Product Releases
and Updates

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
The latest Mobile Apps Build Service (MABS) version will progressively roll out starting today. Safely submit your mobile apps to the App Store and Play Store throughout next year with MABS 8, which uses iOS 15 SDKs and Android 12 with the API level 31. Before updating MABS, you need to update all supported plugins to their latest versions. For more details, check the MABS 8 release notes.
Make the best use of health and fitness data gathered from smartwatches in your mobile apps with the Health & Fitness plugin. Through the Healthkit and Google Fit APIs, you can access, read, and write this data and explore the countless use cases that benefit from it. There are already 16 different variables for you to explore, and many more are coming soon.
You can now group columns under a single header, and create multiple column levels on Data Grid Reactive. Grouped columns improve readability and offer the ability to expand and collapse columns. Server-side pagination is also available to reduce the initial load time of large data sets and instead load them on demand. Check out our working samples and documentation to learn more about it!
You can now easily add polygons and polylines to your map. Customize the look and feel of these shapes and even allow users to interact with them. Check our working samples and respective documentation, and stay tuned for more features we’ll be adding to this component.
Mac users can now use Service Studio natively on macOS! Check out the beautifully redesigned user interface, improved interactions, and themes - including a dark mode. This version also includes new text editors with syntax highlighting, autocomplete, find and replace, line numbering, support for ES6, and much more.
Easily find the most popular screen templates for both Reactive Web and Mobile apps, now displayed in a single discoverable list within the OutSystems UI framework. With improved UI and clearer, more descriptive language, the most widely used templates have been combined for improved findability, allowing you to customize them according to your use case and speed up development.
With Integration Builder, we’ve drastically decreased the time and complexity integrating with common systems of record like SAP, Salesforce, Dynamics, or Sharepoint. Access data and services from these external systems in a matter of minutes with a simple, wizard-based experience. Integration Builder does the heavy lifting for you, ensuring connections are secure and scalable while following architectural best practices. Configure integrations once, and then reuse them multiple times in your OutSystems apps. Learn more about Integration Builder here.
View, select, and edit large amounts of data in a familiar interface and sort data by parameter with Data Grid Reactive, a component built for Reactive Web apps. With this component, you can now create enterprise-grade interfaces for Reactive Web apps, a more suitable and time-effective option than designing a custom solution every time you need to manipulate dense datasets.
It’s now easier to read the technical debt analysis chart in Architecture Dashboard with our new formula approach. Until recently, our analysis chart showed the distribution of technical debt based on module or application count, and their agility. This chart led to difficulties in reading, since a big application full of technical debt marked as red (for low agility) is represented in the same size as a plugin that would normally be small and green (for high agility). This would end up even more complicated when the trend didn’t match the visual amount of agility. Our new formula approach considers the actual size of a module or app in the factory, delivering an improved perception of your factory's technical debt trend.
Easily trace and solve publicly exposed endpoints with this new security pattern. In Reactive Web and Mobile apps, server actions used in the logic of a screen are automatically exposed as REST Endpoints, enabling client-side consumption. If a screen is marked for anonymous access, all consumed server actions will be exposed without authentication. Sometimes, while reusing actions on different screens, you might end up exposing something that you did not intend to. This pattern helps you trace and solve those cases with ease!










