tl;dr : When refreshing a REST API definition, import only structures actually used by the imported methods, instead of *all* the structures exposed by the API. Details : When refreshing a consumed REST API definition, using the right-click "Refresh REST API..." context-menu item, you can select which methods will be imported. However, *ALL* the structures exposed by the API are imported, even if you import just a single method. This in turn triggers as many warnings as there are "Unused Structure", and we then have the tedious and error prone task of removing said unused structures. If only the actually used structures of the selected methods were imported, the task would be much easier and less error prone.

Hospitals will start having issues with ventilators during this high usage times that are approaching. After doing shifts for more than 48 hours it won't be easy for medical and technical staff to properly troubleshoot the cause.For instance, sometimes ventilators stop working and the problem is the UPS. What needs to be done is simply connect the ventilator to the energy outlet rather than the UPS.The purpose of this system will be to allow technical staff to submit issues with ventilators (by brand and model) and have specialists indicating possible solutions.

This idea proposes a built-in visual tool that validates API requests and responses against their defined contracts, such as Swagger or OpenAPI specifications. The tool would automatically detect missing fields, incorrect data types, and deprecated attributes before or during runtime, helping developers catch integration issues early. By making API contract validation visible and easy to understand within OutSystems, teams can reduce production defects and integration failures without relying on external tools or manual testing.

Everyone knows that descriptions are helpful to understand the meaning of a variable or anything. My suggestion is to show the site property description in the lifetime as we can see in the service center.

Whenever we are on the viewing the widget tree of a page or Webblock, if we click on the "Go to <insert element here>" we continue on the same widget tree view mode and need to click again on the widget tree icon to finally see the element we selected as demonstrated on the gif below. The rationale is that if we are using the "Go to" context menu, 9 out of 10 times we want to open the original module to inspect/change the element selected.It would be nice that when we use the "Go to <insert element here>" context menu it would change to the view that actually allow us to "go" to that element

The Forge component page should include more details, that allows one to judge the impact on and OutSystems factory without needed to install it first:Number of Application Objects (AO's)Number of integrationsPaid license required for a third party integrationExternal integrations overview (some components have APIs just to collect usage, this should be more visible.If it bootstraps data on publish (some components generate users, etc.)If applicable version of OutSystems UI used (OutSystems UI has a high rate of updates and deprecated functionality/breaking changes)Regards,Daniel

Will be helpful to have a build-in fuction to remove duplicates from a listExampleList {A, B, C, A, B }Result list {C}

Just like the option to export/download certificates, it would be great to have the same functionality available in the Achievements section as well. The exported file will give information about all the achievements under the achievements section.

There should be ability to add unit tests automatically for any actions. Also a unit tests should be automatically added to a Core Modiules.

To prevent the population included in the group most vulnerable to contagion by the new coronavirus leaving home, namely the elderly and people with chronic diseases, the Municipality of Proença-a-Nova and the Parish Councils and Unions created a solidarity network for situations of emergency, namely for the purchase of medicines or essential goods, among others.In each village, an interlocutor between the population and the Parish Councils is being defined to communicate needs, and the Municipality is responsible for the subsequent delivery of orders.To facilitate all the communication between the interlocutors and the Municipality, volunteers developed a web and a mobile app during the weekend using OutSystems and made available to Municipality employees to use, tracking the daily requests with the necessary details.