When you have an exposed REST API with a lot of methods, it would be useful to be able to group them in folders, like you can do with actions. Same for large consumed APIs, would be useful to group the consumed methods in folders.

When working on a ticket we often touch multiple parts of a module while experimenting. Before publishing, we need a clear overview of: 1. Which elements changed since the last publish 2. What exactly changed (diff vs. last published version) 3. The ability to revert/discard specific changes Please add a built‑in “Changes since last publish” view in Service Studio that: 1. Lists all modified elements in the module. 2. Shows a diff for each element vs. the last published version. 3. Allows reverting changes per element. This would help avoid accidental publishes of unwanted changes and make OutSystems development closer to common Git/.NET workflows.

Be able to create a unit test for a Server / Service / Client (?) / Screen (?) action that shall be executed without developer intervention, for regression purposes.

Hi Outsystems teams, Since the OS charing static entity for 1 AO, to save some cost for clients, in many projects, we hardly use static-entity even though it should use Static-entity for many purposes. We need to use alternative ways to implement the static concept, like using structure, hardcode... This led the development become more complex in design, implement, and more hard-code used, but we can't spend 1 AO for just 5 records stored in static-entity like status, type, etc... Actually many projects opened just to Delete all static entity from the code to save cost. From begining we've learnt how to use Static entity, and in real project we need to learn how to not use Static entity to save AO, this make static entity very dead. Can Outsystems consider to lower the price of AO somehow like count it 1 AO = 3 or 4 static entity, or consider make it free if there are < 10 record store in static entity, this would be a great thing for Outsystems developers and clients. Thanks :)

The new option to publish with an added message is very nice, but too often I forget to click the dropdown arrow and accidentally Publish normally. Because there is no way to add a message after already publishing, this can get quite annoying. I suggest a simple extra configuration checkbox in the Service Studio Preferences to optionally change the "with Message" option to be the default. When enabled, Normal publish should still be available through the dropdown arrow.

Provide a " Check for Updates " / " Update Now " option in both ODC Studio and O11 Service Studio , allowing developers to manually check for and install the latest Studio version . This would be useful when automatic updates don't trigger or when developers want to control when the Studio application is updated. Proposed option: Help → Check for Updates

On ODC we have a system function that pulls the App Name: It would be a good addition if we also had other App information easily available, for instance the revision/tag like GetAppRevision() or GetAppTag(). Currently the only way to get this information is to use ODC REST APIs which would need at least 2 API calls (one for token and one for the deployed asset) and all the overhead that it brings (maintaining API credentials, settings permissions, etc).

Due to the stateless-ness of External Logic in ODC, it is (among many other things) impossible to have the "server part" of SSE (server-sent events) running in ODC. There's just no way around this, so if we want this feature in ODC, it'll need to be built-in. I think extending the current event system with like a client side version would be the most logical approach. Off course, the alternative would be that existing customers keep their O11 environment running forever just to have this feature available. https://www.outsystems.com/forums/discussion/99260/sse-push-event-hub-how-to-create-real-time-notification-of-the-web-app-in-odc/

AI Mentor Studio (Code Quality) only has predefined code analysis patterns but there are many cases where custom patterns might be needed to ensure that code meets organization's specific coding standards. Here are some of the cases where custom code analysis patterns might be useful: Internal rules Validate naming conventions for various components Validate exitance of user auditing on screen actions Preventing team-specific recurring bugs Validate existence of initialization/validation logic of the actions. Like checking SQL query parameters on null values before executing query to prevent heavy executions Check query for existence of specific filters Secure proprietary frameworks Validate that API's OnBeforeRequest has appropriate security checks As a reference SonarQube has following capability Adding coding rules | SonarQube Server | Sonar Documentation The capability to implement custom code analysis patterns will make AI Mentor Studio (Code Quality) adjustable for customer's specific needs, therefore, improve overall quality of application portfolio and reduce governance effort.

Hi, I've run into this a few times. I would like to have the ability to do a simple query with an IN clause, without having to rely on advanced queries. It should accept a list of Identifier. Today we do ( from an aggregate perspective): SELECT * FROM {TASKS} WHERE id = 1 or id = 2 or id = 3 But it would be really awesome if we could do SELECT * FROM {Tasks} WHERE id in (1,2,3) This allows us to do some pretty cool stuff with Lists setc ( eg you can now shim some of the more advanced sql functionality without writing advanced queries). An example would be: myList = SELECT id from People WHERE OrganisationId = 2 SELECT * FROM {Tasks} WHERE personId = myList Which would be 2 actions, and somewhat faster/cleaner than the current way Writing an advanced query ( frowned up by my companies' best practices guide - and I've also found advanced queries tend to be annoying to manage ) Looping through myList and putting the outputs into another list, which is then passed around (this also has a few nasties - lots of DB hits (albeit small ones), and refreshing this with paging is a pain