My suggestion is to implement a feature that allows developers to find and remove unused CSS within all dependent modules and style sheets. This tool would help streamline application development by identifying redundant styles, leading to improved performance and easier maintenance.

Hi all!Maybe would be nice to have the possibility to "copy" and "paste" UI developments from Traditional Web to Reactive Web App. At this moment isn't possible to copy even labels, IFs, expressions or containers.This means that to convert any development from UI, is needed to implement it from scratch!ThanksRuben Machado

Let's say that I want to sync Tickets, Ticket Types, Users and Queues. Tickets and Ticket Types are connected, so I want to join them in a first sync. Users and Queues are related, so I want to join them in a second sync. But, I want both syncs to start at the same time, so that I cut in half the processing time. Right now, even though the description of the TriggerOfflineDataSync action clearly states "Action where you can invoke OfflineDataSync asynchronously", the syncs run one after the other, as you can see in the browser network tab. Some of the syncs rely on endpoints that could take some time to respond, so not doing this concurrently makes our apps feel slow. Users will have to wait extra time to have data available to start working.

In ODC "Add Public Elements" should be similar to O11 "Manage Dependencies". Or, at least, the user should be able to choose between using the new "Add Public Elements" and "Manage Dependencies" with the O11 like visuals and functionalities. In ODC the information provided and selection of Public Elements it's time consuming and developers cannot have proper control on the overall picture. In O11 developers have more control when using Manage Dependencies and can quickly understand what is happening. ODC: O11:

Hi,i recently got aware of a c# library named Polly . Polly is a library where you can define policies to handle execution results and exceptions and perform conditional follow up actions, like retries, retries with wait and others.We would strongly benefit from having an analogous feature in OutSystems esp. when consuming REST APIs. Especially when in need of* Rate limited APIs - APIs where you get an error when you hit the endpoint too many times within a specified timeframe.* Poll based asynchronous APIs - APIs where you initiate a job with one request and need to periodically check the result until you can request the final result of the job.* Unreliable API endpoints - APIs that sometimes time out because they are not well scaled or for any other reason. Requests sometimes time out and sometimes not.It would be a nice feature if we could specify Retry, Retry with Wait and Timeout Policies directly on the REST consume action with optional conditions, e.g.:Retry - max 3 times when StatusCode = 408RetryWithWait - max 3 times, Wait 1,3,5 secondsConditions should be possible to match not only the HTTP Status Code but also the response body. Poll based APIs typically deliver a status request with a code of 200 and the job status als JSON body attribute e.g. JobStatus so a policy condition could look likeWhen StatusCode = 200 AND Response.Body.JobStatus = "Pending"Such a feature would drastically reduce the manual handling e.g. in BPTs asf.Thank you,Stefan

Today, AI Mentor (App Generator) is powerful when it comes to validating best practices, architecture, and quality of applications already developed in OutSystems. My proposal is to expand this capability so that the Mentor can read external source code (for example, from a Git repository, in languages such as Java, .NET, Node.js, Angular, etc.) and: Analyze the structure, business logic, integrations, and existing architecture patterns in the legacy code. Automatically suggest how this code could be rewritten in OutSystems, following modularization, security, and scalability best practices. Generate initial components (entities, actions, APIs, UI blocks) inside an OutSystems module as an acceleration base for migration. Value for the Community and Customers Accelerated migrations: companies with legacy systems could move to OutSystems much faster. Reduced risk: the process would become more predictable and auditable. Productivity: developers focus on evolution instead of manual migration work. Governance: the automatically generated application would already comply with AI Mentor’s best practices. Example Use Case Migrating a management system in .NET/SQL Server to OutSystems. AI Mentor connects to Git, reads the code, identifies entities, logic, and integrations, and suggests a skeleton in OutSystems that developers can refine. Expected Impact Disruption in the modernization process of legacy applications. Competitive advantage for OutSystems compared to other low-code platforms. Faster adoption of the platform by large enterprises with extensive legacy systems.

Hello,Our community forum has become a good platform where lots of problems are getting solved every day. Almost every day I spend some time to look for an activity happening around the forum, and I literally learned so many things from reading it, replying it.However, I was wondering if we can have mobile app design for our community forum. I know we can access our forum site on Mobile since it’s responsive, But using a mobile app is different and quite handy. I hope you will with agree with me.Regards,Sachin Mahawar

In aggregates when we pull an entity, if the platform thinks it should take other entities behind, it takes automatically, and also creates joins automatically. However, these "extra" entities are not always needed. So my idea goes through when we delete an entity from an aggregate, the joins that are created automatically, are also automatically eliminated. It makes it a lot easier to use.

 With reference to this thread: https://www.outsystems.com/forums/discussion/31032/analyitcs-mobile-apps-in-lifetime/Currently, lifetime Analytics only reports on web applications.Please, enable reporting for mobile application on the server and network tabs. It is understandable that the client side of the mobile application would be difficult to report.This functionality has been needed since P10 and is critical to delivering on the promise of platform analytics.There is also an expectation being set on lifetime Analytics when the "Network" tab is selected: "Data collected when applications are running natively on a mobile device"It would be great if the following information was made available:Device type (tablet, mobile)Network type (3G, 2G, the other G, wifi, slowfi)OS Type and version (the 2 usual suspects)Browser Type and version (webkit, blink, etc.)Initial splash load timeEverything else that is reported on the server side for web applicationsThanksOuen

Breaking into tech is tough, especially for entry and mid-level developers who need experience but struggle to gain it without opportunities. What if we created a community-driven challenge where developers build real, useful applications or Forge components that benefit the OutSystems ecosystem while advancing their careers? How It Works Participants can compete solo or in teams, allowing both independent developers and collaborative groups to showcase their skills. Categories include: Application Development – Build fully functional apps that solve real-world problems. Forge Components – Create reusable components that improve development efficiency. UI/UX Enhancements – Design intuitive, accessible interfaces that elevate user experience. The event fosters friendly competition, networking, and hands-on learning. Winners (or standout contributors) receive certification vouchers, accelerating their careers. Why It Matters Bridges the experience gap: In the US, it's difficult to find work without prior experience—this provides tangible projects to showcase. Boosts OutSystems adoption: By targeting aspiring tech professionals, this event could introduce new talent to the platform and generate buzz in the job market. Grows the Forge & community: High-quality contributions enhance the OutSystems ecosystem, making it easier for everyone to build better apps. Additional Challenge Features Mentor guidance from experienced OutSystems developers. Themed challenges (e.g., accessibility, AI integration, automation). Judging criteria based on innovation, impact, usability, and scalability. This initiative could be a game-changer for developers looking to break into tech while also strengthening the OutSystems brand and community resources. Would love to hear thoughts from the community on this!