Much like OutSystems abstracts code into visual drag-and-drop nodes and components, have a similar abstracted visual language for creating advanced SQL queries.

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.

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 :)

Currently, updating a single entity attribute in OutSystems often involves retrieving the entire record, modifying the required attribute, and calling the Update Entity action. It would be useful to have native partial update (PATCH-like) functionality, allowing developers to update specific attributes using the Entity ID without retrieving the complete record or writing Advanced SQL. Benefits: Reduce unnecessary database reads. Simplify development and improve maintainability. Prevent accidental overwriting of unrelated attributes. Potentially improve database performance.

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.

Currently, when dealing with complex data models, managing the Entity Diagram in Service Studio can be tedious as entities and relationship lines easily overlap and cross over each other. I would like to suggest two main improvements for the Entity Diagram canvas: Smart Auto-Rearrange: A button to automatically reorganize the positions of all entities in the active diagram to prevent them from overlapping each other. Orthogonal/Straight Relationship Lines: The ability to render the connection arrows as clean, straight, or 90-degree orthogonal lines (instead of the current diagonal/curved style) so it is much cleaner and easier to trace for documentation purposes.

1) Allow relevant concepts in a comment to be highlighted in bold. 2) Add change tracking to comments, including a timestamp and the user ID of the person making the modification.

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

As we are now having folders everywhere, please do the same for service studio main screen. This way applications can be grouped by context.