In an app you can select the User Provider Module. But IT users are now managed in Lifetime instead of ServiceCenter. Although I understand that for legacy reasons there are still entities Entities and roles with 'SC' in their names. And for cherry on top maybe say Lifetime (IT users) for better clarity?

The ability to clone an extension would be a really really nice-to-have. :-)

As a developer I want to be in control on which ServiceActions or Events can be used in ODC Workflow. Just to make sure no big mistakes can be made by users not fully trained as developers. Ofcourse I can put them together in one app and make agreements with my Workflow users. But it would be much more convenient and robust to have a property on my Service Actions and Events where I can set if it they are allowed to be used in ODC Workflow

I think that the line number where an error ocurrs, could be useful.

It whould be nice to have an overview of all available actions and webservices in Service Center, something like a 4GL dictionary. This would give an overview of Built-in actions all public actions in Sollutions all webservices references of all eSpaces / Extensions and its function (UI / Business layer / Integration Layer) This is also the place to functionaly describe these actions/services

While using expressions in Service Studio, it would be useful if the suggestions automatically select the correct Null function if I type "null", depending on the context.

In many online games with ranking systems, such as League of Legends, players are grouped into tiers and divisions like Bronze, Silver, Gold, Platinum, etc. Each tier reflects a player’s experience and performance, such as how long they’ve been playing and how many wins they’ve achieved. While this is mainly a very simple UI concept, it’s actually a very cool one 😄 For example, if a user’s rank is above 50,000, they could be placed in a tier like Bronze, which can be displayed on their profile and also used as a filter when browsing members. If their rank is below 6,000, they could be Silver, and so on for the other tiers. Features like this were very motivating for me personally. They encourage users to progress for the next tier within the community, serving as a strong source of motivation alongside of course the other elements like badges and achievements. On top of that, tier-based badges could also be added, such as Bronze, Silver, Gold, and Platinum badges when a user reaches one of these tiers, to further reinforce progression and recognition.

It would be nice to configure the header color of Service Center.This way, it would be possible to have a different color for each environment.As a suggestion, this could be set in "Administration -> Environment Configuration" and accept a hexadecimal code or named color.This is how it would look like: Development Environment Test Environment User acceptance testing Environment Configuration

Hi all, As like Export action to image, it's better to have an option for exporting Entity into image, which contains attributes and data type of the attributes in an entity as an image. Regards Murali

 The Vision To create a seamless, AI-powered development workflow by embedding OutSystems Mentor directly within ODC Studio. This integration aims to transform Mentor from a separate assistant into an active co-developer capable of generating features in real-time through natural language prompts. Key Features Embedded AI Pane: A native "Mentor" sidebar within ODC Studio to provide contextual help without leaving the development environment. Prompt-to-Feature Generation: Enable developers to describe small features (e.g., "Create a CRUD wrapper for this entity" or "Build a validation action for this form") via text prompts. Automated Logic Injection: Mentor would draft the suggested Logic, UI patterns, or Workflows directly into the open ODC application for the developer to review and publish. Contextual Awareness: The AI should understand the existing data model and client-side logic to ensure generated features are compatible and follow best practices. The Value Add Increased Velocity: Drastically reduces the time spent on repetitive or boilerplate development tasks. Lower Learning Curve: Assists junior developers in implementing complex patterns by following AI-guided prompts. Reduced Context Switching: Keeps developers focused in a single interface, increasing overall productivity.