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 .

Personal test/learning accounts have very short time limits, selected long ago, before the average wristwatch had gigabytes of storage. This has created a problem that if you don't log in to your account weekly, all your work, like forge components you may be maintaining, get deleted. Please can the timeout be extended based on community rating / responsibilities?

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/

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.

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

When we are developing in Reactive, if we have several data aggregates or data actions in the page, at start this data actions will launch in parallel, not delaying the rendering of the page. But when we refresh the data on an action flow, the flow doesn't continues until the data is fetched. It would be great to have an option to modify that behavour, because sometimes we dind't need to wait for the data to get fetched to continue with the flow, sometimes we only refresh data to update something on the screen

 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).

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

Allow 3rd option on Entities, Actions as "Friend" which will make entities and actions visible to all modules within the Espaces Application, but not to other applications.  This will simplify having to keep entities as read-only and then creating actions to do the CRUD operations of the entity.  It will also improve security so that espaces that shouldn't be using these entities won't have visibility of them.

When working with Advanced SQL actions, there is the option to add test values to the parameters, and run the query with them. The executed query is shown in the "Executed SQL" tab, which is great. However, it would be very helpfull if that query could be extended with the parameters used. e.g. declare @company_id int; set @company_id = 3; SELECT [OSDEV1].dbo.[OSUSR_WU3_COMPANY].[ID] , [OSDEV1].dbo.[OSUSR_WU3_COMPANY].[NAME] FROM [OSDEV1].dbo.[OSUSR_WU3_COMPANY] WHERE [OSDEV1].dbo.[OSUSR_WU3_COMPANY].[ID] = @company_id That would make it possible to copy the query with the used parameter values, and paste it in the database tool and be able to run it directly (instead of having to configure the parameters again). Please note that this is somewhat related to this idea, but I believe my suggestion is better: https://www.outsystems.com/ideas/8176/show-real-value-on-advanced-query-executed-sql/