It would be nice if the platform could expose the underlying stack(.net, js, ...any?) bitwise operators at the Built-In functions, maybe a "Bitwise" folder with AND, OR, Complement, Left Shift and Right Shift.There are several applications for this when masking, dealing with multiple checkboxes/radios, datapoints, conversions, algorithms, and even external connectors to SBCs/Microcontrollers.It seems a bit overkill to have a forge component or adding an extension/block for it.

When we export some Excel data using the Excel To Record List action, the column headers is filled with the name of the field in the structure, but we are not able to translate that name. It will be very usefull to translate this name for Export in different languages

In O11, we are still able to retrieve the description of roles via system entities and display them in our UI In ODC User API, there is not such feature. It will be nice to have them, as a similar point to this Idea , we can't have spaces in the RoleName. And it does really looks awful to just display the role name in the UI

Hi,Would be great for troubleshooting if the runtime values used in query parameters were also logged in the error log text. The tenant Id would also be a good idea to support multi-tenant scenarios.Of course this would only be applicable to query related errors and they could be shown in the log in a very simple manner like:"TenantId = 1Param1 = 123Param2 = "Text"Error in advanced query  (...)"This would allow much faster debug in Service Studio.Cheers,Hermínio

By Default fill in the Description Section of the Aggregate and Timers when a new aggregate or timer or any variable is created to avoid Architecture Dashboard Issues.The user can then change it to any values he wants. This will avoid issues on the Architecture Dashboard which in turn will increase the development speed.

Hi, I have an idea to simplify email development in OutSystems a screen to preview email's HTML with dynamic data directly in the browser. the goal will be, Allow us developers to see the final rendered email (with parameters) in a browser during development. Benefits: Speeds up email design & testing. Easy debugging of layout/data issues. Can be reused as a live “View in Browser” link if needed. Best Regards, Faiz Khan

As developers, we often get requirements where users upload files (PDFs, images, or scanned documents), and we need to extract text or structured data from those files inside our OutSystems applications. Currently, we must integrate external OCR APIs (like Google Vision, Azure Cognitive Services, or Tesseract) manually — which adds extra configuration and cost. It would be great if OutSystems could provide a built-in OCR Extraction Action that allows developers to: Upload a file (PDF, image, DOCX, etc.) Automatically extract and return the text/data content Use it in server or client actions easily This would simplify many automation and document-processing use cases directly in ODC or O11 without third-party integrations. Is there any plan from OutSystems to provide such an OCR capability as a native AI action?

When working with popup's in service studio for a reactive application, they overlap with the screen they are used in. On the forum is a great solution for this problem -> https://www.outsystems.com/forums/discussion/55208/zoom-in-or-out-feature-on-interface-outsystems-service-studio-11/ Why not make it part of a next version of outsystems ui, so everyone has this solution at start ?

In service studio, when we are managing dependencies, for entities, we are able to preview the attributes of the entity. This is very useful, as it allows us to see whether we are adding entities which contains the FK or PK references. In ODC studio, this option is not available. Which means we have to add the public elements, and then go to the data tab and preview the attributes. Good thing we do not have to do a publish first. Because, actually i don't even need to see the data or values, i just want to see the attributes which quite often, it is good enough And the worst part, we can't even resize the pop up in ODC studio. So have to hover over the description one-by-one to look at it

In the Language Translations editor, please enable multi-select dropdown support for the Behavior filter. Currently, when searching for a word to translate, the editor also shows results already marked as Don't Translate, which adds extra effort to filter them out manually. If Service Studio allowed filtering to show only items marked as To Define and Translate, it would significantly simplify the translation process.