Css makes wonderfull things but its not easy to work with when we whant to change something, changing a litle color can make us whant to kill someone, by integranting sass-lang on service studio we can get more power managing our css. check out more info on https://sass-lang.com/

The user should be able to export site properties, which helps in deploy between environments.

When i was attending the Quiz in courses then - The quiz does not have a timer , which allows unlimited time for each question. Quiz is not only about accuracy but also about speed and confidence. Suggestion - There must be a timer for every quiz. A timer makes the quiz more interactive and exciting.

This idea is to suggest that the zoom level in expression editors should be preserved between opening/closing the editors. Example: 1) Open an expression editor 2) Adjust the editor zoom to 200% (CTRL + Scroll Wheel) 3) Close the editor 4) Open the editor again 5) Zoom is back at 100% 6) Increase the zoom again. 7) Repeat 100 times in a day. To reduce eye strain I often increase the zoom in expression editors but as soon as I close the editor the adjustment is lost. Maybe there's a way to keep the zoom preference 'stick' while a service studio instance is open. Thanks, João

The connection timeout error message must include the request that failed, so we can determine screen and data fetch.Currently, the Stack is only mentioning thisCommunicationException: The connection has timed out at c.onTimeout (https://domain/module/scripts/OutSystems.js?dU8nDUaeDPfu6NWEtXEQEQ:3:7337)  at https://domain/module/scripts/OutSystems.js?dU8nDUaeDPfu6NWEtXEQEQ:3:4671Not even the screen name is on the detail of the error.

 Problem: The procedure of changing themes in OutSystems is by and large a process of trial and error. Developers need to update styles and check each screen separately, which takes a lot of time. Enhancement: Introduce a live preview editor for themes that reflects changes automatically on all screens. Developers are free to change colors, fonts, and styles and they can even choose not to publishing or navigating between screens and yet see the result. Benefits: Time is saved as the user is not required to test and switch between screens constantly. The customization of themes is brought about in a quicker manner and with less effort. The look of the app is consistent throughout the entire ‍‌‍‍‌‍‌‍‍‌application.

Even though the ODC Portal is in its early stages, what do you think about adding some colours to the Stages dropdown? (Example: Dev=Green, QA=Yellow, Prod=Orange) We've been told that the ODC Portal is the "substitute" for the Service Center and Lifetime applications. In this ODC Portal, the Admin can basically configure and deploy applications for all the Stages . Although this is great because it has everything in one place, the absence of colour coding can lead to misconfiguration because the user might not notice he/she is in the wrong Stage doing the configurations. Attached are some prints to support the idea.

right click on "output structure" >> Create the output structure (in advanced queries) based on the select statement

Since we currently have a large influx of new users on the forum that love to ask for solution in OML format I think we need to have some form of notification about the risks doing so. Please add a notification before the actual download informing the user that an OML can contain malicious code and that you should not import the OML in your Enterprise Environment. Malicious code will almost always be run via a timer that is started On Deployment. Malicious actions can be; Uploading information about your environment (or data) to an external source. Creating user accounts to gain access now (or later). Providing access to your environment via an API or screen. Running a SQL query that can delete your data. and a whole lot more Perhaps it hasn't happened until now (perhaps it has) but it is better to be informed and warned before it is to late.

I think "For Each" elements should behave the same as "If" elements in regard to its label.When the Label parameter is blank, its Record List should be shown instead.Here's what a For Each with no label currently looks like. Caveat: when reading through the code, I have no clue which list the For Each is iterating until I click it.Here's what it should look like in this example above. Much better:  I can read which list the For Each iterates without having to click it!