If there are any advance queries, replace that by aggregateDon't use foreach Loop in preparationDon't use if conditions in preparationi.e try to avoid if conditions in aggregateApply pagination on list pageDon't show more than 100 records on single pageMove JavaScript webblocks to bottom of pageDon't use preparation aggregates directly in screen actionsBefore using them in screen actions refresh themSuggested by  Suraj.

While creating documentation or looking for mistakes done during the creation of the Data entities, it would be useful to have a "Copy context" or "Generate Context from Entity/Entities" that allows the user to have a quick way to look at the structure of the data completely in a useful format like: Entity: Goal Attribute 1: Id (Goal Identifier) Attribute 2: Name (Text, 250 characters, Mandatory) Attribute 3:....

My idea is to have a Mentor (AI assistent) inside the SQL Editor in ODC/Service Studio to be able to use natural language to write SQL code. There could be an extra tab next to the current ones (SQL - Test Inputs - Test Output - Executed SQL) where you can ask Mentor to write or optimize your SQL code and set Parameters and Output Entities/Structures.

In Service studio, when we manage dependencies, we have an option to show only dependencies which are in use. However, in ODC studio, this option is not available. It will be great to have it there, as this is a very useful feature.

The SortRecordList extension allowed to have multiple sort criterias. The ListSort should have feature parity with that extension, at least.Having this built-in on the platform would be useful for sorting third-party datasources. For example, imagine that a web service returns financial transactions, and has two distinct columns: Date and Time. We would need to sort on both columns to be able to present data in chronological order.

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.

There should be ability to add unit tests automatically for any actions. Also a unit tests should be automatically added to a Core Modiules.

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

While using the Upload widget, it would be really helpful if there were built-in properties to set allowed file types (like .pdf, .jpg, .docx, etc.) and a maximum file size limit (in MB or KB). Right now, we have to write custom logic or JavaScript to validate these things, which takes extra time and can be tricky for less experienced developers. If these options were available directly in the widget, it would save time and make file uploads more secure and user-friendly out of the box.

I would like to see an accelerator in SS (and ODCS) where we could choose to create a timer based on the below template according to the best practices to ensure Data Integrity, Timeout Prevention, Completeness and Doesn't Repeat Work. One could customize it afterwards to his needs or simply choose the current option to create a timer with an empty canvas. The accelerator should also include a "KillTimer" Site Property in the flow to ensure there's always a way to stop a timer when needed.