I think "For Each" elements should behave the same as "If" elements in regard to its label.When the Label parameter is blank, its Record List should be shown instead.Here's what a For Each with no label currently looks like. Caveat: when reading through the code, I have no clue which list the For Each is iterating until I click it.Here's what it should look like in this example above. Much better:  I can read which list the For Each iterates without having to click it!

The ability to clone an extension would be a really really nice-to-have. :-)

In my opinion the combobox margins and padding's in the visual css should be bigger and should contain the OutsystemsUI variables as optionsAs you can see from above screenshot the combobox is really small when we are using variables and also I need to write the variables all the time or copy paste from somewhere else.

 An italian hospital ran out of valves and a company 3d printed the valves: https://www.3dprintingmedia.network/covid-19-3d-printed-valve-for-reanimation-device/My proposal is an app to crowd-source this kind of effort:- Administrators are responsible for registering and validating the registration of legitimate entities with legitimate needs- Entities make requests- The public provides solutionsThis can be implemented by a small team in a very short time and can help save lives.Most people want to help and don't know how, let's give people that chance to contribute.

It whould be nice to have an overview of all available actions and webservices in Service Center, something like a 4GL dictionary. This would give an overview of Built-in actions all public actions in Sollutions all webservices references of all eSpaces / Extensions and its function (UI / Business layer / Integration Layer) This is also the place to functionaly describe these actions/services

This aim of this idea is to propose a proactive, dual-layered security framework for O11 & ODC to ensure PII (Personally Identifiable Information) requirements on data model. The Manual "Is Sensitive" Flag Introduce a high-visibility Data Governance section in the Attribute Properties pane. Developers can manually toggle an "Is Sensitive" flag for attributes. Result: Data is automatically encrypted at rest using AES-256 and masked in all ODC Portal logs. The AI-Powered "PII Sentry" An integrated AI agent monitors the data model in real-time to catch human error. Pattern Recognition: When an entity is created or data is imported via Excel/CSV, the AI scans for sensitive patterns (National IDs, Credit Cards, etc.). Automated Action: The AI interrupts the workflow to suggest: "This field appears to contain PII. Should I enable the 'Is Sensitive' flag for you?"

A collate definition attribute for each table/entity in the join will be useful, so as not to force the use of SQL Advanced and to reduce the risks/chance of errors in the development. By default, the collates will come with what is in the bases of origin of the tables, so that they can then be changed according to the need. We have a scenario in which we make joins between tables with different bases and one of them has the SQL_General_CI_AS collate while the other uses SQL_General_CP850_CI_AS. This shows a warning in the column of the join involved, it allows publishing but incurs a runtime error. I thing something in this position:

I'm not sure if there is already an existing idea like this, the search didn't provide me with a match so I'm creating one...We have the ability to import a swagger 2.0 rest services already, but unlike its SOAP counterpart we lack the ability to do this locally from a fileThis should be added IMHOBest regards,PC

It would be great to have a visual feedback when we have dependencies to update or even when they are outdated and need some action to validate and update them.A preview of what could be to help us.This could be validated when opening the module (as it is already being done) but it would give a visual feedback even when we don't have breaking dependencies. It could also be checked after publishing for example.As this would only validate the used dependencies, probably wouldn't take as much time/effort like when we open the popup itself.

Expose the data in your Outsystems application via an OData service (RESTful API). Just rightclick on the entity and the rest is done for you, including security, streaming and paging. The data is queryable from the outside. The data can be used in Excel, LinqPad, PowerBI, Tableau, and a number of other BI solutions.