<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
0D54z00009BwO5NCAVOkta Identity EngineWorkflowsAnswered2024-04-16T11:29:31.000Z2023-05-16T22:04:19.000Z2023-05-18T03:39:16.000Z

gpyyl (gpyyl) asked a question.

Date Now Card not in local time

Hi Team,

 

I have a flow that didn't work as expected because Date Now gave me UTC time (which I now see is the only value this card returns)

 

My main issue is the inconsistency between the datetimes within workflows - i.e. This was in a scheduled flow that runs at the local time I've specified but Date Now returns UTC. This feels like bad UX.

 

Image is not available

 

Suggested Solution: Allow a timezone selection on the Date Now card


  • TimL.58332 (Workflows)

    @gpyyl (gpyyl)​  - Our Engineering teams are definitely open to suggestions for improvements to the product. We maintain (and recently updated) the https://ideas.okta.com site as a tool for customers to provide ideas/changes they would like to see in Okta. These ideas are reviewed by the PM/Dev teams and many of them over the years have made it into a variety of our offerings.

    Expand Post
    Selected as Best
  • TimL.58332 (Workflows)

    Hello,

     

    UTC (and specifically ISO 8601) is the standard for date/time outputs for any mature application. Operating systems and some applications allow you to set your preferred date/time display and it converts this to the selected time on the fly.

     

    Workflows also has the ability to convert date/time into different formats or timezones.

     

    Here is a quick Example: (Note the conversion on the "Custom" output)

     

    image 

    You can find a full list of Time Zones (TZ) here:

    https://en.wikipedia.org/wiki/List_of_tz_database_time_zones

     

    Expand Post
  • gpyyl (gpyyl)

    Hi @TimL.58332 (Workflows)​ 

     

    Thanks for your response. I understand the complexity of working with Datetime in web systems so my issue is less that Date Now returns UTC time but the inconsistency between Datetimes within workflows - e.g. I scheduled the Flow using the my local timezone in the schedule but Date Now is UTC (perhaps this card could check the timezone set on the schedule -if there is one).

     

    I was also thrown by the inconsistency with standard Javascript Date.now() (which I understand is probably not exactly what these cards use - but there's a lot of similarities). The return value of new Date(Date.now()) being based on your browser's location/timezone - which is irrelevant here as the flow is running on a cloud server in one of the OKTA cells.

     

    I have resolved this issue by using a Date Add card to adjust for our timezone (we never have DST).

     

    All of this is just to say, I feel that the ability to select a timezone on the Date Now card would be a useful addition.

    Expand Post
  • TimL.58332 (Workflows)

    @gpyyl (gpyyl)​  - Our Engineering teams are definitely open to suggestions for improvements to the product. We maintain (and recently updated) the https://ideas.okta.com site as a tool for customers to provide ideas/changes they would like to see in Okta. These ideas are reviewed by the PM/Dev teams and many of them over the years have made it into a variety of our offerings.

    Selected as Best
  • gpyyl (gpyyl)

    Thanks for that @TimL.58332 (Workflows)​! I was going to ask if there was some channel for this. I'll submit this.

     

    I appreciate your time and responses 🙂

This question is closed.
Loading
Date Now Card not in local time