We use cookies (just for analytics) on this website. If you continue we will assume you are happy with it. ok

BeBanjo

Back to release notes

Improved time zone support

Release date: December 14th, 2018 (Revision 1), print this page

For some reason, human beings are not very good at time zone math. We live in an interconnected world, and it’s becoming frequent to have clients working across different time zones. And to make things harder, these distributed teams can each manage content in several time zones. That is time zone HELL!

With these changes - one of the biggest changes to the products we can remember here at BeBanjo - we have tried to minimise the complexity of dealing with time zones. The idea is simple: if you manage content in different time zones, or if you belong to a team far away from your company’s headquarters, life shouldn’t be harder for you.

This document describes this change in full, and, as usual, you can contact support or your Technical Account Manager for further clarification. Also, note that enabling this functionality requires some coordination with your TAM.

The change is based on the idea that a platform in Movida might have specific time zone. When it does, see that we’re now being explicit about the time zone in Movida, for example in the schedule page:

Screenshot 2019-04-03 at 16 48 47

That makes it super easy to quickly understand when the content is scheduled on each platform. Now, let’s imagine that you want to reschedule that content, but you work in a different time zone; well, it’s super easy now:

Screenshot 2019-04-03 at 16 52 44

You will always input the dates in the destination platform’s time zone, but we’ll always translate that to yours, so that it’s harder to make any mistakes. And OK, that’s great when editing one single schedule entry, but I can hear you (from CEST, at the moment 🤓) wondering about bulk scheduling content in several platforms, each with a different time zone. We’ve got you covered!

Screenshot 2019-04-03 at 16 57 04

It works by always defining the content in each platform’s time zone, so, if you used a start date of 06-04-2019 at 13:00, and you had selected platforms in PDT, JST and CEST, it would mean scheduling the content at 06-04-2019 13:00 PDT, 06-04-2019 13:00 JST and 06-04-2019 13:00 CEST.

This is not just for the schedule, but applicable to almost every part of Movida, for example with rights:

Screenshot 2019-04-03 at 17 04 35

Or even selecting a platforms; you can now find easily all the platforms in JST via a schedule page filter:

Screenshot 2019-04-03 at 17 08 12

Well, that’s enough time zones for today. If you face a problem like this today, or your company is planning to distribute content internationally in the future please contact your TAM and we’ll help you to get started with this new functionality.

CEST la vie! 🥁

References

  • movida#7651 Improved time zone support