Timezone management is still a headache and error-prone in OutSystems, even with the automatic conversion between client-timezone and server-timezone that Reactive Web and Mobile apps perform. Often we need to explicitly support input of date/time in multiple timezones and there's no simple way of doing it, and the non-trivial ways require extra unsupported components.

Why not update the existing DateTime data type to include the timezone?… And make the timezone part optional, so that if it's not present the platform maintains the current behaviour of converting from client-timezone to server-timezone and vice-versa.

This would simplify a lot any time-related functionality, while remaining compatible with the current implementation.