It has been my gripe for years ;) ... please please give us a native hashtable implementation ...

It would be nice if we can remove all teams roles from a user in Lifetime instead of pick them one by one. This will be more efecient in factories with large number of teams. Thank you

I understand why we don't have it for Attributes, but it would be REALLY helpful on Attributes, to decide if it can be removed or not.J.Ja

(It is different, but alike to https://www.outsystems.com/ideas/10924/improve-crud-wrapper-generator/ )When working under architecture, we work in different modules which inherit. (E.g. BL inherits CS). This is mostly done using wrappers, which have to be made by the developer.As far as I understand @João Melo wants a right click option on the Created CRUD action of an entity. Which helps speeding up development on that part.But when working in multiple architecture layers, you still have to create actions in the other modules by hand.It would save a huge amount of time when we could select a function in a referenced module, right-click on it, and select an option "Create Wrapper Action". Which would trigger a wrapper function with the same input/output and include the original action.This is not limited to Entities, etc. But could be used on any Action/Function/Service Action/etc...It would be even greater if we could create the wrapper with a selection of optionsCreate Action WrapperCreate Service Action WrapperCreate Rest Service Action Wrapper (kinda more difficult because of the existence of the producer settings)Bonus Idea(Not limited to the wrapper, but also on input/out parameters of inherited types):When we inherit or use an existing item, Architecture dashboard want public action, input/output parameters, etc to have a description. The descriptions can be defaulted based on the action, and when available, why not copy the original description. An EntityId description is usually the same as the input parameter description of the instance. You can change it, if it is different, but 99% the original description (and the name) are fit for business

Context: Debugging mobile applications is more complex compared to web applications. Suggestion: Add enhanced mobile debugging tools, like real-time logs from mobile devices and better network inspection within the Service Studio debugger. Impact: Easier troubleshooting for mobile apps, improving the developer experience.

Outsystems wraps most inputs in a span, as you can see in the screenshots below. In some cases, that leads to cumbersome CSS selectors. For example, when I want to style a label succeeding an input, I need to write the following CSS: span:has(> .checkbox) + label { ... css styling } If I wouldn't be wrapped, I could just simply use the input + label selector. Also leads to a cleaner DOM imho.

Possibility of importing stored procedures as we already do for tables and views. This stored procedures should map into Actions with the input and output parameters.

It would be much easier to Outsystems newcomers such as me to be able to add some of our most used Widgets to a Favorites section, without having to scroll down or manually search for it.

Enable users to dynamically adjust the number of column controls (e.g., 2, 3, 4, etc.) directly by clicking on the column control itself.

It would be interesting to be able to order the modules that make up an application so that the organization proposed by the 4 canvas becomes more evident.I suggest that this ordering is possible by dragging and dropping within the modules list of an application in service studio.