Root release update | March 2023

What's new this month? 🚀

• Root Data Adapter

  We are proud to announce the launch of our latest data tool, the Root Data Adapter. It gives you flexible, unrestricted and easy access to all of your data on Root through a SQL interface provided through AWS Athena. Integrate it with your favourite Business Intelligence tools, such as PowerBI, Qlik or Tableau, to leverage data insights that help you stay competitive and thrive in the market.
  Are you ready to set up the Data Adapter for your organisation? Take a look at our guides.

• Updates to Dates and Timezones

  • Ability to set your organisation and user timezone: Previously, dates on the dashboard have been displayed based on your computer's timezone. Going forward, dates are displayed based on the timezone configured in your User or Organisation settings, with the former taking precedence.
  • How this impacts the Root Platform: Our platform has always assumed "UTC" as the timezone for date conversions, unless the timezone offset is explicitly included in the date input. Going forward, your organisation’s timezone will impact how dates are converted on the Root platform including the API, scheduled jobs and data imports.
  • How changing your organisation’s timezone impacts date inputs: Changing the timezone of your organisation will change the timezone used to convert date inputs. For instance, if you change your organisation timezone from "UTC" to "Africa/Johannesburg" (UTC+2) you will experience the following:
    • API request body:
      { "start_date": "2022-12-15" }
    • API response body
      "UTC" timezone (before change): { "start_date": "2022-12-15T00:00:00Z" }
      "Africa/Johannesburg" timezone (after change): { "start_date": "2022-12-14T22:00:00Z" }
      Please refer to this guide to learn more about timezones.

• Updates to Embed | Sales

  • Custom starting step: You now change the sequence of the Embed |Sales flow by selecting either quote or personal details as the starting step for the flow. Read the docs.
  • Company policyholders: Before, a company could only be designated as the policyholder if the policy scheme type was set to group. However, we have now added the capability to assign a company as the policyholder when the scheme type is individual. This means that, for both group and individual policies, you can now choose to assign either an individual or a company as the policyholder on the policyholder step.
    For more information about Embed, click here.

• Improvements to product module definition defaults

  • We have moved defaults for unit test code files and policy document templates from the Workbench CLI tool to the platform. This ensures that the creation of defaults does not result in unnecessary diff messages, and simplifies the CLI tool codebase.
  • We have created new defaults for Embed markdown files and policy document config, allowing you to adapt defaults rather than building from scratch.
  • Take a look at the Product Module guides for more information.

• New webhook: Policy expired

  We’ve added the new webhook policy_expired, which will fire when a policy has expired.
  See our updated documentation on the webhook objectand webhooks overview for more information.

If you have any suggestions or feedback, please share them with your Project Lead or submit them via the Root product roadmap so that we can take them into account.

Let's build this awesome new future of insurance together 💪