Union of Simple Queries

Can we have a library or component through which we can create the form along with validations using the power of AI. If we want to create a particular form we can just type a prompt like ‘Create a form for customer/user onboarding’ and it generates labels, validations, fields, etc using AI. (Integrations and connections can be made to the AI) Is this a possible thing to do.? It may serve as an accelerator. Your suggestions and insights are encouraged and welcome. Thank you!

A no-brainer: having the possibillity in the Expression Editor to click on a true or false button to have the text.Just like you have now with the null identifiers.Yes, its lazy but that's the common thread with developers :)

When we add an Idea it shows a message "Is your idea original?" Same can be done when we are uploading an asset in forge component that will help duplication of the asset.

Hi,Is there any way Outsystems can add the email feature in Reactive Web without the use of the current workaround by using the action made from a  traditional web appThanks and regardsRaphael Laurence Reyno

Right now roles have a "Name" which cannot have spaces in it, and they have a "description" for longer descriptions like "Admins have the ability to...". What they are missing is a proper "Label" field that lets you put freeform text in.So if I have a role called "SuperAdmin" I would like to give it a label of "Super Admin" so I can display it nicely on the screen.J.Ja

I have noticed, and confirmed, that submitted Forge components in ODC Forge do not currently contribute to the community ranking. Additionally, it appears that there are no planned updates to address this issue. In my opinion, addressing this functionality is important to maintain the significance and value of both ODC and O11 when it's about the community ranking.

It would be nice to be able to scaffold API methods automatically based on entities.The idea is to work similar to some frameworks like Django that based on a data model creates the following methods:If the entity is Account:GET: /api/account/GET: /api/account/{id}/POST: /api/accountPUT: /api/account/{id}/DELETE: /api/account/{id}Of course after the scaffolding will be possible adapt to add validations/security process or anything that is necessary but this can accelerate some developments.

Creation of a widget to be used on the screen's actions that allow a simple and much faster validation of a form. Why?The time that nowadays we take to perform all fields validation in a form is high. Additionally, in a typical "Save" action, it gets very confused when we mix the "twenty" validations of dates, mandatory texts and business logic, with the save action indeed. It is not visually pleasing to read the action. How?Create a widget that visually looks like the form of properties of a entity. In that form, the user can add the fields that need validation, including also the expression that it is used to validate and the error message to show for each field. The widget can return a boolean called "Success" so that the user can continue to work in the "Save" action.

 To optimize AO usage, multiple Static Entities can be merged into a single Static Entity with an additional "Type" attribute to differentiate records. For example, instead of creating separate Static Entities for Country, Currency, and Language, a single MasterData entity can be used with a Type column to categorize records. This approach significantly reduces AO consumption while maintaining flexibility. By filtering data based on the Type attribute, developers can retrieve only the required records, improving performance and maintainability. This method is particularly useful for applications with multiple Static Entities, ensuring better scalability while keeping AO usage low. Would love to hear feedback on this approach!