When publishing new eSpace's between environments via oml there could be an option to choose in which application the module should be stored into instead of having to go to Independent Modules and move the module to the intended application.

99.9999999% of the time when I look at Integrations Log, I don't want to see Performance Probe, license checks, publishing stuff, etc. Hide that ALL unless I check a box. Integrations Log is basically useless without doing searching a filtering because of this.J.Ja

Add Social Buttons to share Ideas .Add some social button like Facebook , Linked in ,Twitter .These buttons fix near to comment and views in idea page when an idea creator want to share his/her ideas just one click is enough to share.

1. Have a 'Yearly' selection Currently, we can select 'Daily, Weekly, Monthly' when we are configuring when timers are suppose to run. It will be a nice to have, if a 'Yearly' selection is available as well. There are some jobs which are only required to run once a year. Currently, we can only build a check, in the logic of the timer, to check whether whether it is a new year before continuing the logic. 2. Have option not to automatically run timer, when it is set from 'Inactive' to 'Active ' We have encountered a situation before, when we need to set the timer to Inactive for debug purposes. As the application is already live in PROD, naturally the status of the timer is Active. Then we found there was a bug, as such, we set the timer to Inactive in PROD, while we are still trying to fix the bug. After fixing and when app was deploy to PROD, we have to switch the timer back to Active. However, once we switch, the timer automatically runs again, even thou it is not the correct time to do so. So our end users panicked, as they know the auto emails, reminders etc, shouldn't be set out during that time of the day. End-users being end-users, they might not understand that we are just trying to fix a bug and then re-activate the timer

In Service Center logs, add a “Quick Explain” button that suggests why the error might have happened (e.g., DB connection timeout, invalid entity reference).

 I would really like to see some improvement in the environment 'initial' setup speed after a publish. Just after a initial deploy the loading of pages can take a very long time, especially when this publish concerns several larger E-spaces. It would be nice if the executed actions during a first run can e.g. be done upfront at the end of a publish. Context: A high latency is considered innoying to end-users, and will be noticed more when a lot of publishes are done during working hours. To avoid this one can delay publishes or  schedule an evening job. The scheduling as an evening job would probably result in " slow system " user notifications every morning after and less control over a publish. Besides that delaying a publish will lead to a longer project cycle. Request: It would be very nice if there would be a caching method that would make sure the webservers' cache would be filled with an initial load of the page / execute of the queries involved so the system would be responsive, even directly after a publish. Possible Workaround: Currently as a workaround I'm thinking about creating an E-space that would execute a HTTPGet on all clickable links in an E-space. I would however need to create a list of all possible links that are to be clicked and besides that need to maintain this while I think the environment is perfectly aware of these links and there is probably a more efficient way to cache both queries and pages.

Right now, it's only possible to a table cell :(How can you add custom border to a Table Line?1) Add a custom class to all the table cells... Outch.2) Run a client Action to a add the class to the tr.Adding directly to the widget table line would be much easier/cleaner.

In OutSystems it is not yet possible to define Android Adaptive Icons. The icon shows a white border on mobile devices. It can be improved to support adaptive icons to ensure icons are fully filled.https://developer.android.com/develop/ui/views/launch/icon_design_adaptive

The Responsive Ruler/Grid Overlay Widget is an amazing widget for everyone working on the UI in OutSystems, specially if you want things to look nice and align perfectly. And your Screen should be pixel perfect then this will help. Think of it as the perspective of a designer - A see-through grid on which you can build and examine your application. You turn it on and off with a button, and with the help of it you have got perfectly spaced lines helping you to make sure everything is aligned properly, spaced evenly, and it majorly helps with the responsiveness of screens. This is like having a ruler or grid paper in real-world, but inside your OutSystems application. Thank You

Would be good to have Advanced SQL template queries in OS.Let's say that by inserting the Customer entity in " OutputEntities / Structure " (or not) we could have templates regarding: DELETE DELETE FROM Customer WHERE Col = 1; INSERT INSERT INTO Customer(Col1, Col2) VALUES (1, 2); SELECT SELECT * FROM Customer WHERE Col = 1; UPDATE UPDATE Customer SET Col = val, Col = val WHERE Col = 1;By clicking in a button, we would have the templates displayed, It can be a great accelerator when developing.PS: Idea taken from Notepad++ plugin "Snippets