Hi,It is a great idea to provide severity of issues on the architecture dashboard - something like Sonar and checkmarx. So the teams can focus on Sever issues first (like Very high, high, medium, low). Something similar to Impact - but impact right now does not show a level of impact.Right now Architecture Dashboard provides everything according to category - but not according to severity.This similar kind of severity based analysis report is provided by paid subscriptions like OmNext, Boncode etc. however since we already have this similar report right out of the box in architecture Dashboard, then why not include it here.Thanks !Vikas

In ODC Studio it can be very helpful if we can have a checkbox for include in menu on screen so if I forgot to enable it on creating i can still add it in menu. Similar as how it is in Service Studio (O11)

Using the attachment as an example, when you have a component selected, you can double click "On Click" to open a properties window and set the destination or action to be executed. (In this example, it is the client action Login).It would be good if at a later time you were able to double click the right hand side of the property (or select 'navigate To' from the dropdown) to select that action in the interface screen or the logic screen.The benefit of this would be that you do not have to search through your tabs for an action or destination,, and can instead navigate straight to it. The back button would then also work to take you back to where you were before you navigated away.

Add Social Buttons to share Ideas .Add some social button like Facebook , Linked in ,Twitter .These buttons fix near to comment and views in idea page when an idea creator want to share his/her ideas just one click is enough to share.

It should be possible to open a specific filter menu from the Aggregate proprieties without the need of opening the aggregate as the image shows:when I click the button it should only show this:for example if I am doing a big change of values in a lot of aggregates a lot of time is wasted opening the aggregate and for sure it would save some time e be more user friendly I guessThanks for earing

Currently, the Outsystems Popup widget does not follow accessibility requirements, notably:- Trapping the Tab focus inside the modal content (the focus continues on the page in the background)- On close, returning the focus to the element that triggered the opening of the popup.The Popup widget is not part of OutsystemsUI, which makes it even harder to work around this problem.Can this be improved?Thanks,Tiago

When we try to run an Advanced Query, in the test button, to see if the query is having the expected behavior, it happens that sometimes we have errors and the error message is never clear (eg: after ')').From what I suggest in continuation to my previous idea, of putting the numbering of the lines in the Adcanced Query, also indicate in this error message the line where we are failing. What do you think of this idea? It could help a lot.Nuno Miguel Verdasca

When using the AddDays() function on an object of type Date, it will return an object of type Date Time. I would expect it to return a Date here since that's what I was working with and AddDays() does not impact that (unlike AddHours(), AddMinutes()). For example: AddDays(CurrDate(), 1) Will return a Date Time, while I'm only trying to obtain tomorrow's date.

We already have the string join as a server action, but since it's server-side only, we can't use it when working on client-side specific logic, like offline mode in mobile apps. Therefore, having a client action with this functionality would be nice.

Hello community!I want to suggest a small functionality that, in my case and probably yours, will reduce some extra interactions with Service Studio.When I want to access the handler action of an event, I have to look for it in the screen actions. In case there are many screen actions, it will add some small extra time (but this is done multiple times).The suggestion I propose is to allow to open the handler action directly from the handler field. In the case of this screenshot, I want to open the DataField_OnChange_Validate.If you have another solution to make this interation more clean, be free to suggest it.Cheers,António Pereira