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.

It would be really great if you in someway could organise your service studio. There are of course possible ways, like;- adding folders (the independent modules is a kind of misc folder)- 4-LC organisedIf this structure is also applied in the Manage Dependencies, that could also really help in finding the right modules  :-) This could be another idea in itself...

Because sometimes you already know your timer execution has gone bad and you just want to stop it.

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.

ODC apps update (Review Library Updates) don't provide any information about what was updated in the updated app. Instead it just have a generic information. In O11 user has more information and control about what is updated and can update item by item. ODC: O11:

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:

Add tools to allow the enhanced organization of application icons in the user's environment in Service Studio. Filter, Sort, View mode (List, thumbnails, ..), ...

I would like to right click on a Entity in a non-production Environment and generate one script with delete in cascade to clear all the records from that entity and avoid the error "The DELETE statement conflicted with the REFERENCE constraint".

Hey guys,I think it would be really helpful to have a new tab besides the TrueChange tab that shows the Architecture Dashboard report for the specific module we're seeing.Apart from being more accessible, developers can easily look at the report in the module scope and more proactively reduce technical debt.

Hello, It's completely fundamental to have a way/tool to migrate App/modules from Reactive to ODC. Right now it's a big bottleneck as we can't open modules created in Service Studio in ODC studio. Will be impossible to convince customers to migrate Apps from Reactive to ODC if the process is no simple and quite fast. Thanks, Paulo Torres