Outsystems don't preserve, by now, session variables in server side, when you call from mobile apps, between calls.This is how it works, and it is "reasonable", but it does preserve some data such as UserId or TenantId (when you do a SwitchTenant) between mobile calls to a server actions for the correct behavior of platform. The problem:If you have a multilingual mobile app, the translations in client side can be resolved with: “ Multilingual Mobile Component ”.But when you have core modules, with server static tables, server process, server sends emails, etc...  What's up with the locale?Currently, the locale, in each call from mobile call is set in the platform default local (for example, en-US). If the user want to retrieve the translation of static tables in his language (for example French), or send emails using the translation resources in french, need to set the locale all the time en each server action that is called by a mobile app.This is also a problem, when you use an aggregate in movile app in screen, and join with an static table, because you can not set locale in server side before aggregate execute, and locale translations allways are retrived in default Platform language. Example:I attach a solution with a mobile app and a core services with an static tables of colors, translated with resources in French, Spanish, and English.We have two server actions, one that returns colors, and the other one that setlocale to french and return colors...We have a mobile app with two buttons, Button "getcolors", that returns the colors without set locale. If you click first, the colors are returned in US (the default locale of platform), and are printed.If you click the second button, locale is setting in french and colors returned in french.If you click second button (and locale is setted), and after you click first button, colors should be returned in french (as the web applications do). But you can see that are returned in english, so locale don't persist between server calls...The second part of mobile screen calle "colors from agregate", is performing an aggregate agains static server table, and, as you can see, retrieves the result in default locale (en-US).This has been explain into support case 2233103, and, we have confirm with Outsystems that there is no workarround once time only, you need to set locale each time you call to a server action. Solution:If you set locale with SetCurrentLocale action in server side, it sounds reasonable that the following calls from this user to servers actions (in that session) you want to use the same language (at least until you make another SetCurrentLocale), so Locale should be also persisted in server side (like tenantId or UserId), between movile calls .

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.

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/

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.

 Need : A scene builder insight service studio for WebXR. Drag and drop 3D elements that bind to Outsystems data entities. Usecase: A field service app where a technician points their glasses at a machine, and Outsystems logic overlay the maintenance history data directly onto the hardware in 3D.