Today, when there is need to do some configuration in the destination environment of a deployment (site properties, timers, end points, etc), this configuration must be made after the deployment is done.Would be nice to have a way of preparing those configurations during the planning and see them being applied automatically during the deployment.

As OutSystems is moving away from providing licenses with unlimited ao's could we get the ao count for forge items listed in the forge?

 Context: When a merge is performed and copy/paste is detected, the system should notify the user immediately. This notification is crucial so the developer understands that the original reference will be lost in subsequent environments — TST, HMG, PPRD, and PRD — with production being the most critical. Entity Risk: Data Loss : Copy/paste can overwrite or eliminate important references, leading to inconsistencies and missing information. Process Impacted : Suspension of Active Processes : Losing references may interrupt workflows or cause unexpected behavior in critical environments. Current Problem : At present, the merge process does not provide a clear “red alert” warning when this situation occurs. As a result, unaware/new developers may unintentionally commit this error, causing data loss and instability. Proposed Improvement: Preventive Alert System Automatically detect copy/paste during merge. Display a high-visibility warning (e.g., “⚠️ Warning: Original reference will be lost”). Developer Awareness & Accountability Require explicit confirmation before allowing the merge to proceed. Log the incident for traceability and quality assurance. Benefits Prevents data loss across environments. Improves system reliability in production. Ensures developers are fully aware of the consequences before committing changes.

I am suggesting the addition of an IsAsynchronous parameter ( non-mandatory, set to False by default ) on the Refresh Data UI Flow Screen action, to tell the Refresh Data block to run the given Data Source in either an asynchronous or synchronous way, depending on the value of that input. This will spare the work of creating dedicated screen actions to refresh the Data Sources separately in a Screen Action to conceive a pure asynchronous Data Source Refresh, when applicable. Best regards!

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.

An AI within the development studio/canvas that analyzes complex Aggregates and SQL queries and suggests performance improvements. For example, it could recommend creating new indexes, simplifying joins, using CTEs or temp tables or using more efficient filter patterns based on the data model and query structure. This could be a more granular version of the existing AI Mentor.

When working on the theme I accidentally introduced an error by putting a square bracket in one of the lines, like the one we can see in line 92 here: This did not raise any errors on TrueChange allowing me to publish the theme and break all the classes that were below that line. Since the theme was visible in the sources of the browser and properly loaded, it took too much time to realize it was a simple syntax error. This could have been avoided if TrueChange would not allow to publish CSS with syntax errors.

Make it possible to consume Service actions from within a library. Within a library I can consume a REST API, but can not consume a service action. A REST API gives additional overhead in respect to a service action call, like additional authentication and autorisation. In a service action this is all safely handled by OutSystems.

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

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: