Currently, OutSystems UI provides built-in Open and Close actions for individual Tooltip components. However, if we review the Tooltip API implementation, we can see that there is also a GetAllTooltips method available. https://github.com/OutSystems/outsystems-ui/blob/53a8f0e/src/scripts/OutSystems/OSUI/Patterns/TooltipAPI.ts#L2 If you want to show all the tooltips in the screen you need to rely on a iteration and trigger the open tooltip action. Add the GetAllTooltips and ShowAllTooltips to the list of OutsystemsUI Actions.

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.

It would be great if we could integrate with Git directly (out of the box) with Service Studio to manage Javascript/JQuery/React/.. and CSS projects.With Git being one of the most popular and powerful Source Control providers, harnessing its power from within Service Studio would just be icing on the cake.

We should be able to define the names of the fields we are exporting to excel.

The new JavaScript editor for mobile apps, is great, but the autocomplete could use some work :)The feature catches comments and strings at the moment, see below.

Please add the ability to upload a demo app for ODC External Logic components.

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.

In Service Studio, static entities have a Description property (like all other things you can create like actions, structures, attributes and so on). However, given the nature of static entities, each record has a specific use, which currently can't be described. It would be nice if it were possible to add a description to each record, in addition to the static entity itself. This will help the developer assign the right value. This description could then also be shown when hovering over a record in the static entity selection pop-up.

While using the Upload widget, it would be really helpful if there were built-in properties to set allowed file types (like .pdf, .jpg, .docx, etc.) and a maximum file size limit (in MB or KB). Right now, we have to write custom logic or JavaScript to validate these things, which takes extra time and can be tricky for less experienced developers. If these options were available directly in the widget, it would save time and make file uploads more secure and user-friendly out of the box.

The use of ReactJs in mobile applications not only allows a quick refresh of the screen but also makes the development process simpler, since it is not necessary to perform ajax refreshment explicitly. It would add value to Web applications