You could increase the amount of database available in the personal environment, as 2GB is often not enough.

Add the "show password" icon in the password field for admin users only

Right now, when we want to consume REST API with authentication (Auth2 or Basic), we should add the credentials manually and hard coded. But if we should use the same credentials for different API, we should have the ability to configure these credentials as Site Properties. With that, we can manage the credentials only once for all the API's.

I find it very odd that the exams contain lots of information not covered in the training material.I'm well aware that this information in contained within the documentation, however reading through pages and pages of text does not suit everyone's learning style and can be pretty tedious.I'm also aware that the expectation is that you put into practice what you’ve learned during training prior to sitting the exam, but that doesn't ensure you acquire all the necessary information.It would be far better to have more comprehensive training courses and cover all the required material, as is standard with most exams.As things stand, unless you have the time and inclination to read through all the documentation, whether you know the additional information or not can come down to luck, which is not at all ideal.In addition to that, many of the questions appear to be trying to trick you by using confusing and ambiguous language, and I'm not sure why this is necessary.It would be better if questions were clear and straight forward, so that it tests your knowledge and not your interpretation of their English grammar, which is sometimes lacking, perhaps due to English not being the first language of those writing it.If, for some reason there is really the reason to include ‘trick’ questions (though I can’t think why), then at the very least, the questions need to be unambiguous and grammatically correct, so that they properly test knowledge and don't trip people up through misunderstanding.

Currently, OutSystems Service Studio does not support changing: The editor font family and font size in the Service Studio interface (Toolbox, Widget Tree, Properties panel, etc.) The overall UI scaling for high-resolution displays The language of the Service Studio interface (menus, property labels, and tooltips remain in English) While we can fully style our application UI, we cannot customize how the Service Studio development environment itself looks or behaves in terms of text visibility and localization. Most leading IDEs (like VS Code, Eclipse, IntelliJ, Android Studio) support: Font and UI customization Localization of interface into various languages By enabling these in Service Studio, OutSystems becomes more developer-friendly, more inclusive and better suited for international markets It would create more impact like Increased developer productivity and satisfaction Compliance with accessibility standards Easier onboarding of non-English speaking teams

We can define Content Security Policy (CSP) through Lifetime and Service Center. This applies the configurations we need to prevent some attacks. It would be great that Outsystems allowed to create a CSP in report mode only (header: Content-Security-Policy-Report-Only). This way we could test our rules before applying the CSP to the full environment. This would also be great if this Content-Security-Policy-Report-Only mode goes to the CSP Reports tab from Outsystems.

An app that seems where I've been in the previous 14 days and cross references with all people using the app. If one of them is infected and crossed our path, we'll be notified that we are are risk and need to be in quarantine.

In some scenarios, we receive the Id from an API as a text data type, and we need to use it to filter records in an Aggregate. To handle this, we convert the text to a long integer using TextToLongInteger() and then to an identifier using LongIntegerToIdentifier() to match against Table.Id. However, this conversion occasionally fails, especially in the production environment . In such cases, the Aggregate filter fails to return the expected results, likely due to type mismatches or runtime issues with the conversion process. This inconsistency makes it challenging to filter data accurately when dealing with dynamic or external data sources Please consider improving this feature by adding native support for safe and consistent type conversion within Aggregates. This would help ensure reliable filtering, especially when working with dynamic or external data sources, and reduce unexpected issues in production environments.

There are similar names in the community and I did notice that some developers can also get confused on who to tag. Or will have some hard time finding the person to tag. It did happened to me a few times. If we can maybe have a tag suggestions, probably will suggest those names first that are already in the conversation, then I think it can help in some ways.

OutSystems created a what's new page to keep everybody aware of what is being released. That's great! But there's no way to be notified every time there is a new entry :(In my case, since I want to be aware and check every awesome stuff released, that would help me be updated.My suggestion is to have an RSS feed or an email (you could use the daily community updates email).Thanks :)