The onchange-property works quite nicely, only it will fire a lot when you are typing. There are use-cases when you have a sort of grid to be entered and you actually only want to save the input when the user hits enter (and loses focus to the next input-widget) There can be a workaround by making an hidden-button etc. etc. but what I really would like to see that the OnBlur will be made standard (alongside the Onchange) so we will have less ajax-calls.

Doing the guided paths under the Learn tab, sometimes there are some lessons I feel like it would be useful to go back to for clarification or just to check some important information, and there are also some pages on the documentation that I like to visit more often to understand or clarify something.I usually look for these on the google search, as it is easier than to look for them on the Learn tab.If there was a way to save these as favorites on my Outsystems Community profile, it would have easier access.

It would be very helpful to have a GetBaseURL  function that would provide the current URL to the current application.  This is extrememly handy when you want to provide a link to the application in an email.

Right now, we can change the default icon of one action, to a custom icon. But when we select a set of two or more actions those are not possible. That could be very useful, if possible, to change an icon to a group of actions at once.

It would be helpful to be able to search for errors on specific modules. Now it's only possible to select 1 module. By having a multiselect, it is possible to check on 2 or more modules that you are interested in at the same time. The other way around, you can "select all" and then deselect a module that is having a lot of errors (which is troubling the error logs) to be able to find the errors you are interested in more easily. The same would be for the application search. Same request is useful for applications dropdown

I think it would be usefull if we could add comments to flow elements, like IFs, switchs and foreachs.Sometimes the comment component is big and it's hard to position in a place where won't overlap other elements.This idea ( https://www.outsystems.com/ideas/346/%5bServiceStudio%5d+add+comment+to+value+assign?IsFromAdvancedSearch=True ) helps a lot, allowing us to add coment to the expression, but it would be easier to read and find this comments if there was a property in element to input some comments.Cheers

Hi, Currently in ODC we cannot do Hotfixes or deploy directly in the environment we want. This is somewhat a limitation if we want to fix a bug in Production and we have a stable version in QA that is currently being used. In order to not impact QA to fix PROD, there should be allowed to deploy directly from DEV to PROD.

The DataGrid is a useful way to display and work with data in a table format. However, because it has several Static Entities, it adds to the AO limit (21 AOs), which can limit the ability of developers to use it in their applications. It would be great if OutSystems could exempt this component from the AO limit, similar to the OutSystemsUI module.

In case  REST or SOAP has Full logging  and message is BIGG like 10 Mb, than full log trace message will be truncated. It means  we are losing  possibility to see at least response headers and  body start.For developer It is very important to see response at least headers, as well usually response is very short and have informative error description inside.Here is simple example of trace file (CURRENT SITUATION): Request Headers:User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client Protocol 4.0.30319.42000)Content-Type: text/xml; charset=utf-8SOAPAction: "sendFile"Host: 10.10.10.101Content-Length: 19986843Request message:<?xml version="1.0" encoding="utf-8"?><soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"><soap:Header></soap:Header><soap:Body><sendFile ><request xmlns=""><document><fileName>filename.jpg</fileName><content>JVBERi0xLjcNJeLjz9MNCjIwMTc1IDAgb2JqDTw8L0xpbmVhcml6ZWQgMS9MIDE0OTg5NDcyL08gMjAxNzkvRSAyMjE0NjUvTiAxMjQvVCAxNDU4NTg1NC9IIFs.... THOUSAND LINES WITH FILE CONTENT ......+kftdt0JAaAjm4GNZIOzcUgXeRsRKtvGG3VKzQxu4TjrKoDXmrQRuAWbS5CHbCFRnc7a/nF6mDwVbT5UlKfWByqu2pzUQNU1Yf0gxfQnohTbMVE4TuCpGygkZQnYfyxeo6JOM<Message truncated in logging because it exceeded the maximum size>As you see full log is truncated due to maximum size. REQUEST:Book some space in the trace for Response. like 4..10 KB at least.it means that Request message will be truncated,  then I will be added Response Headers and  start of the response body. EXPECTED  TRACE To be look like: Request Headers:User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client Protocol 4.0.30319.42000)Content-Type: text/xml; charset=utf-8SOAPAction: "sendFile"Host: 10.10.10.101Content-Length: 19986843Request message:<?xml version="1.0" encoding="utf-8"?><soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"><soap:Header></soap:Header><soap:Body><sendFile ><request xmlns=""><document><fileName>filename.jpg</fileName><content>JVBERi0xLjcNJeLjz9MNCjIwMTc1IDAgb2JqDTw8L0xpbmVhcml6ZWQgMS9MIDE0OTg5NDcyL08gMjAxNzkvRSAyMjE0NjUvTiAxMjQvVCAxNDU4NTg1NC9IIFs.... THOUSAND LINES WITH FILE CONTENT ......+kftdt0JAaAjm4GNZIOzcUgXeRsRKtvGG3VKzQxu4TjrKoDXmrQRuAWbS5CHbCFRnc7a/nF6mDwVbT5UlKfWByqu2pzUQNU1Yf0gxfQnohTbMVE4TuCpGygkZQnYfyxeo6JOM<Request body truncated in logging because it exceeded the maximum size>Status Code: OKResponse Headers:Transfer-Encoding: chunkedContent-Type: text/xml;charset=utf-8Date: Wed, 09 Sep 2020 09:26:03 GMTServer: ApacheResponse message:<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"><SOAP-ENV:Header></SOAP-ENV:Header><SOAP-ENV:Body><ns3:createFileResponse xmlns:ns3=""><request><document><fileName>NewFileAdded000_010</fileName><content>JVBERi0xLjQKMSAwIG9iago8PAovVGl0bGUgKP7/AFYAYQBuAGcAaQBuACAALQAgAFMAZQBsAGYAUwBlAHIAdgBpAGMAZQBSAGUAYwBlAGkAcAB0KQo....... <Response body truncated in logging because it exceeded the maximum size>

Hi Team, We have like and unlike option in the forum. There is no issue if someone dislikes someone's solution or post but how is that person going to know why it is disliked? if this option has transparency, we can ask that particular person for the feedback what's the issue with their solution or post. Regards, Pankaj Pant