During the development, when you add functionality through the editor view itself (not drag and drop from the Logic-Tab, stars are sparkling over the last added LogicNode. It would be great to disable that UX-Element, because als long as those stars are sparkling, you are not able to click the logic node below. This slows down the development speed. Thank you, Kevin

Just like "Action's" folder allow user to add folders to the Entity and Structure tree.

 Problem Statement In ODC, a Client Secret is required in virtually every scenario where an app communicates with external systems or calls ODC Management APIs programmatically: UsersManagement (Forge) → ODC User & Access Management API External IdP integration (OIDC) → Azure AD, Okta, etc. ODC REST API calls → Portfolio API, and others External service integrations → Salesforce, MS Graph, etc. The current behavior is that Client Secrets expire every 90 days by default (maximum 2 years), and renewal is only possible manually through the ODC Portal. Root Cause of the Issue This is not merely an inconvenience — it is a structural constraint that breaks the promise of full automation in ODC-based services. Here is why: ① No programmatic renewal path exists There is currently no Management API endpoint to rotate or renew a Client Secret. This means that no matter how well-automated your app logic is (e.g., a Timer-based user management flow), the secret renewal step always requires direct developer intervention. ② Expiry creates operational risk at scale In production SaaS or B2C environments running on ODC, a missed secret expiry means: All features depending on that secret stop working silently or with cryptic errors End-users are impacted before the team is even aware Recovery requires Portal access by a developer with the right permissions — not something an end-user Admin can resolve ③ The expiry cycle creates recurring developer toil Even with the maximum 2-year expiry configured, and even with calendar reminders or monitoring in place, this is manual, recurring, high-risk maintenance. It runs counter to the Low-Code philosophy of ODC: reducing developer toil and enabling reliable, autonomous operation. Requested Feature(s) Please implement one or more of the following: Option A — Programmatic Secret Renewal via Management API Add a Management API endpoint that allows an authorized app to rotate or renew a Client Secret before expiry. This would enable a Timer-based auto-renewal flow entirely within ODC, with zero developer intervention. POST /api/v1/clients/{clientId}/secrets/rotate→ Returns: new_secret, valid_from, expires_at Option B — No-Expiry Secret Option Allow trusted, internal service accounts to opt into a non-expiring Client Secret, similar to how other platforms (e.g., Azure App Registrations, AWS IAM long-term credentials) provide this option with explicit acknowledgment of the security trade-off. Option C — Secret Rotation with Overlap Window Support a dual-secret validity window during rotation — where both the old and new secrets remain valid for a configurable overlap period (e.g., 24–72 hours). This enables zero-downtime secret rotation in production environments.

On ODC Studio when you create a new agent, there is a configuration named Call Condition. By its description and behavior it should be called Stop Condition to avoid confusion: It is already there when you open the question mark icon:

Support datatype of jsonb, feature of Similarity Search, pgvector as vector database for LLM embedding storage.

Hi, There aren't proper descriptions or steps on how to get certain badges. For example, the badge "Interoperability O11 and ODC" says "Complete the “Future-Proofing your OutSystems Factory with O11 and ODC” Training program" but searching for “Future-Proofing your OutSystems Factory with O11 and ODC” there isn't any item in the list. Also, the filter in the "https://learn.outsystems.com/training/catalog" page only allows 50 characters.

Add the Audit's commonly known attributes: - CreatedAt - CreatedBy - ModifiedAt - ModifiedBy To the System's Site Properties entities (Site_Property, Site_Property_Definition and Site_Property_Shared). I know there are some audit logs when a user changes a site property, but having these in the entities would be helpful.

Add text propriety to the Navigation component in order we can configure the text expressionFor example, change the text items to books. "1 to 10 of 15 books"

When deleting a personal environment, would it be possbile to zip the OML's and send it to the user? Especially for ODC where the personal environment gets shut down within a week of not using it. I just had a personal project I spend 20-30 hours on, and then got a load of work meaning I had no time for the personal project for 2 weeks. When I came back to it the environment is gone and everything I've worked on is gone. If there was some way to restore it, I could just set up a new environement and look at the OMLs, but now it's all for nothing. It feels really demotivating to learn and improve on a personal environment if you have this delete with no backup system on the environment. I know that you don't want to host free environments because it cost you space, but doing this, or maybe even enable self hosting or something for a free version, so you don't have to deal with the storage, would allow us to have a passion for OutSystems outside of work aswell :)

Hi, I'm not sure if I'm the only one experiencing this but my login in outsystems.com does not persist more than a couple of hours even if I have the "Remember me" option enabled. Furthermore, I have to type mail email every time as my browser does not offer autocomplete for the email input (this might be a separate issue). Even when I try to access documentation pages, it asks for my login. If I refresh a couple of times I can access them without session. So clearly something is very wrong with the login system in outsystems.com . Could this be improved / fixed? Thanks, Tiago