There is a limitation in mapping two structures with different types and one element is a list of any type. Service Studio doesn't shows the mapping function.We're only able to Map 1 level, as shown in the example below:The mapping should also work for inner lists elements of a structure.

If you try to use the Mod() (modulus operation, for taking the remainder) function in a Filter of an Aggregate, Service Studio gives an error:"'Mod' function cannot be executed in the database, so it can't receive any attributes from the aggregate as parameter."This is nonsense however, as Microsoft SQL Server has the corresponding "%" operator, and Oracle has a MOD() function, so both supported databases know how to perform a modulus operation just fine. Therefore, Mod() should be allowed in an aggregate.

To put it simply and directly: It would be great to be able to provide Mentor with a screenshot of a screen built in Figma. Who knows, maybe the Mentor can help create amazing projects with that.

To support the secure storage of runtime external access credentials or tokens, it would be useful to have the ability to set Site Properties as Encrypted . CA

Right now when you want en entire Row of a table clickable (or another event), you need to put the OnClick event on every Row Cell and point to the same action every single time which is quite repetitive and prone to mistakes. If you add a new Row Cell because extra data needs to be shown, you need to put the OnClick action again for this specific Row Cell even though it point to the same end point as the other ones. It would be nice if we could put the event handler on the entire Row instead of on the Row cell. Like this, newly added Row Cells will automatically point to the same OnClick action and you won't forget it. The option to put different handlers on the different Row Cells should still stay. This would just be an extra way to make an Action for a whole Row at once.

First off, the "Create Action Wrappers" feature is really useful. When you right-click an Entity and generate the Create and CreateOrUpdate server actions, the platform already checks for Mandatory attributes. If a developer misses assigning a value to a mandatory field, an exception is thrown at the application level. That's a nice touch and saves a lot of headaches. One thing I noticed though is that for Text attributes, there is no validation on the defined Length. So if a developer passes a string that is longer than the max length set on the attribute, the value still goes through to the database and you get the classic "String or binary data would be truncated" error. That's a database level error, not an application level one, and it gives the developer zero context on which attribute caused the problem. Since the platform already knows the Length property of each Text attribute (in the Entity definition), it would be great if the generated wrapper could also validate against it. Same pattern as the Mandatory check, just extending it to include a Length check for Text attributes and throw a meaningful exception before it hits the database. This could help by: Making the generated wrappers more complete and consistent Giving developers clearer error messages during development and runtime Reducing unnecessary database round trips for data that was never going to be accepted anyway Really appreciate how the platform already handles the Mandatory side of things. This would just be a nice extension of that same thinking. Would be great to have this for both O11 and ODC. Thanks for considering!

Well, the title says it all.I mean, having it organized in folders like in the Logic tab would be great.

I often receive certification vouchers but don’t schedule the exam right away. After some time, it becomes difficult to remember which exam each voucher is intended for. It would be very helpful if the voucher email clearly stated the associated certification exam, or if there were a section in the user profile where we could view all available vouchers and see which exams they apply to.

This is a project aimed for Portugal, in a first phase, but which can be extended to other countries.It is just an idea and I count on the support of this forum to make it grow and solve the challenges! VisionEnable and manage the delivery of food and basic goods, in the form of a basket, to people who are more prone to be infected with coronavirus, already has coronavirus or is in quarantine. PersonasHypermarketsVolunteer to indicate beneficiaries and transport basket delivery Use casesRegistration of Hypermarkets- Responsible for creating the basketsRegistration of Volunteers- Responsible for collection and delivery to the beneficiaries respective addressesRegistration of beneficiaries- Registration will be done by the volunteer who indicates a family that meets the conditions to be a beneficiary Challenges- How to check if the family should be considered to benefit?- Definition of the basket. Should we have multiple types with different prices?- Online payments (only).- How to deliver safely? User Stories (draft)US1 - Registration of Volunteers- With facebook or google and with indication of the area of residence to define a range of action- Indication of the hours available to make deliveriesUS2 - Registration of Hypermarkets- As OutSystems has a close relationship with Continente hypermarkets, it would be easier to articulate with them in a first phaseUS3 - Registration of Beneficiaries- This registration must be done by the Volunteers through their account.- Indication of name, address, number of people in the householdUS4 - Task assignment to the Volunteer- At the end of each day, generate a route for the volunteer, which should be done the next day.US5 - Task completion- The beneficiary must indicate that he received the basket.I hope that this helps to understand the idea and that it can grow with the support of everyone.Thanks!

While OutSystems UI provides a solid foundation for functionality, the default Layouts (Top Menu, Side Menu, etc.) and screen templates have started to feel a bit dated compared to modern web standards (e.g., Vercel, Stripe, modern SaaS dashboards). Currently, frontend developers spend a significant amount of time overriding default CSS, adjusting padding, shadows, and font hierarchies to make applications look "fresh" and less like a standard enterprise tool. The Idea: I propose introducing a new set of "Modern" Layouts and Themes within OutSystems UI that prioritize current design trends out-of-the-box. What this should include: Cleaner Aesthetics: More generous whitespace, softer shadows, and modern border-radius defaults. Updated Navigation: Sidebar and Topbar designs that feel more like modern SaaS products (e.g., collapsible floating menus, blurred/glassmorphism backgrounds). Typography Focus: Better default font scaling and hierarchy for readability. Native Dark Mode Polish: Improved contrast ratios for the default dark mode. The Benefit: Faster Time-to-Market: Developers won't need to waste time writing custom CSS just to make the app look modern. Better Sales PoCs: Out-of-the-box apps will look impressive immediately, helping sell the platform to UI-conscious clients. Developer Experience: A more inspiring starting point for UI design. Let’s give OutSystems applications a fresh coat of paint by default!