When using the OfflineDataSync it's currently not possible to add an Input to the TriggerDataSync action. For cases, where you only want to synchronize data for specific record (e.g. an Order with it's orderlines) you cannot send the OrderId along with the TriggerDataSync. I always need to use a work-around in my OfflineDataSync switch by doing something like: A: Substr(SyncUnit,0,11) = "UpdateOrder" and in the client-action: IntegerToIdentifier(TextToInteger((Substr(SyncUnit,11,100)))) in the TriggerOfflineSync I then enter this in the SyncUnit: "UpdateOrder" + OrderId B: use JSON (de)serialize logic as SyncUnit variable. It would be way easier if it's possible to add the custom input parameters (e.g. OrderId) to the TriggerSyncAction and use it directly in my OfflineDataSync.

It would be great to have OutSystems Developer School and bootcamps in south america time zone, too, it would be easier to learn in the morning

In ODC, account creation and recover password already support 2FA. Introduce a 2FA state between credential validation and session creation, exposed through CreateAuthenticationChallenge() and CompleteLogin() APIs. CreateAuthenticationChallenge( Username, Password ) Returns OTP CompleteLogin( Username, Password, ChallengeToken ) This would allow support for several 2FA flows with the built-in IdP.

Add to Entities the Default Value Behavior property similar to what already exists to external databases ( Entity Properties - OutSystems ) so that the default values can be stored as null values in the database when needed.This will prevent developer the need to create their own CRUD SQL queries and use the actions provided by OutSystems when they want to persist NULL value in the database.

Build a Service Studio version to run on cloud so anyone can use it and access it by browser. This way there is no need to have a version for every platform.

90% of the times I use the 'ListIndexOf' function I follow it up with some variation of: MyVar = MyList[ListIndexOf.Position].val It would be helpful if there was a 'ListFind' function (client and server) that returns the element in that position, and not only the index.

Cyclic References need to be True Change warnings.J.Ja

The HTML Element widget is, from what I can tell, limited to a set of tags that OutSystems defined. As new HTML tags are created, and with the surge of technologies like Web Components (that use custom HTML tags), this becomes a limitation and we have to implement workarounds to make a simple thing work. Can this rule be relaxed or even completely removed?

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...

OutSystems displays the table widget in tablet and phone devices as a stack of rows. Each row is shown as a card appended above each other. It would look better if it is displayed as cards, like in a gallery. To achieve this I had to use CSS to change each row style to appear as a gallery of cards. If implemented, it would save much to be done by frontend developers, and add to the UX design of OutSystems. I think it should be a configuration in the table widget, with other options for the display mode, and customizable number of columns for a gallery view mode.