Hello Faris.

You mean on the Cloud? That is standard.

In the OutSystems Cloud all servers are set to work in the UTC time zone. This configuration cannot be changed.

https://success.outsystems.com/Support/Enterprise_Customers/Maintenance_and_Operations/OutSystems_Cloud_and_time_zones

There are some pretty good workarounds,

https://www.outsystems.com/forge/component-overview/500/time-zone

Hi Faris,

The TimeZone component contains a sample page that demonstrates the time conversions. You can look into the logic to see how it is done.

Regards,

Nordin

The component includes an example and has all the actions you need.

You just have to convert between UTC and AST.

Hi Faris,

The TimeZone extension is already added as a dependency in your module. You just need to click on the little arrow on the left for the actions to show up.

Regards,

Nordin

You have to:

Use the ConvertfromUTC function every time you wish to show a date to the user.

To do this I would create a block that converts input datetime.

Use the ConvertToUTC function every time you wish to save a user input date to the database.

To do this, configure your Create/Update actions to do the conversion and always use them instead of the default ones.

My first link has a lot of good resources.

Hello.

Sorry for the delay. I made a small example of the block in Reactive you can look at.

Hi Faris Abdullah Almozini,

If your objective is to add +3 hours to the value obtained from CurrTime() function, you can achieve it by using the in-built AddHours() functions as mentioned below

Code Snippet

AddHours(CurrTime(), 3)

Note: AddHours() returns DateTime value so if you want to display only the incremented Time value you can wrap the AddHours() within the DateTimeToTime() function for value conversion as mentioned below

Code Snippet 

DateTimeToTime(AddHours(CurrTime(), 3))

See the sample app: DemoApp_UTC+3Hr

Hope this helps you!

Regards,

Benjith Sam

Faris

The idea is that you look at the logic and implement the way you need it.

Regarding the "going but to UTC", it should only recalculate if parameters changed. Are you sending new parameters?

Benjith, this is not a simple "add x hours" issue. This is a "different time zone" issue. The difference can change over the year. because of Daylight Saving Time.

Even if it would fix Faris issue, it could be misleading to others looking for the same.

Faris Abdullah Almozini wrote:

 Hello Friend,

You can try put in Assign this command to your variable: AddHours(CurrDateTime(),-3)

Hi Faris Abdullah Almozini and Tom,

@Tom, Your suggestion is similar to what Benjith suggested above (and the correct is, like he mentions, to add +3h, since Faros' timezone is UTC+3), you may want to check Nuno's thoughts on the downside to do it that way, they are spot on.

@Faris Abdullah Almozini, are you still facing this issue after 2.5 months??

Since you seem to be creating a Mobile app (the same applies to Reactive apps btw), you shouldn't have to worry about timezones when using CurrTime() or CurrDateTime() at all:

• on Client actions and Screens, Time and DateTime data types always represent time in the device's timezone
• on Server actions, Time and DateTime data types will always represent time in the server's timezone
• when a Time or a DateTime value is passed from Client to Server (or from Server to Client), OutSystems will automatically do the right conversion.

The Timezone component is useful when, in your Server actions, you want to perform calculations with Time and DateTime values from multiple timezones (Nuno's info is quite complete, if this is what you need, just read it and see how the sample page was implemented on the Timezone component itself)

Hope this makes things clearer!