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

When the screen has too much information and the performance starts to decrease one of the options we have is to create a web block with some of that information and do a lazy load.It would be nice to have something similar to "Extract to action" where you can select the elements in the screen and "Extract to Web Block".In case of a table, it would:- Remove the query from the preparation of the screen into the preparation of the Web Block;- Remove the actions from the screen into the Web Block;- Remove the selected elements into the Web Block;- Add the necessary input parameters to the Web Block.

Considering the fact that the cloud version does not support internal network for IP white listing, I think adding an extra layer of security to secure service center  with Two factor authentication should be a standard in the Outsystems platform.

Please can you add the ability to apply field descriptions to ODC External Logic components. If there is already a way to do it, it's not in any of the very scant documentation.

Right now when you want en entire Row of a table clickable (or another event), you need to put the OnClick event on every Row Cell and point to the same action every single time which is quite repetitive and prone to mistakes. If you add a new Row Cell because extra data needs to be shown, you need to put the OnClick action again for this specific Row Cell even though it point to the same end point as the other ones. It would be nice if we could put the event handler on the entire Row instead of on the Row cell. Like this, newly added Row Cells will automatically point to the same OnClick action and you won't forget it. The option to put different handlers on the different Row Cells should still stay. This would just be an extra way to make an Action for a whole Row at once.

I’m proposing a reusable OutSystems component that brings AI-powered form understanding and automated data extraction directly into OutSystems applications. A reusable OutSystems component that uses AI/ML models (like LayoutLM, Donut, or LLM-based extraction) to automatically understand forms, detect fields, and extract structured data from documents such as invoices, applications, KYC forms, and service requests. This component seamlessly plugs into OutSystems apps, allowing developers to infuse AI-powered form interpretation without custom ML development. It accelerates workflows, eliminates manual data entry, improves accuracy, and enables rapid AI-assisted automation across business processes. This component would eliminate repetitive data-entry tasks, reduce errors, and significantly speed up processes like onboarding, KYC document handling, claims processing, invoice management, and service request intake. Developers can simply drag‑and‑drop this AI module into their workflows, instantly infusing AI-assisted automation without creating or training models themselves. Key Capabilities (Sub‑Topics): AI-driven field detection (text, tables, signatures, checkboxes, IDs). Automatic extraction of structured data from PDFs, scanned forms, and images. Layout-aware document understanding using state-of-the-art vision+language models. Configurable rules + LLM hybrid logic for domain-specific extraction. Confidence scoring to determine whether human validation is needed. Seamless integration with existing OutSystems apps and workflows. Support for multi-format documents (PDF, PNG, JPG, digital/handwritten forms). Drag‑and‑drop integration with OutSystems workflows and business processes. Auto-classification of document type (invoice, form, application, etc.). Business Value: Reduces manual data entry and associated errors. Accelerates process automation across departments. Enables smarter, faster digital transformations. Lowers operational cost and improves compliance. Makes AI accessible to OutSystems developers with no ML expertise. Potential Extensions Integration with OutSystems Case Management framework. Prebuilt connectors for storage, email ingestion, or external document APIs. Auto-learning corrections using feedback loops. Analytics dashboards for throughput and accuracy metrics. Multi-language document understanding for global use cases. Conclusion This AI-assisted form understanding component empowers OutSystems applications with intelligent document automation , enabling organizations to save time, reduce errors, and unlock immediate productivity gains—while giving developers a simple, reusable way to bring powerful AI/ML document-processing capabilities into any application.

When I edit or look up data during development with 'View Data' in my entity, the order of the attributes are so random. I'm getting pretty crazy of scrolling and searching for my attribute and it's value. (Especially in my 225 attribute entity! Yes, I could optimize) Why are the attributes not ordered by the way you ordered them in the entity? or at least on alfabatical order? Seems like an easy fix. Also what decides if a attribute is collapsed or expanded? seems random also.

I think it would be great if there were a way to point co-workers to a specific part of the code, for example as Architecture Dashboard does. This would be super helpful to have because we could show directly what part of the code we are talking about with a co-worker.

If you try to use the Mod() (modulus operation, for taking the remainder) function in a Filter of an Aggregate, Service Studio gives an error:"'Mod' function cannot be executed in the database, so it can't receive any attributes from the aggregate as parameter."This is nonsense however, as Microsoft SQL Server has the corresponding "%" operator, and Oracle has a MOD() function, so both supported databases know how to perform a modulus operation just fine. Therefore, Mod() should be allowed in an aggregate.

It would be really helpful to have an "OutSystems Agent" that has knowledge about our codebases and can answer questions, generate insights, suggest actions, etc etc. It could also be connected to app metrics so we would be do some queries like: Why is X app slow today? What changed in the last deployment? Show me all missing role checks in app X Generate sample test cases for screen / action Y and so much more