Root release update | October 2022

What's new this month? πŸš€

  • Support for using new identification types

    We added the following identification types for policyholders and beneficiaries:

    • Cell phone
    • Email
    • Custom identifiers
      You can enable new identification types using Workbench. Additionally, you can set the default country and the name for the custom identification on a product module. Read the docs.
  • Currency formatted based on browser locale

    Numbers formatted as currency are now formatted using the locale (or language) of the browser. This will affect how the number is displayed e.g. the thousand separators and decimal. To change how the number is formatted, change your browser's language settings to the desired language.

  • Support for all currencies

    We extended the list of supported currencies defined by the ISO 4217 standard. You can set the currency saved on a policy by configuring the billing settings on the product module. The dashboard supports all currency symbols. The prefix field on currency input schema components now accepts the ISO code and will be converted to the correct currency symbol automatically. Read the docs.

  • Improved currency schema component

    You no longer have to configure the currency for the individual validators on currency components. The prefix configured on the component is now used for the validators. This simplifies the configuration required for the schema components. Add the ISO 4217 currency code into the prefix which will automatically be converted to the corresponding currency symbol for the currency component. Read the docs.

  • Extended payment datasource to include payment_method merge vars

    Merge vars for the payment_method object have been added to the communications tooling. You can now reference values in the payment_method object when triggering payment notifications. Read the docs.

  • New webhook payment_method_assigned

    A new webhook has been added that informs you when a payment method is assigned to a policy. Read the docs.

  • Account lockout

    Account lockout has been added to the dashboard authentication of user accounts. After 20 unsuccessful login attempts a user’s account will be locked. An incorrect password or 2FA will count towards an unsuccessful login attempt. The user will be notified on the login page that their account has been locked and they will receive an email. To unlock an account, users can use the reset password feature.

  • Support for updating the date of birth or gender of policyholders on the dashboard

    We extended the dashboard functionality to allow users to update the following policyholder data:

    • Date of birth
    • Gender

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 πŸ’ͺ