ServiceCenter allows you to config 1 set of email settings, some clients/applications may require the use of multiple email servers. Example 1 Vendor 1:  Is using application X, and they want to send emails from their own server mail.vendor1.com using their own email address service@vendor1.com Vendor 2:  Is using application X,, and they too want to send out emails from their own servers mail.vendor2.com using their own email address service@vendor2.com Example 2 eSpace application A is using email service@domainA.com eSpace application B is using email service@domainB.com Please add capability to support these scenarios.

Hello OutSystems Community, When searching for components in the Forge, one of the critical factors for many of us is the Application Object (AO) count. This is especially important for managing infrastructure costs and complexity. The Problem: Currently, the only way to determine an asset's AO count is to open its details page. This process becomes inefficient and time-consuming when you are evaluating multiple assets to find one that fits within a specific AO budget. You have to click into each asset, check the number, go back, and repeat. My Idea: I propose adding a new filter to the Forge search sidebar that allows us to specify a range for the Application Object (AO) count. This could be a simple interface with two fields: Minimum AOs Maximum AOs This would allow us to instantly narrow down the search results to only show assets that meet our specific AO requirements. For example, a developer could search for all assets that have between 1 and 10 AOs. Benefits: Saves Significant Time: Drastically speeds up the process of finding suitable components. Improves AO Management: Allows developers and architects to quickly find assets that fit within their licensing limits or technical budget. Better Decision Making: Helps in quickly assessing the potential complexity of a component before even clicking on it. I believe this would be a small but powerful enhancement to the Forge experience for the entire community. If you agree this would be useful, please vote up! Thanks for your consideration.

One common scenario in various popular REST APIs is objects with dynamic attributes, and also the way empty instances of such objects are sent. With dynamic attributes, I mean something like this: "AvailableLocales" : { "nl-NL" : "Netherlands Dutch", "pt-PT" : "Portugal Portuguese", "en-UK" : "British English" } Currently, you need an On After Response and the ardoJSON extension to interpret this. It would be better if there would be an option to turn this into a key/value pair list directly. Secondly, quite often, an empty list like the above is denoted with the empty array symbol: "AvailableLocales" : [] Even if the dynamic attributes are a closed class, and you'd manage to make all into an attribute, this results in a parsing error. Instead of an error, the Platform should recognize this as an empty array or object, and not give a parse error.

Physical table attributes are not renamed when the entity attributes are renamed, requiring manual upgrade scripts.

 Hi, My idea is to change the service studio color depending on the environment that we are connected. This is to avoid publications in quality environment. Example: dev (green), quality (yellow) and prod (red).

When creating an application with Mentor, I would like to see the effective creation of business processes (BPMs), because in tests, in the requirement document that Mentor read, it has the BPM rules but it seems that it has not yet been implemented.

 Problem: The procedure of changing themes in OutSystems is by and large a process of trial and error. Developers need to update styles and check each screen separately, which takes a lot of time. Enhancement: Introduce a live preview editor for themes that reflects changes automatically on all screens. Developers are free to change colors, fonts, and styles and they can even choose not to publishing or navigating between screens and yet see the result. Benefits: Time is saved as the user is not required to test and switch between screens constantly. The customization of themes is brought about in a quicker manner and with less effort. The look of the app is consistent throughout the entire ‍‌‍‍‌‍‌‍‍‌application.

When tagging someone in the OutSystems Forum using @, multiple people with the same display name can appear. This makes it unclear which person you are actually replying to. To improve clarity and avoid confusion, I suggest these options: Enforce unique usernames that each user can set for themselves. Display this unique username with name consistently across the forum (profile, comments, and mentions). In the mention dropdown, show both name + unique username so members can easily identify the right person. Or We can also go with an easy step, which in the forum email should be displayed with the name, and also in the mention dropdown This will make communication smoother and ensure that members always tag the correct person in forum discussions.

When using the "View or Edit Data" option on an entity, the columns' width should be allowed to be resizable.

Allow 3rd option on Entities, Actions as "Friend" which will make entities and actions visible to all modules within the Espaces Application, but not to other applications.  This will simplify having to keep entities as read-only and then creating actions to do the CRUD operations of the entity.  It will also improve security so that espaces that shouldn't be using these entities won't have visibility of them.