While editing a LifeTime plan, I think it would be useful to have a counter that shows how many applications have been added to the plan . When the plan includes a lot of apps, and you know how many need to be deployed, it can sometimes be hard to tell if the numbers match. For example, let's say I have a plan with 25 apps, but I’ve only added 24. With a counter, I could quickly see that one app was missing from the plan. Right now I have to count the apps to see if I have all of them added. Cheers, João Heleno Mockup of a plan with the number of apps showing near the source environment title.

Currently it is the case that the username for the developer is shown in the created by field for server actions etc. This can be confusing when the username is not in a readable format when it is forced by the company you work at. The name for the developer can be changed and should be readable.

Add Environment name whenever hovering on the opened service studio in the windows task bar in order to distinguish between environments whenever opening muti environments to minimize conflicts.

As a developer, I find myself constantly using properties of lists and data actions like `. Empty ` and `. IsDataFetched `. When assigning to a boolean variable, Service Studio could suggest this properties. See in the following example that I wanted the `Tickets.Empty` property, but it was not suggested.

Be able to create a unit test for a Server / Service / Client (?) / Screen (?) action that shall be executed without developer intervention, for regression purposes.

At initial stage for the developers, while using free Community Version of Service Studio they are not able to connect to the any database on their system like PostgreSQL, MySQL etc. So many problems they faced during time of connection to DB. Need to be resolve ?

The same way we can filter members from staff and Champions/MVPs, it would be great if we were able to find those who are willing to be mentors. Now that there are almost 100 people with that "job", it is hard to keep up. Specially because the OutSystems filter on ADPList is not great. And since you are at it, please add a filter for those who have been speakers. This is helpful for User Group organizers looking for speakers, and the both combined would help potential speakers to find guidance and overcome their fears. In short: every time you add a tag to the profiles, add a filter to it.

A GUI based interface which allows the developers to create public wrapper action in a module. The Developer right clicks on a entity and generates the wrapper actions , which is generated in its own folder and exposed as public.The developer may decide to customise the wrapper actions later in terms of name, input and Output parameters. The concept can also be applied to creating wrapper action for APIs.This will help support the adherence to architecture concepts and security best practices

It would be great to have the option to redeploy an application from a later environment back to an earlier one in the deployment pipeline in ODC . This is not about redeploying and older version of an application. A potential use case for this is when an application is accidentally deleted from the Development environment, allowing it to be redeployed from the Production environment. This is possible in O11 as follows:

OutSystems is not really a front-end friend, it's more like a distant cousin when comparing it with other low-code platforms. My idea is to have a way to retrieve a specific folder from the project to our local machines / laptop similar to how Github works. Using a fetch command we would retrieve the files to a local directory on our laptop. This would give us access directly to implement our own front-end development workflows such as using Visual Studio Code do work with other tools such as TypeScript or SASS. Using a commit/publish/push command would allow us to update specific files/folders to the OutSystems Server with the code to use on the project. All the compiling would be done on our local machine. This would also allow front-end developers to integrate tools such as Grunt to automate processes and speed up our workflows.