Enhancements
Introducing Stateless Quoting (BC-18344)
Stateless Quoting in BriteCore allows carriers to generate new quote prices instantly by leveraging data from an existing policy without saving the quote until they’re ready. It speeds up quoting by preloading default coverages and risk details through Policy Type Templates, automatically applying billing schedules, and copying key information—such as contacts, properties, and prior coverages—from the underlying policy to reduce manual entry. Users can create quotes directly from the rating page or during quote setup, navigate freely across tabs, and resume exactly where they left off. Administrators can configure underlying policy relationships and define reusable templates to ensure consistent, efficient, and standardized quoting workflows across all policy types.
Displaying expanded past claim data in New Claims UI (BC-20517)
The Past Claims section in the updated Claims UI has been enhanced to include essential data for every prior claim, such as loss date, incurred amount, claim status, and loss type, alongside the claim number. This update brings the interface in line with legacy UI standards, presenting all vital information at a glance to help adjusters quickly assess claim history.
Enabled multi-select and bulk actions on claims files (BC-20500)
A multi-file selection and bulk action capability has been added to the new Claims Attachments module, greatly improving operations during complex claims handling. Users can now select multiple files using checkboxes, including a "Select All" option, and apply bulk actions such as moving files, marking privacy status, updating print state, or deletion, all in one step.
SQL Editor - Added audit capabilities (BC-20475)
A new audit log capability was introduced to the SQL Editor, supporting compliance requirements such as SOX. This enhancement tracks every change made in custom reports, logging the author, timestamp, action, and detailed differences between previous and current queries. The solution builds upon existing version control features for stock reports and extends audit transparency to all custom user-generated reports. By enabling granular tracking of report changes, the update provides improved accountability and easier compliance verification for administrators and users.
SQL Editor - Support customization of column formatting for Excel reports (BC-20389)
The release introduced improved handling of distinct formats, such as currency, phone numbers, ZIP codes, percentages, dates, times, durations, booleans, hyperlinks and, emails. Currency values now elegantly display negatives with a leading minus, while integer values preserve leading zeros for phone and ZIP codes regardless of data source. The changes facilitate enhanced data clarity, reporting integrity, and user flexibility in tailoring reports for financial users and analysts.
SQL Editor - Support custom parameters (BC-20167)
Enhancements to the SQL Editor introduced simplified custom parameter support for SQL Editor reports. The UI now specifically highlights parameter inputs for relevant reports. These changes collectively help users define custom filters and conditions for their reports while decreasing overall complexity and operational burden.
Task definitions | Task definitions UI (BC-20058)
A comprehensive management UI for task definitions was introduced within the system settings, making it possible for customers to create, update, and delete task types without API or direct database access. These changes empower users to configure workflow task types more intuitively and efficiently, providing greater control over operational processes.
STP - Support access to rate per inputs (BC-19708)
A new capability was added to facilitate access to Rate Per user inputs within the Straight Through Processing (STP) context. A variable for user input values was introduced, enabling advanced STP rules that require these parameters when evaluating automated quote and rating scenarios.
STP - Notifying that loss history was run (BC-19675)
Error handling was implemented in STP rules to address failures and exceptions in the integration with LexisNexis CLUE/ISO loss history checks. If a trigger to the vendor service fails, the system now notifies the agent that CLUE was unable to run, automatically routes the submission to underwriting, and records the incident for audit purposes. This ensures agents are properly alerted to transaction failures, improving compliance and reducing the risk of overlooked errors in automated workflows.
User experience improvement - automatic policy commitment and issuance when e-sign status is pending and/or completed (BC-20148)
Policy issuance was streamlined for situations where the eSign process is completed and straight-through processing (STP) is approved. Rather than requiring manual intervention by the agent, the system now automatically commits and issues the policy upon successful electronic signature completion and STP approval. This automation reduces application-processing delays, minimizes manual workload, and enhances operational efficiency for all users engaged in policy management.
Defects
Ability to select between multiple applicable catastrophes during claim creation (BC-18925)
Claim creation now supports selecting from multiple active catastrophes when the Date of Loss overlaps more than one event. Previously, with automatic CAT assignment enabled, the system applied only the first matching event, leading to incorrect associations and extra cleanup for agents. The new update prompts users to choose from all applicable catastrophes, improving accuracy, reporting, and efficiency—especially in complex loss scenarios.
Return premium check not generating (BC-20627)
BriteCore addressed an issue with the return premium check generation for some canceled and rewritten policies. With the modification in place, refund checks for canceled and rewritten policies are generated as expected and unblock impacted users.
OFAC certificate error when requesting Financial Antiterrorism Cross-Reference (BC-20625)
BriteCore addressed an issue where a certificate verification error blocked users from running the Financial Anti-Terrorism Cross-Reference report. The root cause was incompatibility between recent code changes and some older libraries, and the issue has now been fixed.
Application Questions performance issue (BC-20604)
BriteCore addressed a performance degradation issue in the application questions section of the quoting wizard. User experience is now improved, with faster UI operations and reduced system strain.
Application questions notes not being generated (BC-20587)
A critical issue was addressed where notes documenting changes to Application Questions were not being generated, which led to gaps in the audit trail and traceability. This resolution restores full visibility into question change history, which is vital for audits and troubleshooting.
Setting to hide "Agency Sweep" options from the UI for agents (BC-20556)
A UI defect was addressed by introducing a setting to control the visibility of the "Agency Sweep" payment option for agents. This change prevents unintended access and confusion among agents whose workflows do not require sweep functionality, adhering to organizational preferences. The logic now checks for agent-related payment permissions before displaying the option, avoiding navigation errors and ensuring only intended payment pathways are visible. This refinement improves agent experience and reduces support burden from misdirected usage.
Task Assignee dropdown not populating on first load & remove background card overlap in Tasks Detailed View (BC-20538)
An interface issue in the Tasks Workbench was corrected where the Assignee dropdown failed to populate on the initial task load and a background card appeared behind the task detail panel, compromising visual clarity. The fix ensures the dropdown is properly populated when a user first opens a task, and the UI layering is now consistent and visually clean.
JPEG upload fails in new Claims Attachments page (BC-20535)
A defect preventing JPEG image uploads in the new Claims UI Attachments page was resolved, eliminating workflow blockages for adjusters who needed to upload photo documentation. The failure stemmed from an older virus scanning integration and legacy configuration, which was subsequently removed and redesigned. After this update, JPEG and other accepted file formats now upload successfully, error handling is improved, and claims documentation can proceed promptly without reverting to the old UI.
Changes to loss causes are not reflected in the Claims list page (BC-20497)
Updates to loss causes within individual claims were not visible on the Claims list page due to incomplete synchronization with the search index. The fix now ensures that changes to loss causes trigger an update to the index, immediately reflecting these edits throughout the UI and preventing data discrepancies.
Fix for require credit score checks vendor when it's not configured (BC-20477)
A validation defect was corrected where the system continued to require credit score checks on auto quotes even when no credit score vendor was configured, causing unnecessary errors for users. The logic now verifies the presence of a vendor before enforcing the credit score requirement, allowing quotes to proceed as intended when no vendor is available. This update prevents rating errors and supports accurate quote submissions across all auto policy workflows.
Claims | Adjuster/Supervisor email notification now works on new UI (BC-20448)
Email notifications for Adjuster and Supervisor assignments in the Claims module were not sent when managed via the new UI, though they functioned in the legacy interface. The underlying logic was updated to address this edge case, ensuring notifications are dispatched and notations logged whenever a role assignment occurs, regardless of UI version. This correction supports timely communication and maintains accurate tracking throughout claims assignments.
Claims reinsurer not showing in accounting (BC-20379)
A defect was corrected in the new Claims UI where the reinsurer selection and display functionality was missing in the accounting tab. The feature had worked in the legacy interface but was omitted during UI refactoring. The fix ensures users can now view and select reinsurers for claim-level recoveries as required, restoring expected claims management functionality and minimizing risk of financial reporting gaps.
BriteQuote suspensions: county error and zip code error bugs (BC-20274)
Error messaging for quoting suspensions based on county and zip code was clarified and simplified in the UI. With the update, agents and underwriters now receive succinct messages identifying the location-based suspension, improving clarity and workflow continuity when quoting in restricted areas.
Loss address missing when pulled from policy (BC-20269)
A user interface bug was addressed wherein loss addresses failed to display, sometimes appearing as “[object Object],” when loss date changes led to a new policy revision. The system now automatically remaps the loss address when revisions change, with a fallback to a “Not Listed” option for any unmatched scenarios. These improvements restore address visibility, accuracy, and data confidence across claims.
Line item hitting persistent builder with incorrect data (BC-20218)
An issue was addressed that caused renewal blocks on policies with dynamic category options for special line items, specifically due to incorrect persistent builder validation. The fix updates the logic and reduces the chance for erroneous blocking of policy renewals. This mitigates client churn risk and ensures policies can be processed accurately.
Quote Wizard endorsement flow for agents allow change in policy effective date (BC-20194)
A policy workflow defect was corrected where agents could improperly backdate the effective date during endorsements. The system now enforces the allowed date range for effective dates when processing changes in the Quote Wizard Endorsement Flow, preventing agents from circumventing core business rules and ensuring only valid dates are accepted. This update maintains the integrity of historical policy records in compliance with administrative requirements.
Default items into sub lines not being filtered correctly (BC-20055)
BriteCore resolved a defect involving the improper filtering of default policy type items in sub-lines. The update ensures only relevant items are included in each sub-line and enhances the underlying schema. This correction increases the precision of policy setup and mitigates classification and configuration errors.
Changing authority limits does not generate notes (BC-20010)
Auditability was restored to the claims authority limit update process by ensuring that changes now trigger note creation and a recorded trail. Previously, these updates did not generate notes, resulting in a gap for compliance and historical tracking purposes. With the fix, all authority modifications are now properly logged and visible in the audit history, supporting regulatory and operational reporting needs.
Copy LED - policy type not recognized on revision when prior LEDs had deletions (BC-19792)
An issue was addressed that caused policy types deleted in previous Line Effective Dates (LEDs) to be unrecognizable during policy revision or renewal, even when copied back with support tools. The issue originated from a gap in continuity propagation, breaking lineage across LEDs and leaving copied types invisible in the Policy module. The resolution preserves the necessary references so copied types appear correctly during renewal and revision, restoring workflow continuity for agents.
Duplicate emails sent - specifically "Files that printed for xyz on.." emails (BC-19531)
An issue resulting in duplicate daily "Files that printed" emails was corrected, This was caused due to potential race conditions in the underlying job, where multiple server nodes could simultaneously send the report. BriteCore introduced a locking mechanism that now ensures the job only runs once per cycle, eliminating duplicate notifications.