Root release update | June 2023

What's new this month? πŸš€

  • Retry mechanism and enhanced error messaging for SMS notifications

    Platform now checks if policy documents are ready before creating notifications, triggering an error notification if they are not ready within the retry period. Additionally, we have improved error messaging by including the notification type, facilitating the issuance of notifications with accurate document links. For more information on configuring SMS templates, please refer to our documentation.

  • Once-off policy automatic payment creation for external and debit orders

    Payments for once-off policies are now automatically created upon assigning a payment method. If the policy start date is today, the payment date will be set to the next viable billing day for timely submission. If the start date is in the future, the payment date assigned is the start date, assuming it's a viable billing day, if not, it chooses the next viable day. This functionality operates independently of billing jobs. Card payment methods continue to function as before, unaffected by these changes.

  • New handlebars helpers: round, roundup, and rounddown

    We have added three new handlebars helpers for rounding calculations. These helpers are designed to facilitate accurate rounding of mathematical operations, particularly when working with currency values. You can now leverage these helpers to ensure precise rounding in your templates. Refer to our documentation for more information on using these helpers effectively.

  • New Workbench commands

    • rp invoke: You now have the ability to issue a policy directly from your local environment using rp invoke. You can choose to create a quote (--quote) or an application (--application). By default, the policy issue flow will use the latest draft version, unless specified as live (--live). Additionally, you can view the generated quote, application, or policy package in the terminal using rp invoke --verbose.
    • rp generate --payload: This new feature leverages the joi validation schemas in the product module to generate API payloads for the quote endpoint and the application endpoint. To generate the quote payload, use the command: rp generate --payloads quote. For the application payload, use: rp generate --payloads application.
    • rp create: With this feature, you can easily create a new product module on Root and retrieve the codebase from Root into a newly created directory on your local machine. Simply run the command: rp create <api-key> <product-module-name> <product-module-key>.
    • To get started on Workbench, take a look at these docs.
  • Improvement to Embed

    • Quote splitting: Clients can now split their quote questions into two parts using the sectionIndex property in the quote schema. This feature allows for improved customisation and organisation of quote questions within the embed flow. For more information on configuring quote splitting, please refer to our documentation.
    • Allow Custom ID Types: Custom identification types are now supported on the Embed flow. In order to use this feature, the custom identification type should be passed as a prefill value.
  • Design and UX Improvements on Dashboard

    • Empty and no results redesign: We have rolled out redesigned versions of the empty and no results pages for the policy, claim, complaints, and applications views.
    • Alignment of buttons on overlays: We have adjusted the alignment of footer buttons on overlays to ensure visual consistency and improve the user experience.
    • Roles select on Add team member overlay: To enhance usability, we have replaced the radio buttons with a select component for the roles field on the β€˜Add team member’ overlay.
    • Improved design of modal for creating a new organisation: We have resolved spacing issues in the workflow and updated the informational content at the bottom of the modal into an info alert.

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