Static entities are like constants, and they can be used in many eSpaces. Unfortunately there is no way to look for usages of a particular record in all eSpaces, although there is possiblity to find usages inside current eSpace only.For example, we have an entity of shared translations, which contains many many records and is referenced everywhere. If we want to clean it, suspecting that some of the records are not used, or to remove duplicates, it's very hard to check the usages. Or, another case, if you want to find where the record (constant) is used to investigate the logic. Would be great if this was possible.

We usually get a warning  when we want to publish and a debug is running. Our only options are to Publish (it will suspend debug and resume debug later) or to cancel Publish so we can manually stop debug.What about a third option "Stop Debugging and Publish"?

I think certifications could be a deserved bonus points section for the Community Ranking.After all it shows engagement with the OutSystems community, right?

I thought it would be interesting if the conditions had the optimization I present below. There could be a simplification for these two situations: 1st => equality 2º => inequality If we have "and" and "or" together, this not apply.

 In Service Center there is a setting to redirect e-mails sent by the platform to a defined list e-mail addresses for testing purposes. It would be useful if this could be set per eSpace, for example in the Operation tab of the eSpace screen. In this way you can test your e-mails, without receiving all other test e-mails from other eSpaces, or bothering other developers that also want to test their e-mails.

Refresh your dependencies without having to open all sorts of panels (very time consuming). Bonus: You can also see when code has changed :)As a addon on: https://www.outsystems.com/ideas/6095/refresh-all-dependencies-in-service-studio-menu

By including CPU and Memory history graphs , administrators can easily determine if an unresponsive environment is caused by a single front-end server or if all servers are overloaded. This information would allow them to identify the root cause of the problem and take appropriate measures to resolve it.

As we know inline CSS creates performance problems in our applications.One suggestion would be, a bit like in Trusted Advisor (image below), to be able to search for all inline CSS.Just like in the container parameters (for example), when you have fields like Margin Top, or Align ... When you fill these parameters with values, what the page will generate in HTML is inline CSS.The possibility of being able to search for this information would be a huge help.Although the first point of this idea is being implemented in Trusted Advisor, not all customers have access to this platform.Another alternative suggestion that I give you, will ServiceStudio be able to generate warnings when we have style inline. So you would not have to search.Regards,Nuno Miguel Verdasca

It would help with the documentation if you can tag Users(Developers) in a comment for a flow in an action. and maybe put it in a notification list somewhere that somebody tagged them in a comment

I think this feature could be improved.It would be cool if we could know from what espaces/extensions the elements being deleted are from.Right now it only tells me what is being deleted. It doesn't tell us from where !