OutSystems did an awesome job with redesigning the icon system which is used in the Hybrid version of Service Studio.However I think some icon designs got worse, mostly noted the input and output parameter icons:In the old design the arrow in and out are very clearIn the new design:Regards,Daniel

Every time we create a input widgets we want to assign the  Label for user identification , If the  LABEL was generated Automatically while creating a Input Widgets And also assign it's value to corresponding Input widgets , It is easy and Time saving process for Developer.

As of now radio button and checkbox size we can modify using css only. It would be good if we have size attribute for radio button and checkbox like how we are having for icons.

Many usergroup events conducts quiz at the end of the session. It would be good to have a section to display quiz winner as how we are displaying now organizers in the event page. It will surely encourage participants

As of now OutSystems Community profile score is based on user participation in forms, training, sharing ideas and forge. I know many leaders who are contributing for Community Growth via usergroups. Also many users actively participating in usergroup session. If we allocate some points for usergroup activities (organizer, speaker, quiz winner, participant ) it will be great. Just a wish 🙂

 Quickly Integrate Everything and Connect to Anything -  this is one of the main advantage of OutSystems. Integration play crucial role in any application development. It would be good if we have separate guided path for integration experts. We can add rest api simple customizations, advanced customizations, Handling REST errors, REST Api authentication, SOAP API, Integration studio, Listing all existing connectors in forge and so on.

Be able to create a unit test for a Server / Service / Client (?) / Screen (?) action that shall be executed without developer intervention, for regression purposes.

 The BaseTheme used in Outsystems, as like most of the designers in the market, use the   multiple of 8  rule to create sizes for margins, padding, font sizes, grids... So, if BaseTheme uses the same rule for variables for everything why not use it in the Style Tab too?   Benefits : Less maintenance , Easier for the Develop team to match mockups margins and paddings. Less frustration,  Help experience between the Develop team and the Ui/Ux/ FrontEnd teams easy and softly. Less work for the FrontEnd team finding wrong margins and paddings. Apply best practices , (One-click change everywhere) , Even if there is inline CSS (which isn’t the best practice) when the variable is changed on the theme, the value is automatically updated everywhere. CSS learning ,  Make the Develop team more familiar with the CSS variables.

When you publish a module and get a warnings about outdated producers (i.e. modules with outdated references), it would be handy to be able to right click on an outdated producer and have the option to refresh all references for it and republish it in one click without even opening it up.Of course you would also want the option to open the module instead, in case you didn't want to refresh all dependencies, but this would be a great shortcut when you have a number of outdated producers. Or if you just opened up the module, it could automatically start up with the references open ready to be refreshed as required.

The problem i would like solved:We have recently created different Teams in our Outsystems development structure.This has lead to the inability to handle BPT processes (Terminate, suspend, etc.) in Service center, for processes from our own applications.Since we have dev ops in our scrum team, we need to be able to handle these kind of application related features ourselves.So the idea is to make the Permission model a bit more flexible so companies can change some permissions in roles to fit the needs of their organization.