The AI Mentor Studio is already very powerful but we always look for new ways to make it even more helpful. Here are some suggestions of improvement: 1. New Filter for Changed Elements When applying a filter to show alerts analyzed within the past two weeks, we sometimes still see alerts for elements that haven’t been modified in years. While older alerts are important, they should be reviewed in different contexts. A filter that displays only elements that have been actively changed within the selected timeframe would improve efficiency. 2. New "Brainstorming" State Some alerts involve complex issues where immediate fixes could pose risks. While the "Remind Me Later" status helps, some alerts need to be reconsidered at a later stage in the project without requiring monthly snoozing. Introducing a "Brainstorming" state would provide a clearer distinction for alerts that require further discussion before resolution. 3. New Filter for Unassigned Alerts Currently, users can filter alerts assigned to specific users, but there is no direct way to view alerts that have not been assigned to anyone. While exporting alerts to Excel allows for this, having an in-app filter to display unassigned alerts would be much more convenient and efficient. Hopefully these suggestions will be taken into consideration :) Cheers, Vanessa Espírito Santo

OutSystems now supports storing settings as secrets in both OutSystems 11 (Site Properties as Secrets) and OutSystems ODC. However, secrets often have an expiration date, and without proper tracking, they can expire unnoticed, causing disruptions. Proposed ideas : Optional Expiration Date for Secrets – Allow users to set an expiration date for secrets stored in Site Properties (OutSystems 11) and Secrets (OutSystems ODC). Reminder Notifications – Enable reminders to be sent before expiration to a specified role so they can take action. This feature would help OutSystems 11 / ODC users proactively manage secrets and avoid unexpected failures due to expired credentials.

It would be great if I could expand an assignment to some structure like is already possible for parameters of an action.

A module in Service Studio will register a "change" when viewing data from an entity in some contexts, requiring the developer to either re-publish or to click "Don't Save" when closing the module: If a developer is only viewing data, no changes have really been made, right? I would prefer not to have to click this "Don't Save" button. Below are the different contexts I tested and whether a "change" occurred as a result. Option 1: "View Data" on a static entity on element defined in the module Result: no "change" Option 2: "View or Edit Data" on a regular entity on element defined in the module Result: no "change" Option 3: "View Data" on a static entity that is being consumed from another module Result: a "change" occurs Option 4: "View Data" on a regular entity that is being consumed from another module Result: a "change" occurs

Builtin round function should enable one to indicate the round precision: Round(number, precision) where: Number is the value to round Precision: number of decimal places after round (if positive), number of position to the left side of the decimal separator where to round (if negative).

Rank the badges on the certificates, instead of just showing them by date. Put the expert/Professional badges at the top, making them bigger, possible with a line under that section, and don't show the lower "Associate" certifications that they supersede, or put them smaller at the bottom: (They are only at the bottom in this example because I passed them first.) Thus:

Add a small icon decoration so that on the espace tree we can differentiate which actions are public on an espace. While you're at it do it also for the ones that are functions...

The ODC REST APIs do not currently seem to expose webhook events for the resources that are exposed. It would help automation scenarios and use cases for OutSystems to expose the ability to create a webhook subscription for certain events. There are likely many use cases here but some examples: Webhook events for user events: User creation User updated User deleted Webhooks for build events: Build started Build completed Webhooks for deployment events: Deployment started Deployment completed Publish started Published completed

My idea is to keeping the existing behavior but with the possibility to turn off automatic fetching data.Suggestion: Button like Test button (advanced queries) inside the aggregator to be able to disconnect or connect to the server.

As of now OutSystems Community profile score is based on user participation in forums, training, sharing ideas and forge. I know many leaders who are contributing for Community Growth via usergroups. Also many users actively participating in usergroup session. If we allocate some points for usergroup activities (organizer, speaker, quiz winner, participant ) it will be great. Just a wish 🙂