Often, I want to get a list of all espaces with broken and/or missing references.It would be a nice feature to have a combobox on top of the espace and extension list which allows to filter based on status- all- all ok- missing references- broken references- missing & broken references

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.

Recently I had a problem when updating the OutSystemsUI library, the version I updated had a bug. As I continued development, I only later realized that there were some misbehaving components, and I soon suspected the OutSystems UI update. This way I had to go back several versions of my application, to get back to the last version of OutSystems UI, without any problems. This can happen with any library, and without more serious scenarios. There doesn't need to be many versions available to choose from, I believe that between 3 and 5 would be enough.

In some projects and when refactoring some logic, we can leave some variables that are only assigned and never used. The idea would be to improve TrueChange to show a warning saying exactly that. "Local Variable is assigned but never used"

No one have doubts about that aggregates are very powerful but in lot of cases the Simple Queries do the same and are more appropriate.The main reasons for this idea is this post . And I just passed to an Idea to know how much developers agreed with this so Outsystems can bring back Simple Query since the code is already there.Thanks and Version 9 is awesome!

Need to be able to show a total footer at the bottom of record list widgets (Table Records & List Records) and the functions necessary to calculate totals, etc.

OS11 can connect with SAP using SAP Group Logon, but that is not available on ODC. On ODC only SAP Direct Connection is available. It's important because many clients only have SAP Group Logon active in Production environments for load balancing.

While using expressions in Service Studio, it would be useful if the suggestions automatically select the correct Null function if I type "null", depending on the context.

When calling a service action, the platform seem to internally set a fixed 100 seconds timeout on the request, so if the action takes longer then that, a "time out" exception is raised on the "Client side" but the action will keep running on the "server side".I'm not sure if i'm missing a setting here, but in case i'm not, my suggestion would be to either raise the 100 seconds timeout or make it configurable when calling service actions.

Hi,I would like to suggest that it might be helpful if Service Studio alerts when using preparation data on screen actions, which increases hugely the view state and it would be aligned with the performance best practices .