Enhancements
Task Management
BriteCore’s Task Management module (Tasks) centralizes and streamlines how work is initiated, assigned, tracked, and completed across claims and policies. The module is tightly integrated with the core system so that tasks always live in the context of a specific entity (such as a policy or claim) and each user gets their own task workbench to manage the workload efficiently.
Adding default ‘None’ value for empty Line Item Questions (BC-20791)
Default value initialization for line item questions was updated to avoid populating empty placeholder objects for structured question types such as address and contact-like fields. Instead of inserting empty structures, initialization logic was revised so these question types defaulted to None, reducing confusion and preventing downstream logic from treating placeholders as meaningful answers. These changes improved the accuracy of underwriting and validation flows that depend on whether a question was truly answered versus merely pre-populated.
Store payor name and email from secure payment (BC-19430)
BriteCore has added support for receiving payer identity details from the external payment flow and persisting them with the payment record. Previously, the platform was not capturing and displaying the name and email address of the payor for electronic payments made with Stripe, which reduced visibility for billing and accounting teams reviewing payment history. Clients now have improved traceability for reconciliations and customer service follow-ups.
Defaults to first property in policy property list and adds editable option for multi-property policies when associating property to claim (BC-18452)
This enhancement streamlines claim workflows by automatically preselecting the first property on a policy when users need to associate a property when creating a claim. Previously, users had to manually select a property even in common scenarios where the first property was the intended choice, which added unnecessary clicks and slowed down claim intake and processing. When a policy contains multiple properties, the selection remains editable so users can quickly choose the appropriate alternative property without losing flexibility.
Allow automatic filling of counties for business locations (BC-13853)
This enhancement improves configuration efficiency by allowing administrators to automatically populate counties for a selected state when setting up business locations. Previously, the county setup required manual entry or repetitive selection, which was time-consuming and increased the likelihood of missing or inconsistent configuration.
Add detailed invoice allocation info to payment retrieval and payment-made events (BC-20454)
Enhanced the payment retrieval API to return invoice-level allocation details for a payment, including invoice_amount, amount_paid (for that specific payment), and amount_due, plus supporting metadata (e.g., invoice identifiers/descriptions, status, revision/external references, and due dates where applicable). Covered scenarios such as partial payments, multiple payments completing an invoice, and excluding invoices already fully paid by prior payments, with accompanying unit tests.
Defects
Disable username input alias for users in BriteAuth Sites (BC-21328)
BriteCore now displays the username alias as read-only on the contacts page for users on sites using BriteAuth. BriteCore resolved an issue where in cases when the user was already invited, the username alias input should have been displayed as read-only on the contacts page. Editing it would not have had an effect but it was still shown as editable.
Wrong error message when revision not found - api/v2/quotes/delete_full_quote (BC-21302)
When users invoked the delete quote endpoint using an external system reference and the quote could not be found, the API returned a confusing “Not Found: None” message that did not indicate which identifier failed. The error handling has been adjusted so the correct identifier is preserved and surfaced consistently in the error message. This ensures that when a delete request fails, additional details are provided as part of the error message.
Quote changes not persisting while STP is pending underwriting review (BC-21216)
When a quote was in a workflow state that restricted editing, users could still make changes and click Rate & Save, but the system would silently refuse to persist those updates. This created a misleading experience where the UI appeared to accept changes, yet a refresh reverted values to their previous state with no explanation. The behavior was corrected so the system returned a clear, user-facing warning when an edit attempt was blocked by the configured review-state lock. This ensured underwriters and other users understood that the quote was not editable in its current review state and why their changes were not saved. The improvement reduced confusion and prevented users from assuming rating or underwriting adjustments had been captured when they had not. Overall, the quote workflow behaved more transparently and predictably in locked review states.
Quote/policy new attachments UI delete folder was not working (BC-21176)
BriteCore resolved an issue where occasionally, when users attempted to delete a read-only attachment or folder in the new attachments interface, the deletion request could fail but the UI still reported success. This created an inconsistent experience where users believed content had been removed even though it remained in place. The deletion workflow has been updated so the UI validates the server response and only reports success when the delete operation actually succeeds.
Claims displayed military time and inconsistent date formats across components (BC-21171)
Claims had displayed dates and date-times using inconsistent formats across different screens and dialogs, which created confusion for users reviewing loss details, transactions, and notes. This change standardizes date presentation across the claims experience so users can see a consistent format.
Read permissions did not enforce read-only behavior in the contact module (BC-21110)
The Contact module had not consistently enforced read-only behavior when a user only had “Read” access, which meant interactive controls could appear enabled even when edits should not have been permitted. As part of this fix, more granular permissions are checked and enforced that override less granular permissions. As a result, users now experience a more consistent authorization experience across all workflows.
Vehicle model changed after saving when entered manually (BC-21014)
Vehicles created through an external prefill import could arrive without a populated vehicle model, prompting users to manually enter a model value during quoting. When the vehicle was later saved or updated, an automatic VIN-based prefill could run and overwrite the user’s manual entry, which was confusing and led to unexpected data changes. The fix enriches imported vehicles with VIN-based prefill data earlier in the workflow so the model value is correctly populated at the time of import when available. This prevented user-entered values from being replaced by background lookups.
Rating not invalidated when adding or removing properties (BC-21006)
BriteCore resolved an issue where properties were added or removed from a quote but the system did not consistently invalidate the existing rating state, which allowed stale premium values to remain visible and sometimes actionable. The fix centralizes rating invalidation so that adding, removing, or updating property locations reliably resets the rated state and prompts the appropriate re-rate behavior.
Alert email link opened claim in legacy claims interface instead of new Claims interface (BC-20901)
Claim alert emails had included links that could open claims in the legacy claims interface even when the new Claims experience was intended, causing inconsistent navigation for users. The fix introduces conditional redirects that account for claim type and configuration flags so that the correct interface is used consistently for the intended scenarios.
Underlying policy email type caused errors in PUP contact editing (BC-20795)
When a contact was mapped from an underlying policy into a PUP workflow, an email type value could appear that was not supported in the PUP contact editing UI, leading to validation errors when Users attempted to save edits. This mismatch stemmed from inconsistent email type options across different parts of the application and legacy values that did not align with the current dropdown choices. The fix standardized the supported email types across the platform to a canonical set and aligned UI labels and defaults with that canonical behavior. It also added stronger backend defaults and validation so newly created email records consistently had an appropriate type and did not rely on inconsistent legacy values. A migration script normalized existing stored values into the canonical set so pre-existing records would not continue to break editing flows. As a result, Users could edit and save contacts in the quoting workflow without encountering confusing validation failures caused by unsupported email type values.
E-signature completion page blocked (BC-21433)
After an agent completed an embedded e-signature session, the signing experience could be blocked on the completion step due to updated security restrictions from the eSignature provider. This release updates how we handle the completion state so the embedded flow can finish cleanly without trying to load the blocked completion page. Agents should now consistently reach a successful end state after signing.