In the Dropdown Search component, it would be beneficial to enhance the OnChange event by allowing it to include additional attributes. Currently, OnChange only provides five default attributes from the DropdownOption structure: Value, Label, ImageUrlOrIconClass, GroupName, and Description. It would be helpful to introduce a JSON attribute where developers can pass extra information about the selected item. This enhancement would reduce the need for additional local variables and data aggregations, streamlining the retrieval of supplementary details within the component. Currently: Ideally:

It would be nice if there is a comment widget I could place on Screens and Blocks of Reactive Web Apps and Mobile Apps, like it is possible for Traditional Web.

It would be really useful to keep the filters selected once we return from the Detail of the Error. It would save us some time.

Currently "da - Danish" is missing from the OutSystems UI library. As mentioned in this thread https://www.outsystems.com/forums/discussion/57768/outsystems-ui-allows-for-translations-on-outsystems-ui-widgets/ we can not add this ourselves, so we hope this can be resolved by the OutSystems team.

We have 100+ apps in the Dev environment and it is extremely hard to search if the application name is forgotten.So, if you can add a simple feature to Pin the favorite application and can be seen either on the top of the list or left side top of recent modules. Also add the ability to sequence it so I can order it as my priority changes.It will help all developers and saves time as it is cumbersome now to quickly open any project if there are many in the environment. Each module only opens specific module not the whole application.

Having an option on the screen or in the button parameters to prevent the user from double clicking on any element twice or others when the server is processing.Per example if the server is slow the action logic may still be processing and some users have the tendency to double click buttons (like Create/Save) repeatedly, duplicating records (per example).You can avoid this by using the Button Loading widget on Mobile and Reactive Apps, but there is no option for the whole screen. On Traditional Web you have to implement your own logic or use a Forge Component (Page Loader) or ( Button Locker), per example.

One of the purposes of publishing a solution, is to refresh all modules in it. Since the developer would be aware that he/she is applying a major change, why not to add an option to remove locale unused items in the module. Just make the feature configurable.

When we are submitting an asset to the forge we have this helpful checklist of things that we have to follow so that our asset can be sent to review. From experience, assets are rejected if they do not have a " Try now ". I think it would save everybody's time if this was included in this checklist. It would be nice to also have it mentioned in the docs . Cheers, Tiago

Setting the Oracle Parameters for case insensitive searchingWe need to set NLS_COMP=LINGUISTIC and NLS_SORT=BINARY_CI in order to use 10gR2 case insensitivity.  Since these are session modifiable, it is not as simple as setting them in the initialization parameters.We can set them in the initialization parameters but they then only affect the server and not the client side.  The following PL/SQL was used for a search screen:execute immediate 'alter session set NLS_COMP=LINGUISTIC';execute immediate  'alter session set NLS_SORT=BINARY_CI';

Sometimes you have two buttons that you want to have as the "Default" button based on different conditions. For example, if you have a screen with basic and advanced search, you want the "Search" button to be the default button, but you have a different "Seach" button in the If. J.Ja