Hi Team, Is there a possibility to integrate automatic notification to all the consumers, in case of any upgrade in the forge components. Right now the process is manual, where one has to keep track of the updates in forge periodically and perform the relevant installation. A notification from platform in this regard, will be helpful. Thanks and Regards, Priyadharshini Sridharan

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.

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:

 I would really like to see some improvement in the environment 'initial' setup speed after a publish. Just after a initial deploy the loading of pages can take a very long time, especially when this publish concerns several larger E-spaces. It would be nice if the executed actions during a first run can e.g. be done upfront at the end of a publish. Context: A high latency is considered innoying to end-users, and will be noticed more when a lot of publishes are done during working hours. To avoid this one can delay publishes or  schedule an evening job. The scheduling as an evening job would probably result in " slow system " user notifications every morning after and less control over a publish. Besides that delaying a publish will lead to a longer project cycle. Request: It would be very nice if there would be a caching method that would make sure the webservers' cache would be filled with an initial load of the page / execute of the queries involved so the system would be responsive, even directly after a publish. Possible Workaround: Currently as a workaround I'm thinking about creating an E-space that would execute a HTTPGet on all clickable links in an E-space. I would however need to create a list of all possible links that are to be clicked and besides that need to maintain this while I think the environment is perfectly aware of these links and there is probably a more efficient way to cache both queries and pages.

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.

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...

It would be useful to have the functionality to drag an entity attr and create an aggregate filtered by this attribute. To match the filtered attr, could show a popup to suggest the user to choose the input / variable to filter in query, or create a new one (input / variable).

Whenever I search something in forums, It shows as "{Search Keyword} - Search posts in Forums".Instead, we can suggest at least top 5 posts relevant to that keyword. So that, the users can find of what they're looking for.

Context: Debugging mobile applications is more complex compared to web applications. Suggestion: Add enhanced mobile debugging tools, like real-time logs from mobile devices and better network inspection within the Service Studio debugger. Impact: Easier troubleshooting for mobile apps, improving the developer experience.

in condition it will be better to have 'In' and 'Between' functions