Hi, As a secutiry increase to our applications it would be nice if we could assign roles (former permission areas) to screen actions and user actions. This way users that didn't have permission to run them, would never be able to use firebug and other tools in order to activate buttons that trigger the action and we wouldn't need to always be "asking" in every action, if the user has permission to run it. Another benefit would be, by unchecking the anonymous role, we could also automatically know if a session timed out, without having to "ask" that also in every action. What do you guys think?

Hi,Would be great for troubleshooting if the runtime values used in query parameters were also logged in the error log text. The tenant Id would also be a good idea to support multi-tenant scenarios.Of course this would only be applicable to query related errors and they could be shown in the log in a very simple manner like:"TenantId = 1Param1 = 123Param2 = "Text"Error in advanced query  (...)"This would allow much faster debug in Service Studio.Cheers,Hermínio

Due to maintenance proposes, it would be nice to force the application users logout.It would be nice to have available one option to clear all the application user sessions and force the users to login.

Hi OutSystems Team, It would be incredibly valuable to introduce a feature in Service Studio that allows developers to select and manage specific versions of producers when configuring dependencies. This enhancement would align with the familiar workflow of Visual Studio’s package manager, empowering teams with precise control over which producer versions their applications depend on. Key Benefits: Stability & Reliability: Locking dependencies to verified versions minimizes the risk of unexpected changes or regressions. Simplified Rollback: Facilitates quick reversion to previous versions if newer updates introduce issues. Improved Developer Experience: Mirrors established practices in other development environments, making dependency management more intuitive. Collaboration Support: Promotes consistency across teams by ensuring uniform dependency versions, reducing integration conflicts. Please find below a mockup illustrating the proposed implementation.

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.

Create a grid component that has advanced features like dragable columns, native grid editable fields, filter options, resizable columns, better sorting.  The Kendo UI grids are a good example.https://demos.telerik.com/kendo-ui/grid/index

In O11 , when you copy logic, screens, or any other elements from one ( source ) module and paste them into another ( destination ) module, any external references used by the copied elements of the source module are automatically added to the destination module. This is quite helpful sometimes, especially when you are trying to copy screens/logic from one application to another (I had to do this a bunch of times in the past, for various reasons). However, in ODC , this is not the case. Once some elements (referencing some dependencies) are copied from one module to another, none of the references are automatically added (unlike in O11 ). This results in hundreds of errors sometimes, which could be reduced to just a few if automatic dependency referencing worked like in O11 . It would be great if this automatic dependency referencing is added to ODC as well, unless there's a valid reason for excluding this feature in ODC . Thanks in advance, looking forward to hearing about others' experiences and feedback :)

Add Environment name whenever hovering on the opened service studio in the windows task bar in order to distinguish between environments whenever opening muti environments to minimize conflicts.

Hi OutSystems Team, In the OutSystems Support channel , implement a time tracking rule based on SLAs , as some clients use this metric and end up counting elapsed time, which is incorrect. When the issue remains on the client's side, the SLA should not count, or if the client "disappears" and does not close the ticket, this time should also not be counted. This helps OutSystems protect itself from misunderstandings and potential penalties (fines) from the client, which could lead to misinterpretations. The current view considers tickets as either open or closed. Time tracking helps with OutSystems' resolution metrics and protects the company from other interpretations and metrics. It would be beneficial if this data were exported along with the ticket ( spreadsheet generation ).

When we have the need to invoke the same entity twice in advanced queries we have the absolute need to put an alias in one of them, to distinguish them. The thing is that service studio puts a warning to it if you use Alias.* ... Perhaps one could assign an alias to the output structure?