In ODC "Add Public Elements" should be similar to O11 "Manage Dependencies". Or, at least, the user should be able to choose between using the new "Add Public Elements" and "Manage Dependencies" with the O11 like visuals and functionalities. In ODC the information provided and selection of Public Elements it's time consuming and developers cannot have proper control on the overall picture. In O11 developers have more control when using Manage Dependencies and can quickly understand what is happening. ODC: O11:

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

In Service Studio, static entities have a Description property (like all other things you can create like actions, structures, attributes and so on). However, given the nature of static entities, each record has a specific use, which currently can't be described. It would be nice if it were possible to add a description to each record, in addition to the static entity itself. This will help the developer assign the right value. This description could then also be shown when hovering over a record in the static entity selection pop-up.

New Accessibility category in Ideas and new Accessibilty tag in Forums. It may be that this was decided internally as not necessary, but with accessibility becoming a must, and since it's a very broad topic, I feel that a dedicated category and tag in the Ideas and Forums, respectively, would benefit and facilitate the search for this topic.

The use of ReactJs in mobile applications not only allows a quick refresh of the screen but also makes the development process simpler, since it is not necessary to perform ajax refreshment explicitly. It would add value to Web applications

The <span> that gets added around items in ListRecords causes a lot of issues with jQuery and other things. For example, we tried using a div with display: table-cell and it did not work because of this. J.Ja

 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.

like switching between different devices , switching between design modes in the studio

When dealing with mathematical calculations or complex queries it's easy to lose track of parentheses.Check the attached image for an example of highlighted parentheses on Notepad++.

It would be helpful to be able to create multiple plans and schedule when they are being published or add them to a publishing queue.Our company has a large number of applications and we are running into the situation where we have so many applications its taking a long time to publish.  If we can split up the applications being published and schedule it to run in off-hours it would improve performance.Another case is we have multiple developers trying to publish to the same environment. Sometimes we forget to go back so the QA spends time waiting for all of the changes to be published for testing.