Able to bookmark Documentation, Tech Talk, Dev zone Articles under My Profile.

Static entities are like constants, and they can be used in many eSpaces. Unfortunately there is no way to look for usages of a particular record in all eSpaces, although there is possiblity to find usages inside current eSpace only.For example, we have an entity of shared translations, which contains many many records and is referenced everywhere. If we want to clean it, suspecting that some of the records are not used, or to remove duplicates, it's very hard to check the usages. Or, another case, if you want to find where the record (constant) is used to investigate the logic. Would be great if this was possible.

Hi just want to add a BETWEEN operation in the aggregate where clause, as it's much simpler than the >= and <=

For mobile apps, we frequently leverage in the use of local storage to gain in speed and traffic exchanges.With no Advanced Queries in local storage we cannot do complex queries. I'm limited to the functionalities of the Aggregate.

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.

Since we cannot have Advanced queries for Local Storage, it would be useful if we have a CRUD action that deletes all the records given by a List likewise that is already done by the "CreateOrUpdateAll" action.

We have many List operations both on client and server-side, however we don't have one that would return a range (a subset) of a list, for the provided index and count parameters. This action would correspond to .NET's List.GetRange(index, count) method . An example use-case would be: - We have a large list with 1M+ records - We want to bulk process these records (e.g. BulkInsert) but want to avoid poor performance - In a loop, we get a subset of these records (e.g. 50K records) and do a bulk operation - We adjust the index parameter of ListGetRange and get the next batch of 50K records to process The current workaround is using a foreach and ListAppend, or adding additional code to make it work.

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.

 Greetings Folks,Before I jump on Idea discussion, would like to share my use-case :I have around 60+ modules using the multilingual web component under one single product. We use a third-party paid translator tool to manage the translations.Every time by the end of the sprint, we export the Translations files for all 60 modules via downloading the solution & then using cmd's which in the end give us translation files.Now the actual pain is to update back each respective translated file by using the service studio of a module. Idea :It would be easy for developers If we get an option to directly update all the bulk files via service-center or any means like service-studio or API at once.For instance, like Service Center showing all the modules using the multilingual web component & we have an option to either update any single module resource or all at once.

Hi OutSystems Team, In the OutSystems Support channel , implement a time tracking rule based on SLAs , as some clients use this metric and end up counting elapsed time, which is incorrect. When the issue remains on the client's side, the SLA should not count, or if the client "disappears" and does not close the ticket, this time should also not be counted. This helps OutSystems protect itself from misunderstandings and potential penalties (fines) from the client, which could lead to misinterpretations. The current view considers tickets as either open or closed. Time tracking helps with OutSystems' resolution metrics and protects the company from other interpretations and metrics. It would be beneficial if this data were exported along with the ticket ( spreadsheet generation ).