I suggest adding an arrow to collapse or expand code ranges in the JavaScript Editor, similar to the functionality already available in the CSS Editor. It would improve the usability when working with large blocks of code.

Like many others of you, I read from the ideas, we also have problems indicating changed/new labels.When you add a new label, the label will be indicated 'To be defined', but when you copy another label, the translation will be same a the old one, and it's it's indication is 'Translation'. And also, if you change a label, the indication won't change back to 'To be defined.So, how can we identify that a label have to be reviewed? We have hundreds of labels to translate and every Sprint there are some changes. It's impossible to review all the labels again and again.Since my idea of putting those changed labels back into 'To be defined' is rejected by OutSystems since users only doing typos have to put everything back into 'Translate'  again... I got a better idea now. Let's add a last_changed_date(time) so we can sort on that field and only check the labels we changed recently.Please like this idea to get this into attention of our Outsystems IDE developers.

The new Data Grid is fantastic, but the fact that you have to add an ActionColumn and that that is the only one that can have an OnClick handler attached is quite limiting. It would be very nice to have the option to do the following:1. Add an OnClick handler to each column regardless of type2.Add an OnClick to an entire row so that they can click on any column and it triggers the handlerI would suggest that the Cell OnClick overrides the row one... but the individual cells click probably more important. Or potentially just allow one or the other.

Currently, supermarkets limit the number of people inside the space, but there is a problem outside the commercial space, with the cluster of people waiting for their turn to be able to enter and purchase the goods they need.The idea is to create an application that performs the virtual queue management in which people can schedule their place in the queue before leaving home. The application generates a number in the virtual queue and will indicate to the user what time is most likely for him to enter the supermarket. In addition to the information in the application, the user receives an SMS indicating the place in the queue and the estimated time of entry. The information is updated with time intervals to be defined (5m, 10m, 15m, etc.). It will be necessary that each of the participating stores use the application and agree to create a specific virtual queue for the users of this application.The application can be applied to othet type of stores than supermarkets. Stores that use the application will be helping to reduce the risk of contagion, as there are clusters of people outside the commercial space.

The logs generated by the platform (screens, errors, integrations...) help us a lot when we are investigating an error. But I think it would be better if the platform allowed us to turn off these logs. We have recurring problems with the log database due to the large number of logs generated by accessing screens and integrations. Most of the time we do not need these logs but we cannot prevent them from being saved. We know that the logs are saved asynchronously, so there is no impact on the application (we use a separate database for logs), but we would like to have autonomy to turn on/off the generation of logs.

It would be nice to be able to set the required order of columns when output in the excel file.We've had various requirements/complaints about the column ordering in exported files that make life harder than it needs to be for business users.PS: I am eager to assist in extending the widget ;)

Hi Team, As having more dependencies increases the size of your Module and increases the duration of 1-Click Publish.It would be great if user get warnings in TrueChange to remove all unnecessary dependencies of module.As of now i don't get any clue that no of unused dependency in module has increased to  a large number.Thanks,Preeti Kumari

With REST services, we can open the documentation from the context menu. With SOAP web services, we have to type the URL (which is not easy to find) to get there. It would be great if we had a context menu option "Show Documentation" for SOAP as well.

Ensure that the popup and modal work with the keyboard and that the focus follows this navigation, and when closing the popup/modal the user returns to the place where the popup opened. Currently every project needs to add extra javascript to make it work in accordance with WCAG regulations.

The scenario is an attribute that is decided not be used anymore in an entity, but its deletion is not a good policy at that point.The only way to "deprecate" is adding a comment in the description, which is not a safe solution because it doesn't prevent developers to keep using it.So there could be a property in the attribute (called Deprecated) that could grey out the field and warn about its usage in SQLs and other actions.