Cronofy changelog
Cronofy changelog
www.cronofy.com

Canadian French support

 

Calendar authorization

 

Elements

 

 

Support for Canadian French fr-CA has been added to our UI Elements from v1.33.0, Real-Time Scheduling pages, and OAuth authorization flows.

Locales are detected automatically by default, and so this is already live for the pages we serve.

For those of you using UI Elements, check out the separate UI Elements changelog for any considerations when upgrading from your current version to get this support.

New date picker

 

Dashboard

 

 

We're putting a lot of work into improving our accessibility at Cronofy. You may have noticed some minor changes in how we're using color in recent times to this end.

A more noticeable change, and the first major milestone on our journey, is our new date picker which can be found helping you filter requests on your developer dashboard.

Date picker screenshot

It's built from the ground up with a primary focus on accessibility, it's a great step forward from the browser-native control we were using before.

We'll be taking what we've learned from this and applying it across our whole platform.

Bookable Events moved to beta

 

API

 

Elements

 

Beta

 

 

Bookable Events describe specific times that can be offered for scheduling. Along with having both time and duration then can also be used to track registrations for events and thus have an optional capacity to limit the number of registrations.

We've seen Bookable Events leveraged for use-cases from webinar booking to hiring assessment day management.

As part of this, Bookable Events Availability queries can now be used with our Slot Picker UI Element.


If you have any questions, or need any help, please get in touch via the Support Widget or via email to support@cronofy.com

Scheduler enhancements

 

Scheduler

 

 

We've made a few improvements to the Cronofy Scheduler over recent weeks.


Mark events as private

Out the box, the events created by the Scheduler match the default visibility of your calendar within your organization.

You can now choose for the events created by the Cronofy Scheduler to be explicitly marked as private for an extra layer of privacy.

Reminder emails

You can now opt-in to receive a reminder email before events organized via the Scheduler. These will only be sent to you as the organizer, you'll remain in complete control of the communication with your recipients.

You can choose to receive a reminder from between 5 and 60 minutes before an event is due to start.

Public links

As well as being able to send a personalized link to people, you can offer your availability to anyone via a Public Link.


All these new features can be managed via your Scheduler Preferences page.

If you have any questions, or need any help, please get in touch via the Support Widget or via email to support@cronofy.com

Developer Management

 

Dashboard

 

 

A much-requested feature has been allowing you to manage user access to your Applications in the Developer Dashboard. Well, it's here 🎉.

To do this we've introduced the concept of Organizational Units (OU) that you can invite people to. All of our existing users have been added to one of these based on their existing application access and billing relationships.

You'll see the ones you have access to in the left hand navigation. Each one is called 'xxxx Settings'.

org-unit-menu-item.d3a5d4ee6d889fe027f7ae318a9dadcecfe7d26900b514ab396adec6e2bedf34.png

At least one user, generally the creator of your primary Application, has been made the Owner of the OU. All other users have been given Developer or Support permissions according to what access they had in place.

Owners can change the permissions of existing users, including making them Owners as well. They can also invite new users to the OU with the set of permissions that they need.

We recommend that you log in and check what has been setup and confirm that it meets your requirements.

If you need any help with configuration, just let us know through the Support Widget or via email: support@cronofy.com.

More in the Application Management section of our documentation.

Conference detail templates

 

Alpha

 

 

Templating introduces the option to take control over the appearance of Conferencing details by adding templates into your event description and location description, which are rendered with the best available information.

This feature launches with two template variables:

  • {{ cronofy.conferencing.join_url }} which represents the join URL for your conference
  • {{ cronofy.conferencing.invite_block }} which represents the full dial-in details block generated by your conferencing provider.

Fallback values are used if conferencing details are not yet available. These values are localized using the new locale parameter and currently only support en (English).

An event can now be generated using this content:

{
  "event_id": "templating-001",
  "summary": "Board meeting",
  "description": "We'll be discussing the next set of milestones.\\n{{ cronofy.conferencing.invite_block }}",
  "location": {
    "description": "{{ cronofy.conferencing.join_url }}"
  },
  "start": "2021-01-31T15:30:00Z",
  "end": "2021-01-31T17:00:00Z",
  "conferencing": {
    "profile_id": "default"
  },
  "locale": "en"
}

This will be rendered into the calendar with the conferencing details, or if conferencing cannot be immediately generated (if, for example, the user's profile needs to be relinked) then they evaluate to "(Details to follow)", being updated when conferencing details are created.

You can find out more in our Templating documentation

Additional Enterprise Connect delegated authorization request errors

 

Calendar authorization

 

 

Enterprise Connect delegated authorization requests errors have been extended to report back on some additional, rare error cases.

Two additional cases are now reported:

  • When access has been granted but the initial calendar synchronization has been unable to complete, a callback will now fire to report a sync_failing error.
  • Requests which fail after multiple attempts are now reported with a request_expired error when they will no longer be retried.

Full details can be found in the Request User/Resource Access documentation.

Availability Query Sync Statuses

 

API

 

 

The latest addition to the API helps you make scheduling decisions with greater confidence.

We now support returning a summary of participants' synchronization statuses when you are making an Availability Query.

This allows you to handle cases where stale or incomplete data (caused by authorization issues or calendar provider downtime, for example) means we can't guarantee the query has been done using a completely up-to-date view of participants' calendars.

Opt-in to this by setting the new include_member_statuses flag to true on the request:

POST /v1/availability HTTP/1.1
Host: api.cronofy.com
Authorization: Bearer {API_KEY}
Content-Type: application/json; charset=utf-8

{
  ...your availability query...
  "include_member_statuses": true
}

And you'll get the new member_statuses field in the Availability Query response:

HTTP/1.1 200 OK
Content-Type: application/json; charset=utf-8

{
  ...availability query results...
  "member_statuses": [
    {
      "sub": "acc_678347111010113",
      "sync_status": "active"
    },
    {
      "sub": "acc_545665722612031",
      "sync_status": "pending"
    },
    {
      "sub": "acc_126865445645615",
      "sync_status": "disconnected"
    }
  ]
}

As a reminder, this information is already available in a more granular form by querying accounts' Profile Information, or you may handle this case by subscribing to the profile_disconnected Push Notification; However, we expect for many workflows, this single summarized view will be more convenient.

Integrated Conferencing: explicit Google Meet

 

Beta

 

 

We support many providers as part of our Conferencing Services featureset. One conferencing provider that differs from most is Google Meet. It's effectively a feature of Google Calendar itself, which has benefits (no additional authentication needed!) and drawbacks (it's not calendar agnostic). As a result, up to now, it's only been possible to get Google Meet conferencing on an event by relying on our default conferencing behaviour, which is dependent on user preferences; requesting Google Meet explicitly hasn't been possible.

We've added the concept of integrated conferencing to solve this. When creating an event, you can use this new keyword to explicitly ask for the conferencing service built into the destination calendar. Currently, we support Google Meet for Google Calendar events, but the model allows for supporting additional similar services in the future.

On calendars, we now expose a new property of calendar_integrated_conferencing_available:

{
    "calendars": [
        {
            "provider_name": "google",
            "profile_id": "pro_XpiPsafvvQBklzIg",
            "profile_name": "marty.mcfly@gmail.com",
            "calendar_id": "cal_XpiEasdgfBklzIg_ePxSn6rdfxdLHU-Q",
            "calendar_name": "marty.mcfly@gmail.com",
            "calendar_readonly": false,
            "calendar_deleted": false,
            "calendar_primary": true,
            "calendar_integrated_conferencing_available": true,
            "permission_level": "sandbox"
        }
    ]
}

When it's available, you can create events with the new conferencing profile keyword of integrated:

{
    "event_id": "ns5gua3jcb8",
    "start": "2020-11-22T12:00:00Z",
    "end": "2020-11-22T13:00:00Z",
    "summary": "Second stage interview",
    "conferencing": {
        "profile_id": "integrated"
    }
}

Read more in our Conferencing Services documentation.

Explicit Conferencing details

 

Beta

 

 

We've added the ability to explicitly set conferencing join details on events.

This expands the use cases where you can take advantage of Cronofy's and calendar providers' native understanding of conferencing. You may need to integrate with a conferencing service that we don't yet support conferencing creation for, or perhaps you have an existing integration that you wish to leverage.

This API call:

{
    "event_id": "i5ndr7orehwwyh",
    "summary": "One-to-one check-in",
    "start": "2020-07-23T09:00:00Z",
    "end": "2020-07-23T10:00:00Z",
    "tzid": "Etc/UTC",
    "conferencing": {
        "profile_id": "explicit",
        "provider_description": "Videotech virtual meeting",
        "join_url": "https://videotech.com/join-call/xyz"
    }
}

will give the following results in Google Calendar, for example:

Screenshot 2020-07-22 at 10.21.15.png

Read the Conferencing Services API documentation for more details.