X

The Integration blog covers the latest in product updates, best practices, customer stories, and more.

  • October 2, 2018

Timezone functionality in OIC Schedules

Arya Sanyal
Software Development Director

Timezone is a very powerful feature while dealing with schedule integrations. Now user can create schedules in desired timezones.

Step-by-step guide

Following steps will help you to set a preferred timezone and enables you to create a schedule in the desired timezone.

1. Select Preferences by clicking on the user menu (Note this is the Preferences under OIC user menu. This is not the Oracle Cloud My Services Preferences):

 

 

 

 

 

 

2. Select Timezone and then click on Save button. Here, I selected "New York - Eastern Time (ET)" as per below snapshot:

3. While creating a schedule for Scheduled Integration, you can see "This schedule is effective:" section shows From and Until dates in selected timezone. There is also a new entry "Time zone", which displays the selected time zone.

4. Next, when you go to "Schedule and Future Runs" page after successfully creating a schedule, following new changes can be observed:

  • New field "Schedule Time Zone" displays the timezone in which schedule has been created. All runs get executed as per this time zone
  • Future runs timestamps are in the selected timezone as per the current session

Note: Even if user selects different timezone in another browser session, this page ("Schedule Time zone" ) will continue displaying timezone in which schedule has been created. All future runs will execute as per this timezone.

Let's take an example:

  • In the above screenshots, I created a schedule with New York - Eastern Time (ET).
  • Now in a new browser session, let's change the time zone from New York - Eastern Time (ET) to Los  Angeles  - Pacific Time (PT).
  • "Schedule Time zone" continues showing the timezone which was used while creating a schedule. All other dates and times displays current browser session timezone.
  • In the below screenshot, current browser session timezone is Los Angeles - Pacific Time (PT) and the schedule was created in New York - Eastern Time (ET). Future Runs displays the runs in the current session timezone - which is the exact time corresponding to the Schedule Time Zone.

 

Join the discussion

Comments ( 5 )
  • Irina Blumen Wednesday, October 3, 2018
    Nice feature.
    On the Runs page, wouldn’t it be helpful to turn the static time stamp above the list to a switcher? User could change the displayed times of future runs from the “Current Time Zone” to the “Schedule Time Zone” so he doesn’t have to do the mental calculation?
  • Arya Wednesday, October 24, 2018
    Thanks Irina!
    That's a great feedback.
  • Kumar Thursday, November 7, 2019
    Hi Arya,
    Thanks for sharing the nice feature. If i want to revert back to original settings (UTC) what steps i need to follow? I don't see any option to revert.

    Regards
    Kumar
  • Mike Harrison Wednesday, December 4, 2019
    This is what I'd like to use, but in practice it does not work. First, the timezone preference does not stick. It reverts back to UTC the next time I log in. Second, if I schedule a job to run in a non-UTC timezone, it does not schedule it to run at the correct time. It either uses the UTC time but has the right timezone (so it's scheduled to run at the wrong time) or it looks OK when I schedule it but if I go back in later it is changed. Either way the schedule is all messed up unless I use UTC for everything.
  • Sumeet Wednesday, March 4, 2020
    Hi Kuwar,
    In your use case, you need to follow these steps.
    1. Change the user preference to UTC (Refer step 1 and step 2 of the blog)
    2. Now delete the existing schedule of your scheduled integration≥
    3. Now create a new schedule for your scheduled integration. This will reflect the latest value of the user preferences timezone.

    Thanks,
    Sumeet
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.