Enhancements

Embedded Analytics Dashboard Errors Now Return Accurate Error Responses (BC-22885)

Previously, when an embedded analytics dashboard failed to load, the system returned a success response even though an error had occurred, making failures harder to detect and troubleshoot. The system now returns a proper error response for upstream dashboard failures while preserving the detailed error message shown in the user interface.

SQL Reports Are Now Validated When Saved (BC-22764)

Previously, a SQL report could be saved with errors such as references to columns or tables that do not exist, and the problem would only surface when the scheduled report later failed to run. BriteCore now validates each report sheet's SQL at save time, checking syntax, table and column references, and unresolved parameter tokens, so configuration mistakes are caught immediately instead of causing failed report runs.

SQL Editor Now Prevents Invalid Excel Worksheet Names (BC-22759)

Excel rejects worksheet names that are too long, blank, or contain certain characters, and previously the SQL Editor only surfaced these problems after a report failed to save or generate. The SQL Editor now validates worksheet names as users type, shows an inline explanation next to the offending sheet, and disables saving until the name is corrected, so generated Excel reports open cleanly.

Larger SQL Definitions Now Supported for Multi Sheet Reports (BC-22728)

The storage capacity for report sheet SQL definitions has been significantly increased, allowing users to build larger and more complex multi sheet SQL reports without hitting the previous size limit.

Report Filenames Now Support Custom Parameter Formatting (BC-22627)

Report output filenames and display titles are now generated consistently across all report types, and users can customize how parameters appear in filename templates. A new format syntax supports custom date formatting along with uppercase, lowercase, and title case options for text parameters.

Defects

Quote API Now Accepts Phone Numbers Supplied in the Phones Array (BC-21282)

BriteCore identified and resolved an issue where, with the required phone number setting enabled, the quote creation API did not recognize phone numbers supplied in the phones array as satisfying the requirement, which could block contact processing and prevent a rate from being returned. The API now accepts a valid phone number provided through any supported phone field, and rating proceeds normally.

Lockbox Payment Processing No Longer Fails After a Database Rollback (BC-22714)

BriteCore identified and resolved an issue where an error during automated lockbox payment processing could cause a database rollback that prevented the remaining payments in the batch from posting, leaving some policies incorrectly headed toward pending cancellation. Lockbox batches now process reliably so payments post as expected.

Automated Payments No Longer Pull When No Balance Is Due (BC-21156)

BriteCore identified and resolved an issue where the system could incorrectly pull an automated payment on a policy even though a manual payment had already brought the balance to zero, resulting in an unwanted charge and an inaccurate underpaid summary on the payment record. Automated payments now correctly respect the current balance and the scheduled withdrawal date.

Manual Payments Now Process for Policy Numbers Containing Special Characters (BC-21080)

BriteCore identified and resolved an issue where manual payments, such as checks or cash, could not be applied to policies whose policy numbers contained certain special characters. The payment screen displayed an invalid number warning and the payment was not processed. Manual payments now process correctly regardless of special characters in the policy number.

Claim Activity Notes Now Show Readable Labels Instead of Internal Identifiers (BC-22840)

BriteCore identified and resolved an issue where claim activity notes for added, updated, or deleted exposures and claim properties displayed a long internal record identifier instead of meaningful information. These notes now display a human readable label built from the coverage, loss, and claimant details so adjusters can immediately understand what changed.

Claim Payments With Accounting Details No Longer Fail With an Exposure Error (BC-22754)

BriteCore identified and resolved an issue where claim payments could fail with an exposure identifier error when invoice number, vendor identifier, and vendor location details were entered on the Accounting tab. Claim payments with accounting details now process successfully.

Claim Payment Integration Errors No Longer Report Misleading Connection Failures (BC-22391)

BriteCore identified and resolved an issue where a claim payment could be reported as failed with an integration connection error even though the payment had actually been issued successfully by the accounting integration. The error reporting has been corrected so claim payment statuses accurately reflect the outcome of the integration request.

Loss Reserves Defined by Underwriting Rules Now Auto Populate on Claim Exposures (BC-22347)

BriteCore identified and resolved an issue where loss reserves configured through underwriting rules for a specific loss cause did not automatically populate when an exposure was added to a claim. Reserves defined by these rules now populate on claim exposures as configured.

Coverage Limit Selection Restored on the Auto Quote Rating Step (BC-22934)

BriteCore identified and resolved an issue where the coverage limit selection was missing from the rating step when creating a new auto quote, preventing the quote from being rated or submitted. The limit selection now displays correctly so auto quotes can be completed.

Vehicle Lookup Now Works Using Year Make and Model When a VIN Is Not Provided (BC-22556)

BriteCore identified and resolved an issue where the vehicle lookup on the auto quote flow silently skipped attribute prefill when a VIN was not provided, even though a complete year, make, and model had been entered. The lookup now retrieves vehicle attributes from year, make, and model when no VIN is available, while preserving the existing behavior when a VIN is present.

Quotes Created Through the API No Longer Hang on the Risk Details Screen (BC-21390)

BriteCore identified and resolved an issue where quotes created through the extended quote creation API caused the Agent Portal to hang indefinitely when navigating to the Risk Details screen. These quotes now load normally so agents can continue working them in the portal.

Require Explicit Selection Setting Now Respected for Standard Rating Categories (BC-20522)

BriteCore identified and resolved an issue where the setting that requires users to make an explicit selection in the Policy Wizard, rather than accepting a pre selected default, was not honored for standard rating categories. With the setting enabled, the wizard now correctly prompts for a selection on first load while preserving values the user has already chosen.

Agent Contact Page Loads Faster for Contacts With Many Policies (BC-21449)

BriteCore identified and resolved a performance issue where the contact information page took a long time to load for agent contacts associated with a large number of policies. The page now loads significantly faster for these contacts.

Agents Can Now Reliably Find Policies in Search (BC-19533)

BriteCore identified and resolved an issue where a policy could stop appearing in search results for a specific agent even though other users could find it, and rebuilding the search index only fixed the problem temporarily. The search index now stays consistent so agents can reliably find the policies they have permission to view.

Property Coverage by Limit Report No Longer Fails for Similar Agency Names (BC-22881)

BriteCore identified and resolved an issue where the Property Coverage by Limit report could fail to generate when it included agencies whose names shortened to the same Excel worksheet name, differing only in letter casing. The report now automatically generates unique worksheet names so it completes successfully in these cases.

Nightly Report Data Refresh Jobs Now Recover From Temporary Database Congestion (BC-22793)

BriteCore identified and resolved an issue where nightly report data refresh jobs could fail when many sites accessed the database simultaneously, causing the entire job to restart from scratch. These jobs now automatically retry after temporary database connection errors, making overnight report data refreshes more reliable.

Financial Anti Terrorism Cross Reference Report No Longer Fails With Certificate Errors (BC-21082)

BriteCore identified and resolved an issue where the Financial Anti Terrorism Cross Reference report, used for OFAC (Office of Foreign Assets Control) screening, could fail with a certificate error when contacting the screening service. The underlying request library has been updated so the report runs reliably without requiring a configuration workaround.

Document Generation No Longer Fails When the Recipient Has No Email Address (BC-22833)

BriteCore identified and resolved an issue where generating a document for email delivery failed when the recipient contact had no email address on file, even though the PDF itself had been generated successfully. The system now handles contacts without an email address gracefully instead of marking the entire document task as failed.

Endorsement Billing Statements Now Generate and Deliver Correctly (BC-22753)

BriteCore identified and resolved an issue where billing statements triggered by endorsements failed during post processing in the standard document generation path. Although the PDF was created, it never entered the print queue for mailing and did not appear under the policy documents. Endorsement billing statements are now processed, queued, and displayed correctly.

Document Generation No Longer Produces Empty Files After a Database Conflict (BC-22501)

BriteCore identified and resolved an issue where a temporary database conflict during document generation could cause the process to fail in a way that left a zero size document indexed on the policy. Document generation now handles these conflicts correctly so deliverables are produced completely and reliably.

Endorsements No Longer Blocked by an Outdated Recurring Billing Contact (BC-22603)

BriteCore identified and resolved an issue where an endorsement could not be committed when the recurring billing schedule was tied to a contact who was no longer on the policy, because the current named insured was missing from the recurring billing dropdown. The named insured on the policy is now available for selection so users can update recurring billing and commit the endorsement.

Negative Commission Delays Now Calculate Correctly at the Agency Group Level (BC-21347)

BriteCore identified and resolved inconsistencies in how delayed negative commissions were handled when agencies are paid at the agency group level. Previously the negative balance check was always performed for each individual agency, which could incorrectly delay amounts that the group total would cover, or incorrectly mark amounts as paid when the group total was negative. A new setting allows the delay decision to be made against the agency group total so commission records accurately reflect what was paid.

Nightly Policy Transaction Export No Longer Fails on Certain Question Values (BC-22711)

BriteCore identified and resolved an issue where the nightly policy transaction export to a downstream data vendor failed with a generation error caused by certain question values in the policy data. The nightly export now completes successfully.

Mailings With Large Document Sets Now Create Successfully (BC-22367)

BriteCore identified and resolved an issue where creating a mailing could fail when the combined set of documents for the mailing was too large. Mailings with large document sets now process successfully.

Convenience Fee API Endpoints Now Accept an Optional Policy Identifier (BC-22967)

The convenience fee retrieval API endpoints now accept an optional policy identifier parameter, allowing callers to retrieve and preview convenience fees in the context of a specific policy. This was shipped as a hotfix to support a BriteApps release.

Agency Download Initial Load Files Now Generate Successfully (BC-22755)

BriteCore identified and resolved an issue where generating the initial load files for agency download integrations failed due to a permissions error when accessing stored credentials. Initial load files for agencies now generate successfully. This fix was shipped as a hotfix.