Root release update | November 2022

What's new this month? 🚀

• Added idempotency to endpoints for creating and updating payments

  Use our new idempotency functionality to guard against accidental duplicates when using the create & update payment endpoints. Take a look at our updated API reference here.

• Improvements to sandbox mode on Dashboard

  We have improved safety in sandbox mode by preventing users from changing production data and configurations while they are in sandbox mode. This has been implemented in two ways:
  For domains that are differentiated by environment (i.e. API keys, data export runs, scheduled data exports) we now enforce the environment split on the Dashboard. This will mean that when you are in sandbox mode, you can only work with sandbox data, and when you are in live mode, you can only work with production data.
  For domains that are not differentiated by environment (communications, data stores, data export templates) we restrict access to these features if the following two conditions hold:

  • The user is in sandbox mode
  • The organisation has been enabled for live operational use
    We have also added a confirmation modal when you switch between sandbox and live mode for added safety.

• New optional policy document certificate

  We added a new optional policy document called certificate to the product module code. This document is disabled by default and can be enabled using Workbench. If enabled, the document is regenerated and sent to the policyholder on the same events as the policy schedule. Read the docs.

• Custom policy document file names

  You can now specify custom filenames for policy documents included as attachments in emails to policyholders. Handlebars can be used to dynamically include policy and policyholder data in the filename. Read the docs.

• Ability to manually trigger schedule functions

  You can now trigger a schedule function for a specific policy by making a POST request to /policies/:policy_id/scheduled-functions/:function_name/trigger. This provides additional flexibility in managing policies, and enables policy lifecycle testing via the API. Read the docs.

• New lifecycle hook: After claim decision acknowledged

  You can now add a new lifecycle hook to the product module code, afterClaimDecisionAcknowledged. This lifecycle hook is triggered whenever a claim decision (approved, repudiated, goodwill or no claim) is acknowledged by the claims supervisor, or via the API. This allows you to generate side effects from these actions, such as sending custom notifications to policyholders or claimants. Read the docs.

• New lifecycle hook: After alteration package applied

  You can now add the afterAlterationPackageApplied lifecycle hook to the product module code, which is triggered after an alteration package is applied to a policy. This function accepts the policy, policyholder and alteration_package objects as parameters, as well as the alteration_hook_key. This allows you to generate side-effects from this action, such as triggering custom notifications, updating policy data or calling external services. Read the docs.

• Additional parameters for event hooks

  We have added additional optional parameters to the following product module code functions for increased flexibility and availability of useful data when executing product module code:
  We have added the policyholder object as an optional parameter to all lifecycle hooks and scheduled functions.
  We have added the policy and policyholder objects as optional parameters to the validateAlterationPackageRequest function.

  Read the updated docs:

  • Lifecycle hooks
  • Scheduled functions
  • Alteration hooks

• Editing policyholder identification number

  You can now update the policyholder identification number on the policyholder detail view. Please note that this does not include the policyholder identification type, only the policyholder identification number.

• Update available for cell phone numbers

  We have added the ability to update users’ cell phone numbers to international numbers.

• Manual verification of external payment methods is now available

  Users that are managing policies with external payment methods can now manually verify blocked payment methods on the management dashboard.

If you have any suggestions or feedback, please share them with your customer success manager 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 💪