With the quiz being added to the Web Develop Web Application course, I would love to see one for the Mobile course as well. It really helps validate your understanding of what you just learned. And of course this is a really nice way of getting a glimpse of the questions you can expect when going for the certification.

Since a while now, it's possible to convert an Aggregate to an SQL query. This is a great feature, but it has a number of limitations. For one, discoverability is low. Why not add it to the context menu when clicking an Aggregate?Secondly, the limitations listed are annoying, if Service Studio can run the query on the database, it should be able to convert it to SQL. The limitations listed: The option to convert an Aggregate to a SQL element will only be available if your Aggregate doesn't include: Structures in Sources Calculated Attributes Group By attributes Dynamic SortsIt would be nice if this feature would be improved, so that all (or most) of these limitations are gone.

When right-clicking Publish in ODC, if the options for Dev, Test, and Prod environments were displayed directly, developers could quickly navigate to the corresponding environment URL without having to search for it manually.

The logs generated by the platform (screens, errors, integrations...) help us a lot when we are investigating an error. But I think it would be better if the platform allowed us to turn off these logs. We have recurring problems with the log database due to the large number of logs generated by accessing screens and integrations. Most of the time we do not need these logs but we cannot prevent them from being saved. We know that the logs are saved asynchronously, so there is no impact on the application (we use a separate database for logs), but we would like to have autonomy to turn on/off the generation of logs.

I would love for us to be able to put comments in the un-utilised areas around the canvas in mobile apps and reactive apps. Similar to the way the comments in Action screens work, these could be used for comments on why something has been put in, or reminders for development work yet to complete on this screen, or bugs to fix. The comment widget would need to be added to the widget tray on the left, and then it could be dragged to the grey background.

We could have the option of, within the context of espace in Service Studio, perhaps in the Module menu, "Move Espace to ...", the same action that occurs from within the context of the Application, where you choose which application to use for the space be moved.This is useful, for example, when cloning a space, either to test some functionality separately or even to definitely split the architecture (This would avoid, for example, having to go to Independent Modules and then move again).

Like many others of you, I read from the ideas, we also have problems indicating changed/new labels.When you add a new label, the label will be indicated 'To be defined', but when you copy another label, the translation will be same a the old one, and it's it's indication is 'Translation'. And also, if you change a label, the indication won't change back to 'To be defined.So, how can we identify that a label have to be reviewed? We have hundreds of labels to translate and every Sprint there are some changes. It's impossible to review all the labels again and again.Since my idea of putting those changed labels back into 'To be defined' is rejected by OutSystems since users only doing typos have to put everything back into 'Translate'  again... I got a better idea now. Let's add a last_changed_date(time) so we can sort on that field and only check the labels we changed recently.Please like this idea to get this into attention of our Outsystems IDE developers.

These existing feature of Service Studio CSS Tags is a very nice feature to use when making custom components. Example Service Studio CSS Tags: ``` css .component-wrapper { color: black; -servicestudio-color: red; } ``` My idea is expand on the Service Studio CSS Tags for CSS Selectors such that an entire selector can be conditional shown in ServiceStudio using just one -servicestudio- prefix. Example Service Studio CSS Selectors : ``` css .component-wrapper { color: black; } -servicestudio-component-wrapper { color: red; } ``` Ideally anything using the -servicestudio prefix should removed from the runtime CSS at compile/deployment time.

The new Data Grid is fantastic, but the fact that you have to add an ActionColumn and that that is the only one that can have an OnClick handler attached is quite limiting. It would be very nice to have the option to do the following:1. Add an OnClick handler to each column regardless of type2.Add an OnClick to an entire row so that they can click on any column and it triggers the handlerI would suggest that the Cell OnClick overrides the row one... but the individual cells click probably more important. Or potentially just allow one or the other.

Currently, supermarkets limit the number of people inside the space, but there is a problem outside the commercial space, with the cluster of people waiting for their turn to be able to enter and purchase the goods they need.The idea is to create an application that performs the virtual queue management in which people can schedule their place in the queue before leaving home. The application generates a number in the virtual queue and will indicate to the user what time is most likely for him to enter the supermarket. In addition to the information in the application, the user receives an SMS indicating the place in the queue and the estimated time of entry. The information is updated with time intervals to be defined (5m, 10m, 15m, etc.). It will be necessary that each of the participating stores use the application and agree to create a specific virtual queue for the users of this application.The application can be applied to othet type of stores than supermarkets. Stores that use the application will be helping to reduce the risk of contagion, as there are clusters of people outside the commercial space.