It is possible to consume a REST API using the PATCH method, but it isn't possible to expose a REST API with it. PATCH is meant for selectively updating data (instead of all at once, like PUT). I would like the Platform to support PATCH for an exposed REST API as well.However, PATCH is useless without being able to detect which fields (Attributes) have been sent by the calling party. Currently, if a consuming party doesn't send all the fields, the Platform will set them to the default value. This works for most cases, but not for a PATCH. Therefore, when supporting PATCH, there must be some way (via a runtime property) for the Platform to indicate which fields have been sent, and which were not.

Developers often forget to add a Prompt for Input fields, even when a Label exists. This leads to inconsistent UI and lower usability. Proposed Solution: If the Prompt is empty, OutSystems automatically sets it to match the Label text. Developers can still override it manually. Works for single-line and multi-line text inputs, across Web, Reactive, and Mobile apps. Example: Label: Email Prompt: (empty)→ Automatically set to: "Email"

Instead of having only a straight line, see forum post: https://www.outsystems.com/forums/discussion/5275/action-flow-how-to-make-angles-in-connectors-lines/

 Idea Summary Improve the OutSystems Date Picker component to handle DateTime values more accurately and consistently by introducing timezone-aware options and ensuring correct date selection behavior across all data types. Issue Description The current behavior of the Date Picker in OutSystems is inconsistent depending on the data type it is bound to: When bound to a Date type, the selected date is passed and stored correctly. When bound to a DateTime type, the selected date often shifts to one day earlier than expected. This issue appears to stem from server-side time zone conversion, and it becomes particularly problematic in global applications, where users in different time zones experience inconsistent results. Key Improvements Needed Consistent Handling of selected date values regardless of whether the field is Date or DateTime. Time Zone Awareness to avoid unintended shifts due to UTC or server time assumptions. Developer Control via an optional toggle or setting in the Date Picker to treat DateTime values as local dates by default. Suggested Enhancements Add a "Treat as Local DateTime" option in the Date Picker widget settings. Ensure that when a date is selected, it reflects midnight of the selected day in the local time zone unless explicitly configured otherwise. Provide clear documentation or tooltip guidance within the widget for Date vs DateTime behavior. Impact of the Issue Off-by-one-day errors when storing or displaying selected dates. Increased debugging effort due to non-obvious time zone conversions. Reduced trust in date handling for end users, especially in global or multi-regional apps. Higher complexity in development when working with DateTime fields that should behave like Dates. Benefits of the Enhancement Eliminates unexpected date shifts and off-by-one-day errors. Simplifies development and reduces debugging time for apps using DateTime. Improves accuracy and reliability of date-related data across different regions. Enhances the user experience with a more intuitive and predictable Date Picker. Supports global applications where proper time zone handling is essential.

Being able to see line numbers when editing CSS/JS files larger than 50 lines is a must. Currently I'm fighting through a 7000 line JS without this feature, and it's really a pain. Thanks community for voting this up and thanks OS for implementing this today :)

Just like "Is Auto Number" option Have an "Is Auto UniqueIdentifier" option to automatically generate GUID for entity primary key id.

The AI Mentor Studio is already very powerful but we always look for new ways to make it even more helpful. Currently, alerts are assigned to the last person who modified an element. However, in some cases, the alert is triggered due to changes made by someone else. Adding an option to manually reassign alerts would help ensure they are directed to the most relevant person. Hopefully these suggestions will be taken into consideration :) Cheers, Vanessa Espírito Santo

In some cases the feedback message widget is displayed to long/short. It possible to change that but then you'll need to clone the RW eSpace and make the change youself. It would be nice if there was a input paramter where the display time could be set. On this way it's more useble in different situations.

The idea would be to encourage people to do the lockdown and see whose around is doing the same.Possible features:- Integrating with Google maps, we could add our home to this network and see our neighbors- Share tips with our neighborhood (how to do shopping, what is open, limits, etc)- Share specific needs that might arise in a neighborhood (for example, someone senior that can't go buy stuff, etc)- In a broader scope, share tips for lockdown with kids, seniors, etc- We can add a "gamification logic" to rank neighborhoods with more people on lockdown, achievements, etc.This is just a quick idea that can be definitely improved with our community!

It would be great to have a diferent icon on actions that are using the cache property, in order to be visual distinguishable. Automatically because you can do it manually. This could be very usefull when debugging to see the code and to see that the action is cached