It would be nice if we could cancel the publishing solution process on service center.

I the Rest configuration in Service Center should have the same fields that are in Service Studio. When I configure the Authentication in Service Studio appear the field Scopes But in Service Center this field doesn't exist You should have the same fields in both places

I see a lot of spam posts in the forum. Add a button so we can report this.

Sometimes we launch a deployment, you go back the next day thinking the teams have the new features on the target enviroment and... sorprise! it´s sttoped waiting for confirmation for the impact on running business processes, and loose several hours for the deployment start and finish. Also, if you have two steps, this question it´s asking two times! (if always review on stage 2, please, don´t ask on stage 1). Something than could be ideal for us if you have a parameter to say if you want to ask or not the impact on the running business processes so the LT don´t ask and continue with the deployment (something that works as deployment in two stages, that you can decide in wich enviroments you want to ask or not).

I love the free personal environments that OutSystems offers the community free of charge! It offers a lot of freedom to develop and test applications without the burden of contaminating your own business environments.On various circumstances I had problems with my personal environment. It was offline for days and had to raise a ticket with support. It would be great if I have the option to reset my personal environment to the initial state. Meaning that all customizations and configurations on my personal environment are wiped.

I see this feature as a must-have on the concept of Build It Fast, Right, and For the Future!So I would like to start with an example:Imagine you need to create an action/function that given certain parameters it will return you a text, this action/function can be done in a client-side action/function (does not require server logic), but you need to use the same action in an asynchronous logic which will require a server-side action/function.With this, at the moment, you need to decide on two approaches, both with pros and cons:1 - You go for the code reusability approach, which is you implement a server-side action/function, and on the client-side, when needed you make a request to the server using this server-side action/function. So the benefit of this approach is that you have a centralized place to manage this action/function, however, you will perform server requests when they could be avoided.2 - You go for the more performant approach, which is, you implement a client-side action/function and you implement the same logic on a server-side action/function. The benefit of this one is that you will spare the requests towards the server when you are using the action/function in the client-side logic, but you will always have to maintain the logic in two places. The idea would be to create a folder in between Client Actions and Server Actions that could be called Hybrid Actions, and these actions could be used both as Client and Server actions, when it was used on the Client side it would behave as a client-side action and in server-side it would run as a server-action.I know that the code generated under the hoods is different, but it is there where OutSystems brings its maximum value by abstracting the developers of the high code layer :)

When creating an aggregate with the PK, please set the Max Records default to 1.May sound a bit trivial, and this is just an idea from a code-quality point of view :-) making the developer aware that the property Max records need to have a value. Otherwise you might run into an Unlimited Result-set impacting your application in a negative way.

When using the "View or Edit Data" option on an entity, the columns' width should be allowed to be resizable.

 Need : A scene builder insight service studio for WebXR. Drag and drop 3D elements that bind to Outsystems data entities. Usecase: A field service app where a technician points their glasses at a machine, and Outsystems logic overlay the maintenance history data directly onto the hardware in 3D.

Service Studio and Service Center should show the Forge application version.If I install an application from Forge, the version should be visible in Service Studio and Service Center. This way we can easilly compare the version we have installed with the latest versions from Forge.In Service Studio it could be visible in the apllication screen (see attached print screen)