This first started as a forum thread but I think that an Idea will get a bit more traction: https://www.outsystems.com/forums/discussion/60035/reactive-keep-submenu-open-after-selection/?utm_source=community&utm_medium=email&utm_campaign=forum-reply=#Post249116 The IdeaI have a menu that contains a Submenu. This is implement as shown below;Whenever I open the submenu and click on one of it's items the page opens but the submenu closes. I rather want it to stay open.Note that having it open by default is no issue, that's simply by adding the css class "open" to the ExtendedClass parameter. And I could of course create a whole elaborate mess of client actions and local variables to detect if I need to add the "open" class to the submenu but I was wondering if there is a nicer and cleaner method for this?Please note that by adding this "open" class to the submenu you get a nasty flicker. After moving to a new page the submenu is being closed by the platform only to be opened again by the CSS class. This leads to a series of animations that looks real ugly.Demo: https://vkoning.outsystemscloud.com/LeafletJSReactiveDemo/EventsToggleEventsDownload: https://www.outsystems.com/forge/component-overview/6907/leafletjs-reactivenote: No, this is not an advertorial in disguise. I really want to have a nice and clean solution for this problem and this application has and easy to share behavior of my issue.

Now if we don't want to show the content of a web block in their consumers we need to add an if statement there to show an image or whatever we want to show in the consumers. Like in the image below:It would be good to have an attribute in the block to set an exhibition icon, and this would avoid us to write code only to show an image that also pollutes the content of the web block.

This idea proposes a built-in visual tool that validates API requests and responses against their defined contracts, such as Swagger or OpenAPI specifications. The tool would automatically detect missing fields, incorrect data types, and deprecated attributes before or during runtime, helping developers catch integration issues early. By making API contract validation visible and easy to understand within OutSystems, teams can reduce production defects and integration failures without relying on external tools or manual testing.

Hi all,In our Infrasctrure we have more than one Development Environment, but we can only use Architecture Dashboard for one Development Environment.From Documentation :"Currently, you cannot have more than 1 Code Analysis environment (usually development environment) per installation, i.e, with the same activation code."I know that is only impacts in big software factories with different development pipelines, but is a nice tool for all developers.

Based on the public CVE database, OutSystems Estudio could notify you when a component, library or other external item has a public CVE (Common Vulnerabilities and Exposures). Example: I found a javascript library that allows you to upload and manipulate images, and I implemented it in my OutSystems application. But I didn't know that this library in the version I implemented was vulnerable, publicly known. So, just as the studio today shows some warnings during development, it would be interesting now that it uses AI, for the platform to somehow visually show that the version of the library I implemented has a CVE (Common Vulnerabilities and Exposures). This would increase the level of security and help developers or projects that do not have a security team to validate or do pentesting. Imagine, a warning appears in the studio: Component XYZ has a CVE registered in this version. :)

Add deployment plan and deployment notes in ODC, like there are in O11.

Currently, We have the option to add new Entities and attributes and similar UI screens from the ODC portal. A enhancement to ODC AI mentor that enabled extension of existing applications by automatically identifying and reusing dependencies within the same/different ODC environment / integrations. Enhance ODC AI Mentor to support the following flow: Allow the developer to upload a BRD /FRD or provide promt describing the required extension. AI mentor analyzes the input and automatically refers the existing app in th ODC environment. AI mentor identifies and fetches relevant dependencies, such as Entities, Server actions, Integrations, Business rules, UI components if applicable based on this , AI mentor generates a new module and links it with the existing app dependencies. Sample example: If an existing lets say Movie Booking App doesnot have a ratings and feedback module , the developer can, either upload a BRD describing the feature or provide a prompt to refer existing app from this AI mentor identifies existing entities like Movies,Users,Bookings etc... AI Mentor creates a new module for ratings & feedback and links it to the existing entities This feature would be very useful for developers and make it efficient to build and extend applications in ODC. Thank you

Dropdown Search widget puts a margin at the end of the selected value, in order to create a buffer between the value and the action in the end. However, in pages with right-to-left direction, the margin is not reversed, it remains the same. Here is an example of LTR & RTL pages: English Arabic

While using some tools like IcoMoon to extend the icon collection to fit more with my project theme, I face an issue with dual color icons. I am talking about the icons that is defacto mono color, but some paths has opacity, to apply shadow or set background color for example. This icons inherit a single color form its parent, or by applied color using classes, like normal icons. Some icons may be rendered with many paths. If the icon need 1 or 2 paths, it can be applied with pseudo elements, "::before" and "::after". Icon: delete-01 Icon: delete-02 However, if it need more than 2 paths, then OutSystems' icon widget cannot be used. Instead I uses "HTML Element" and add "span" elements in it. Icon: delete-03 So it would be easier if the Icon widget detects the number of needed paths by it self, or has a lot of paths appended in it to support a wider range of icons in it.

Right now, once a secret site property is created, you can’t see or validate the actual value—especially in production environments, where developers don’t have access and only a dedicated support team configures the values. This creates a risk: if the value is entered incorrectly, there's no easy way to check or confirm it. Benefit: It would help with auditing and validation. Teams could verify that the correct value is set, even in restricted environments, and avoid errors caused by misconfiguration. Thanks