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.

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 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

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 is impossible to break/continue if you have more then one nested foreach cycle.Adding an action like a terminator to a cycle could lead to the previous one, for example.

OS11 can connect with SAP using SAP Group Logon, but that is not available on ODC. On ODC only SAP Direct Connection is available. It's important because many clients only have SAP Group Logon active in Production environments for load balancing.

This idea is a suggestion for OutSystems UI but also for an improvement on Service Studio. Add support for a dark theme in OutSystemsUI. This version of the theme would be similar to the viewport simulation approach, with classes in the body tag displaying which type of device the user has. The new classes would be "dark" and "light". Add a ThemeSwitcher Pattern to OutSystemsUI. This pattern would be responsible for managing the theme, keeping the user's preference in local storage/client variables. Add a dark theme simulation in Service Studio Again, similar to the viewport simulation that lets the developer see the page in 3 different screen sizes, there would be an option to see the page in dark or light mode. The dark theme is a great modern addition to any app, because it lets users choose which theme is best for their condition. Having it integrated both in OutSystemsUI and ServiceCenter would allow OutSystems developers to have an implementation of this feature that is both universal and officially suported.

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