Allow images in conversational Mentor conversation to allow us to give UI examples

Currently when we are trying to create a new idea for ODC, we get this warning: While I understand why this exists, it removes a key value of the community: visibility, discussion, and voting. If the problem is to ensure that the suggestion goes directly to the ODC team, wouldn't it be better to just notify said team when a new idea is created with the ODC category?

Currently in LifeTime, there is no easy way to identify which applications have bespoke (application-level) Content Security Policies configured. To check this, we must manually open each application and review its security settings in each environment. This becomes difficult to manage at scale, especially when CSPs are applied selectively across multiple applications and environments. It also introduces risk, as teams must rely on memory or manual tracking to know where custom CSPs have been configured. It would be highly beneficial to have: - A way to filter or list applications with custom CSPs in LifeTime Visibility per environment to understand where overrides exist - A clear indication of whether an application is using environment-level CSP vs application-level CSP This would significantly improve security governance, reduce manual effort, and help teams maintain consistent and auditable CSP configurations across their platform.

I think there should be a reset button that allows users to reset questions to default, remove the answers so that users can try answering the quiz questions again after coming back to review the material.First time i made some small mistakes, and now after 3 months i want to test my knowledge and i can't do it because the questions are already answered. Do i have to make a new account?

Mentor is outstanding for developing components when you can explain your vision with language — although at times an image truly conveys more than words. His works well for pictures of current user interfaces (from other apps, or even other parts of your own app), images of whiteboard drawings, or any additional visual aid. That translation step is where things get lost. The idea is let us submit a photo alongside the Mentor chat, and give Mentor the task to examine it and generate the OutSystems component that matches it. This would work for captures of current user interfaces (from other apps, or even other parts of your own app), photos of whiteboard sketches, or any other pictorial reference. The value here is huge for teams that work fast. Instead of taking time writing detailed prompts, you just insert a screenshot and let Mentor figure it out. This might turn Mentor effectively advantageous for a wider range of daily development scenarios, beyond merely assisting people experienced in formulating prompts.

ODC Portal should have a screen with a interface to manage all the setting of the OuSystems Cloud connector, instead of a command line.

Today is only possible to search an application by name. But would be nice to have some kind of filtering too. Today I missed a way of filtering by type (web, mobile, service). Also for example hide the applications that came from forge. But for sure there is a lot more filtering that we can use. Would be nice to discuss around this topicAnd image to be clear the screen I'm talking about:

I observe that the people who are new in Outsystems they complete the course but when it comes to certification exams they found question in exam confusing and they perform poor in exams.  I think there should be at least one mock test before certification.

It would be great to have a Start Index  property in Aggregates so that I can have pagination patterns even without UI. This way, I could state that I want 50 records starting from record 50 (e.g. to display them in the second page of a table).

Hello, community! 👋 Having worked with OutSystems over the past few years—surviving the nightmares of broken references and monolithic architectures in O11, and now exploring the isolation of microservices and the AI Agent Workbench in ODC—I started reflecting on the next evolutionary leap for our platform. OutSystems Mentor already helps us generate screens and initial logic from prompts, which is fantastic. But what about large-scale maintenance and refactoring? Our beloved TrueChange is brilliant at pointing out where the application broke. If I change the signature of a core Server Action (e.g., changing an Input from Text to a Record/Structure) or delete an attribute from an Entity, TrueChange turns everything red in the Consumers. But I still have to go into 20 different modules and fix the mapping manually. The missing feature today: TrueChange Auto-Healing (AI Semantic Refactoring) What if ODC integrated an AI engine directly into TrueChange that didn't just point out the error, but wrote the fix automatically for your review? How it would work in practice: The Trigger: You change the return of an API or the structure of an Entity in your Producer module. The Analysis: The AI Auto-Healing engine detects that 15 Consumer apps broke. Instead of just throwing errors, the AI analyzes the semantics of your change. The Action: The engine scans the Server Actions and Data Actions of the consumers and rewrites the mapping logic (adding Assigns, converting data types based on context, or modifying Aggregates). The Code Review: In ODC Studio, you get a "Pull Request" style notification. You see a visual diff (before/after) of the logic altered by the AI across all consumers, and you just click "Accept All" or reject and adjust it manually. This would transform the platform from "Low-Code" to "Zero-Maintenance Code" at the architecture layer.