Working with multiple environments simultaneously is a standard practice, but Service Studio makes it hard to distinguish between them at a glance. Currently, a developer must check the status bar to know if they are in Dev, QA, or Prod. Introduce an "Environment Theme" feature where we can assign a specific color to each infrastructure. If I'm in Production, the Service Studio UI (or at least the tab bar) should have a distinct color (e.g., Red). Add the environment name as a prefix to the tab title (e.g., "[PROD] MyModule"). This would prevent accidental changes in the wrong environment and significantly improve the UX for developers managing complex lifecycles.

Hi, I've run into this a few times. I would like to have the ability to do a simple query with an IN clause, without having to rely on advanced queries. It should accept a list of Identifier. Today we do ( from an aggregate perspective): SELECT * FROM {TASKS} WHERE id = 1 or id = 2 or id = 3 But it would be really awesome if we could do SELECT * FROM {Tasks} WHERE id in (1,2,3) This allows us to do some pretty cool stuff with Lists setc ( eg you can now shim some of the more advanced sql functionality without writing advanced queries). An example would be: myList = SELECT id from People WHERE OrganisationId = 2 SELECT * FROM {Tasks} WHERE personId = myList Which would be 2 actions, and somewhat faster/cleaner than the current way Writing an advanced query ( frowned up by my companies' best practices guide - and I've also found advanced queries tend to be annoying to manage ) Looping through myList and putting the outputs into another list, which is then passed around (this also has a few nasties - lots of DB hits (albeit small ones), and refreshing this with paging is a pain

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.

To add a link or a way to quickly open the Event Handler Action from Properties / Events of UI Widget. This can be extended to On After Fetch of Fetch Data From Server or UI Aggregrate. This will improve the developer experience to quickly open the Client/ Screen Action that assigned as Event Handler or After Fetch Event rather than scroll up and down Elements Tree For Button and link, we can quickly double click the Element in the canvas to quickly access the OnClick Event Handler already, however, this should be good if there's a similar way for other Widget like Dropdown, Switch, Custom WebBlock with Events, Data Fetch Aggregate...

Adding Native Semantic Search capabilities within the OutSystems platform. This would allow developers to implement search features that understand the user's intent and the contextual meaning of their queries. Key Features: Vector Embedding Support: Built-in capability to generate and store vector embeddings for database records directly within the platform. Natural Language Queries: Users can search using phrases like "fresh products near me" instead of specific product names, and the system should understand the intent. Multilingual Semantic Search: Since many apps are regional, the search should understand queries in local languages like Malayalam and map them to relevant results even if the keywords don't match exactly. AI Orchestrator Integration: Seamless integration with OutSystems AI Orchestrator to leverage models like Google Gemini or OpenAI for retrieving search results. Why it matters: Integrating semantic search will revolutionize how users interact with data in OutSystems apps. It improves user experience by providing more relevant results, which is critical for the success of systems.

Extend the platform's JavaScript Node and Client Action invocation contract to include a fifth built-in parameter: $event, exposing the native browser Event object alongside the existing $parameters, $actions, $roles, and $public. The change would be additive and non-breaking - I assume. Use case : implement an OnKeyUp handler that runs logic only when Enter is pressed, without manually wiring addEventListener/removeEventListener — the platform already manages the event listener, it just needs to forward what it receives.

Hi If I'm using Data Fabric connector for O11, I get a Private Gateway out-of-the-box, creating a secure, encrypted tunnel between my ODC tenant and my O11 environment. If I'm doing REST API O11 ODC, I still have to design connectivity myself. OutSystems provides coexistence capabilities between: -OutSystems 11 (O11) -OutSystems Developer Cloud (ODC) These allow to: -Expose APIs/services from O11 to ODC Consume O11 logic from ODC apps (and vice versa) However: This is based on standard integration mechanisms (REST APIs, networking configuration, identity setup), not on an automatically provisioned “private gateway”. For this situations where the services are on O11 set the REST API property API Consumer to ODC and on ODC are set to REST API property API Producer to O11 it would be useful to have a Private Gateway out-of-the-box. Regards

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.

In OutSystems Platform publishing is like comitting your changes to Version Management. It would be extremely helpful to be able to add comments on the 1 Click Publish process. This would be even more flexible if one could drill down these comments by changed object (webscreen, webblock, action, webreference action, etc)

As we are now having folders everywhere, please do the same for service studio main screen. This way applications can be grouped by context.