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!

While learning and working with JavaScript inside OutSystems, I experienced a situation where an error in my JavaScript code was not indicated while I was writing it. For example, I declared an array using const and later tried to assign a new value to the array variable. I was not aware that this was an error, and the JavaScript editor did not provide any indication while I was writing the code. I only encountered the error when I tried to publish the application. As a developer who is learning JavaScript, it was difficult to identify the mistake without immediate feedback. My suggestion: It would be very helpful if the JavaScript editor in Service Studio could detect common JavaScript errors while the code is being written and indicate them visually, for example with a red underline or error marker. Hovering over the marked code could also display a short explanation of the error. This would allow developers to identify and correct JavaScript errors immediately instead of discovering them only during publishing. I believe this would improve the development experience, particularly for developers who do not have extensive JavaScript experience.

When we create a new solution with some Modules use missing or inconsistence dependencies or some Modules have outdated dependencies or some Modules are Offline or Modules have outdated dependencies that may be incompatible" in... Service Center > Factory >Solutions > New Solution It would be good if we could filter by type of inconsistence. This is happening on version 11.22.0. Best Regards, Paulo Russo . www.paulorusso.pt

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.

Hello Everyone. When we access the Application > Applications tab in Lifetime and want to extract all versions of existing applications from all applications in the OutSystems Factory, we don't have the option to download everything. My idea is this: to have an Export button like "Download Versions List" Button on this page to automate this time-consuming process. See the image below. Best Regards, Paulo Russo .

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!

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.

I would like to suggest a feature that allows developers to navigate directly from a UI element in the running application to the corresponding element in OutSystems Service Studio. Current Challenge When debugging or making changes to an application, developers often need to identify which screen, container, widget, text, button, or other UI element is responsible for a particular part of the application. Currently, developers may need to manually search through screens and UI hierarchies in Service Studio to locate the corresponding element. This can be time-consuming, especially in large applications with complex screen structures. Proposed Solution Introduce a “Open in Service Studio” / “Go to Source” option for UI elements. For example: Run the application. Select or right-click on a UI element, such as a Text, Button, Container, or Input. Select “Open in Service Studio” or “Go to Source.” Service Studio opens the corresponding application and screen. The selected UI element is automatically highlighted in the widget tree. Example If I see a text on the application: “Customer Details” I should be able to select that text and choose: Go to Service Studio → Service Studio would then open the relevant Screen and automatically select the corresponding Text widget. Additional Possibility This could potentially be implemented through a debug/developer mode, so the feature would only be available to authorized developers and would not expose development information to normal end users. It could also work for: Text Buttons Links Containers Inputs Images Lists Forms Other UI widgets Benefits Significantly reduces debugging and navigation time Makes it easier to understand existing applications Helps developers quickly identify the source of a UI element Particularly useful for large and complex applications Improves the overall developer experience in Service Studio Makes UI troubleshooting much faster Suggested Feature Name “Go to Source” – Navigate from UI Element to Service Studio I believe this could be a very useful productivity feature for OutSystems developers, especially when working with large applications and complex screen hierarchies.

I would really like to see some sort of "auto arrange" for Service Studio that just moves the items in an action to have nice even spacing, put the work for For loops to the side, make branches look nice, etc.J.Ja

Today, when there is need to do some configuration in the destination environment of a deployment (site properties, timers, end points, etc), this configuration must be made after the deployment is done.Would be nice to have a way of preparing those configurations during the planning and see them being applied automatically during the deployment.