Hello, The list of components on Profile only matches the O11 components, not reflect the ODC components. Even in Forge when i select My assets only the O11 shows. Best Regards

The current Community platform suffers from performance limitations and provides a restricted level of user interactivity. To improve the overall user experience, I propose migrating the Community to a Reactive Web architecture within OutSystems. The growth and increased user engagement in the OutSystems Community can be attributed to a more intuitive, faster, and interactive experience that encourages users to actively participate, share knowledge, and return to the platform more frequently. Let’s move forward with this improvement to unlock a faster, more engaging, and truly collaborative community experience for all users. This is a developer’s observation based on system usage and user experience.

Although there exist about 15 ideas on improving handling of unused references, non of them state the obvious: it could be done easily by OutSystems fully automatically! My proposal is that developers keep whatever references in DEV (or remove them if they want), but that on deploy to the next environment, OutSystems first automatically removes any unused references, before it starts the deployment. There is in my opinion NEVER a need for unused dependencies in the next environment where someone deploys an application to. As is is never needed, it can always automatically be removed.

 Problem Debugging Reactive screens can be difficult when developers need to understand the current state of local variables, client variables, input parameters, screen data, and browser storage. How this suggestion can help A dedicated Reactive Debug Panel would give developers a centralized view of the screen state during runtime, reducing the need for temporary labels, console logs, or manual debugging workarounds. Implementation example Add a debug panel available during preview/debug mode showing: Current Screen: RequestDetail Local Variables Client Variables Input Parameters Data Actions Local Storage Session Storage The panel could allow developers to inspect values in real time and optionally copy them as JSON.

 Problem In large modules, unused local variables, input parameters, output parameters, and assignments can accumulate over time. This makes the code harder to maintain and can confuse developers during debugging. How this suggestion can help A better unused element detector would improve code quality, reduce technical debt, and help teams clean modules before publishing. Implementation example Service Studio could show warnings such as: Local variable 'TempStatus' is never used. Input parameter 'RequestId' is not referenced. Output parameter 'SuccessMessage' is never assigned. It could also provide a quick action: Remove unused variable

There are plenty of scenarios in which the base built-in actions are not enough. For example, if creation of a specific entity record demands that other entity records be also created, or if certain restrictions apply that cannot be modeled with static "default values". Or simply because you want to audit operations over sensitive entities. Currently the way to do this with the Agile Platform is clumsy: isolate entities in their own eSpace, make them available read-only, and create sets of actions to do the required tasks. This works, but: It is ugly - when actually using those actions, you will not see them associated with entities; you need to remember that they need to be imported, look for them under "referenced actions", remember from which eSpace they come from - or go look in the entity list; It can lead to errors - if a new developer in a project using the pattern, for some reason, is not properly informed, he might simply go into the eSpace and switch the read-only property off, anticipating that it being that way was an error.

While editing a LifeTime plan, I think it would be useful to have a counter that shows how many applications have been added to the plan . When the plan includes a lot of apps, and you know how many need to be deployed, it can sometimes be hard to tell if the numbers match. For example, let's say I have a plan with 25 apps, but I’ve only added 24. With a counter, I could quickly see that one app was missing from the plan. Right now I have to count the apps to see if I have all of them added. Cheers, João Heleno Mockup of a plan with the number of apps showing near the source environment title.

Currently, we have Service Studio on Windows and Apple machines. We always have to update it and it's not possible e.g. to use it on Linux. Other Low Code and No Code providers have have it web based. Please investigate it you can make Service Studio web based.

When working in environments with many apps and modules, finding the ones we use daily can take unnecessary time. It would be useful to have a "Mark as Favorite" option for modules in Service Studio. This would allow developers to quickly access their most frequently used modules when opening the environment. For example: A star icon next to the module name; A "Favorites" section on the home screen; A filter to show only favorite modules.

As a Software Engineer, I have noticed that handling high-resolution images is a common challenge in mobile performance. Applications like marketplaces Apps often deal with numerous user-uploaded product images, which can lead to slow loading times and high data consumption. The Proposal: I suggest implementing a Native Image Optimization feature directly within the OutSystems mobile framework. Key Features: Automatic Client-Side Compression: Images should be automatically compressed on the device before being uploaded to the server to save bandwidth. WebP Support: Built-in support to convert images to modern formats like WebP, which offer superior compression without losing quality. Dynamic Image Resizing: The ability to serve different image resolutions based on the user's device screen size and network conditions (2G, 3G, or 4G/5G). Lazy Loading & Caching: Advanced, easy-to-configure caching mechanisms to ensure that images load instantly for returning users. Why it matters: This feature will significantly enhance the user experience (UX) for mobile users in regions with limited internet connectivity. It will also reduce infrastructure costs related to storage and data transfer for developers and businesses alike.