Currently in OutSystems, developers often need to wrap widgets inside a Container or an If widget just to control their visibility. This makes the UI tree more complex and adds unnecessary nodes. Proposed Solution Add a “Visible ” property directly on all widgets. Accepts a Boolean expression No need to wrap the widget inside Containers or If widgets Works for all widget types (Text, Input, Button, List, etc.) Automatically hides/shows the widget based on the expression Example Visible : User.IsAdmin = True The widget is only visible if the expression is true — without adding a Container.

I very much liked in former times the three developer classifications: Associate Professional Expert Professional has unfortunately disappeared now. I think the personal step from Associate to Expert, when setting career goals is a big one. The range from Associate to Expert is too big. I would very much like a reviving the professional status, after the Associate classificaton when a developer obtains any three of the six required additional certifications for an OutSystems Expert to get rewarded as "OutSystems Professional Developer"

Right now when a user navigates to a URL that is not associated with a page or the URL for a page that has been removed, you end up at an ugly 404 page located in /customHandlers/ As seen in this forum post you can edit the custom Handler's page directly, but my understanding this would change it for all apps, and doesn't seem possible in a Cloud environment. It would be nice if we at least had the option of configuring the 404 page, similar to the Invalid permissions or Internal error pages. Especially if one of the inputs of this page was the originally attempted URL, meaning we could redirect the users if they were attempting to go to an old screen that was removed, but the content is now elsewhere. Thanks!

IDEA: Creation of an environment for certified developers (with at least 6 months or 1 year of certification) where he/she could test the advanced skills to pass the professional certification, the management of environment, lifetime, to create plugins or give support to the ones created when had access to such environment, etcThis would solve the lack of practice of many developers who want to give an extra step in the career and don't have opportunity to test in the company where he/she is working and would spend months or years just with theoretical knowledge until have the opportunity to test what have learnt; and for the developers who created a component but no longer have access to the lifetime would be a good chance to update the components.

Service Studio is supposed to be a WYSIWYG IDE. However, when working with things displayed in conditional situations, the layouts tend to shrink, resize, warp, or whatever else, breaking the preview. Example: This search with filters section is something very common to be found in many apps. This is a screenshot from the preview in Service Studio, and matches exactly what renders on the website after publishing. However a requirement came up to hide the bottom two under a role check, wrapping them in an If to only display them if they come up True: If published, rendered it looks fine, but the preview in Service Studio breaks There are some tricks; wrap the If in a container, put an empty container in the False branch... but those are just workarounds which shouldn't be necessary (and sometimes, as in the screenshots, they don't work) The idea, in short, is: make Service Studio render the contents as the CSS rules say it will render, If or no If

As requested by OutSystems Support Team, I am creating this Idea because it's important that the build log for any compilation on mobile on ODC be similiar to what we have in O11. Today, the mobile build is a huge amount of text that can be difficult to understand what is the main reason your mobile app is not compiling. In O11, it's more easy to understand. Maybe on ODC, put the main error on the top (or at the end) of the file so the developer can easily identify the root cause of the APK/IPA being broken upon compilation.

There could be some magic feature that would make this time saver feature. :-)Then we could make a simple query to build the 'skeleton' of a query and then introduce the aditional rules that cannot be defined in a simple query.

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.

The help page you are given a link to when publishing from ODC to the Forge is completely blank. Can someone add some details please?

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