When developing mobile app, you can use static entitities.However they are not available if your application is running offline.Most mobile apps we develop are based on offline first principal, making usage of static entitities useless.

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

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:

I have noticed, and confirmed, that submitted Forge components in ODC Forge do not currently contribute to the community ranking. Additionally, it appears that there are no planned updates to address this issue. In my opinion, addressing this functionality is important to maintain the significance and value of both ODC and O11 when it's about the community ranking.

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.

The debate about the null values is still alive and kicking in the OutSystems community. This shouldn't be a "war" between team No Null Values and team Null Values. Null values do exist in other platforms and they can't simple be ignored. It's not the first time since I work with OutSystems that I need to differentiate between a 0 and null values. Of course there are some workarounds, but are they the best approach? I don't think so. What if we could settle this "battle" once and for all? I propose giving developers the power to decide if null values should be the default for an attribute when creating it. Attribute per attribute. There could be an extra option in the attribute property, bellow "Default value", a checkbox with the label "allow null values". Always unselected by default. Simple right? And this is a common option in other platforms. It sounds reasonable to me and may solve the "war", as everyone can have their predilect choice.

There should be a functionality in which if we add locale and select language we want to translate can automatically translate original text to translate text without filling 'Translation in' column. That is we don'n need to translate any text , it will automatically detect all texts and show the translation according to the languages provided in the outsystems. thanks..

In an app you can select the User Provider Module. But IT users are now managed in Lifetime instead of ServiceCenter. Although I understand that for legacy reasons there are still entities Entities and roles with 'SC' in their names. And for cherry on top maybe say Lifetime (IT users) for better clarity?

In the Dropdown Search component, it would be beneficial to enhance the OnChange event by allowing it to include additional attributes. Currently, OnChange only provides five default attributes from the DropdownOption structure: Value, Label, ImageUrlOrIconClass, GroupName, and Description. It would be helpful to introduce a JSON attribute where developers can pass extra information about the selected item. This enhancement would reduce the need for additional local variables and data aggregations, streamlining the retrieval of supplementary details within the component. Currently: Ideally:

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.