It would be interesting after selecting several Server Actions to be able to place them in a folder by right-clicking the mouse. "Enclose in Folder". In the same way that it is done with the Widgets in which we select several elements in the Widget Tree, for example, and the "Enclose in Container" or "Enclose in If" option appears.

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.

While using expressions in Service Studio, it would be useful if the suggestions automatically select the correct Null function if I type "null", depending on the context.

For a DropdownSearch there are options for translating/changing NoResultText and SearchPrompt It would be good if the OptionalConfigs also have a configuration for clearButtonText

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.

I don't know about you, but I always check if an Aggregate has actually Found something, instead of it being empty.So, in an If Condition after an Aggregate, I keep selecting the Aggregate.List.Empty suggestion, then editting it to "not Aggregate.List.Empty".Could ServiceStudio be updated so the not-variant is also present in the list of Suggestions?

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.

The Demos in Forge projects take up a TON of SUs/AOs. But if you delete the demos after installing, the next time you upgrade the component you get the demo code again.Solution: have the component author upload a demo (OAP, OML, or OSP) separately from the component itself (OAP, OML, OSP, or XIF). Then allow the Forge user a choice of "Download Component Only" or "Download Component + Demo".To make this better, add a "Project" that is similar to an OSP, but can contain Applications as well. That way, the Demo can be a separate Application from the Component, and they can be delivered together in one download. A level above "Application" has been requested a few times already.J.Ja

It would be very helpful to have a consolidated view of all Consumed APIs and Site Properties within the Service Center, under the Factory tab. Currently, when moving from one environment to another, it's difficult to track where each API is being consumed. Even if we know the API is in use, we still have to manually navigate through each application, then into the module, and finally into the integration settings to make changes. The same challenge applies to Site Properties. Having everything in one centralized location would streamline the process significantly. Open to any suggestions! 🙂

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