It would be nice to have a button on the aggregates to switch the join direction between the entities. This is because, if we have a lot of entities and we need to switch the join to obtain the correct data, we will need to go through an extensive list, find the entity and then do the same on the other side. Here is a mockup as an example.

On the OutSystems version 11.10.16 Aggregates tend to be difficult to read, since both Sources and Joins areas are very small:Furthermore, the combobox and inputs in the "Test Values" tab are very small and it is not possible to see the chosen values properly (static entities values or text values):It would be great if the vertical space in Sources and Joins were increased and the spaces of "Test Values" could be increased so that the developer could be able to see what he is choosing or writing.

Collation is a problem in sorting when you have characters like "ÅÄÖ". Those are sorted incorrectly.Platform thinks that those ÅÄ = A and Ö = O , but that is wrong. Those should be after Z ....TUVWXYZ ÅÄÖIdea how to fix this:possibility to set collation in lifetime on platform level (this sets platform default level collation)possibility to set collation in application (module properties > overwrites platform level collation)When user sets collation either ways, platform adds automatically database searches  (SQLs + aggregates) COLLATE clause after TEXT attributes.Maybe add possibility to remove use of it in aggregates (checkbox: use collation [x]).SELECT {Sorting}.* FROM {Sorting} WHERE {Sorting}.[Sortedcolumn] LIKE '%'+ @SearchString + '%' COLLATE Finnish_Swedish_CI_AS ORDER BY @TableSort COLLATE Finnish_Swedish_CI_ASAnother possibility is to set collation on server or directly database, but this is probably not possible in AWS? See community discussion and current workaround: https://www.outsystems.com/forums/discussion/63776/incorrect-sorting-of-scandinavian-characters/#

"setCurrentLocal" is an action that allows us to choose the language of the application. For example, if I want the application's local language to be Portuguese, I would put "pt-PT" in the input of this action. Once we choose the language, it would be interesting if the built-in functions of OutSystems returned the output in the chosen local language, in this case, Portuguese. For example, using the formatDateTime(date, "ddMMMMyyyy") function would return "01Julho2023" instead of "01July2023" if the application's local language is set to Portuguese. This way, we wouldn't have to translate the function's output.

OutSystems already provides entity relationship diagrams after creating entities, but it would be even more useful to have a simple, editable flowchart feature to visually represent the data or process flow throughout the project. This feature would help developers and teams easily map out how data moves between screens, actions, and entities without needing to use external tools like Draw.io, Miro, or Lucidchart. It would be a quick way to narrate workflows or data movements directly within OutSystems during client discussions or internal planning. Example: For instance, consider a project with entities like Customer, Order, and Invoice. A built-in flowchart could show how data flows: Customer → Order → Invoice → Payment , and developers could edit or annotate the flow to demonstrate logic or upcoming changes. This visual approach would make it easier to explain ideas, document workflows, and align technical and non-technical stakeholders all within Service Studio.

The option to remove unused dependencies by eSpace is realy great! But I think it can be implemented to Applications at all. It wold be nice to have an option in ServiceCenter to remove all unused dependencies by an Application.

Hi all,I would like to request an addition to the configuration tool/ server.hsconf.More and more we run into customers hosting there OutSystem platform in Azure resources segmented in a dev/tst, acc and prod subscriptions, resource groups, ect…. Each segment with its own servers, scale sets and a SQL managed instances to provide database needs. With an Azure Active Directory tenant to provide users authentication for the platform, and no “real” AD in sight.On the application side this handled beautifully by OutSystems. But in the situation above we are currently forced to use SQL authentication because there is no option to manage user authentication for the back end via ADD.Can you please add the option to use ADD users, service principals and/or managed identities as an authentication mechanism in the connection between the platform and an ASMI?! This for manageability and security benefits.Thanks in advance!

There is a great subdomain "charts.outsystems.com" that explains how the charts can be customized. However, I think it is missing some crucial information. For example, there is the following page that explains different chart types and how to implement them: https://charts.outsystems.com/samples/chart-with-multiple-chart-types There is a warning there implying that it is not possible to do a "step line chart" with the config options of the chart block (see attachment): "Currently, it's possible to convert any series to the following types: Line, LineSpline, Area, AreaSpline, Column, Bar and Pie." In reality, it is actually possible to do this with addon extensibility configurations; i.e. with a certain client action ( SetHighchartsSeriesConfigs ) from the Charts library, as partly explained in this video: https://www.youtube.com/watch?v=uzNnX7oqhNY It would be great if such information is also added to the https://charts.outsystems.com/ subdomain.

90% of the times I use the 'ListIndexOf' function I follow it up with some variation of: MyVar = MyList[ListIndexOf.Position].val It would be helpful if there was a 'ListFind' function (client and server) that returns the element in that position, and not only the index.

Sometimes you have two buttons that you want to have as the "Default" button based on different conditions. For example, if you have a screen with basic and advanced search, you want the "Search" button to be the default button, but you have a different "Seach" button in the If. J.Ja