Enhancements

Global Fields for Dynamic Document Templates (BC-21919)

BriteCore now supports global fields in Dynamic Document Templates, allowing you to control wording dynamically at the time a document is generated. Instead of maintaining separate templates for different states or scenarios, you can define reusable logic that adjusts language automatically based on your data. These calculated fields support dependencies between fields and include a built-in testing tool, making it easier to validate and manage your document logic in one place.

Permission to Prevent Editing of Issued Check Payments (BC-21811)

BriteCore added a permission that controls whether a user can edit check payments on claims via the claims processing screen. Carriers can now restrict who is able to alter issued checks, reducing the risk of unauthorized or fraudulent changes.

Save As Button in the SQL Editor (BC-22128)

BriteCore added a Save As button to the SQL Editor so users can duplicate reports directly without copy-pasting content across multiple tabs. Previously a multi-tab report was very difficult to recreate with a different name.

Calculation Line Items Included in the list_sub_lines API Endpoint Response (BC-22115)

The list_sub_lines API endpoint now returns calculation line items alongside coverages, matching the behavior of the list_coverages API endpoint for consumers that need both types of data in a single call.

Faster Policy List Filter Options Endpoint (BC-22145)

BriteCore eliminated an inefficient query pattern in the policy list filter options endpoint, dramatically reducing response times from several seconds to near-instant for users opening the policy list.

User Alert for Oversized Email Attachments (BC-15957)

BriteCore resolved an issue where email attachments over 18 megabytes were silently removed from outgoing policy and claims emails, causing recipients to receive messages without the intended documents. The system now warns users before sending or attaching oversized files.

Bugs (Fixes)

Improved Handling of Deleted Reports in the SQL Editor (BC-22031)

Improved SQL Editor behavior when reports are deleted in another tab or session. The editor now detects deleted reports and prevents stale report names from appearing, ensuring the UI reflects the current state.

Reliable File Execution and Naming in the Report Copilot (BC-22058)

BriteCore corrected out-of-sync behavior in the SQL Editor where renaming and saving reports could cause the wrong report to run. Buffer detection, save state, and the executed report name are now consistent with each other.

Preserve Report Content When Applying Copilot Fragment Suggestions (BC-22059)

BriteCore corrected the Copy to Report behavior in the Report Copilot so that agent-suggested fragments no longer overwrite the entire report buffer when a user chooses to apply them.

Report Scheduler Filename Handling for FTP Delivery (BC-21960)

BriteCore corrected a defect where the report scheduler inserted extra spaces into destination filenames during variable substitution when delivering reports to FTP or sFTP servers. Scheduled reports now arrive with the expected filenames.

Multi-Exposure Claim Payments After a Voided Payment (BC-21053)

BriteCore resolved a floating-point calculation edge case that could cause multi-exposure claim payments to fail after a prior payment had been voided. Payments now process reliably across exposures.

Endpoint Locking During Rapid Claim Status Changes (BC-21907)

Rapid claim status changes could previously leave the endpoint locked without any user-facing message. Locking behavior and error messaging have been improved so users see clear feedback and can recover quickly.

Persistent Builder Resolution When All Line Items Are Complete (BC-21997)

BriteCore resolved a case where the Persistent Builder refused to resolve even when all line items showed as completed, which had been blocking rating and saving for affected policies.

Claim Parties With the Other Role Now Persist (BC-22086)

BriteCore corrected a defect where adding a claim party with the Other role appeared to succeed but was never actually saved. Contacts added with the Other role now appear on the Parties tab as expected.

Adding an Inspected Date to a Claim Dispute (BC-21933)

BriteCore fixed an error that appeared when adding an Inspected Date to a claim dispute, allowing dispute details to be saved successfully.

HazardHub Mappings Populate on Policy Type Change (BC-21872)

BriteCore fixed an issue where HazardHub data was not propagating to the Builder tab after a policy type change, which had forced agents to manually re-select values that should have populated automatically.

Policy Number Displayed After Claim Assignment (BC-22165)

BriteCore corrected the claim interface to show the policy number, rather than an internal database identifier, after a policy is assigned to a claim, and added a progress indicator while the assignment is in flight.

Default Agency Setting Behavior on New Quotes (BC-21767)

When the default-agency setting is disabled, the Agency field on new quotes now appears blank and only shows agencies actually assigned to the agent, hiding discontinued agencies from selection.

Rules API Endpoint Validates Category Against Policy Type (BC-22116)

The rules API endpoint now validates that a rule's category is allowed for the target policy type, preventing, for example, property-specific rules from being created on auto policies.

Validation Error Rule Effect Configuration (BC-22196)

BriteCore fixed the Validation Error rule-effect configuration screen so it no longer displays unrelated fields while the effect is being configured.

Audit Trail for the Process Policy as Renewal Setting (BC-21359)

Toggling the Process Policy as Renewal setting now writes a policy note capturing who changed the setting and on which term, improving auditability of renewal processing decisions.