Enhanced Billing Statement Remittance Control for Payment Card Information Display: BriteCore has introduced a new feature allowing carriers to hide the payment card form on stock billing statement remittance slips, even if they accept credit card payments. This functionality is facilitated through a setting named "hide-card-form-billing-statement." When this setting is configured as "true," the payment card form is removed from billing statement remittance slips, offering carriers the flexibility to control the visibility of this information based on their preferences (BC-11868).
Enhanced Commission Rate Flexibility for county-based strategies: This improvement aims to give carriers more flexibility in how they determine commission rates for different areas. Currently, BriteCore allows companies to set commission rates based on different factors like the type of agent or whether it's a new or renewed policy. However, some companies want even more precise control, like setting different rates for specific counties.
To address this, BriteCore made a change that lets companies set unique commission rates for certain counties. This change is useful, for example, when a company wants to give lower commission rates for areas that are more prone to disasters.
This new feature will work by adding a special option that lets companies choose different commission rates based on specific criteria. For instance, a company could decide to have a lower commission rate for policies in certain counties that they consider "high risk."
To use this feature during the setup of a new policy type, add a commission rate line item with the expected rate calculation, and then choose that specific line item from the "commission set by this policy wide mandatory calculation" dropdown menu (BC-11286).
Enhanced ISO Passport integration to include more data: BriteCore enhanced our existing integration with ISO Passport by expanding the reporting capabilities to include the retrieval of "Distance to Coast" information using the code LOCNW110. This information is now available in the response.
To make use of this new report in the rating process, BriteCore introduced the variables distanceToCoast and distanceToCoastRange that administrative users can use in evaluations for rating purposes.
Furthermore, BriteCore has integrated this data into the BriteQuote V2 rating. Clients currently utilizing BriteQuote V1 can access this feature for quoting purposes by upgrading to BriteQuote V2.
To use this feature in BriteQuote V2, follow these steps:
- In the Quote Wizard Configuration enable the setting “show-dtc-fields”.
- In the Quote Wizard, create a quote and proceed to the risk information section.
- Click on "Get Protection Class."
- Confirm that the "Distance to Coast" field is displayed.
For rating purposes, insurers can retrieve the range name from the ISO Protection Class by using the field this.property.iso_pc_data.get('distanceToCoastRangeName').
Remember, insurers can incorporate this information into their rating configuration by setting up a new line item (TS-1190).
Enhancing Performance: Streamlined Data Retrieval for Faster Functionality: BriteCore made improvements to two functions, addLineItem and addSubLine, that were running slowly when dealing with policies that had a lot of details. The issue occurred when the builder page was generating – it took longer than needed because it was processing unnecessary information for all the details, even when a user only needed specific data for the visible part of the application. To make things faster and smoother for users, BriteCore now optimized how these functions work. Instead of going through all the details, BriteCore now only fetches and processes the essential information for what's currently being shown on the screen. This change has resulted in a significant speed improvement for these functions and an overall better user experience. (BC-11503)
Location Selection and Preservation issue: A recent update (BC-10480) was implemented to improve the preservation of location data such as city, county, and country when entering Zip codes. However, this update inadvertently caused an issue where users couldn't select alternative location options upon page load, requiring them to modify and revert their Zip code entry. To address this new issue, the approach was revised to always display a dropdown of location choices upon entering a Zip code, reinstating the original behavior. Additionally, the saved location data is now included in the options list if it's not already there, ensuring that users can easily select their preferred location without compromising the accuracy of county-specific distinctions (BC-11911).
Daily Cash Receipt page not loading: A recurring issue has been identified where users encountered a "504 Error" while loading the daily cash receipts page. Although refreshing the page has sometimes worked, the error had become more frequent and less responsive to refresh attempts. The problem lied in how the system retrieved information, causing delays. To address this, a solution has been implemented to make this process faster by creating a more efficient way to find the required information. Testing has shown that this change significantly improves the page loading time. This solution ensures a smoother loading of the daily cash receipts page (BC-10247).
E-Signature Configuration Logging and Note Visibility: Previously, when making changes to e-signature configurations, there was no record of these changes, and no easy way to view general e-signature notes. To address this, now, whenever a change is made to e-signature configurations, a note is automatically generated that captures the old and new settings. This provides a clear record of configuration adjustments. Additionally, the system has been updated to categorize e-signature notes under "SETTINGS," allowing for convenient access to both e-signature and general settings notes in one place. This enhancement ensures better transparency and traceability of e-signature configuration changes, facilitating effective monitoring and management (BC-11378).
Endpoint Recovery to Support Alternative Signature Vendor Integration: Certain endpoints were removed in October 2022 due to the discontinuation of HelloSign integration. However, a client was using some of these endpoints for an external signature vendor. To address this, we have recovered two endpoints that have broader applicability beyond HelloSign, ensuring external integrations remain unaffected while maintaining system integrity and flexibility for future integrations. This change underscores our commitment to meeting client needs and optimizing system functionality (BC-11761).
eSignature completion monitoring: The change aims to ensure a seamless experience when monitoring the completion of e-signatures and the submission of quotes. Previously, a discrepancy arose when an agent signed a quote and initiated e-signature, as the system wrongly indicated all signatures were completed, potentially enabling the agent to modify the application even when awaiting the named insured's signature completion. To rectify this, we have added a new step to display has the completion pop-up, along with an additional message informing users about the ongoing submission of the quote. This enhancement offers more accurate feedback during the e-signature process, prevents inadvertent modifications, and provides Agents with transparent submission status (BC-11848).