My idea is to have a similar mechanism that is done with Exception Handlers to REST APIs errors, this is, the ability to choose if we want to log the error or not.For example, in the OnAfterResponse of a REST API I would like to don't log the exception that occurs when condition 2 is true.This exception is logged with the module REST (Consume).

Hello,Just a small thing where sometimes when you'll create an action you'll need an input/output/local variable that is based on a structure. Instead of making a new variable and fill in the right name (where you sometimes first check the name of the (referenced) structure it would be nice to have the option to copy a structure and paste that structure as an input/output or local variable to an action.Just like this:Kind regards,Evert

As someone who always has a lot of tabs opened, it would be awesome to have the option to install the ODC Portal as a PWA.

My idea is to improve current List Navigation widget, which imho is not intuitive neither informative and takes too much valuable space for redundant or no use functionality.Why a button with (...) that has no action?Or page numbers for Prev/Next pages when we already have Previous and Next buttons?How do we know how many pages are there?How can we get back to first page? Existing List Navigation widget:My idea is to keep Previous and Next, add a First and Last Page button, highlight the current page and in between have a (...) button to enable navigation to one of those pages in between.This could apply only to lists with >= 10 pages. Up to 9 pages just buttons with page numbers would be enough.Suggestions to improve on this are welcome.

When retrieving findings from AI Mentor Studio via the API, it should be possible to obtain the findings that were snoozed, as well as the user and the date when they were modified.

Add a Ranking column and sort to this list. This would be helpful to get an overview of the team ranking and check how active they are in the OutSystems community.

In the Language Translations editor, please enable multi-select dropdown support for the Behavior filter. Currently, when searching for a word to translate, the editor also shows results already marked as Don't Translate, which adds extra effort to filter them out manually. If Service Studio allowed filtering to show only items marked as To Define and Translate, it would significantly simplify the translation process.

In many online games with ranking systems, such as League of Legends, players are grouped into tiers and divisions like Bronze, Silver, Gold, Platinum, etc. Each tier reflects a player’s experience and performance, such as how long they’ve been playing and how many wins they’ve achieved. While this is mainly a very simple UI concept, it’s actually a very cool one 😄 For example, if a user’s rank is above 50,000, they could be placed in a tier like Bronze, which can be displayed on their profile and also used as a filter when browsing members. If their rank is below 6,000, they could be Silver, and so on for the other tiers. Features like this were very motivating for me personally. They encourage users to progress for the next tier within the community, serving as a strong source of motivation alongside of course the other elements like badges and achievements. On top of that, tier-based badges could also be added, such as Bronze, Silver, Gold, and Platinum badges when a user reaches one of these tiers, to further reinforce progression and recognition.

When an input parameter is removed from an action in OutSystems, the platform should automatically remove all references and assignments of that parameter throughout the application to maintain consistency and prevent warning.

Sometimes it is necessary to use the executed sql and it would be very useful if you had some configuration to display the value of the variables.