Sometimes you have two buttons that you want to have as the "Default" button based on different conditions. For example, if you have a screen with basic and advanced search, you want the "Search" button to be the default button, but you have a different "Seach" button in the If. J.Ja

It would be nice if there is a comment widget I could place on Screens and Blocks of Reactive Web Apps and Mobile Apps, like it is possible for Traditional Web.

Hi guys,A question that everyone has been asking after changing the certifications, and with this I think that was pleasing to many ... is why the specialization in Mobile does not appear in the Diploma that we download. I think it would be an asset to have this information also present in our certifications (and specializations) diploma from OutSystems.Cheers,Miguel

In O11 , when you copy logic, screens, or any other elements from one ( source ) module and paste them into another ( destination ) module, any external references used by the copied elements of the source module are automatically added to the destination module. This is quite helpful sometimes, especially when you are trying to copy screens/logic from one application to another (I had to do this a bunch of times in the past, for various reasons). However, in ODC , this is not the case. Once some elements (referencing some dependencies) are copied from one module to another, none of the references are automatically added (unlike in O11 ). This results in hundreds of errors sometimes, which could be reduced to just a few if automatic dependency referencing worked like in O11 . It would be great if this automatic dependency referencing is added to ODC as well, unless there's a valid reason for excluding this feature in ODC . Thanks in advance, looking forward to hearing about others' experiences and feedback :)

Hi OutSystems Team, It would be incredibly valuable to introduce a feature in Service Studio that allows developers to select and manage specific versions of producers when configuring dependencies. This enhancement would align with the familiar workflow of Visual Studio’s package manager, empowering teams with precise control over which producer versions their applications depend on. Key Benefits: Stability & Reliability: Locking dependencies to verified versions minimizes the risk of unexpected changes or regressions. Simplified Rollback: Facilitates quick reversion to previous versions if newer updates introduce issues. Improved Developer Experience: Mirrors established practices in other development environments, making dependency management more intuitive. Collaboration Support: Promotes consistency across teams by ensuring uniform dependency versions, reducing integration conflicts. Please find below a mockup illustrating the proposed implementation.

I would like Service Studio to automatically add code to the assignment after I have named it in this specific way:[NameOfAnInernalVariable]++Obviously, the automatically added code should be:NameOfAnInernalVariable = NameOfAnInernalVariable + 1Perhaps it would also make sense to do this for types other than int - example:NameOfAnInernalVariable  = AddDays(NameOfAnInernalVariable, 1)Although technically simple, this behaviour would save me a lot of time when developing.

Having an option on the screen or in the button parameters to prevent the user from double clicking on any element twice or others when the server is processing.Per example if the server is slow the action logic may still be processing and some users have the tendency to double click buttons (like Create/Save) repeatedly, duplicating records (per example).You can avoid this by using the Button Loading widget on Mobile and Reactive Apps, but there is no option for the whole screen. On Traditional Web you have to implement your own logic or use a Forge Component (Page Loader) or ( Button Locker), per example.

Please add a magical button to retry a failed deployment.It would be a time-saver to not have to create a new staging, validate the plan again and re-deploy.

Would be nice to have an option copy a single value from previewed data.PS: Although, I noticed that Ctrl+C copies all the values from the selected column.

The HTML Element widget is, from what I can tell, limited to a set of tags that OutSystems defined. As new HTML tags are created, and with the surge of technologies like Web Components (that use custom HTML tags), this becomes a limitation and we have to implement workarounds to make a simple thing work. Can this rule be relaxed or even completely removed?