At this moment, when we set the "Align" property of a container, it generates the align property in the HTML.Example:Align -> RightGenerates: <div align="right"></div>My proposal is to generate "system" classes the same way "OSInline" is added when a container doesn't have "Width" property set.My suggestion is (following above example):Align -> RightGenerates: <div class="OSAlignRight"></div>.OSAlignRight {    text-align: right;}.ar .OSAlignRight {    text-align: left;}The motivation:- I'm working in Arabic applications and it's a pain in the ass to go around that "align" property. Even after telling the whole dev team "don't use that crap, use our classes".Please, also update the SILK UI "out-of-the-box" RTL stylesheet to override this system classes.

Once in a while I have a project where 2 (or more) different types of users ( paid/free consumer/business etc) use the same application/flow/pages but require different styling.I know currently I can:- make different applications- make 2 flows- etcBut these options often result in doing double workSo I can:- Use a webblock with conditional css (not very pretty)- Use a class and write seperate code for each case in the css fileThe latter will result in unnecessary code in the css file (currently the best option I think thought)So it would be nice to have a (site property controlled) conditional theme. This way we can make a base them and then base the conditional themes on that.Alternatively allowing for SCSS would be a nice addition to create user personalized themes in your applications in a pretty way

It would be great if the reactive data grid provided associative columns or dependency between columns.For example, there are two dropdown columns, one called Function and the other called Role. When a Function is selected, the dropdown Role will display only the roles belonging to the selected Function.I think it is a very important functionality, used in a lot of cases, so it would be very good having it in the reactive data grid.Thank you

Hi,The Log Content flag on an email should continue to be a Boolean, but not a hard-coded one.  I like the idea of logging the email, but only for a certain amount of time or as result of an expression. Shouldn't make me publish a new version to change this behavior.João

It would be very usefull if the platform would somehow support or at least make it easier to copy all (entity) data from a production-server to (for example) a quality server. I don't want to copy just the entire database, as this would also include timer-settings etc. which could contain production-paths. Ideally, there would be an (external) tool which lists all espaces with their entities, and you can check which ones you want to transfer to another database.

Similar to when I drag a screen action to the screen and OutSystems automatically creates a button on the screen, it would be nice to drag a client action and have OutSystems create a wrapper screen action (that calls that client action) and a button on the screen

the possibility to query a record list (ie. local/input variable) would rock!instead of querying/manipulating one/multiple entities multiple times, untill you have all relevant data together.why not query a record list already available? even if it consists only of structuresthis would seriously increase performance and reduce complexity.specially since you dont need those loops with an IF anymore, that simply skip all records untill youve reached the one you want.thanks for liking!

Recently I had a problem when updating the OutSystemsUI library, the version I updated had a bug. As I continued development, I only later realized that there were some misbehaving components, and I soon suspected the OutSystems UI update. This way I had to go back several versions of my application, to get back to the last version of OutSystems UI, without any problems. This can happen with any library, and without more serious scenarios. There doesn't need to be many versions available to choose from, I believe that between 3 and 5 would be enough.

I have been taking guided paths and courses from the Learn page, but when I'm looking for a new course to take, the courses that I have already done are mixed with the ones that I have not. It would be good if I was able to filter and see only the courses that are yet to be done.

Currently, OutSystems documentation provides a list of compatible browsers for generated applications. However, verifying this compatibility at runtime requires developers to manually implement logic using functions like GetBrowser or GetUserAgent from the HTTPRequestHandler extension. This approach has drawbacks: Manual Maintenance: Developers must update their code whenever the official compatibility list changes, risking outdated implementations. Difficult Diagnosis: Identifying issues caused by unsupported browsers can be time-consuming, as seen in a real case where support intervention was required. Suggestion:Introduce a built-in Action in the platform to automatically verify browser compatibility using OutSystems’ maintained compatibility list. Benefits: Simplifies development by removing the need for custom maintenance. Speeds up issue diagnosis related to browser compatibility. Enhances user experience by providing immediate feedback if an unsupported browser is detected. IsBrowserCompatible() -> Boolean The Action would return True for compatible browsers and False otherwise. Additional functionality could provide details about the detected browser and compatibility issues.