Enhancements
New Show/Hide Effective Time Setting
This update introduces a new setting that allows users to control the visibility of the policy effective time on stock documents. When this setting is set to "false," the system will no longer display "12:01 am standard time" alongside the effective date on stock documents. This enhancement provides users with the flexibility to customize how effective times are presented on stock documents (BC-12063).
Expandable 'To' Field for Emailing Policy/Claim Information
Users can now conveniently navigate through the “To” field to verify the entered/selected email addresses before sending, reducing the risk of sending information to invalid or incorrect email addresses. This enhancement enhances the user experience and minimizes the potential for critical errors when emailing policy or claim information directly from BriteCore (BC-11611).
Improved Configurability on Line Item Rating Setting for Calculation Line Items
BriteCore now allows users to configure the "Line item is not rated pro-rata or by term factor" setting via the user interface (UI) for Calculation line items. Previously, this setting was automatically configured as checked for Calculation line items, even if it was disabled in the database. This resulted in a discrepancy between the UI and the actual configuration. With this enhancement now in production, users can easily configure this setting through the UI for Calculation line items, and when it is disabled, the UI accurately reflects it as unchecked. This improvement streamlines the configuration process and ensures consistency between the UI and the underlying settings (BC-11601).
Enhancing eSignature Workflow with Tagging Support for Multiple Insureds
BriteCore has enhanced our eSignature workflow for both legacy and BriteQuote V2 by introducing a tagging feature that supports multiple insured parties signing on separate lines within documents. Previously, documents expected all applicants to sign on the same lines, which posed limitations for co-applicants. Now, document preparers can add and position distinct signature tags for each insured party, clearly indicating their roles as "applicant" or "co-applicant." These tags maintain document formatting, prevent overlaps or conflicts, and accommodate additional tags for more than two insured parties. When sent for eSignature, the platform prompts each insured party to sign on their designated line, ensuring a seamless user experience while enhancing flexibility in the signing process (BC-12034).
Improved Integration with LexisNexis Credit Scoring Vendor
BriteCore has identified a need to enhance our integration with LexisNexis Credit Scoring vendor. LexisNexis now discourages the use of VPNs that rely on the "https://webxml.choicepoint.com/britecore" endpoint. To address this, we've implemented a solution to update our vendor setup to support secure internet connections, aligning with LexisNexis' preferred methods. However, for backward compatibility, BriteCore retains the option to fall back to the old endpoint if the username and password are not configured (BC-10021).
Persistent E-Signature Selection and Data Retention
A recent production change addresses a user experience issue where, during the application process, if an agent selected E-Signature as the option and pre-filled the Email Information, but then needed to go back to a prior step (e.g., to pull up Loss History or Credit Score), the information entered would be lost, and the system defaulted back to Wet Signature. With this enhancement, the E-Signature selection and the information entered now persist even when navigating back to previous steps. (BC-12046).
Defects
Payment Application Logic Update for Policies with No Revisions
Certain users reported errors when attempting manual payments on policy terms without committed revisions. Previously, when users encountered this scenario, they received an error message stating, "You must have a revision to initialize the policy accounting class. Policy Number: {policy_number}." This error hindered the payment application process. To address this, BriteCore refined the backend logic for selecting the term for payment processing. With this update, only policy terms without revisions in the "archived" state are considered. As a result, users can smoothly make manual payments without encountering the previous error message, improving their overall experience and ensuring accurate payment processing (BC-11910).
Ivans eDoc | Improved Ivans Uploader
In the process of implementing the new Ivans uploader for eDocs, two notable issues were addressed. Firstly, a row lock problem encountered during batch file uploads has been resolved to enhance system stability, minimizing the risk of timeouts. Additionally, email notifications sent to clients were adjusted to accurately reflect the queuing status of PDF file uploads, eliminating client confusion when eDocs uploads failed after receiving misleading success notifications. These changes contribute to a more reliable and transparent Ivans uploader experience for Loudoun users (BC-12107).
Prevent Data Loss in Builder for Unsubmitted Quotes
This change addresses a critical issue where the builder data was at risk of being wiped out when agents or underwriters opened an unsubmitted quote, especially during concurrent rate and save API calls. To mitigate this risk, BriteCore introduced a check that displays a message to the user, prompting them to refresh the page if any changes have been made since the builder was initially loaded. This proactive measure ensures data integrity and prevents accidental data loss, enhancing the user experience and reducing the potential for errors when working with unsubmitted quotes in the builder. (BC-11684).
Enhancing Precision in Insurance Policy Revisions
During the creation of new policy revisions, an issue regarding the accuracy of coverage limits emerged. A discrepancy was noted when comparing the newly revised coverage limits to the declarations sent to clients during policy renewals. This disparity arose from variations in how decimal numbers were handled by the system in the user interface compared to when the system initiated the renewal process. To rectify this inconsistency, a solution was implemented to ensure uniform precision in calculations. Furthermore, the system now adheres to a default rounding scheme that rounds numbers to the nearest value, significantly enhancing accuracy. These enhancements provide clients with consistent and precise coverage limits in policy revisions (BC-11969).