Please add the ability to upload a demo app for ODC External Logic components.

Currently each time a site property is saved, the new value is applied to the factory. This is separately done for each site property value that you adjust. In core modules applying the new setting can take some time. It would be nice if it is possible to change multiple site property values before applying the new settings to the whole environment.

On ODC Studio when you create a new agent, there is a configuration named Call Condition. By its description and behavior it should be called Stop Condition to avoid confusion: It is already there when you open the question mark icon:

Implement the Star rating with the user review for the forge asset with some prebuild radio popups for the ODC forge asset and making a filter by rating in the ODC page

Since OutSystems recommends a separation of deployment and release by using Feature Toggles, I think it makes sense for this feature to be available in the unified ODC Portal and more integrated with the deployment process.

Allow changing variable values while debugging

Currently, when using the Advanced SQL tool in OutSystems, developers are required to define an Output Structure even for SQL statements that do not return any data — such as INSERT, UPDATE, or DELETE queries. This mandatory output requirement introduces unnecessary steps in the development process. It creates confusion for beginners and adds extra overhead to simple operations that are not supposed to return results. Proposed Improvement: Introduce two different types of SQL tools to improve clarity and usability: ExecuteSQL_Select: for queries that return data (e.g., SELECT). ExecuteSQL_NonQuery: for queries that do not return data (e.g., INSERT, UPDATE, DELETE). ExecuteSQL_Scalar: for single-value queries (e.g., COUNT, MIN, MAX). These naming conventions are inspired by C# and other modern frameworks and would help improve developer efficiency and code readability. This change would eliminate the unnecessary requirement of defining output structures for non-query operations and streamline the development workflow.

An integrated " AI Audit Trail ." that attaches the original natural language prompts and business requirements to every generated element. This would allow the architect to click any logic node and see the" intent history," helping to debug AI " hallucinations" in complex business rules.

A "Service Studio Lite" that runs in the browser for quick logic fixes and metadata reviews, offloading the heavy rendering to the cloud and reducing the dependency on a high-spec Windows/Mac desktop client.

ODC apps update (Review Library Updates) don't provide any information about what was updated in the updated app. Instead it just have a generic information. In O11 user has more information and control about what is updated and can update item by item. ODC: O11: