GraphQL is an API standard that provides a more efficient, powerful and flexible alternative to REST web services.Source: https://graphql.org/

With AI being our right hand and helping us with a lot of the product management/vision, it could be possible to create a standard widget structure in the widget tree from a HTML. Use Case: 1 - Use favourite LLM 2 - Generate mockup (using OSUI as theme for the generation - better results) 3 - Copy HTML 4 - Right click screen in ODC/O11 5 - "Build Widget Tree from HTML" 6 - The screen is populated with a bunch of widgets that respect the html

Quite often I go through some modules to clean it from elements that are not used anymore. It would be great if there was a way to know all the components that are not used inside a module and maybe delete them similar to the remove unused dependencies instead of going through every element and clicking find usages in all modules and then deleting it manually if not 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.

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.

We have a scenario where we set the default value of a structure attribute which is displayed on the UI. These default values are not picked up by the translation editor. Idea: add structure default values to the translation editor.

When the screen has too much information and the performance starts to decrease one of the options we have is to create a web block with some of that information and do a lazy load.It would be nice to have something similar to "Extract to action" where you can select the elements in the screen and "Extract to Web Block".In case of a table, it would:- Remove the query from the preparation of the screen into the preparation of the Web Block;- Remove the actions from the screen into the Web Block;- Remove the selected elements into the Web Block;- Add the necessary input parameters to the Web Block.