A button to record a debug session, which would make it possible for us to go back in the debug if we wanted to or save it to watch it later while looking at the logic of what we are trying to fix.

On Service Studio, it would be nice to have an icon indicating if there are modules inside the applications that are broken (with errors).For instance, I've updated a component and after that there are 2 apps with broken eSpaces, but in my Service Studio list view of the apps I don't have a way to see it. I need to go into Service Center and go to the eSpaces' list, filter by the ones with errors, check the application and open on Service Studio to refresh the dependencies and publish (jumping in two different "windows" just to clear the errors).

Can we have a feature to view the history of resolved technical debt in AI Mentor Studio? This should include details such as what was resolved, who fixed it and marked it as resolved, and when it was resolved. And export as Excel.

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.

If I want to check for the latest version of the OutSystems naming conventions, I have to go to a Video lesson and check it. https://www.outsystems.com/learn/lesson/1223/module-naming/?LearningPathId=0This is troublesome and a dedicated page or link could be available at https://success.outsystems.com/Documentation/Best_Practices/OutSystems_Platform_Best_PracticesThank you!

Hi All,I was thinking why can't we have automated client side logics. I have came up across with a barrier where client side logic should run automatically on given schedule or if the data is created or updated in database. We can't always go with the JavaScript to refresh data or call client action every 30 sec or 1 min to check the updated data.We have Timer and BPT for server side logic. So I was thinking of having the same for client side logic. It would be great!!:)

In a multi team development environment, changes can be made to an integration such as ingesting a new field in a dev environment (ie adding a new attribute to an entity). Using Integration Builder, this attribute might be added to the integration and work as expected in the Development environment. However, if that integration is now required to be deployed with those changes through to production, but the integrated database doesn't have the required attribute deployed to production, this can cause production errors. My suggestion is to provide a log of changes showing what additions or subtractions have been made to an integration so that they can be validated prior to any deployment. Alternatively, during the preparation of a deployment, test that all integration attributes are valid and pause a deployment to alert of this missing attribute.

 When we publish a component, we earn points on our profile, when we answer a question on the forum, we earn points on our profile, when we watch training, we earn points on our profile. But, when we send a security report through the OutSystems page, we do not earn points on our profile. Just like answering a question on the forum, or publishing a component, people who analyze and send security reports to OutSystems are also contributing to a safer product. Analyzing, detailing, writing and sending a security report to OutSystems, in my opinion, should be scored, as the professional has an account in the community and is helping to keep the product or website safer .

In the Architecture Patterns in ODC course, it would be very helpful to have simple examples of how to apply the patterns mentioned along the course.

Hi, There should be a Color picker widget In the OutSystems UI Module. So we don't need to use other components and possibly not increase Application Object on the server. Or can be added Input Type as a color for the input widget so it will make a color picker. Yes, we can overwrite the property if have the Input Type as color it will be good.