Currently when I want to delete records from an entity and I get an error, the error gives a technical name of the entity that prevents me from deleting a record. Please show the name of the entity as noted on the logic tab

I would like to suggest having option to enable or disable logging for each service action by adding optional parameter to service action "Enable Logging" by default true but developer can change it to false. Something similar to log email content. I understand service action has same behavior as Rest API so it has 3 logging options (Default, troubleshoot, Full) but this option used per module so its affecting all service actions into the module but sometimes I need to change logging for one of service actions only. We faced a case that we have service action that has too much traffic calling it so it log every hit to API log table into OutSystems Log database which causing a huge increase into size of table although our logging level is default. It is not important or no business need for us to log this action so we stopped logging for service actions into this module to avoid this increase. As another workaround we replaced this service action with server action. We are using O11

The Object data type can be used to communicate data to and from extensions, but isn't much of use otherwise. Furthermore, it is not possible to use an Object as attribute in a structure, and I'm not sure whether Objects should be possible in a List (they are, but kinda via a workaround, even as attribute). Also, many Forge components dealing with generic data force the user to use RecordLists, as there's no other way to alter data in an extension. My proposal:1) Allow structure attributes of type Object;2) Officially allow Lists (and Record Lists) of type Object;3) Have a FromObject function that reverses ToObject (and throws an exception when incompatible types are used), so extensions that manipulate generic data (e.g. XML Records) can output Records as well as Lists.An Object will never be a "first class citizen", but they have their uses, and the proposals above would make the life of the advanced developer a little bit better when dealing with abstract data.

Currently, ODC does not provide a mechanism to extract or automatically generate documentation for applications. In previous versions, such as OS11, tools like OutDoc and direct access to OutSystems metadata allowed teams to generate technical documentation more easily. The proposal is to introduce an AI-powered capability that can analyze an existing application or library within ODC and automatically generate technical documentation, such as: application architecture overview dependencies and libraries used module and component structure APIs and integrations main functional flows This feature would significantly reduce the manual effort required to create documentation, improve knowledge sharing across teams, and ensure that documentation remains up-to-date with the evolution of the codebase.

Usually we deploy several modules/applications at the same time as they are all related or dependent. Sometimes the first module gets a timeout/compilation error, this forces us to wait several hours before the deploy ultimately fails. It should be very easy to either STOP the deployment completely, or just LEAVE OUT this one single module which is having the issue. This could also very well be a bug since it wasn't an issue in the prior platform release.... *I already have a ticket open with support where the reply was: "Minimum specs have been increased, so consider an upgrade of some sort". However the ticket is still open and supposedly there is an ongoing investigation.

I'd like to be able to remove some attributes or connections from the Diagram without affecting the database. Only to make them more readable.Example: I'm analyzing entities related with User and all of them have an extra connection because of the CreatedBy field. I'd like to remove the field or the connection from the screen to make the diagram easier to read, but not to really delete it.I hoped this Hide/Show attributes in Diagram was what I was looking for, but I need more.

When modeling the database or simply creating entities, it would be great if the platform suggested the creation of basic auditing fields, like CreatedOn, CreatedBy, UpdatedOn, UpdatedBy.Of course it shouldn't mandatory, and the platform should be smart enough to understand when the entity is a good case for these types of fields. That's why I'm categorising it as in AI/ML.Apart from that, it would be great if the platform set CurrDateTime() default value for CreatedOn.Some sort of integration with another popular idea around custom wrapper actions would be appreciated too.

Microsoft has a service called Microsoft Learn MCP Server (microsoft.docs.mcp). With this service, tools like Claude Desktop, VS Code, or AI agents can get information only from Microsoft’s official documentation. Links: https://learn.microsoft.com/training/support/mcp https://github.com/microsoftdocs/mcp If OutSystems had a similar MCP server, it would be very helpful. Here are some reasons: Tools like Claude Desktop or VS Code could search only OutSystems official documentation Companies could easily add official OutSystems info to their support tools or knowledge systems Developers could build AI agents that use OutSystems official documentation For OutSystems developers, using official info through an MCP server would be very useful. I hope OutSystems will think about making a service like Microsoft Learn MCP Server.

We need fine-grained control over indexes. There are things like "fill factor" which we can set through SQL Management Studio, but we cannot set through Service Studio. This is a problem for 3 reasons: 1. Who knows when a deploy will wipe it out? 2. Customers on the OutSystems cloud do not have access to the DB to add it. 3. We love to manage everything through proper OutSystems tools! J.Ja

When creating an application with Mentor, I would like to see the effective creation of business processes (BPMs), because in tests, in the requirement document that Mentor read, it has the BPM rules but it seems that it has not yet been implemented.