I the Rest configuration in Service Center should have the same fields that are in Service Studio. When I configure the Authentication in Service Studio appear the field Scopes But in Service Center this field doesn't exist You should have the same fields in both places

 Proposal In Lifetime, when we do a promotion to another environment, we have the ability to add custom steps between environments to create a pipeline. In these custom steps we could connect to AI mentor, BDD tests, another test tolls or even a custom application. In a simple vision this could be a URL parameterisation and a result that is expected. Added value to OutSystems customers 1. Avoid to spend more money in 3rd party tools and devops engineers to create custom pipelines (Azure devops, Jenkins, ...) 2. Increase speed in delivery because all steps are inside our platform 3. Simplified and unified release process.

Breaking into tech is tough, especially for entry and mid-level developers who need experience but struggle to gain it without opportunities. What if we created a community-driven challenge where developers build real, useful applications or Forge components that benefit the OutSystems ecosystem while advancing their careers? How It Works Participants can compete solo or in teams, allowing both independent developers and collaborative groups to showcase their skills. Categories include: Application Development – Build fully functional apps that solve real-world problems. Forge Components – Create reusable components that improve development efficiency. UI/UX Enhancements – Design intuitive, accessible interfaces that elevate user experience. The event fosters friendly competition, networking, and hands-on learning. Winners (or standout contributors) receive certification vouchers, accelerating their careers. Why It Matters Bridges the experience gap: In the US, it's difficult to find work without prior experience—this provides tangible projects to showcase. Boosts OutSystems adoption: By targeting aspiring tech professionals, this event could introduce new talent to the platform and generate buzz in the job market. Grows the Forge & community: High-quality contributions enhance the OutSystems ecosystem, making it easier for everyone to build better apps. Additional Challenge Features Mentor guidance from experienced OutSystems developers. Themed challenges (e.g., accessibility, AI integration, automation). Judging criteria based on innovation, impact, usability, and scalability. This initiative could be a game-changer for developers looking to break into tech while also strengthening the OutSystems brand and community resources. Would love to hear thoughts from the community on this!

It could be useful the existence of a kind of widget , similar to the page count richwidget, focus to the creation of reports (with auto pagination, Header repetition, SusTotal, total, ...) to be printed .

When we do a merge with two OML, would be useful to have a search box to filter whats been shows in Compare and Merge box.

 Problem Debugging Reactive screens can be difficult when developers need to understand the current state of local variables, client variables, input parameters, screen data, and browser storage. How this suggestion can help A dedicated Reactive Debug Panel would give developers a centralized view of the screen state during runtime, reducing the need for temporary labels, console logs, or manual debugging workarounds. Implementation example Add a debug panel available during preview/debug mode showing: Current Screen: RequestDetail Local Variables Client Variables Input Parameters Data Actions Local Storage Session Storage The panel could allow developers to inspect values in real time and optionally copy them as JSON.

Hi guys, we use something similar here, but we do it manually.We know that good architecture is very important in our projects. It is a wonder if we could see in our tree view the actions and other dependencies with the same color they were classified in the discovery tool.For instance: library modules can have the default icon green and core modules a default color orange.So, when you are in a green module and try to consume an action from the core module, you can see you are doing something wrong directly on your tree view and safe time to run the discovery and check this later.Even the developer who is not so expert in 4LC can help to keep the architecture in the right lines.

Moving forward would there be any plans to support rollout of web applications in the form of Progressive Web Apps https://developers.google.com/web/progressive-web-apps/ https://developers.google.com/web/showcase/This allows no installation, fast web applications, service worker, greater productivity and SEO.

[Service Studio]If you are developing a Big Action full of Sub-Actions all with plenty of mandatory entry points, it would be useful to have a new Sub-Folder area where no Validations were made on the "Work in progress" Actions/Functions that way you could publish the eSpace until all the new actions could be used.That area would also include Finished and Validated Actions with no usage anywhere else within the eSpace

When are we gonna have a option to access the metadata from a OML file?In my case i need to generate report for instance, all screens and their input/output parameters to a given Espace.This information exist only in the OML file. Therefore only the Service Studio is able to open it. Maybe some component which could translate it?I think its important feature for enterprise grade Frameworks like Outsystems.With best regards,Slavi Popov