Process Node Scheduling

RE: Process Node Scheduling

sanchitg0002 — Fri, 31 Mar 2023 16:57:08 GMT

Glad to know that.🙂

RE: Process Node Scheduling

GauravSingh — Fri, 31 Mar 2023 16:38:53 GMT

Thankyou Sanchit, that's what i was looking for. 🙂

RE: Process Node Scheduling

sanchitg0002 — Fri, 31 Mar 2023 06:14:50 GMT

Thanks for the detailed explanation.

What I can understand is that you want to convert the date time input provided by the user according to the site primary timezone if the user input timezone do not matches with site timezone otherwise you keep it as is.

a!localVariables(
  local!now: now(),
  local!split: split(ri!inputTime, ":"),
  local!day: day(ri!inputDate),
  local!month: month(ri!inputDate),
  local!year: year(ri!inputDate),
  local!inputDateTime: gmt(
    datetime(
      local!year,
      local!month,
      local!day,
      local!split[1],
      local!split[2],
      local!split[3]
    )
  ),
  local!siteTimezone: usertimezone(loggedInUser()),
  local!actualUserTime: if(
    local!siteTimezone = ri!inputTimezone,
    local!inputDateTime,
    local(
      gmt(local!inputDateTime, ri!inputTimezone)
    )
  ),
  if(
    local!actualUserTime < local!now,
    local!now,
    local!actualUserTime
  )
)

Explanation of the code:

So, datetime() adds timezone offset of the server to any value provided, first we need to revert it back (using gmt() ). And then check if the timezone of site matches with the user input timezone, if it does then you just compare it with now(), otherwise first we need to remove the timezone offset provided by the user so that we can have datetime in UTC (using gmt() ) and then add the timezone offset of server to get the final datetime (using local() ) to compare with now().

Hope it solves your problem. I have tested it with some values, you can try and let know if it works the way you want it or not.

RE: Process Node Scheduling

GauravSingh — Thu, 30 Mar 2023 22:08:31 GMT

Hi Sanchit,

Case 1:

Lets say user enter date as 01/31/2023 time as "00:00:00" and timezone as IST

and users timezone is in IST and current datetime is 01/31/2023 03:30 AM +GMT 5:30

Since time that user has entered is in past Expression must return the current time i.e 01/31/2023 03:30 AM +GMT 5:30

Case2:

User enters date as 01/31/2023 time as "00:00:00" and timezone as GMT,

and users timezone is in IST and current datetime is 01/31/2023 03:30 AM +GMT 5:30

Since time that user has entered is in future as 01/31/2023 00:00 GMT will be 01/31/2023 05:30 AM +GMT 5:30

Expression must return the time i.e 01/31/2023 05:30 AM +GMT 5:30

Case 3:

User enters date as 01/30/2023 time as "21:30:00" and timezone as GMT,

and users timezone is in IST and current datetime is 01/31/2023 03:30 AM +GMT 5:30

Since time that user has entered is in past as 01/30/2023 21:30 GMT will be 01/31/2023 03:00 AM +GMT 5:30

expression must return the time i.e 01/31/2023 03:00 AM +GMT 5:30

RE: Process Node Scheduling

sanchitg0002 — Thu, 30 Mar 2023 10:45:53 GMT

How exactly do you want it to be converted? Can you tell us with an example?

RE: Process Node Scheduling

GauravSingh — Thu, 30 Mar 2023 10:38:09 GMT

Hi Harshit,

Yes, I'm doing the same the only challenge is that values is not getting converted properly.

I want this date/time/timezone to be converted properly which is not happening for now.

RE: Process Node Scheduling

Harshit Bumb (Appyzie) — Thu, 30 Mar 2023 05:23:48 GMT

My bad. I just realized that you must be doing the same but you're not able to construct the value to pass in.

RE: Process Node Scheduling

Harshit Bumb (Appyzie) — Thu, 30 Mar 2023 05:09:35 GMT

Why don't you just construct a date time with a timezone value and pass it in this configuration?