I suggest excluding the static entities from the counting of Application Objects , as saving it leads to spaghetti code, and using it does not indicate the complexity or magnitude of the project.

A few months after go live, production users start complaining that they randomly lose their session in a mobile app.The conclusion from your testers is that users are logging out of a reactive web application in their desktop browsers, and 5 minutes later they lose the mobile session."IMPOSSIBLE!" - you say - "Logging out from the browser cannot possibly terminate the mobile session 5 minutes later, that's absurd and unheard of"So you try to investigate it yourself and, sure enough, the tester was right. Logging out from the desktop browser indeed terminates not only the mobile session, but every other session of the user. Oh, you also find out that this is documented and deliberate: "When the end user logs out of an application, all sessions are terminated".You investigate further, and begin to realize that it's impossible to preserve the mobile session after the user has logged out from a browser . It's also impossible for the user to use multiple browsers on different devices , or even multiple browsers on the same device, because any logout action would terminate all sessions in all browsers. This is unexpected behavior that contradicts how the web works.You reconvene with your testers to brainstorm workarounds, but you're not taken seriously: "Surely this very expensive platform and market leader can support an application running on two browsers simultaneously!" All you can do is wish it did...If this scenario has happened to you on any project, please like this idea and share with others. Together we can change how the Logout works, and enable this very basic feature which is having two independent sessions on distinct devices.

Quite often, I am repeating the same set of joins in queries (both normal and advanced), that I would ordinarily put in a view. Think e.g. of a CRM system that regularly needs "all active clients" or an ordering system that needs "all open orders". Of course if you need just that, it's easy to put it in an action, but I often find myself needing the result and join that with some other tables. Unfortunately, for some reason OS does not allow to define database views, which imho is a great gap. Therefore, I'd really like to see support for database views or something similar (e.g. queries you can define on eSpace level and join the result of with another query, but that amounts to the same).

Hi,In Reactive Web Apps I've noticed that when navigating to public screens from other modules the transition is very slow - it shows a blank screen first, then it starts loading the screen and the CSS, causing a Flash of unstyled content.This takes about 2 to 4 seconds, making it a horrible experience.Upon further investigation, I've discovered that OutSystems is treating the navigation as a navigation to a totally different application, loading again all the necessary resources (JS, HTML, CSS). This is very atypical for a Single Page Application.This makes segregating front ends a major trade-off.Can this be improved?Thanks,Tiago

Hi, this is just an idea for a developer's perspective, it would be nice to have the ODC workflow builder in ODC Studio itself instead of going back and forth from ODC studio to ODC Portal when developing for the workflow.

Provide the ability to configure application specific test email lists that override the Service Center policy. Still continue to keep the "Redirect Emails to Test List" active in service centre, but provide ability to set list of test email addresses specifically for an individual application. This should ensure any email triggered by that specific application routes only to its designated app level email addresses, bypassing the service centre environment-level list.

Currently each time a site property is saved, the new value is applied to the factory. This is separately done for each site property value that you adjust. In core modules applying the new setting can take some time. It would be nice if it is possible to change multiple site property values before applying the new settings to the whole environment.

The default behaviour of datetime variables in Reactive apps is to convert from UTC to local time. This is a great in a lot of use cases, but hard to work with if a user want to see data in a different timezone.In this forum question , some 'hacks' are proposed:Use datetimes as textCompensate at server side for the difference in client timezoneThe prefered solution is to let developers set the config for this automatic conversion. The default behaviour to convert is good, but make an option to overwrite the default behaviour.

Sometimes I do development in my 4K monitor and its hard for me to do development in the studio because everything is small. If the studio has UI Scaling feature then I can scale the studio's UI to make it everything in the studio (texts & buttons) bigger

As OutSystems is moving away from providing licenses with unlimited ao's could we get the ao count for forge items listed in the forge?