Root release update | May 2021

What's new this month? 🚀

This sprint has been a big one with some exciting new features, building blocks and fixes being shipped! From the long awaited alteration hooks to supporting non-policyholders to pay for policies. Check out the update for the detail.

• Alteration Hooks

  You can now configure Alteration Hooks on a product module. As a recap, Alteration Hooks allow creating custom “functions” to run on a policy, like adding/removing covered people, discounting premium, changing cover amounts etc. It is more granular and customisable compared to a full requote, which requires all fields to be re-captured.

• AWS S3 destination support for data exports

  Data exports now support sending files to AWS S3 buckets, in addition to the existing SFTP and HTTPS adapters. This means that customers who use AWS have the option of using S3 as an alternative to maintaining an SFTP server, which is arguably easier and cheaper for them.
  Note: you cannot yet configure HTTPS or S3 destinations on the dashboard. The Root team has to do this internally. Dashboard support is planned for our next sprint.

• Endpoint to retrieve all claims for given policy

  A new endpoint was added to allow retrieving all claims for a given policy. The endpoint is GET /v1/insurance/policies/:policy_id/claims, and can be found in the API documentation.

• afterPolicyCancelled and afterPolicyIssued lifecycle hooks

  Two new lifecycle hooks were added to product modules: afterPolicyCancelled, which is called after a policy is cancelled and afterPolicyIssued, which is called after a policy is issued.
  These new lifecycle hooks follow the same format as all existing hooks, and also allow you to return product module actions.

• Payment method data source for data exports

  A new data source for payment method information was added to data exports, allowing users to export payment methods in bulk. This includes information around payment method status (blocked, failed verification etc.), which is useful for customer retention.

• Non-policyholder payment methods

  Customers can now indicate if the payment method on a policy belongs to someone other than the policyholder. If so, then they will be required to enter in the bank account holder’s SA ID number, which will be used in bank account verification instead of the policyholder’s details.

• Custom roles UI fixes

  A number of UI fixes and improvements were made to the custom roles tooling.

• Allow updating billing day in update_policy lifecycle action

  The update_policy product module action now supports an optional billingDay field to update the billing day of the policy.

• Cancel all pending payments when marking payment method as blocked or failed verification

  When a payment method is marked as blocked or failed verification, any pending payments for the policy will be automatically cancelled. This would previously have caused payment alerts and required manual intervention before submitting batches.

• Fix for updating billing day on application

  Previously, attempting to update the billing day on applications would throw un-related product module validation errors. This has now been resolved, and users can update billing days on application payment methods without errors.

That's it for this sprint. We'll be posting a Release Update every two weeks to summarise what has gone live and has become available across the platform.

If you have any suggestions or feedback, please share with your account manager so that we can take it into account.

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