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.

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.

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.

 It would be great if any new ODC forge component could be listed in OutSystems Community newsletters , as daily digests.

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.

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';

In a multi team development environment, changes can be made to an integration such as ingesting a new field in a dev environment (ie adding a new attribute to an entity). Using Integration Builder, this attribute might be added to the integration and work as expected in the Development environment. However, if that integration is now required to be deployed with those changes through to production, but the integrated database doesn't have the required attribute deployed to production, this can cause production errors. My suggestion is to provide a log of changes showing what additions or subtractions have been made to an integration so that they can be validated prior to any deployment. Alternatively, during the preparation of a deployment, test that all integration attributes are valid and pause a deployment to alert of this missing attribute.

Enhance the OutSystems Entity Actions Wrappers Accelerator to: Centralize validation logic: Automatically create a dedicated wrapper for validation rules specific to an entity. Consolidate Create and Update: Generate a single, unified server action that handles both entity creation and updates, utilizing the centralized validation wrapper for consistent and maintainable logic." This approach would: Reduce code duplication: By separating and centralizing validation logic, developers avoid maintaining identical or similar rules in both Create and Update actions. Improve maintainability: Changes to validation rules can be implemented in a single location, ensuring consistency and reducing the risk of errors. Simplify development: Streamline the development process by requiring fewer actions and reducing the need to manage duplicate logic. This enhancement would significantly improve the efficiency and maintainability of applications built with the OutSystems platform.

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