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.

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

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...

So the openapi specification that is found in the documentation of the ODC Rest APIs has the openapi version set to 3.0.4. However, if you feed it as input to consume in ODC Studio, only versions up to 3.0.3 are supported. Anything higher is (currently) just refused. it returns the very meaningful message that the format is not recognized. (for which i'll make another idea) So why not keep these 2 in line, and only put versions in the documentation when they are also supported in ODC Studio?

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

Currently, only Images, Scripts, and (Deployed) Resources expose their runtime path. It would be valuable to extend this property to Stylesheets as well, since they can be considered a resource like any other. Access to this property would give developers greater flexibility in managing the CSS cascade, particularly in more complex scenarios.

 Problem When working with complex structures, lists, aggregates, or data actions, developers often need to reuse a full variable path. Today, this usually requires manually navigating the data tree and rewriting the reference. How this suggestion can help A simple “Copy Full Reference” option would improve productivity and reduce typing mistakes, especially in large Reactive applications with complex data models. Implementation example Right-click on any variable, attribute, or structure field and select: Copy Full Reference Example output: GetRequestById.List.Current.Request.Approver.Name This could work inside Assigns, Expressions, Conditions, Client Actions, and Server Actions.

Mentor is outstanding for developing components when you can explain your vision with language — although at times an image truly conveys more than words. His works well for pictures of current user interfaces (from other apps, or even other parts of your own app), images of whiteboard drawings, or any additional visual aid. That translation step is where things get lost. The idea is let us submit a photo alongside the Mentor chat, and give Mentor the task to examine it and generate the OutSystems component that matches it. This would work for captures of current user interfaces (from other apps, or even other parts of your own app), photos of whiteboard sketches, or any other pictorial reference. The value here is huge for teams that work fast. Instead of taking time writing detailed prompts, you just insert a screenshot and let Mentor figure it out. This might turn Mentor effectively advantageous for a wider range of daily development scenarios, beyond merely assisting people experienced in formulating prompts.

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".

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.