All modern IDEs include some form of AI-powered coding assistance. While Service Studio does suggest certain nodes, it lacks the capability to enhance a developer's logic with meaningful autocomplete suggestions. It would be nice to have a co-pilot-like feature in Service Studio.

While in Debug Mode, have the chance of setting the Execution to step-back in the flow. Along with this Idea  debugging will be quicker.

In some situations the platform should auto refresh espaces and publish them (if possible).Scenario:Public Entities consumed by several espaces.There's the need to add a new column or record for static entities.Consumers will be outdated/broken.When the espace with the change is published which has consumers, should check if its possible to auto-refresh the consumer, and if so refresh it and publish it automatically.By the way it would be nice to have more filters on Espaces List in SC.

Currently, the Serialize node only provide an option to exclude attributes that have default values. However, there is no option to explicitly exclude custom-selected attributes. This capability is especially useful for logging scenarios . In many cases, creating an additional Structure just to map and exclude specific attributes is redundant and unnecessary. Most serialized outputs are eventually passed to a JavaScript node , written to logs, or stored in a database purely for logging purposes. Allowing developers to select which attributes should be excluded during serialization would significantly reduce development time, keep the code cleaner, and improve maintainability. It would also eliminate the need for extra mapping structures that add complexity without real value.

As confirmed by OutSystems in this forum topic , data fetch actions are not optimized and instead passing all screen data in every request payload. Even if the parameters are not used anywhere in the data action. Please optimize this.

Quite often I go through some modules to clean it from elements that are not used anymore. It would be great if there was a way to know all the components that are not used inside a module and maybe delete them similar to the remove unused dependencies instead of going through every element and clicking find usages in all modules and then deleting it manually if not used

GDPR requires organizations to implement appropriate technical and organizational measures to ensure a level of security appropriate to the risk. CMK supports this requirement by enabling strong encryption practices, which are critical for protecting personal data against unauthorized access. Currently enforcing customers own encryption key is only available through application level which requires extensive implementation cost that will delay projects and cause customer frustration, when their other resources in Azure or data platforms like Snowflake support CMK out of the box. As part of an enhanced security add-on it would be great with such functionality at platform level.

Hi,Service Studio could help our developers in maintainability/architecture tasks doing an analysis on all "Unused public objects". This option could be something like "Remove Unused Dependencies" but could check all objects that don't have usage in other modules.+ will allow developers keep applications smaller, delete unused features+ spare a lot of time, because this tasks is manually our days+ already have a manual task for that, so Outsystems will only automate, no extra work needed

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

Just like Service Studio, it would be great to have an auto-update feature in Integration Studio as well. This would streamline the upgrade process and ensure consistency across tools.