Whenever we are on the viewing the widget tree of a page or Webblock, if we click on the "Go to <insert element here>" we continue on the same widget tree view mode and need to click again on the widget tree icon to finally see the element we selected as demonstrated on the gif below. The rationale is that if we are using the "Go to" context menu, 9 out of 10 times we want to open the original module to inspect/change the element selected.It would be nice that when we use the "Go to <insert element here>" context menu it would change to the view that actually allow us to "go" to that element

The Julian Number to Date Converter on the ODC platform enables users to quickly and accurately convert Julian dates into standard calendar dates. It simplifies date interpretation for datasets that use Julian numbering, ensuring consistency, readability, and error-free date handling across analytics, reporting, and operational workflows. This utility improves efficiency when working with legacy systems, data integrations, and time-based calculations within ODC

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

 New functionality: It would be nice to select some logic nodes, right click and "🔒 lock" them. How it will affect the developer? When you want to do changes, you have to unlock the nodes and provide a comment/reason why you want to change them. Other effects? During the merge or code update, all commented changes are shown so each developer knows something happened there. This would be a good functionality to protect Interface-code or some heavy business logic that normaly does not need to be changed. When would this come into play? Replace All / Find'n'Replace might change code that should only be changed with care APIs/Interfaces might be changed because of a call or so, but more than just one person should be informed about this Law relevant logic might be changed etc.

As NextStep 2012 says 'Simplicity'.A switch widget on a webscreen will make the web screens more simple to understand!

 Proposal In Lifetime, when we do a promotion to another environment, we have the ability to add custom steps between environments to create a pipeline. In these custom steps we could connect to AI mentor, BDD tests, another test tolls or even a custom application. In a simple vision this could be a URL parameterisation and a result that is expected. Added value to OutSystems customers 1. Avoid to spend more money in 3rd party tools and devops engineers to create custom pipelines (Azure devops, Jenkins, ...) 2. Increase speed in delivery because all steps are inside our platform 3. Simplified and unified release process.

Create the possibility of folders in the CSS editor.This way we can better organize the components and make it easier to update them.

Some teams have been keeping technical documentation on a separate document format instead of generating using OutDoc to leverage, which makes this Indicator, especially in cases where the Application is not meant to be a component or widget, unnecessary.So, maybe if there was a Settings feature where we could set this Indicator as optional / mandatory for a given Application, it would be helpful.

Will be helpful to have a build-in fuction to remove duplicates from a listExampleList {A, B, C, A, B }Result list {C}

It would be great to have a test at the end of each "path" to verify if you miss something important. Also it would be great if that question will be at the same format as on the certifications exams.