It is only possible to assign fixed-style classes to table rows, not dynamic ones, based on the row value. It would be beneficial to have the ability to add classes and events to a row based on an expression. This way, we can apply styling and events to an entire row instead of every cell, reducing duplicate code.

When creating a new application in Service Studio, I really appreciate how the platform automatically extracts the primary theme color and generates a default logo based on the uploaded application icon. This greatly helps with the initial branding setup. However, I’ve noticed that the favicon is not automatically set in the same way. It would be a great improvement if the favicon could also be auto-generated or defaulted to the uploaded application icon, just like the logo and color theme. This would ensure a more consistent visual identity for new applications right from the start, without requiring additional manual steps. Thank you for your continuous improvements and for considering this suggestion!

Recently, I noticed that any simple comment on an idea followed by dozens or even thousands of people triggers a flood of email notifications, which often turn out to be unnecessary. I believe a good solution would be to implement some kind of restriction for ideas with a large number of subscribers or even disable email notifications for already implemented ideas. Many users, like myself, may not realize this happens and end up posting messages that don’t add value to the community. An alternative could be to display a warning before posting a comment, explaining how the forum notifications work and encouraging more relevant contributions.

Premise: When projects and team dynamics become complex, people end up having to maintain reverse-engineer code, often with little or no documentation. Idea: Any action in ODC Studio would have an "AI Summarize" option. This will do an AI Analysis of the action, including analysis of all of the consumers of that action, and produce a human-readable summary of the action. Target: This could transform the 'maintainability' category of AI Mentor into a mostly automated feature.

When utilising forge components in a project, these modules can add to the project's overall technical debt, particularly in security and performance. Sometimes, modifications may be required for these modules if issues arise in these areas before they can be released to higher environments. It would be beneficial if the forge could display each component's AI Mentor Dashboard score (level of tech debt). This would assist in identifying high-quality components, especially when similar components are available. Additionally, it would incentivise component authors to improve their components.

In multiple enterprise conversations, a recurring concern I encounter is around long-term platform dependency and source code ownership. Prospective clients often ask whether, in a worst-case scenario or strategic pivot, they would have the ability to access and operationalize their application source code independently of the platform. To address this more effectively during pre-sales and architecture discussions, it would be extremely valuable to have a feature in the trial or demo environment that allows export of the application source code in a structured .NET format that can be deployed in a standard .NET setup. Having the ability to demonstrate this live would: Instantly reduce perceived vendor lock-in concerns Increase architectural confidence among CTOs and enterprise architects Accelerate decision cycles during evaluation Strengthen positioning against traditional custom development arguments In many cases, the hesitation is not about capability; it is about control and reversibility. If we can showcase that portability exists in a tangible way, it materially improves conversion confidence. This capability would significantly enhance enterprise adoption conversations.

It would be nice to have Auto-Save in Service Studio that could be turned On and Off by the user. It's very annoying  to lose work when "something" crashes...

 Description : On the Asset Moderation History page, it would be extremely helpful to have Edit and Delete buttons for user comments. Currently, if a user accidentally submits a comment multiple times, such as due to button loading delays or double-clicks, there is no way to either delete the duplicate or update the text. Use Case Example : I recently experienced this issue where, due to a slight UI lag, I unintentionally clicked the "Comment" button twice in the Add Comment PopUp. The same comment was added twice to the moderation history. Unfortunately, I wasn't able to delete the extra comment or update it with corrected or different information. This can lead to confusion or clutter in the comment history. Proposed Solution : Add Edit and Delete buttons for each comment in the Asset Moderation History list. Ensure appropriate permissions or audit trail is maintained to preserve moderation integrity. This enhancement will improve user experience and data cleanliness in moderation workflows.

We should be able to test connectivity between the environment (FE) and other endpoints using SC.In order to use this feature, we are required to install other forge components tool like "NetChecker"

Currently, joining Entities and Lists in aggregates is not possible.However, OutSystems isn't far off from being able to make this work either.Most of the major relational databases have introduced functionality to be able to join tables with unstructured data - JSON and XML are a examples.I had an issue with slow rendering times on pages which got data from integrations and had to loop through the lists to link it with the SQL database in our OutSystems environment.I noticed that there would be about 5ms latency between every Aggregate in the For Each loop which was used to build the List Structure required to render the content on screen.My workaround was to:Fetch data from the integrationJSON SerializeAssign to text input of Advanced SQLUse a CTE with OPENJSONJoin with the OutSystems {Entities}This led to me having only one interaction with the database and being able to build the List I needed much quicker.The query looked almost like this:;WITH CTE AS (    SELECT * FROM OPENJSON( @textparameter )          WITH (                Column1   NVARCHAR(100)   '$.Column1',                Column2   NVARCHAR(100)   '$.Column2'          ))SELECT {Entity}.* FROM {Entity}INNER JOIN CTE    ON {Entity}.[LocalReference] = CTE.[Column1]An unexpected, but welcome side effect was that the Database was able to join the data quicker due to query planner/optimizer spawning off multiple threads to do the heavy lifting whereas my OutSystems process was single threaded.