The DataGrid is a useful way to display and work with data in a table format. However, because it has several Static Entities, it adds to the AO limit (21 AOs), which can limit the ability of developers to use it in their applications. It would be great if OutSystems could exempt this component from the AO limit, similar to the OutSystemsUI module.

Guys,If the "Manage Dependencies" window only shows the used dependencies by default, It would be more time saving when I just want to refresh dependencies that I already have.Even with the performance revision you made recently on this screen.  On a recent dev environment it takes sometimes 2-5 sec do show ALL modules I have, to create new dependencies, and almost all the time I just want to refresh the ones I already have.I know that there is a button to strict the collection, BUT the data was already loaded and the time has already taken.Please consider this.

When designing a REST API, it would become beneficial for the generated swagger file to include an 'enum' that defines possible values for parameters representing static entity identifiers. Consider the following scenario (see attachment) as an example: Within the REST API method, there exists an input parameter of the Entity1 identifier type. However, the generated swagger file merely denotes this parameter as a string without providing further elucidation. By incorporating an 'enum' into the swagger, additional clarity can be imparted regarding the acceptable values for this parameter. In this instance, the enum would specify: [a, b, c].

It would be great if the training videos for a course queued up and automatically skipped to the next video and demo, especially in full screen mode.For example, I'm taking the Aggregates 101 course. There are 6 lessons and a quiz. I put the course on full screen mode because some of the demos are hard to see in the window, but then as soon as the 3-5 minute lesson ends I have to exit full screen to select the next demo. There are other recommended lessons at the end of each lesson, but they are the ones that I was trying to watch. I

To make OutSystems more powerful, the Forge should integrate with third-party platforms like: AWS, Azure, and Google Cloud: One-click deployable AI models, APIs, and cloud services. Business Apps (SAP, Microsoft Dynamics, etc.): Pre-built connectors for seamless integration. Open Source & No-Code Tools: Integrate with platforms like Zapier, Make (formerly Integromat), and Power Automate.

There's already a similar Idea regarding configuration per environment , but this one is slightly different: very common plugins can be used by several apps in a factory, but each may need that different configurations. An example of that can be the Camera or Geolocation plugins, where the permissions labels (CAMERA_USAGE_DESCRIPTION, PHOTOLIBRARY_USAGE_DESCRIPTION, etc) may need to be customized per app.A nice way to handle there per app variations could be the client app setting those in its own Extensibility Configurations, that would override the json defined in the plugin's Extensibility Configurations.

It would be nice to have a quick way to refresh all my references and publish them from Service Studio.....  I am dying of a million mouse clicks :) click...click...click...

I would like to have the ability to work off line with out having to upload the file for Intellectual Property.  In doing this I would run off of my local community edition, but later be able to change the server back to the development server when I have a connection again.

The "Convert feature of aggregate to SQL" enables users to convert an aggregate (a query that retrieves data from a database) into an SQL widget. This feature is very useful because it allows developers to work with SQL directly, giving them more flexibility and control over the queries they execute. However, there is a limitation to this feature when it comes to sorting. If you apply dynamic sorting (sorting based on user input or other variables) within the aggregate, you cannot utilize the "aggregate to SQL" feature. This means that the conversion of the aggregate to an SQL widget will not include the dynamic sorting functionality. On the other hand, if you only require sorting based on a single attribute or column, you can still use the "aggregate to SQL" feature. This means that the conversion will include the single attribute sorting functionality, allowing you to sort the results based on a specific column in the SQL query. Overall, the "Convert feature of aggregate to SQL" is a valuable tool for developers, but it has some limitations when it comes to dynamic sorting within the aggregate. However, single attribute sorting can still be utilized effectively with the "aggregate to SQL" feature.

Now when I filter courses with same topic and I want to see insights of them, I have to do the filtering again and again, It would be nice If it was possible to open each course on new tab. Not naccesarily on click right away, but at least be able to use "open link in new tab" (this one now redirects in full catalog).