Some application are built specifically for development purposes (SQL Sandbox, impersonate pages etc..) and It would be useful to have a setting which could designate an application as Not For Production to avoid having them deployed into a production environment.This could be a configured on the application level.

The Demos in Forge projects take up a TON of SUs/AOs. But if you delete the demos after installing, the next time you upgrade the component you get the demo code again.Solution: have the component author upload a demo (OAP, OML, or OSP) separately from the component itself (OAP, OML, OSP, or XIF). Then allow the Forge user a choice of "Download Component Only" or "Download Component + Demo".To make this better, add a "Project" that is similar to an OSP, but can contain Applications as well. That way, the Demo can be a separate Application from the Component, and they can be delivered together in one download. A level above "Application" has been requested a few times already.J.Ja

The personal environment become unavailable if the storage reaches 100%. So many people are not aware of this. So if we can trigger a warning at around 95% storage space used and once its reach 100% you will not be allowed to access the environment. Please take necessary steps. So user will never run out of this issue.

When the Date Picker widget is placed inside a popup container, its calendar popup has a z-index that is too low to appear above the popup. In my application, the date field is mandatory, so this behavior acts as a blocker in the testing and validation process. Resolving this issue would greatly help developers during unit testing and proceed further.

Proper documentation is essential for maintaining and collaborating on OutSystems projects, but manually filling in descriptions can be time-consuming and often overlooked. I propose an AI-powered feature that automatically suggests descriptions for elements such as: Variables Actions Screens Blocks Entities The AI would analyze the element’s name, its usage in the code, and overall context to generate an accurate description. The developer would then simply accept or edit the suggestion , making the process faster and more efficient. Benefits: ✅ Time-saving documentation process – Developers can focus more on implementation and less on manually writing descriptions. ✅ Standardization – Generated descriptions would follow a consistent and clear format, improving readability and maintainability. ✅ Better collaboration – Teams can quickly understand the purpose of each element, even if they weren’t involved in its creation. ✅ Easier onboarding for new developers – New team members can familiarize themselves with the codebase more quickly. This feature would enhance documentation quality and significantly boost developer productivity in OutSystems projects. If you find this feature useful, upvote and share your thoughts!

Add an over all quiz module at the end of the Reactive Web Developer Course, It will give Overall idea about the Certification Exam and It give some confidence to candidate while taking Exam.And those Question not to be repeated or not to be same question comes in between modules.it will help to beginners as like me

Like ForumThread: https://www.outsystems.com/forums/discussion/62101/how-to-remove-a-native-platform-configuration-for-a-mobile-app/ we can add config and generate an app. But are unable to disable/delete that config. Add option Disable Native Platform, Like PWA Config has. when not used, still all versions are going through the MABS. Reasons 1. We tested an app for perfomance in NativeAndroid vs the PWA version. The PWA versions was good enough so we want to go forward only with the PWA. but are now unable to remove that config. 2. We had multiple mobile native apps that only used components that are now also supported within PWA. Therefor we would like to clean up the builds and generations of APK if we are not needing them. 3. strange to add config and we are unable to deleten or make disable it.

Ability to zoom in and out in the main window in order to have a better control when inserting or moving elements.

Currently all comments have the same color. In Dark Theme they appear black and in Light Theme they appear gray. This makes it difficult to distinguish important notes or identify who added them. The proposed idea is to allow users to define the color of their own comments so that in action flows it becomes easier to see who contributed. If full customization is not feasible an alternative would be to provide three predefined colors such as normal yellow and red to indicate severity or importance. This would help draw attention to critical comments and prevent them from being overlooked.

It would be nice to have a button on the aggregates to switch the join direction between the entities. This is because, if we have a lot of entities and we need to switch the join to obtain the correct data, we will need to go through an extensive list, find the entity and then do the same on the other side. Here is a mockup as an example.