Upgrade the standard File Upload widget to a comprehensive "File Manager" component. Beyond just uploading, this widget should natively support: Removal: Easily delete a file before submission. Review: Integrated Preview and Download actions for subsequent users in a workflow. This eliminates the need for developers to build custom "Download/Preview" patterns every time they create an approval-based form, providing a seamless experience for both the uploader and the reviewer.

Hi, Just published an app in O11 after undoing some steps. Then noticed that Service Studio automatically undid my undone and published a latest version without my changes and even without giving me a warning or an option to select. Please: Don't try to automate things that should not be automated. The developer should be the one in control at all times. Also, every time I publish, the laptop gets a bit unresponsive till it finishes. I don't know what was changed in this version but has some issues. Note that issues in copy-paste are on-going for several versions now. This might be because of some background processing for automations but are impacting when we need to copy text inside Service Studio (that doesn't get copied). Best regards, Miguel Garcia

Enable to Test an Action giving new input parameters.

 Problem Debugging layout issues in Reactive Web apps can be time-consuming. Developers often need to inspect CSS, containers, flex behavior, spacing, width, and alignment directly in the browser, but Service Studio does not provide a clear visual way to understand why a layout is breaking. How this suggestion can help A built-in Layout Inspector would help developers quickly identify spacing, alignment, overflow, flex/grid behavior, and responsive issues without switching constantly between Service Studio and browser DevTools. Implementation example Add a right-click option on widgets: Inspect Layout It could show: Widget: Container_Main Display: Flex Direction: Row Gap: 16px Width: 100% Padding: 24px Overflow: Hidden Parent Container: Section_Content It could also highlight margins, padding, and parent-child relationships visually inside Service Studio.

Full widespread support for null values, in all layers: database, actions, ...Not fake zeros disguised as nulls, but real thing, the ones that we can compare to is null. The ones that mean "I don't know the value for this... I don't even know if its zero"

I would like to be able to use HTML content in the email body in Reactive apps.Html content is needed to sent emails with a nice layout from Reactive apps.Expressions in Traditional Applications have the "Escape Content" attribute. When you set it to "No" a mail sent by a Traditional Application is delivered as a HTML Document. This is not possible in Reactive applications.The HTML Element can also not be used in an email in Reactive app.The only current solution would be, to create a Traditional Application just for sending the email and provide a public EmailSend-Method. But that is a lot of overhead just to send a mail.

when refactoring entities between espaces, manual database scripts are required to migrate data to the new physical entity

Would be a (minor) quality of life feature if you could bind a label to an input if you simply drag and drop it from the tool box on the left straight on the Input widget. For example here, this widget is bound to a "Max records" local variable, to control how many records an aggregate returns. If I drag the label on to it, it could do several things: Add the label on top of the Input Set the Input Widget automatically on the Label properties, and give it a name like "InputName_Label" Set the text for the label on a 'best guess' case, depending on what the input is bound to (for example here, Max records) This could work for all other input type widgets: text area, switches, checkboxes, dropdowns, etc.

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

OutSystems is actively supporting integration of ODC and O11. Currently, the only way to consume logic from each other is to use a REST API. This is cumbersome and portentially unsafe. It would be much easier if the Platform allowed consuming Service Actions instead (which in essence are also REST methods, but easier to use). So O11 logic could consume an ODC Service Action, and ODC logic could consume an O11 Service Action. This would greatly enhance easy operability, and be secure out of the box.