Genesys Cloud - Developer Community!

 View Only

Sign Up

  • 1.  Permanent Daylight Savings Time Change

    Posted 7 days ago

    If the US is to implement the proposed change to permanent Daylight Savings Time, what - if anything - will need to be done as far as schedules to account for the change or will Genesys handle this in the background?


    #Architect

    ------------------------------
    Jared Pavlecic
    ------------------------------


  • 2.  RE: Permanent Daylight Savings Time Change

    Posted yesterday

    That's a good question, I would think it should be handled automatically for the most part. Here are some items that come to mind that may be something to consider, it will be interesting if and when we get there, so great looking ahead.

    What you should verify

    1. Schedules use named time zones

      • Good: America/Chicago
      • Bad: fixed UTC offsets such as UTC-6

    2. Data Actions / Integrations

      • If you have custom APIs, Power Automate flows, Azure functions, reports, or scripts that assume DST starts in March and ends in November, those may need review.

    3. Outbound Campaign Scheduling

      • Campaign start/end times tied to local time zones should adjust automatically if the underlying time zone rules change.
      • If you have logic that converts times manually, review it.

    4. Workforce Management

      • Forecasts, schedules, and adherence processes using local time zones should generally continue to function, but any custom reporting built around DST transitions should be tested.


    ------------------------------
    Luke Murphy
    Genesys Cloud Developer
    CCS Medical
    ------------------------------



  • 3.  RE: Permanent Daylight Savings Time Change

    Posted yesterday

    Hi Jared,

    From my understanding, if the change is ultimately enacted, I would expect Genesys Cloud to handle it through updates to the underlying time zone definitions rather than customers having to manually adjust every schedule. Genesys Cloud uses time zones (rather than fixed UTC offsets) for schedules, so when governments change DST rules, platforms typically adopt the updated time zone data. That said, I'd still recommend validating any business-critical schedules, Architect flows, WEM schedules, and integrations after such a change



    ------------------------------
    Phaneendra
    Technical Solutions Consultant
    ------------------------------



  • 4.  RE: Permanent Daylight Savings Time Change

    Posted 19 hours ago

    Hi,

    One area I'd probably test after any timezone rule change is historical and scheduled reporting.
    The platform may handle the timezone updates automatically, but it's always worth validating reports that span the transition period to make sure the data is presented as expected.

    thanks


    ------------------------------
    Ashiesh Sharma
    GCX- GCP, ARC, SCR, QM
    Producer | Conductor | Composer
    BT plc
    ------------------------------



Related Content