Hello,As Forge applications grow in use, the support cases grow as well. Take a look for instance to the XML Records component which has over 100 comments in a show-more-10-records-per-page version. There's no way to search on a support case list if a similar support case has been open. Eventually, this is a reason for why such components have eventually the same question posed time and time again.

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!

Factory configuration current design makes it very time consuming to apply setting to a large number of eSpaces, or even to your entire factory. It is also difficult to see what is or is not applied if you have a large factory. Suggestions: Allow user to select how many eSpaces user can see in the list. Currently limited to 10. Allow user to sort eSpaces by any of the columns on the table.

When we are building an integration if it has a lot of actions it would be helpful if we could create a folder so we can group actions.

Implement a real-time collaborative environment where multiple developers can work on the same application simultaneously, similar to Google Docs. This would enhance teamwork and reduce version control issues.

 Description: Automatically convert imported ER diagrams into OutSystems data models, reducing manual effort and accelerating development. Problem: Manual ER diagram translation is slow and error-prone. Solution: Implement an ER diagram import feature with automated entity, attribute, and relationship generation, plus a visual editor and validation. Benefits: Faster development, fewer errors, increased productivity, improved collaboration, and better data governance.

Idea Summary: Enhance the resilience of the OutSystems UI Date Picker widget initialization, specifically when testing mobile views using Chrome DevTools' device simulation. Currently, the widget does not always reinitialize properly after a hard refresh in this environment, potentially leading to confusion during development and QA. Issue Description: When simulating a mobile device in Chrome DevTools and performing a hard refresh, the Date Picker widget occasionally fails to initialize correctly. This behavior appears to be due to: JavaScript/UI libraries not consistently re-triggering widget initialization in simulated environments. The use of dynamic selectors (e.g., .active, input.form-control.OSFillParent.input.active ) in the widget’s initialization logic, which may not be immediately available after a refresh. Key Observations: On actual mobile devices (e.g., Safari on iOS), the widget functions reliably, even after refreshes. In Chrome DevTools mobile simulation, the widget behaves correctly on initial load or when toggling to mobile view but fails after a hard refresh. Impact: Creates confusion during testing and QA phases. May mislead developers into thinking the widget is broken. Increases friction when debugging using browser tools. Suggested Improvements: Make initialization more robust in simulated environments. Avoid dependency on dynamic class-based selectors that may not exist immediately on load. Implement fallback logic or explicit reinitialization to handle DevTools mobile simulation scenarios. Thanks, Senthil

I would be great to have the possibility of creating a timer when right clicking on an action.It could be one of the possibilities of the right click menu.

Add Social Buttons to share Ideas .Add some social button like Facebook , Linked in ,Twitter .These buttons fix near to comment and views in idea page when an idea creator want to share his/her ideas just one click is enough to share.

 I would really like to see some improvement in the environment 'initial' setup speed after a publish. Just after a initial deploy the loading of pages can take a very long time, especially when this publish concerns several larger E-spaces. It would be nice if the executed actions during a first run can e.g. be done upfront at the end of a publish. Context: A high latency is considered innoying to end-users, and will be noticed more when a lot of publishes are done during working hours. To avoid this one can delay publishes or  schedule an evening job. The scheduling as an evening job would probably result in " slow system " user notifications every morning after and less control over a publish. Besides that delaying a publish will lead to a longer project cycle. Request: It would be very nice if there would be a caching method that would make sure the webservers' cache would be filled with an initial load of the page / execute of the queries involved so the system would be responsive, even directly after a publish. Possible Workaround: Currently as a workaround I'm thinking about creating an E-space that would execute a HTTPGet on all clickable links in an E-space. I would however need to create a list of all possible links that are to be clicked and besides that need to maintain this while I think the environment is perfectly aware of these links and there is probably a more efficient way to cache both queries and pages.