One of the worst problems is when literals are hard coded. It is really bad for maintainability, you have to change them one by one and you can never know if you have changed them all. I would like it if there was a way to have an overview of all the places where hard coded strings are used for coding. For example if a text is used in an if-statement or together with an '=' mark it as a finding.

It would be great to have a diferent icon on actions that are using the cache property, in order to be visual distinguishable. Automatically because you can do it manually. This could be very usefull when debugging to see the code and to see that the action is cached

I know that for the purposes of the existing master class, the exercise fits perfectly, but it is done in version 9 and I think it should be upgraded to version 11. Just as it would be useful for everyone to have other exercises that cover more business process topics.Being a topic where there are so many topics to learn, it would be helpful to add more thematic content with more exercises for your learning to be bigger.Cheers,Nuno Verdasca

Certification exam for each type of course is difficult one, sometimes we know the answer but due to lack of sample questions practice we choose wrong answers during exam. Since exam is associate with some cost, so it will not be worthy for candidate to loss the Exam in any category.We can put some validation condition to have the access of Question Bank, like: Training videos should be mark as completed, Sample APP should be created and submitted by candidate's personal environment and candidate should have attended Boot camp related to it.This will increase the chance of clearing the exam as well as boost the confidence in candidate. We can also associate some price to these question bank.

We need fine-grained control over indexes. There are things like "fill factor" which we can set through SQL Management Studio, but we cannot set through Service Studio. This is a problem for 3 reasons: 1. Who knows when a deploy will wipe it out? 2. Customers on the OutSystems cloud do not have access to the DB to add it. 3. We love to manage everything through proper OutSystems tools! J.Ja

In O11 we can end other debugging sessions by republishing the module. However, this does not work in ODC. It would be nice if there is a button next to each "active session" in the Users section of the Debugger tab in ODC Studio. With the click of the button, the debug session of the other account would end. This way, we can make sure that the app continues running normally without hitting the debugger activated by other accounts, in case the other users are unable to end their session. Security-wise it would be nice to give this option only to organizational accounts with elevated roles, e.g. the tech lead role.

Dropdown search widget required default mandatory validation message. Need to add validation message and Mandatory message in Dropdown search widget. Developer and Front-end users will get benefits.

In an Outsystems project we find ourselves building in an application in the middle of a landscape where communication with web services is not always there. This situation makes it very difficult to test a complete flow since dependencies of other systems are quite often down.In order to surpass this situation making the application more independent for testing purposes, the idea is to try to have a module with a mock of those services and just changing the entry point on DEV / TST environment to make it work.The problem is the external parties' web services have hyphens ("-") on the URL path of the web methods and when we are creating the mock service to expose, Service Studio considers the "-" an illegal character.

Provide the ability to set the extended properties on reactive emails in the same way they are available in traditional. There is currently no way to set extended properties on reactive emails, this currently means we will have technical debt in maintaining an secondary application purely to send emails to enable setting importance, out of office suppression, expiry etcThe following is an example of the traditional extended properties in a traditional emailThe above is used to suppress out of office messages for mailings and prevents a deluge of out of office responses when a number of emails are sent.Importance is set on some emails based on the business process being followed e.g. high risk/value the importance can be set to High and the email client shows the importance of the email.The extended properties on the email has solved a number of issues with email visibility in a users inbox by adding the relevant property e.g. importance, sensitivity and also expiry has meant that processes that do rely on an email get the relevant attention required.

It would be very useful to have a system event similar to OnApplicationReady but like OnSessionEnd or OnSessionExpire. The idea would be that whenever the user's session expires, the event is triggered and the necessary actions can be taken when the session ends.