Several of the patterns provided by OutSystems UI can be used as replacements for native widgets (e.g. Input or ComboBox), but since they are not native HTML elements they cannot be bound to a Label and take advantage of the Is Mandatory text decoration nor the focus switch when the Label is clicked/touched.It would be an interesting language development if any Block could optionally define one of its widgets as the default widget for this purpose though! Blocks with a default widget defined would then be available for selection on the Label's Input Widget dropdown.OutSystems UI and any other pattern library could then make use of this and integrate seamlessly with the existing Form behavior.Idea sparked by this post : https://www.outsystems.com/forums/discussion/64101/outsystems-ui-dropdownsearch-is-not-a-valid-label-input-widget/

There is a protocol growing fast in the gen ai community called MCP(Model Context Protocol). The current SDK does not support C#. I think it would be awesome if Outsystems allowed you to create MCP Server in a OS environment in a really fast way making apps useful for external AI agents.

With multilingual in a web or mobile project , it is necessary to show dates in the respective languages.The idea would be to have an extra field in the FormatDateTime function that would allow you to receive the location and return the formatted translated date.All the Locales would be expressed according to the RFC 1766 standard format.Examples:In English (default): Friday, 08 november, 2019In Dutch: Vrijdag, 08 november, 2019In French: Vendredi, 08 novembre, 2019In Spanish: Viernes, 08 noviembre, 2019

 ServiceCenter allows you to config 1 set of email settings, some clients/applications may require the use of multiple email servers. Example 1 Vendor 1:  Is using application X, and they want to send emails from their own server mail.vendor1.com using their own email address service@vendor1.com Vendor 2:  Is using application X,, and they too want to send out emails from their own servers mail.vendor2.com using their own email address service@vendor2.com Example 2 eSpace application A is using email service@domainA.com eSpace application B is using email service@domainB.com Please add capability to support these scenarios.

Hello Guys,It would be great if solution publish process could be enhanced to be faster. Our project has many modules and takes longer than we require in our continuous integration process to publish a solution.Just to give a bit of context with an example - in our daily continuous integration process, we publish a solution against our DEV environment and, if everything goes well, we push it to the next environment for next day QA testing. The issue we face is that with the time it takes, if anything goes wrong with either of these solution publishes, we can have a hard time to react on time to fix the problem and to try again, on the same day.

OutSystems did an awesome job with redesigning the icon system which is used in the Hybrid version of Service Studio.However I think some icon designs got worse, mostly noted the input and output parameter icons:In the old design the arrow in and out are very clearIn the new design:Regards,Daniel

Currently, OutSystems developers cloud (ODC) is only available as paid service but it would be great if it is made available to the general developer community as well to experience and explore it. 1. We may be able to suggest some additional ideas and improvements needed for the portal. 2. Will make us gain practical experience in it. Which can also help us plan to include it in upcoming projects.

Physical table attributes are not renamed when the entity attributes are renamed, requiring manual upgrade scripts.

Currently, we need to manually create and implement audit trails for every data change (Create, Update, Delete). This process is repetitive, error-prone, and adds significant development time. It also leads to performance issues, bloats the AOs, and creates complex, hard-to-maintain flows. Solution: Automated and Integrated Audit Logging The proposed solution is a built-in Service Studio feature that automates the entire process. Developers would simply enable an "Audit Log" property on an entity. The platform would then: Automatically inject highly optimized, asynchronous logging logic into the entity's database actions. Handle all performance optimizations behind the scenes to avoid slowing down the main transaction. Prevent the creation of extra AOs, as the audit data would be managed by the platform itself. This transforms a complex, manual task into a single-click action, freeing developers to focus on core business logic while ensuring consistent, high-performance, and reliable data security and compliance.

 Hi, My idea is to change the service studio color depending on the environment that we are connected. This is to avoid publications in quality environment. Example: dev (green), quality (yellow) and prod (red).