I propose adding an optional parameter to the Round() and FormatDecimal() functions to select the rounding strategy (e.g., Round Half Up, Round Down, Ceil, Floor ). Currently, OutSystems client-side uses Decimal.js with a hardcoded default of ROUND_HALF_EVEN . While standard, industries like Fintech and Brokerage often require different methods (like ROUND_HALF_UP for taxes or ROUND_DOWN for fractional shares). Update the built-in functions to support an optional rounding parameter: FormatDecimal(Decimal, Integer, Text, Text, [RoundingMode] )

Self-quarantine is a very important part of journey to deal with Corona Virus. There can be instances where  people in self quarantine might need help with basics around household stuff, groceries etc. which they cannot step out to get. A portal where patients can post for help and then people in the vicinity can offer for help. Then based on the responses the patient can choose any one to help and provide additional details like address , contact details as required.

With the creation of this new feature of disabling elements in the action flows, "garbage" of unused logic can be accumulated in a fast way. If it was possible to find these disabled elements in a fast way, it could be very useful in my opinion.

When using the SingleSignOnMobile plugin in my mobile app, I noticed it was taking some time to process my requests. On further inspection, I noticed that multiple server calls are made before redirecting to the SSO page. By looking at the code, I can easily tell that GetToken and GetRequestDomain are unnecessary server side calls. GetToken is used to do a string split. This can be done client side in javascript. ~400ms of processing would be saved. GetRequestDomain is used to get the current host. This is also achievable in javascript (look at window.location). Another ~200ms would be saved. In short, currently OutSystems apps that make use of this plugin take an extra half a second (or more) to process because the plugin code has some serious performance problems. This looks very easy to fix, just by replacing server calls with javascript. Can a new version of this plugin be released that tackles these issues?

 Issue: The Table Grid component in OutSystems is currently missing several helpful features found in the Data Grid, including the column picker. As a result, developers frequently resort to the Data Grid solely for offering column customization features, even though the Table Grid would be more suitable for less complex scenarios. Moreover, the Table Grid lacks a native feature to establish row gaps (spacing between rows), which would enhance readability and visual aesthetics in numerous situations. Concept: Upgrade the Table Grid feature by incorporating: A column selection tool enabling users to dynamically display or conceal columns. A row gap feature to manage spacing between rows for improved visual appeal and readability. Advantages: Lowers the necessity to utilize Data Grid for straightforward use cases. Enhances user experience via personalization and improved layout management. Maintains lighter pages that are simpler to manage while providing increased flexibility.

It is just a minor issue but it happens that I want to change the order of the variables in an Assign.

Hello,In several organizations there is a need to perform periodic access reviews because of regulatory requirements, and for doing this it implies to extract the list of users and roles with the permissions peer environment. So having this in consideration my sugestion is that in LifeTime Users List (/lifetime/Users_List.aspx) and Roles List (/lifetime/Roles_List.aspx), the Administrator would be allowed to export this information to Excel or/and pdf.Thanks,Miguel Oliveira

Let’s create an app where emergency and medical personnel can place a reservation for groceries with their supermarket of choice. This way when they finish their long and tiring shift, they just have to drive by that supermarket to pick up their already packed up groceries (e.g. by showing medical ID). And if that supermarket is willing to deliver the groceries themselves, they can do it at a moment that is convenient for the emergency and medical personnel.This way, we can give back to the hard working emergency and medical personnel. We help them by setting aside the groceries they need so they don’t have to find nothing but empty shelves in their supermarket after a long shift.A couple of features:- Registration page for supermarkets who are willing to participate (pick up/delivery options)- Place Groceries order (pick up/deliver) by specific supermarket or by radius (so supermarkets within that radius can pick up an order)- Calendar reservation for grocery shipments- Search by supermarket name or for nearest participating supermarket (based on address or GPS location)- And more...Due to COVID-19 in a lot of countries it has become an issue that our hard working emergency and medical personnel either don’t find the groceries they need because of high demand and long shifts or they don’t find the time to/are to tired to do their groceries after a long shift.I think this is app would be of great help to them and a lot of countries might find this idea useful.They care for us, we ‘GroceryCare’ for them!

When you configure Log Redaction to "Yes" it is only redacted if the header is sent on the exact same case as seen on Service Studio. It should have been case insensitive as RFC 7230 Section 3.2 states: Each header field consists of a case-insensitive field name followed by a colon (":"), optional leading whitespace, the field value, and optional trailing whitespace. This behavior happens with or without Name in Request set.

Add deployment plan and deployment notes in ODC, like there are in O11.