Hi all, here's my idea for the OutSystems Forge portal. About Forge components for O11, I think it's usefull to add three important details: Very often, the Forge components don't have the correct module naming convention. So, we have to assign the correct layer in Discovery. It's crucial to have suggestions from the Forge component developer about the correct layer to assign. Usually, we have to solve discovery problems (as upper references, side references) due to this missing naming convention. The first point usually helps to solve the technical debt level in AI mentor, but not all the issues. It's interesting to show the AI mentor analysis about Forge components itself for two reasons: To permit the Forge component developer to define if the problem is known and if it's a false positive or something like this. To highlight the technical debt level before to install short descriptions about Roles based on Roles' description. Usually this description is missing or incomplete This idea is to encourage developers to follow best practices and to help the CoE to address this issue efficiently. thank you, Roberta

Hello,In blocks, when selecting a OnClick event, there is no New Event shortcut like there is a New Client Action :In the case there are events in the block we can select them, but usually I find myself only having the need to create the event when setting the OnClick  handler. As it is right now, one has to create an Event  and then come back to the OnClick to link it to the Event .Regards,João

I'm proposing that OutSystems introduce built-in entity-level validation for OutSystems Developer Cloud (ODC) and, if feasible, in the upcoming OS11. This feature could streamline validation processes, reduce reliance on custom solutions, and enhance data integrity for CRUD operations across applications. In my recent article on Dynamic Validation in OutSystems CRUD (link), I explored how developers can implement custom entity-level validations using entity and attribute-specific validation logic. Making this approach native to the platform would save development time, enhance consistency, and further support low-code efficiency. Would love feedback from the community and insights on whether this aligns with current OutSystems roadmap considerations!

As we have ability to create 1-level Folder to organize Actions, Entities and so on. Please consider to add that information into the search result panel, either in separate colum or utilize the existing Location column with format / or ./ if Action is in root path.

If I create an If-Statement and I execute a server action and return back in the If-Statement (see picture) then this can be potentionaly unsafe. This can result in an infinite loop.It would be nice if OutSystems could warn me on that one by marking the If-Statement like it warns me in other places.

Hey there, Problem Since Outsystems 11, the versioning on the release notes web page changed to show the Release number instead of the Version number: But if we look at the version of our Development Environment, we see the version number: There is no way to know (at least that I know of) the match between Version and Release numbers other than downloading a Release version, installing and see what is that version belongs. Idea Show on the Release Notes and Development Environment both Release and Version Numbers

When you are adding fields to an entity you are able to do it using shortcut CTRL+N but when adding parameters on advanced Query you are not.It was nice to have this concept to create anything.

Hello Team,Thank you for the new update in outystems, I saw now we can search espace in the lifetime while deployment and also we can see all applications & difference applications filters, which is very good functionality given by outsystems. I have an idea to make it more better and simple. I want outsystems to provide previous version deployment functionality in lifetime. For example -Let assume application name ABC had version 1.54 in dev and  1.50 in QAIf developer deploy version 1.54 from dev to QA but some thing went wrong or he want to revert back all the changes and make QA 1.50 again, then he can..This is my Idea to make lifetime deployment more better and flexible to developers.

If Solutions also saved effective value of site properties for current version rollbacks would be much easier.

Whenever we have multiple errors (or performance issues) in both ODC Studio and Service Studio, we may want to evaluate the impact of the issues (number of occurrences) and according to that, we will work on strategies to solve them. In the print below, for instance, it would add a lot of value if we could apply an order by Error Description on the records. In the scope of the image, we have 5 different errors but one of them happens more frequently than the other ones so I would tackle this one first. Although, that might have a different outcome if we take into consideration all the issues listed and, the priority might change.