At this point of time it is not possible to select multiple resource file during import.

Create a Built-in Function Switch, under the Miscellaneous tab. It makes it easier for developers to understand the intended behavior than having several if's chained. It may cause fewer errors, since it is not necessary to check the same variable/condition several times.

Inconvenience:If a user is having multiple accounts, they can very well able to link their primary account with their secondary accounts, but their community ranking doesn't get linked. because of this the ranking gets disturbed.Idea:In order to maintain proper ranking, Outsystems can provide an option called "Merge Ranks". By using this, the rank of the primary account will get reflected in all the linked accounts. So that, the secondary accounts won't disturb the ranking order. If user is not interested in merging their ranks, then they won't opt for it.

Currently, if we define a Sorting by an attribute, that sorting becomes unresponsive after introducing a Group By in the aggregate, as the sorted attribute is no longer part of the aggregate output . This does not raise any errors or warnings in the TrueChange Tab or any signaling in the workspace. I find that this is an easily overlooked situation that can lead to unexpected behavior or inconsistent results. I suggest the implementation of a typical Outsystems background validation that triggers a warning (written on the TrueChange Tab and a visual cue on the aggregate) whenever the aggregate's sorting references attributes that are not part of the aggregate output after a Group By, ensuring consistency and preventing silent issues.

While using some tools like IcoMoon to extend the icon collection to fit more with my project theme, I face an issue with dual color icons. I am talking about the icons that is defacto mono color, but some paths has opacity, to apply shadow or set background color for example. This icons inherit a single color form its parent, or by applied color using classes, like normal icons. Some icons may be rendered with many paths. If the icon need 1 or 2 paths, it can be applied with pseudo elements, "::before" and "::after". Icon: delete-01 Icon: delete-02 However, if it need more than 2 paths, then OutSystems' icon widget cannot be used. Instead I uses "HTML Element" and add "span" elements in it. Icon: delete-03 So it would be easier if the Icon widget detects the number of needed paths by it self, or has a lot of paths appended in it to support a wider range of icons in it.

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.

Sometimes I want to pass only a small feature from one environment to another and when I merge them I have like 20 different devs with a check box to unselect. If there was an option "Select All" on each side, i could easily take all out and select the only one I want to merge. Ex:

Like ListClear action there should be one for records. With just one action and just passing the record name as argument it could set the record attributes to the default values. This would be easier, faster and much cleaner than setting all attributes one by one or assigning the record to a blank one.

When I have a block containing a pop up, that pop up will be collapsed in instances of that block. When I have a placeholder inside that pop up, and I need to add a significant amount of design inside that placeholder, using the widget tree only gets very tedious. Therefor I would like to be able to display the content of the block, or at least the placeholders.

A propose a public bug tracker for issues in the OutSystems platform. I understand why OutSystems would be reluctant to do this but here's some advantages: Transparency : a public bug tracker shows commitment to transparency and accountability, building trust with the community and customers. Community Collaboration : it allows users to report bugs, suggest fixes, and contribute to the platform's development. Improved Communication: users get visibility into the status of reported bugs, avoiding redundant reports. Prioritization by Demand : users can vote on issues they care about most, helping OutSystems prioritize fixes based on real-world demand. Knowledge Sharing : a public bug tracker serves as a centralized knowledge base where users can search for known issues and workarounds. ( Disclaimer: an LLM did help me write some of this ) The motivation of this idea comes from the time wasted recently creating support cases for problems that were already identified by the OutSystems team. Many of these problems have forum posts with dead ends, where people were left without an answer. I would imagine this would also free up time from the support team. Cheers, Tiago