Enhancements
Enhanced Vehicle Quoting Experience with Manual Fallback for VIN Lookup Unavailability (BC-18005)
This release introduces a manual fallback option for situations where VIN lookup services fail or are unavailable. The quoting flow now includes a Manual Lookup button that appears conditionally, allowing users to retrieve vehicle data manually. When no VIN lookup vendor is installed but fallback is configured, the Manual Lookup button appears immediately, enabling users to enter year and cost information. When a VIN lookup vendor is installed and fallback is configured, the system attempts automatic lookup first, displaying the Manual Lookup button only if the VIN lookup fails. These enhancements ensure quoting can proceed smoothly regardless of VIN lookup vendor status, reducing disruptions and improving quoting efficiency.
Enhance API Response for getToBePrinted (BC-17950)
Enhanced the system’s response for the api/v1/printing/getToBePrinted operation by adding an optional parameter to include address field. This parameter defaults to false to maintain existing behavior, and when set to true, it includes address components in the response.
API Update - Support RevisionInvoiceNumber when retrieving documents (BC-17906)
Extended the document retrieval API to support querying by Revision Invoice Number. This change allows users to target specific invoice revisions when pulling documents, improving accuracy in scenarios involving reissued or updated billing statements.
Billing Schedule as rating Factor across all roles (BC-17565)
BriteCore has enhanced the Quoting Wizard to address billing schedule selection issues, especially for pay plans available to non-named insureds. Previously, payment plans like “Escrow Billing” were not available in the billing schedule dropdown because the system defaulted to the Named Insured, and the bill-to-whom could not be selected during the quote phase. With this update, BriteCore now retrieves all billing schedules regardless of the initial bill-to-whom selection and enforces compatibility checks.
Property Page Rounding Lat/Long (BC-18362)
Precision improvements were made to geographic data handling by ensuring that latitude and longitude values are correctly displayed with 6 decimal points. These changes provide more accurate and consistent geographic data, thereby improving the reliability of geographic-dependent operations, such as mapping, rating and risk analysis.
Add new rule effect "Generate Deliverable" in rules configuration UI (BC-18213)
The rules configuration interface in the Events module now includes a new rule effect labeled "Generate Deliverable." This feature allows administrators to dynamically select from a list of custom deliverable documents, streamlining automated document generation and reducing configuration errors through a structured user interface.
Defects
Prepared dataframes [ITEMS] does not mirror production structure (BC-18556)
Resolved an issue involving mismatches between data structures used in development and those in the production environment. The resolution ensures consistency and compatibility, significantly reducing the risk of runtime errors and improving the overall reliability of data-driven workflows.
Advanced setting ‘stp-make-detailed-note’ not working (BC-18546)
Resolved an issue in the STP workflow that caused errors or inconsistencies when creating detailed notes. With the advanced setting stp-make-detailed-note enabled, the system now generates accurate notes based on the results returned from STP rules and automatically adds them to the policy’s notes section.
DMV Virginia report failed (BC-18456)
Corrected an issue specifically impacting the generation of DMV reports for Virginia, which previously resulted in failures or incomplete reports. Following this fix, the report generation process functions correctly, ensuring regulatory compliance and accurate record keeping.
Error When Setting Future LED through Admin (BC-18348)
BriteCore has resolved an issue related to renewal effective date validation. Previously, if policies had been set up for renewal and a user tried to change the LED to an earlier date than the renewal date, the affected policies could not be renewed. With the addition of a new force flag and a detailed table that displays each affected policy details, the user can choose to renew the policies.
Attachment incorrectly showing in Declaration folder (BC-18261)
This release enhances the system’s form attachment handling to ensure that documents are accurately managed during policy renewals. The update introduces a dual validation process that cross-checks both form name details (such as form code, edition number, and description) and form identifiers to prevent duplicate attachments. It also improves performance by consolidating multiple database queries into a single, more efficient query, reducing system load without increasing memory usage. These improvements ensure that attachments are processed correctly according to configuration and prevent unexpected documents from appearing in renewal packages. The update resolves previous issues where attachments, such as certificates or privacy disclosures, were incorrectly included in renewal documents despite not being configured to do so.
Failed Ivans downloads (BC-18176)
Corrected an issue causing failures in policy document downloads through the Ivans integration. When a policy was copied then the copied policy wasn’t reported. After the correction, downloads are functioning reliably, restoring confidence in automated document delivery and significantly reducing manual intervention.