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/

When working on the theme I accidentally introduced an error by putting a square bracket in one of the lines, like the one we can see in line 92 here: This did not raise any errors on TrueChange allowing me to publish the theme and break all the classes that were below that line. Since the theme was visible in the sources of the browser and properly loaded, it took too much time to realize it was a simple syntax error. This could have been avoided if TrueChange would not allow to publish CSS with syntax errors.

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

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.

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.

Considering the fact that the cloud version does not support internal network for IP white listing, I think adding an extra layer of security to secure service center  with Two factor authentication should be a standard in the Outsystems platform.