Just like in Traditional Web, it would be nice to have a simple way of translation prompts/text/static entities.

Hello! I would like to propose a feature enhancement for AI Mentor that would allow manual synchronization of one or more specific applications via an API. This capability would be highly beneficial, particularly for teams integrating AI Mentor into a CI/CD pipeline to improve application quality. Why This is Important Currently, AI Mentor’s synchronization process covers the entire factory and follows a periodic schedule, which does not align well with CI/CD workflows. In modern development practices, quality checks need to be integrated at key points in the pipeline, ensuring that applications are analyzed at the right time—before deployment, after code changes, or during specific release stages. Proposed Solution Providing an API endpoint to trigger synchronization for selected applications would enable: Faster Quality Feedback: Developers can validate application health immediately after changes, reducing the time to detect and fix issues. Efficient Resource Usage: Instead of scanning the entire factory, teams can focus AI Mentor’s analysis on the relevant applications, optimizing processing time. Improved CI/CD Integration: This would enable seamless automation within pipelines, ensuring that applications meet quality standards before reaching production. This addition would greatly enhance AI Mentor’s usability in enterprise DevOps environments. Looking forward to your thoughts. Best regards,

With the introduction of the Dynamic Case Management Framework, OutSystems advocates to use GUID as a unique Text Identifier (see https://success.outsystems.com/Documentation/Case_Management/Create_a_case_management_app ).Apart from that GUID as identifiers have some other use cases too:Less "hackable" URLs to your application pages than when using Integer IdentifiersLess meaningful Identifiers (Employee number 2 is probably longer with the company than Employee number 58)You want the data to be uniquely-identified, no matter where it came from.You need to be able to combine data from difference sources with little-to-no chance of duplicate GUIDs.Furthermore, you don't want or don't care about the users needing to remember an ID themselvesIt would be nice if there is more support in the Platform:Add a new datatype called GUID, with an AutoNumber option.Add a popup menu option to generate a GUID and set it as a string literal for any attribute of datatype GUIDAdd built-in feature to also generate a GUID for Mobile and Reactive, as it is currently only available server side. Yes Forge component exists to help you, but this should be build in.

While creating Agentic App. the models on the ODC portal are available for every developer without restriction. this could hinder with governance policies while dealing with multiple teams. Suggesting to add Management layer similar to OS 11 lifetime teams to manage development teams more effectively enabling governance of apps and AI Models.

If I have applications installed from Forge like "SilkUI Framework" or "Google Maps", Service Center and\or Service Studio could notify me if there are newer versions available.This way Forge would work like a real App Store and notify the users each time a new version of an app is available, and with a click we could instantly update those apps.This option should be configurable from Service Center \ LifeTime.

When working on a large project it is common to do fairly much the same deployment each sprint into our QA environments. It would be great if we could setup the deployment in lifetime, give it a name and save for future deployments. We can sort of do this at the moment but you can only have one saved plus it saves the current versions of everything so if espaces are updated in the source environment you don't get those updates when you finally go back in and deploy the saved plan. It will still need to run all the normal validation checks each time and allow us to add additional applications before hitting the deploy but would at least save time adding all the same common ones each time. Yes we could do this by creating a solution and deploying via servicecenter but then it is a multi step process and we don't get all the additional reference checks and auto including from the validation step.

To prevent an agent from accidently executing multiple times without supervision. It would be good to add a security feature to disable specific agents on the ODC Portal for each environment.

When you create your personal free environment with OutSystems, you cannot change the generated name, which in some cases is hard to remember.If you could set your personal environment name like picking a username, would be great :-)

It would be nice if OutSystems would provide a reactive version of the Data Grid component.Given the amount of post on the forum regarding data grid related topics, it is fair to say it is a popular component that developers use. With the shift from tradional web to reactive web applications, it would be a pitty to not have this component available as a reactive version.

The idea is to add the possibility to classify the type of advanced query we need. This is very important because when we are using a SELECT query, we need to insert the output correctly. But when we only want to create an UPDATE query or a DELETE query, e.g. bulk update or bulk delete, the output structure is not important and by classify, for example, we don't need to insert an output chosen by us.Another example of a rule applied using this type, there is no need to insert a TOP in the DELETE or UPDATE queries and of course no Max. Records.