When I set a description to a timer in service studio, I can't read this description at the timer in service center. It would be nice to being able to read the description of a timer in service center so that I don't need to open the eSpace to see where the timer was used for.

Outsystems wraps most inputs in a span, as you can see in the screenshots below. In some cases, that leads to cumbersome CSS selectors. For example, when I want to style a label succeeding an input, I need to write the following CSS: span:has(> .checkbox) + label { ... css styling } If I wouldn't be wrapped, I could just simply use the input + label selector. Also leads to a cleaner DOM imho.

Ai Recommendation in action flow like if i touch the flow like a new pop will appear and tells what are the possible widgets with the prebuild works that can able to place here with the reference of previous acions/widgets outcomes

After add locales instead of  use the translations locale lists present on the interface-multilingual locales it woud be nice to have the possibility of select a text in preview mode  on service studio and translate it in the context of the page.

If we are implementing the BDD framework than there some possibility should be there for getting the Code coverage. It will be us analytical report that how much scenario is covered

Prod data is not always so confidential to developers that it really needs to be hidden in Service Studio. Having it available makes it much easier to solve problems in Prod.A flag to display or not could be available to admin.

Problem: When setting up the Extensibility Configurations JSON for a mobile plugin, we often need to define the URL to a private Git repository. Currently, the only way to do this securely is to: Manually construct the full URL, including the secret token (e.g., https://@github.com//.git). Place this entire string into a single Application Setting. Mark that setting as "Secret" to protect the token. This process works, but it has a major drawback: it completely hides repository visibility. Because the entire URL is secret, no one can see which repository is being configured (the owner and repo name) without having permissions to view/edit secrets. Over time, this leads to confusion and makes the application difficult to maintain. Proposed Solutions: I propose two potential solutions to improve this workflow: Solution 1: Allow Concatenation in Application Settings Allow the value of an Application Setting to be built by concatenating other settings. This would let us define the parts visibly and keep only the token secret. For example: MyPlugin_Owner (Text, Visible): my-company MyPlugin_Repo (Text, Visible): my-private-plugin MyPlugin_Token (Secret, Hidden): ghp_abc123... MyPlugin_FullUrl (Text): https:// + $extensibilitySettings.MyPlugin_Token + @github.com/ + $extensibilitySettings.MyPlugin_Owner + / + $extensibilitySettings.MyPlugin_Repo + .git The Extensibility JSON would then just reference $extensibilitySettings.MyPlugin_FullUrl. Solution 2: Create a "Git Repository" Setting Type (Ideal) This is a more platform-native solution. Introduce a new, special "Type" for Application Settings, let's call it "Git Repository". When a developer selects this type, the ODC portal would show a structured form instead of a single text box: Git Host: (e.g., github.com) Owner Name: (e.g., my-company) Repository Name: (e.g., my-private-plugin) Git Token: (This field would only accept a reference to another setting, like $extensibilitySettings.MySecretGitToken, ensuring the token is managed securely as a separate Secret). Bonus Feature: Crucially, add a "Test Connection" button next to this setting in the ODC portal. This would allow the developer to instantly verify if the credentials and URL are correct before wasting 10-15 minutes on a MABS build just to see it fail with a "Permission Denied" error. Benefits: Solution 1 adds flexibility. Solution 2 would dramatically improve the developer experience, maintain full security, and save countless hours of developer time lost to failed builds.

Hi Team, Is there a possibility to integrate automatic notification to all the consumers, in case of any upgrade in the forge components. Right now the process is manual, where one has to keep track of the updates in forge periodically and perform the relevant installation. A notification from platform in this regard, will be helpful. Thanks and Regards, Priyadharshini Sridharan

In ODC Studio it can be very helpful if we can have a checkbox for include in menu on screen so if I forgot to enable it on creating i can still add it in menu. Similar as how it is in Service Studio (O11)

In OutSystems it is not yet possible to define Android Adaptive Icons. The icon shows a white border on mobile devices. It can be improved to support adaptive icons to ensure icons are fully filled.https://developer.android.com/develop/ui/views/launch/icon_design_adaptive