Hello, we have thousand of fake references between espaces, created by unused references, that are created wrong outdated espaces.Also are creating false positive architecture violations, and we suspect that can affect solution publish time.We have more that 400 publish per day, so asking developers to click on remove unused references on each publish does not make any sense.If we think that most of these references come from invisible actions, like copy paste between espaces, on add references with multiple other references, these should be and automatic action, on Service Studio publish, or on Service Center solution publish, like publish with full compilations one.In my opinion, in Service Center, its mandatory, specially when you have huge factory like ours with 1500 espaces, and you want to clean up legacy code.

Currently, OutSystems allows exporting the BPT Process Flow as an image, which is very useful for documentation and communication. However, this export only shows the high-level activities and does not include the logic implemented inside each activity. Adding the ability to export the internal logic of BPT Activities as an image would complement the existing Process Flow export, allowing developers to capture both the high-level process view and the detailed activity implementation.

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.

 TLDR: CSS Layers are a way to define order of precedence in the case of multiple cascade layers. The suggestion is to implement a way to define these layers, to further improve the development of custom themes and layouts. Why?Being able to define cascade layers allows the developers to separate stylesheets into a hierarchy of priority. Quoting the MDN article:"[A cascade layer] enables the creation of simpler CSS selectors because you do not have to ensure that a selector will have high enough specificity to override competing rules; all you need to ensure is that it appears in a later layer."In practical OutSystems terms, this means that the OutSystems UI stylesheet could sit in an early layer while the Custom Theme of an application could be placed in a later layer, hence avoiding overriding conflicts with existing rules. Furthermore, in environments where a Custom Theme exists, but a superset theme is applied to specific applications, conflicts of specificity could also be avoided. How?This layer definition could be placed in a per-CSS file basis: it's just another parameter like "Name", "Description", "Public", etc. The layer order (or precedence list) could be defined in the Theme Editor, or be set in Service Center.

I see a lot of spam posts in the forum. Add a button so we can report this.

Several of the patterns provided by OutSystems UI can be used as replacements for native widgets (e.g. Input or ComboBox), but since they are not native HTML elements they cannot be bound to a Label and take advantage of the Is Mandatory text decoration nor the focus switch when the Label is clicked/touched.It would be an interesting language development if any Block could optionally define one of its widgets as the default widget for this purpose though! Blocks with a default widget defined would then be available for selection on the Label's Input Widget dropdown.OutSystems UI and any other pattern library could then make use of this and integrate seamlessly with the existing Form behavior.Idea sparked by this post : https://www.outsystems.com/forums/discussion/64101/outsystems-ui-dropdownsearch-is-not-a-valid-label-input-widget/

Implement an additional functionality that allows searching for all uses of a CSS class across all consumer modules of that stylesheet. The front-end teams would greatly benefit from this measure, as it streamlines development and enhances maintenance processes.

In O11 we can end other debugging sessions by republishing the module. However, this does not work in ODC. It would be nice if there is a button next to each "active session" in the Users section of the Debugger tab in ODC Studio. With the click of the button, the debug session of the other account would end. This way, we can make sure that the app continues running normally without hitting the debugger activated by other accounts, in case the other users are unable to end their session. Security-wise it would be nice to give this option only to organizational accounts with elevated roles, e.g. the tech lead role.

I love the free personal environments that OutSystems offers the community free of charge! It offers a lot of freedom to develop and test applications without the burden of contaminating your own business environments.On various circumstances I had problems with my personal environment. It was offline for days and had to raise a ticket with support. It would be great if I have the option to reset my personal environment to the initial state. Meaning that all customizations and configurations on my personal environment are wiped.

Recently I often have to merge changes to the older environment, unfortunately, because this process is exhausting. The target environment is way behind (which is basically the reason why we need to use merge), and so the merge dialog pre-selects everything in the source module (as the newer version), and I have to spend a lot of time simply unchecking all that, because usually I need to merge only few elements. A module can be big and there can be conflicts, which turns this into nightmare. The quickest way I know is to go down with arrow key and use space to select, but every time when it hits the conflict - the popup dialog requires mouse click. To make things worse, sometimes studio does automatic merge, and it's not always possible to unselect it. Then after spending around 20 minutes on this, I find that the action was incorrectly merged, and this means starting again. Anyway, this could be significantly easier if there was an option to select everything from either source or target, and then you would go and modify only the elements actually needed.