Add a small icon decoration so that on the espace tree we can differentiate which actions are public on an espace. While you're at it do it also for the ones that are functions...

It'd be great to have something similar to client actions in a mobile app for the web app. I feel like some of the logic we have in the screen actions is not that complex and has to be done on the client side to speed up the UI. We sure have some javascript capabilities, but it's not that good comparing to client actions in mobile.

 AppFlow is a fantastic cloud tool to build and deploy mobile apps in an automated way. Right now, OutSystems developers have to manually take care of uploading their mobile apps to the app stores, and managing all that complexity. Since AppFlow is a tool made by Ionic , which was acquired by OutSystems I believe it would be of great value to developers to have these tools integrated, saving a lot of time and headaches. Cheers, Tiago

With the introduction of Reactive, it is not possible any more to get user session data. That is probably a technical choice or limitation. The service center application now manages the user session and its data are not accessible. It would be great if an action is added (to service center) to terminate a user session by the user id. This feature is really useful and will help in managing users and do auto logouts. Now we have to keep a shadow session management on top of OS to do such things.

There is a limitation in OutSystems Service Studio where folders cannot be nested inside other folders. As a result, application elements must be kept in a flat structure, which reduces clarity, organization, and long-term maintainability. Why not allow developers the flexibility to create a better and more structured folder management system?

In lastest OS version (10.0.815) we saw that there are a new area with the recently opened modules in our environment. Could be nice if we have the hability to pick eSpaces as bookmark and look at them in a new separator next to Recent Modules :)Bookmarks list:Application (the star define what is set as bookmark or not):Thanks,César

I find it very odd that the exams contain lots of information not covered in the training material.I'm well aware that this information in contained within the documentation, however reading through pages and pages of text does not suit everyone's learning style and can be pretty tedious.I'm also aware that the expectation is that you put into practice what you’ve learned during training prior to sitting the exam, but that doesn't ensure you acquire all the necessary information.It would be far better to have more comprehensive training courses and cover all the required material, as is standard with most exams.As things stand, unless you have the time and inclination to read through all the documentation, whether you know the additional information or not can come down to luck, which is not at all ideal.In addition to that, many of the questions appear to be trying to trick you by using confusing and ambiguous language, and I'm not sure why this is necessary.It would be better if questions were clear and straight forward, so that it tests your knowledge and not your interpretation of their English grammar, which is sometimes lacking, perhaps due to English not being the first language of those writing it.If, for some reason there is really the reason to include ‘trick’ questions (though I can’t think why), then at the very least, the questions need to be unambiguous and grammatically correct, so that they properly test knowledge and don't trip people up through misunderstanding.

When we create a screen or action some time we create a lot of local variables. It would be cool if we could select all these variables and with right click create a structure with them keeping the data type of each variable.

In O11 Forge, you can directly upload a demo application for the component you are publishing. In ODC Forge, you have to select the library you want to publish, but you cannot also specify a demo app. So currently the only way to provide a demo application is to publish it separately. It would be nice if, when publishing a library, you could also optionally specify a demo app for publishing together. This would make finding the associated demo easier and would also give the ODC Forge a clearer structure.

the possibility to query a record list (ie. local/input variable) would rock!instead of querying/manipulating one/multiple entities multiple times, untill you have all relevant data together.why not query a record list already available? even if it consists only of structuresthis would seriously increase performance and reduce complexity.specially since you dont need those loops with an IF anymore, that simply skip all records untill youve reached the one you want.thanks for liking!