Hi everyone,I spend a lot of time inactivating the users who should not have access to an environment for some reason. What I would like to suggest is for us to have the ability to set an expiration date for each user that is not an administrator.This way I can easily manage the users on my factory especially when we have outsourced developers.

 New functionality: It would be nice to select some logic nodes, right click and "🔒 lock" them. How it will affect the developer? When you want to do changes, you have to unlock the nodes and provide a comment/reason why you want to change them. Other effects? During the merge or code update, all commented changes are shown so each developer knows something happened there. This would be a good functionality to protect Interface-code or some heavy business logic that normaly does not need to be changed. When would this come into play? Replace All / Find'n'Replace might change code that should only be changed with care APIs/Interfaces might be changed because of a call or so, but more than just one person should be informed about this Law relevant logic might be changed etc.

Service Studio should provide more built-in icons for actions. Upload icons is a pain process and allowing developer to upload any kind of images polutes the code readability. If Service Studio could provide some icon options this could standalize the code flow. I would suggest icons for Private actions like: If this could be done automatically, it would be great.

Currently when I want to delete records from an entity and I get an error, the error gives a technical name of the entity that prevents me from deleting a record. Please show the name of the entity as noted on the logic tab

 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.

For a DropdownSearch there are options for translating/changing NoResultText and SearchPrompt It would be good if the OptionalConfigs also have a configuration for clearButtonText

Please can you add the ability to apply field descriptions to ODC External Logic components. If there is already a way to do it, it's not in any of the very scant documentation.

To monitor errors in Service Center, having the kind of exceptions that have been raised could be very helpful. The exceptions are already on the error log but not their Type, for example, "Database Exception", "Security Exception" and for User Exceptions, it would be very helpful. Should have filters / categorized.

Branching could be useful in different situations, some more relevant than others, but on big factories with a team with several developers, it could be very useful.A situation that occurs frequently is when we receive a change request which requires changes on core entities, this will break the environment , and will affect other developers that are working on a different feature, but are prevented of testing/developing without pain since the environment is broken.So it would be great of having an way of creating a branching per pta of a solution, were the developer could make the change that will break the environment isolated, finishes the development, could test it isolated again (remeber that i've mentioned a branch of the solution), if everything is ok, perform the merge of the branches, create a new solution and schedule the publish.Im mentioning PTA was a way of doing it, it could be by branch, if it was possible to work on different espaces on a context of a branchIf i was a smoker i would quit smoking with this feature :)

As a Developer i want full insight in where my code is used. Right now it is not shown when my ServiceActions, Events or Screen are used in ODC Workflow. I would like to have this info added to my usages to get complete info on where my code is used.