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.

More and more data is shared between teams in JSON format in addition to Excel. It would be great if we can get a new option to import/bootstrap data into entities based on a JSON format.I would expect the same functionality as the "Import New Entities from Excel..." option but then a JSON file as source.

Hi, It would be great to copy an end-user group to another stage. Since I want my role groups on DEV to be on QA and PRD, I need to manually recreate those group. It would be nice if I could copy a group to another stage to save time. In the attachments I provided a suggestion for the location of this function. I wouldn't suggest to ONLY add this feature in the Group detail page, since this will add clicks (there's an Ellipsis in the right top corner there as well).

When you search by something on Service Studio, in another modules we could have a sort on the results and/or an export of the results into excel. we could have a button to export it, as an example shown (on the left side of the buttons) on the printscreen attached to this idea

I have a idea that could be highly beneficial for active forum users. Currently, there is no option to receive email notifications for every new post in the forum. This means users must frequently refresh the forum to stay updated. To enhance engagement and responsiveness, I propose adding a new option under: 📌 Forum Settings → Content Preferences → Review My Preferences → Email Notifications Here, we already have checkboxes for various email alerts. My suggestion is to introduce a new checkbox for "Notify me of new forum posts." This will allow active users to get real-time email alerts whenever a new question is posted, enabling faster responses and reducing the need for manual checking. This small enhancement could make a big difference in improving forum activity and user experience! Screenshot's for your reference :

Hello all,When opening a Forge Component in Service Studio, can we improve the experience by having a popup/dialog with 2 options and the proper explanation of the consequences?1. Customization - Service Studio will create a clone of the Forge Component and it will remove any linkage to Forge, you will no longer receive updates and you will be responsible for the maintenance of this customization2. Maintenance/Troubleshoot  - You will be able to change and debug this Forge Component directly in Service Studio and it will continue to receive updates from Forge, any change done which is not in the updated version will be lostI think for  new developers this will avoid the pitfall of changing something and later regret of that decision, by showing a popup with the proper explanation you can have a better decisionThanks in advance,Fábio

Make the Documentation parameter (yes/no) of the exposed service customized by environment and/or require authentication.An easy way to do this is if the documentation parameter can be configured with a site property, then we can disable/enable it for each environment, or another solution would be to disable documentation in the serviceCenter.Another good feature is the possibility to define some authentication action to access this documentation.

It would be great for those who do support work to have more than only 10 environments to choose on "Switch Environment" popup.We have several clients with at least 3 environments each and it's not possible to store all of them on "Switch Environment" popup.

Most of the screenshots provided on the forge components are hard to ready because they are too small. It would be great if we could click and see a larger version of the screenshot.

An option to set idle timeout would be helpful. What I mean here is, if a user has logged in into my site/application and has not performed any activity for say 'X' minutes , then hell be logged out.