I have two needs.show ALL USERS who currently are blocked from a LOGIN.Show the most recent LoginAttempts for ALL users.Neither are these are handled well from the USERS espace.Regarding #1, the IPAddress_GetBlocks  server action can be used to quickly show ALL IP addresses which are currently in a blocked state. There should be an equivalent USERS_GetBlocks  action to return the blocking state of ALL users.Currently I would have to loop through all 8000+ users and individually call User_GetBlockedStatus  before I could know this information.Regarding #2 - the USERS espace has a public page (although it's not in the menu)  e..g https://my.environment.com/Users/GetUserLoginAttempts.aspx which allows me to quickly view all login attempts. But this doesn't work for a multi-tenant application. It only shows LoginAttempts in the default USERS module. A simple solution would be either:a) Expose the LoginAttempt  table as PUBLIC + READ ONLY; then we could easily query it.b) A new serveraction e.g . IPAddress_GetLoginAttempts  which would optionally pass the UserName/IPAddress to filter on.Our support team is frustrated at the lack of ability to easily view the recent login attempts, and this would greatly ease the situation.

When deploying from one environment to another, sometimes there are applications that have dependencies that Lifetime detects and tries to recomplie and redeploy. This is shown in the example below: In this case I have only 1 dependency, but sometimes I have more than 50 and it gets very cumbersome to have to uncheck all (as sometimes I don't want the apps to be recompiled because the change doesn't really affect them and impacts deploy times). So I'm asking for a simple "check all" and "uncheck all" boxes right above the dependency counter. Thank you.

The forge still has a content issue. Specifically there are still quite a few espaces that were clearly tests, training demos, etc that people have uploaded to the forge erroneously.Please add a "Report submission" button to the forge items so that we can report bad links.Some examples: https://www.outsystems.com/forge/component/1031/testingpopup/ https://www.outsystems.com/forge/component/1791/capp/ https://www.outsystems.com/forge/component/1046/addi-test/ https://www.outsystems.com/forge/component/1746/darss/ https://www.outsystems.com/forge/component/1427/infinious/ https://www.outsystems.com/forge/component/1631/flyfast/Clearly  none of these need to be on the forge, and should be removed.Any time someone comes by something like that there should be an easy way to report them.If there is already a method for doing this, please make it much more obvious and easy to find.

The idea is to be able to reflect back on the past and see your growth within the community from what was the opening rank you had what were your key milestones of your certifications what were the key milestones of breaking into certain ranks and overall to reflect back on your journey within the out systems community. Providing this timeline graph would be something that will be motivational for the current user as well as for anyone visiting a profile of an MVP or a champion or a mentor to see how they have grown within the out systems community.

When publishing new eSpace's between environments via oml there could be an option to choose in which application the module should be stored into instead of having to go to Independent Modules and move the module to the intended application.

I suggest to make avaliable an option to filter using a 'except'/'not' clause, on Service Center logs.As today it is, we can filter most logs in Service Center by a lot of options, making it easy to track an app/espace/message while searching for something specific...On the other hand, when you are doing the oposite, like looking through all messagens in search for something amiss or out of place, having the same app/espace appearing over and over again, makes things a lot more challenging... specially when you need to pass through pages of the same content...

More than once I've been baffled while debugging or inspecting code how something could ever work, or works like it does, when finally realizing an expression continues "below the fold". It would be nice if Service Studio would clearly indicate, using an ellipsis or arrow icon or the like, that an expression is continued on the next line. This goes for input parameter assignments, normal assignments, screen expressions etc.Example:a > 2   and a < 4Service Studio will only show "a > 2" without an indication that there's more. Then debug, and have a = 4 and try to find out why the condition fails...

Nonprofits can innovate very quickly with Outsystems, but their wallet is not nearly as large as the enterprise organizations that Outsystems has been doing pricing for.  For registered 501(c)(3) organizations in the US, I would recommend a much lower price in order to help them gain entry to this amazing product.  For a typical setup that would cost, say, $60K USD for enterprises, I would recommend lowering it to $10K or $20K USD.

Add in servicestudio the option of downloading an image with the architecture of the application modules and their related modules.Or, downloading an image with the architecture of an solution.Example:

 The optional chaining (?.) operator accesses an object's property or calls a function. If the object accessed or function called using this operator is undefined or null, the expression short circuits and evaluates to undefined instead of throwing an error. Source: MDN This operator is widely used and supported but OutSystems still gives us a (wrong) warning when using it inside javascript nodes. I think this should be improved. Probably just an editor update is needed. Cheers, Tiago