Many REST services implement sending files, documents etc. by having a body with multipart/form-data. There are many questions on the forum about this, e.g. here , here and here . Unfortunately, the OutSystems Platform lacks native support for this, leading to workarounds like this Forge Component or "manually" modifying the request data in the OnBeforeRequest, which leads to things ugly code like this:(Yeah, that's mine :).)So it would be a great addition to the Platform if it had native support for multipart/form-data for REST services, at the very least for consuming them. That would make our lives just a tad bit easier!

With AI being our right hand and helping us with a lot of the product management/vision, it could be possible to create a standard widget structure in the widget tree from a HTML. Use Case: 1 - Use favourite LLM 2 - Generate mockup (using OSUI as theme for the generation - better results) 3 - Copy HTML 4 - Right click screen in ODC/O11 5 - "Build Widget Tree from HTML" 6 - The screen is populated with a bunch of widgets that respect the html

I suggest excluding the static entities from the counting of Application Objects , as saving it leads to spaghetti code, and using it does not indicate the complexity or magnitude of the project.

Implement the Star rating with the user review for the forge asset with some prebuild radio popups for the ODC forge asset and making a filter by rating in the ODC page

Hi everyone, I would like to propose the creation of an official training path and a specialization certification focused on Digital Accessibility, covering both OutSystems 11 and OutSystems Developer Cloud (ODC). As Low-Code developers, we have the responsibility to ensure that applications are inclusive by deeply applying WCAG standards within Service Studio and ODC Studio. My suggestion is for OutSystems to offer: Accessibility Guided Path: A comprehensive training focused on using OutSystems UI accessibly, handling ARIA roles, managing focus, keyboard navigation, and testing with screen readers. Specialization Exam: A technical validation for developers who have mastered the implementation of accessible interfaces in Reactive and ODC applications. Profile Badge: An official badge on the community profile, allowing partners and clients to easily identify developers capable of delivering high-quality, inclusive projects. Why is this important? Market Differentiation: Accessibility-certified professionals are rare and highly valued by large enterprises. Product Quality: It reduces technical debt and ensures that "High Performance Low-Code" also means "High Inclusion." Platform Strength: It demonstrates that OutSystems leads the market not only in speed but also in social and technical responsibility. I believe an "Accessibility Specialist" badge would elevate the technical level of our community and help build a digital world for everyone. #Accessibility #Certification

Right now when a user navigates to a URL that is not associated with a page or the URL for a page that has been removed, you end up at an ugly 404 page located in /customHandlers/ As seen in this forum post you can edit the custom Handler's page directly, but my understanding this would change it for all apps, and doesn't seem possible in a Cloud environment. It would be nice if we at least had the option of configuring the 404 page, similar to the Invalid permissions or Internal error pages. Especially if one of the inputs of this page was the originally attempted URL, meaning we could redirect the users if they were attempting to go to an old screen that was removed, but the content is now elsewhere. Thanks!

Hello @OutSystems Community. When we create an OutSystems Support case we are not always aware of its importance. My idea is to allow the possibility of clicking on the Tag with the severity of Issue (level of difficulty) of Support Case resolution for example "Normal" to "High" to open a popup with the possibility of changing the level of difficulty of the ticket. This idea is also in order to help the OutSystems Support team to better track the degree of demand that the resolution of each support case may require. Best Regards, Paulo Russo .

IDEA: Creation of an environment for certified developers (with at least 6 months or 1 year of certification) where he/she could test the advanced skills to pass the professional certification, the management of environment, lifetime, to create plugins or give support to the ones created when had access to such environment, etcThis would solve the lack of practice of many developers who want to give an extra step in the career and don't have opportunity to test in the company where he/she is working and would spend months or years just with theoretical knowledge until have the opportunity to test what have learnt; and for the developers who created a component but no longer have access to the lifetime would be a good chance to update the components.

There could be some magic feature that would make this time saver feature. :-)Then we could make a simple query to build the 'skeleton' of a query and then introduce the aditional rules that cannot be defined in a simple query.

Problem: Currently OutSystems ODC provides the User and access management API and Portfolio API to access the platform functionalities from code. However, connection is done via a custom consume REST Connectors, and they consume quite a lot of AOs to one's license (15+). This also Proposal: Connectors, that do not count towards the total AO count of a license. This could be achieved via a couple of alternative options: -an OutSystems-provided official connectors, that similarly to the System's libraries do not count towards the total AO consumption -unsupported custom Forge Connectors (like now), that have the option to be reviewed and aaproved by the OutSystems team, and they do not count towards the AO consumption -out-of-the-box way of consuming the APIs as part of the platform (inside System library Actions or similar)