Enhancements
Adding Scheduled Items to STP Rules Context (BC-18392)
BriteCore has enhanced the platform to support scheduled items within the STP (Straight Through Processing) rules engine, enabling more intelligent and automated underwriting decisions. This improvement addresses specific customer needs where rules must evaluate scheduled items, such as high-value property or equipment, before allowing or stopping a quote. By incorporating these items into the rules context, BriteCore improves underwriting accuracy, reduces manual intervention, and supports faster, more efficient quoting workflows.
Automatically Generating Deliverables with New Underwriting Rules (BC-18212)
A new underwriting rule effect called “Generate Deliverable” has been added to the rules engine, allowing documents or artifacts to be automatically generated based on specific rule conditions tied to a policy or quote. This enhancement increases automation and gives insurers greater control over deliverable workflows through configurable, rules-based logic, improving efficiency and reducing manual steps in the document generation process.
Displaying ‘Watch’ Tag on Parties/Contacts in Claims (BC-18205)
A visual update was made to both the legacy and new claims UIs to display a “watch:yes” indicator on parties or contacts marked for watch status. This improvement provides better visibility into flagged individuals, allowing users to quickly identify key parties requiring special attention or review.
Enabling Pre-Bind Betterview Inspections (BC-18073)
Functionality was added to support pre-bind Betterview inspections. This enhancement enables underwriters to request and review property inspection data before a policy is bound, improving risk assessment and underwriting precision. The integration strengthens pre-bind workflows and aligns clients with broader inspection-based underwriting practices.
Adding Loss Cause Column to Claims Search Results (BC-18175)
The Claims search page has been enhanced with a new Loss Cause column, giving adjusters and claims professionals immediate visibility into the root cause of each claim directly from the search results. By surfacing this crucial information up front, the enhancement streamlines claim triage and prioritization, enabling faster, more informed decision-making.
Defects
Custom Fields Not Rendering Properly (BC-18393)
BriteCore addressed an issue where the "Input Required" pop-up window failed to display input fields when creating a deliverable that required user configuration. While the pop-up window and form were rendering, the necessary fields were not visible which prevented users from providing required input. Now all configured input fields are correctly rendered within the modal for user interaction during deliverable creation.
Secure Payment Page Payments Not Showing on Payment Log (BC-18383)
BriteCore addressed an issue where some payments made through the Secure Payment page were not appearing on the Payment Log page. This inconsistency confused users attempting to reconcile transactions. With this latest update, now all relevant payments are properly displayed in the Payment Log for accurate tracking and auditing.
Application Error When Viewing Report Status (BC-18268)
An application error was corrected that previously prevented users from viewing report status under certain customer environments. With this correction, the report status now functions correctly.
Multiple Action Buttons Missing from Admin Builder (BC-18260)
An issue was resolved where multiple action buttons were missing from the Admin Builder interface, including key buttons that are used for configuring and managing UI components. This issue was particularly impactful for administrative users who rely on these controls for customization and configuration tasks. With the update, the missing buttons are now correctly rendered, restoring full functionality to the Admin Builder.
Future Term Quote Wizard Endorsement Defaults to Wrong Type (BC-18241)
An issue was resolved where, during a future-term endorsement, if the billing schedules for the current and future terms differed, simply viewing the billing tab caused the current term's billing schedule to change to match the future term. This resulted in duplicate invoices and, for policies on auto pay, triggered drafts for backdated charges. While admin actions correctly applied changes only to the intended term, agent actions during future-term endorsements unintentionally affected both terms. This behavior has now been fixed to ensure that billing schedule changes during endorsements remain isolated to the selected term.
MIB Inspection Policy Error (BC-18202)
An issue was resolved where policies encountered MIB (Mutual Inspection Bureau) inspection errors during automated data retrieval. These errors were preventing critical inspection data from being pulled into the policy workflow, disrupting underwriting processes. The root cause was traced to a formatting mismatch in the MIB request payload, which has been corrected. With this update, MIB inspections now proceed without interruption, restoring the seamless data ingestion required for efficient risk evaluation.
Suspensions Not Applying (BC-18157)
A defect was resolved in which policy suspensions configured were not being applied as expected. This issue resulted in policies remaining active or incorrectly processed despite qualifying for suspension due to non-payment or other configured triggers. The suspension logic now activates under the correct conditions, enforcing business rules and maintaining policy lifecycle integrity.
Incorrect Deleted/Voided Dates for Reinstated Invoices (BC-18074)
BriteCore addressed an issue where some timestamps in Policy and Payment Accounting were not being accurately recorded. This led to potential inconsistencies in reports depending on when they were run. By resolving this issue in this latest release, the data is now properly recorded, ensuring historical accuracy and consistency across all relevant reports.
Display Issue in Policy Summary Screen - Agency Appears as Undefined (BC-17878)
BriteCore addressed an issue where the agency field in the policy summary screen was showing “undefined” instead of the correct agency name. This happened because the system wasn’t properly connecting the data to the display. The agency name now appears correctly, making the summary screen clearer and more accurate.