It would be good to have CRUD Wrappers for Local Entities as we have for Server entities

By Default fill in the Description Section of the Aggregate and Timers when a new aggregate or timer or any variable is created to avoid Architecture Dashboard Issues.The user can then change it to any values he wants. This will avoid issues on the Architecture Dashboard which in turn will increase the development speed.

Currently, joining Entities and Lists in aggregates is not possible.However, OutSystems isn't far off from being able to make this work either.Most of the major relational databases have introduced functionality to be able to join tables with unstructured data - JSON and XML are a examples.I had an issue with slow rendering times on pages which got data from integrations and had to loop through the lists to link it with the SQL database in our OutSystems environment.I noticed that there would be about 5ms latency between every Aggregate in the For Each loop which was used to build the List Structure required to render the content on screen.My workaround was to:Fetch data from the integrationJSON SerializeAssign to text input of Advanced SQLUse a CTE with OPENJSONJoin with the OutSystems {Entities}This led to me having only one interaction with the database and being able to build the List I needed much quicker.The query looked almost like this:;WITH CTE AS (    SELECT * FROM OPENJSON( @textparameter )          WITH (                Column1   NVARCHAR(100)   '$.Column1',                Column2   NVARCHAR(100)   '$.Column2'          ))SELECT {Entity}.* FROM {Entity}INNER JOIN CTE    ON {Entity}.[LocalReference] = CTE.[Column1]An unexpected, but welcome side effect was that the Database was able to join the data quicker due to query planner/optimizer spawning off multiple threads to do the heavy lifting whereas my OutSystems process was single threaded.

The HTML Element widget is, from what I can tell, limited to a set of tags that OutSystems defined. As new HTML tags are created, and with the surge of technologies like Web Components (that use custom HTML tags), this becomes a limitation and we have to implement workarounds to make a simple thing work. Can this rule be relaxed or even completely removed?

To prevent an agent from accidently executing multiple times without supervision. It would be good to add a security feature to disable specific agents on the ODC Portal for each environment.

Hi,MABS Version has become an important aspect that need's to be clear while anyone of forge comes & download the Mobile Plugin.Most of the developers has been started to struggle on MABS version as of the plugins are not yet been upgraded.To address the issue, at least outsystem can give a way by which a Plugin Owner can specify the supported MABS version. Same like it highlight the supported Outsystems version.Please provide a separate field to mention the MABS version while uploading the plugin.

At the moment the maximum length of an action name is 50 characters. This is way too small for having effective and readable names.You end up truncating names which has a negative impact of readability, maintainability.So please increase them by a lot. at least 255 characters.

At this moment, the "By" of listSort is not dynamic, which means it will not allow a variable that does not have the same name as one of the columns in the list. This will result in having something like: 1st option or 2nd option It would be interesting to have something like this: Since the "SortBy" would already bring the name of the column, it would be something straightforward.

When the Date Picker widget is placed inside a popup container, its calendar popup has a z-index that is too low to appear above the popup. In my application, the date field is mandatory, so this behavior acts as a blocker in the testing and validation process. Resolving this issue would greatly help developers during unit testing and proceed further.

We need an online system/portal/store where we can purchase OutSystems swag, like t-shirts, decals/stickers, etc.