In lastest OS version (10.0.815) we saw that there are a new area with the recently opened modules in our environment. Could be nice if we have the hability to pick eSpaces as bookmark and look at them in a new separator next to Recent Modules :)Bookmarks list:Application (the star define what is set as bookmark or not):Thanks,César

The AI Mentor Studio is already very powerful but we always look for new ways to make it even more helpful. Here are some suggestions of improvement: 1. New Filter for Changed Elements When applying a filter to show alerts analyzed within the past two weeks, we sometimes still see alerts for elements that haven’t been modified in years. While older alerts are important, they should be reviewed in different contexts. A filter that displays only elements that have been actively changed within the selected timeframe would improve efficiency. 2. New "Brainstorming" State Some alerts involve complex issues where immediate fixes could pose risks. While the "Remind Me Later" status helps, some alerts need to be reconsidered at a later stage in the project without requiring monthly snoozing. Introducing a "Brainstorming" state would provide a clearer distinction for alerts that require further discussion before resolution. 3. New Filter for Unassigned Alerts Currently, users can filter alerts assigned to specific users, but there is no direct way to view alerts that have not been assigned to anyone. While exporting alerts to Excel allows for this, having an in-app filter to display unassigned alerts would be much more convenient and efficient. Hopefully these suggestions will be taken into consideration :) Cheers, Vanessa Espírito Santo

Currently, OutSystems Service Studio does not support changing: The editor font family and font size in the Service Studio interface (Toolbox, Widget Tree, Properties panel, etc.) The overall UI scaling for high-resolution displays The language of the Service Studio interface (menus, property labels, and tooltips remain in English) While we can fully style our application UI, we cannot customize how the Service Studio development environment itself looks or behaves in terms of text visibility and localization. Most leading IDEs (like VS Code, Eclipse, IntelliJ, Android Studio) support: Font and UI customization Localization of interface into various languages By enabling these in Service Studio, OutSystems becomes more developer-friendly, more inclusive and better suited for international markets It would create more impact like Increased developer productivity and satisfaction Compliance with accessibility standards Easier onboarding of non-English speaking teams

When we create a screen or action some time we create a lot of local variables. It would be cool if we could select all these variables and with right click create a structure with them keeping the data type of each variable.

Hello OutSystems Community, Building on the theme of making Application Objects (AOs) more visible in the Forge, I have another simple but powerful suggestion. The Problem: When we search for assets, the results page shows a list of component "cards." Each card displays useful info like ratings and download counts. However, to see the AO count, a critical piece of information for assessing impact and cost, we must click to open the asset's detail page. My Idea: My proposal is to display the AO count directly on the asset card in the search results list. This could be a small and clean UI element, perhaps next to the download or rating indicators. It would give us immediate, at-a-glance information for every component on the page. For example, the card could look something like this: [Asset Name] Rating: ★★★★★ (25) Downloads: 2.5k AOs: 8 <-- New information here Benefits: Instant Comparison: Allows developers to immediately compare the AO "weight" of different components without ever leaving the search results page. Improved User Experience: Reduces clicks and streamlines the workflow for finding the right asset, making the Forge much more efficient to browse. Works Perfectly with Filters: This visual aid would be a perfect companion to an AO filtering feature. We could filter for a range (e.g., 1-20 AOs) and then instantly see the precise count for each result to make the best choice. This small UI enhancement would have a huge positive impact on our daily workflow in the Forge. Thanks for your consideration.

It would be great if OutSystems could collaborate with partner companies to offer internship opportunities for newcomers in the community. While the OutSystems Developer School already helps many beginners learn the platform, having a structured internship program would give them valuable real-world experience and a chance to apply their knowledge in live projects. Through this initiative, OutSystems could also recommend top-performing learners or certified developers to partner companies, helping new talents get recognized and boosting their confidence to grow further in their OutSystems careers.

In OutSystems, when a user tries to access a specific page without an active login session , they are redirected to the login page. However, after successfully logging in, the user is not redirected back to the original URL they attempted to access. Instead, they are sent to the default portal or home page. This behavior can be inconvenient from a user's perspective. Users are forced to manually navigate back to the desired URL, which disrupts their experience, especially in scenarios where deep links or bookmarked URLs are involved. Proposed Solution: Modify the authentication flow so that if a user is redirected to the login page due to an inactive session, their original URL is preserved. After a successful login, the user should be redirected to the URL they initially attempted to access, rather than the default portal or home page. Benefits: Improved user experience and satisfaction. Enhanced support for deep links and bookmarked pages. More intuitive behavior aligned with common expectations for web applications. This enhancement would make OutSystems more user-friendly, particularly for scenarios requiring frequent logins or when users access the application via shared links.

Hi all, As like Export action to image, it's better to have an option for exporting Entity into image, which contains attributes and data type of the attributes in an entity as an image. Regards Murali

 Problem Statement In ODC, a Client Secret is required in virtually every scenario where an app communicates with external systems or calls ODC Management APIs programmatically: UsersManagement (Forge) → ODC User & Access Management API External IdP integration (OIDC) → Azure AD, Okta, etc. ODC REST API calls → Portfolio API, and others External service integrations → Salesforce, MS Graph, etc. The current behavior is that Client Secrets expire every 90 days by default (maximum 2 years), and renewal is only possible manually through the ODC Portal. Root Cause of the Issue This is not merely an inconvenience — it is a structural constraint that breaks the promise of full automation in ODC-based services. Here is why: ① No programmatic renewal path exists There is currently no Management API endpoint to rotate or renew a Client Secret. This means that no matter how well-automated your app logic is (e.g., a Timer-based user management flow), the secret renewal step always requires direct developer intervention. ② Expiry creates operational risk at scale In production SaaS or B2C environments running on ODC, a missed secret expiry means: All features depending on that secret stop working silently or with cryptic errors End-users are impacted before the team is even aware Recovery requires Portal access by a developer with the right permissions — not something an end-user Admin can resolve ③ The expiry cycle creates recurring developer toil Even with the maximum 2-year expiry configured, and even with calendar reminders or monitoring in place, this is manual, recurring, high-risk maintenance. It runs counter to the Low-Code philosophy of ODC: reducing developer toil and enabling reliable, autonomous operation. Requested Feature(s) Please implement one or more of the following: Option A — Programmatic Secret Renewal via Management API Add a Management API endpoint that allows an authorized app to rotate or renew a Client Secret before expiry. This would enable a Timer-based auto-renewal flow entirely within ODC, with zero developer intervention. POST /api/v1/clients/{clientId}/secrets/rotate→ Returns: new_secret, valid_from, expires_at Option B — No-Expiry Secret Option Allow trusted, internal service accounts to opt into a non-expiring Client Secret, similar to how other platforms (e.g., Azure App Registrations, AWS IAM long-term credentials) provide this option with explicit acknowledgment of the security trade-off. Option C — Secret Rotation with Overlap Window Support a dual-secret validity window during rotation — where both the old and new secrets remain valid for a configurable overlap period (e.g., 24–72 hours). This enables zero-downtime secret rotation in production environments.

When the option "Find usages in all eSpaces"  is selected, and we have more that one eSpace using the resource would be useful to have the option to select the eSpaces to be open.