User Interface Changes by Area
Where this release changes screens that existing users already use, by area of BriteCore. Each line says which page changed and why. Select a ticket number to jump to its full write-up later in this document.
Policies
| What changed and why | Ticket |
|---|---|
| The Processing page on the Policies menu was changed to offer a new page-per-section experience, starting with Pending Emails, so that staff can send selected emails instead of all of them at once. | BC-27615 |
| The policy type selection on the policy page (Policies menu) was changed to complete on an agency-billed revision and list the items it removed, so that users no longer hit a rollback error and can see what changed. | BC-18570 |
| The Add/Modify Subjectivity popup and the Mark as Satisfied icon on the policy page (Policies menu) were changed to state the specific reason a save failed, so that users know what to fix. | BC-19128 |
| The Endorsement Review and Show Policy Changes popups on the policy page (Policies menu) were changed to display note text and file names exactly as typed, so that notes always read as plain text. | BC-27192 |
| The Contacts tab on the policy page (Policies menu) was changed to keep a saved motor vehicle or credit report available, so that the report can be opened again without failing. | BC-27417 |
Quoting
| What changed and why | Ticket |
|---|---|
| The Named Insured form on the Contacts step of the Quote Wizard (Policies menu) was changed to leave Legal Entity Type empty when a user tabs past it, so that a legal entity type is never recorded that nobody chose. | BC-27295 |
| The Coverages screen of the Auto Quote Wizard (Policies menu) was changed to show driver accident and violation rule messages together in one dialog, so that the messages are actually seen and no longer interrupt the driver and vehicle forms or block rating. | BC-27495 |
| The Setup step of the agent Quote Wizard and the agent Policy Setup page were changed to refuse a policy type change on a mid-term endorsement of a committed term, so that the policy's items and the premium already earned are not lost. | BC-27753 |
| The Questions tab of the agent Quote Wizard was changed to flag CLUE loss history pulled for a previous named insured or address as outdated and to re-check it at submit and approval, so that a quote is not underwritten on someone else's loss history. | BC-21491 |
| The mortgagee dialog in the classic Builder and the Quote Wizard (Policies menu) was changed to keep the loss payee chosen for a scheduled item, so that later saves no longer overwrite it. | BC-23358 |
| The Related Coverages dialog in the Quote Wizard (Policies menu) was changed to add mandatory coverages however it is closed, and to open one dialog at a time, so that required coverages are not skipped. | BC-24371 |
| The Related Coverages dialog opened from the policy-wide section of the Quote Wizard was changed to offer only policy-wide coverages and to list failures in one message, so that users are not offered coverages that cannot be added there. | BC-24372 |
| The Quote Wizard (Policies menu) was changed to stop opening the Related Coverages dialog when an underwriting rule adds a grouped coverage, so that users are not interrupted by a dialog they did not trigger. | BC-24374 |
| The Setup step of the agent Quote Wizard was changed to keep an endorsement's existing coverages and items when the agent continues, so that an endorsement does not reset the policy to defaults. | BC-26462 |
| The Rating step of the agent Quote Wizard was changed to keep optional endorsements removed after the agent removes them, so that moving between steps does not add them back or clear the rate. | BC-26743 |
| The Classic Property page of a quote or policy (Policies menu) was changed to show Verisk's cannot-place-address message as an inline warning, so that the user can keep working on the page. | BC-27058 |
| The Classic Property page of a quote or policy (Policies menu) was changed to keep the address, county and map in step with the latest address picked, so that location lookups and maps are never run against a previous address. | BC-27076 |
| The Contacts step of the Auto Quote Wizard (Policies menu) was changed to ignore a second click on Save while a Named Insured is saving, so that the same Named Insured is not added twice. | BC-27246 |
| The Extra Information section for vehicles, watercraft and drivers on an auto quote was changed to one question per row, so that the full question text can be read and is no longer cut off. | BC-27309 |
| The agent Policy Setup page was changed to show only the validation message when a submission is stopped, so that agents see the real reason and not an unexpected-error popup on top of it. | BC-27339 |
| Rate & Save in the Classic Builder (back office and agent portal) was changed to leave a removed optional coverage off, so that rating does not add back a coverage the user took off. | BC-27780 |
Claims
| What changed and why | Ticket |
|---|---|
| The Damaged Properties tab on the claim page (Claims menu) was changed to take Property Type from a searchable lookup list, so that carriers can maintain their own property types in place of 12 fixed values. | BC-17826 |
| The Claim Information card on the claim page (Claims menu) was changed to put Bifurcate Claim and New Dispute under one Actions menu, so that claim actions sit in one place and a dispute can be started from the claim. | BC-18149 |
| The claim Accounting page in the agent portal was changed to hide the Payment Method column in Payment History when that claims setting is off, so that agents see only what the carrier has chosen to show. | BC-17828 |
| The System Tags page on the Settings > System Wide menu was changed to list tagged claim payments and to find payments by claim number or payee, so that claim payment tags can be reviewed and corrected in one place. | BC-18886 |
| The Make Payment and Edit Payment dialogs on the claim page (Claims menu) were changed to hold the payment until system tags have loaded, so that a claim payment is never saved without its tags. | BC-18887 |
| The Claims page on the Settings > Modules menu was changed to unlock the Enable return payments checkbox, so that an administrator can turn return payments on or off without contacting BriteCore. | BC-26426 |
| Claim submission under the newer claim numbering option was changed to keep the number given when the claim was created, so that a claim's number does not change between creation and submission. | BC-27378 |
| The add-vehicle form on File a Claim and on the claim Vehicles tab (Claims menu) was changed to clear required-field messages as soon as a field is filled, so that users are not shown errors that no longer apply. | BC-27421 |
| The Parties tab on the new claim page (Claims menu) was changed to update an existing party when the same contact is chosen again, so that a claim does not end up with duplicate parties or repeated import notes. | BC-27498 |
| The Accounting section on the new claim page (Claims menu) was changed to show the Per Risk XL reinsurance retention for the loss date, so that the new page gives adjusters the same reinsurance information as the classic page. | BC-20663 |
| The Information tab on the new claim page (Claims menu) was changed to add an ISO A-PLUS card with a Report this claim switch, so that carriers using ISO A-PLUS reporting can choose claim by claim what goes in the monthly file. | BC-26163 |
Payments and billing
| What changed and why | Ticket |
|---|---|
| The public Secure Checkout payment page was changed to lock the payment plan for visitors who are not signed in, so that only a signed-in user can change the payment plan on an existing policy. | BC-27118 |
| The results page shown after a group payment on Secure Checkout was changed to list one row per policy with its own View Payment Confirmation link, so that each payor opens the receipt for the right policy. | BC-20093 |
| The Commission Payments page on the Payments menu was changed to process only the rows selected on the current tab, so that commission payments the user did not select are no longer processed or marked reviewed. | BC-27666 |
| The Add Payment Method dialog was changed to close and show an Unable to load payment form alert when Stripe cannot load, so that users see the reason and are not left with a blank form. | BC-23900 |
| The public payment page and the back-office Payment Status window were changed to show a readable message when an eDatabase payment fails during a processor outage, so that payors and staff understand what happened and check the account before retrying. | BC-26872 |
| The payment plan dropdown on the Secure Checkout payment page was changed to show the policy's actual plan even when that plan is hidden from the public page, so that a payor sees the right plan and can switch back to it. | BC-27117 |
| The account history on the Accounts Receivable page was changed to show the Description as plain text, so that markup typed into a reason is displayed as text and not rendered. | BC-27397 |
| The Stripe Add Payment Method window on the Billing > Billing Setup page was changed to require a name and a valid email, so that every saved payment method carries the payor's contact details. | BC-26926 |
| The payment page was changed to tell the payor not to resubmit when an eDatabase payment's outcome is unknown, and to hold new payments on that policy, so that a payor is not charged twice. | BC-27033 |
Workflows
| What changed and why | Ticket |
|---|---|
| The workflow designer on the Settings > Modules > Workflows menu was changed to add Generate Deliverable and Evaluation nodes, with code-driven field values and a rule of one Yes and one No branch, so that carriers can build document and decision steps into a workflow and cannot publish an incomplete branch. | BC-26619, BC-27318, BC-27319 |
| The Workflows page on the Settings > Modules menu was changed to include default claims workflows that produce the Claim Acknowledgment Letter, so that carriers control when the letter goes out themselves, in place of a single on/off setting. | BC-26858 |
| The buttons and loading indicators on the Workflows pages (Settings > Modules menu) were changed to stay still while loading, so that the screen does not shift under the user and loading looks the same as elsewhere in BriteCore. | BC-27442 |
Lines, rules and product setup
| What changed and why | Ticket |
|---|---|
| The policy type Details page and the line item Setup tab on the Lines menu, and the Deliverables page on the Settings menu, were changed to add a Priority field, so that carriers decide where each form and deliverable prints in the Declaration Package. | BC-26681 |
| The rules editor's variables browser and in-app rules documentation were changed to show a type and description for every field on the revision, policy term and prior term records, so that rule writers pick the right field and a misspelled name is caught at validation, before the rule runs. | BC-27037 |
| The Edit Line Item screen on the Lines menu was changed to warn on save when a calculation reads an item name used on more than one sub-line, so that a calculation does not silently read the wrong item. | BC-27488 |
| The System Tags page on the Settings menu was changed to show a warning panel on the NxTech AL3 Codes tag, so that carriers using IVANS downloads can see which lines and policy types are missing an AL3 code. | BC-27424 |
Documents and attachments
| What changed and why | Ticket |
|---|---|
| The Attachments step of the Quote Wizard (Policies menu) was changed to add a Type column to the attachments list, so that users can see what kind of file each attachment is without opening it. | BC-20183 |
| The label editor for photos and attachments was changed to show a message and restore the old label when a relabel is refused, so that users are not misled into thinking the change was saved. | BC-26073 |
| Custom deliverables that check e-signature status, such as a Policy Application, were changed to generate again on agent submission and from the administrator preview and create actions, so that these documents are produced and no longer fail. | BC-27336 |
| The Custom Deliverable popup on the policy page (Policies menu) was changed to build a Declaration Package even when a form has a blank page, and to report a failure honestly, so that users get the package or know it was not created. | BC-27357 |
| The Declaration Package for a policy (Policies menu) was changed to include a form that an endorsement or renewal brings in with a new item, so that the insured receives every form that applies to the change. | BC-27472 |
| The PDF viewer on Attachments pages was changed to display PDF files that used to open blank, so that attachments can be read in BriteCore when the built-in viewer is on. | BC-27671 |
Search and contacts
| What changed and why | Ticket |
|---|---|
| The Policy Search, Claims Search and Contacts List pages on the Policies, Claims and Contacts menus were changed to open without the cursor in the search box, so that the quick search keyboard shortcuts work as soon as the page loads. | BC-18150 |
New Features and Enhancements
Generate Deliverable Node in Workflows (BC-27319)
The Workflows designer has a new Generate Deliverable node that files a chosen deliverable on the policy with a selected print state (default, TBD or do not print) and a print date, either the default or a set number of days after generation. The Policy Issued trigger now also indicates whether the policy is a renewal and its term number, so a Gateway can send renewals and new business down different branches. The run history shows which deliverable was generated, and a failed generation is recorded as an error that stops only that branch.
Generate Deliverable Workflow Step Can Set Dynamic Field Values (BC-26619)
In workflows, the Generate Deliverable step can now set the dynamic fields of the deliverable it produces, such as a mailing address, message, or closing note. Each field can use the template default, a fixed value, or the result of advanced code, so one document template can serve several workflows with different content. Deliverables generated in the background now also carry their dynamic field values, where they previously printed defaults or blank values.
Typed Fields and Descriptions for Rule Record Variables (BC-27037)
In the rules editor, the revision, policy term and prior term record variables now declare each of their fields with a type and a description. The variables browser and the in-app rules documentation can show what each record offers, and a misspelled field name is caught when the rule is validated rather than only when the rule runs. The set of fields available on each record is unchanged.
Popup Message Rules for Driver Violations Now Show on the Coverages Screen (BC-27495)
In the Auto quote wizard, Add Popup Message rules based on a driver's accidents and violations never displayed their message. The Coverages screen now shows these messages in a dialog without blocking rating, and Add Popup Message can be used on rules in the driver category. Add Popup Message is no longer available on the vehicle, driver and watercraft form rule categories, so popups that previously appeared on the driver and vehicle forms no longer display there; an existing form rule that carries a popup message is skipped without an error.
Attachment Type Shown in the Quote Wizard Attachments List (BC-20183)
On the Attachments step of the Quote Wizard, the Type selected when uploading a file was saved and searchable but never shown in the attachments list. The list now includes a Type column showing each file's Type, or a dash when the file has none, including after a search by Type or an edit. Clearing the Type in Edit File now removes it from the file, and sites with no file types configured continue to see no Type column.
Loss Payees on Scheduled Items Saved and Displayed Consistently (BC-23358)
In the classic Builder and the Quote Wizard, loss payees on scheduled items were stored in inconsistent formats, which could cause errors or leave a payee off where it should appear. A loss payee selected in the mortgagee dialog could also be overwritten by a later save of the page. Loss payees are now stored in one consistent format on every save, each scheduled row keeps its own selection, and existing payees are no longer removed when the loss payee option is turned off for an item type.
Per Risk XL Retention Shown in the New Claim Accounting (BC-20663)
The Accounting section of the new claim page did not show the reinsurance retention that the classic claim Accounting page displays for Per Risk XL contracts. It now shows the retention from the contract term that covers the claim's loss date: one amount for a single retention, or separate property and liability amounts for a separate retention. No retention is shown when the claim has no loss date or no term covers it, and the existing excess of loss permissions control who can see each amount.
ISO A-PLUS Reporting Controls on the New Claim Page (xf)
On the Information tab of the new claim page, an ISO A-PLUS card now appears after Policy Information when the ISO A-PLUS Reporting vendor is turned on and the claim has a policy. It holds the Transaction Type choice of Individual or Business and a Report this claim to ISO A-PLUS switch, which defaults to Yes; setting it to No leaves the claim out of the monthly ISO A-PLUS file, for losses another carrier already reports. The switch replaces the Dual Masthead checkbox from the legacy claim screen, and claims already marked there carry over. Both controls now require permission to view and change, and each change is recorded in a claim note.
Claim Acknowledgment Letter Generated by Default Workflows (BC-26858)
The Claim Acknowledgement Letter is now generated by claims workflows that BriteCore installs on every site, which carriers can view, pause, edit, copy or delete in Settings > Modules > Workflows. Previously the letter followed fixed rules that could not be changed, and a claim that had been saved once as Pending, Unsubmitted never received it when it was later opened. The letter is now produced on that path as well, and the separate setting that controlled the letter on agent claim submission has been retired.
Control What Prints Before and After the Declaration (BC-26680, BC-26681)
You can now add forms and deliverables, such as a Welcome Letter, to the Declaration Package and choose whether each prints before or after the Declaration. Each recipient’s copy opens with the page addressed to them, so every insured, mortgagee or agent gets a package that starts with their own cover letter. Set the placement under Policy Type > Details, on a line item’s Setup tab or in Settings > Deliverables. A negative number places an item before the Declaration and a positive number places it after. Packages you haven’t configured print exactly as they do today.
New Policies Processing Experience with Selective Pending Emails (BC-27615)
Policies > Processing now offers a Try the new experience switch in the top navigation for users with access to the page. Turned on, each processing section opens as its own page under a Processing group in the Policies menu, and the Pending Emails page loads faster, can be sorted and searched, and lets users select rows and send only those with Process Selected Pending Emails. The classic page remains the default at every login, and it now shows the correct LexisNexis C.L.U.E. schedule form for carriers on a daily schedule.
Premium Finance Companies Available to Rules (BC-27142)
Premium finance companies added in the Premium Finance Companies section of a quote were not visible to rules, so underwriting triggers, straight-through processing rules and conditional logic could not check whether a quote had one. Rules can now read the premium finance companies on a quote, including details such as the company name, and can test whether any are present. The in-app rules documentation lists the new data point, and existing rules that use additional interests behave as before.
Email Alert for IVANS Transactions With a Blank Line of Business Code (BC-27423)
For the IVANS download, when a Line has no NxTech AL3 Codes system tag, its policy transactions are sent with a blank Line of Business code and IVANS skips them without notice. BriteCore now emails the carrier's IVANS notification recipients one alert per transaction file, listing the affected transactions with policy number, transaction code, Line, Line effective date, policy type and agency, along with how to correct the tag under Settings > System Wide > System Tags. The transaction file itself is still created and uploaded exactly as before.
Warning for Lines and Policy Types Missing an NxTech AL3 Code (BC-27424)
On the System Tags page in Settings, selecting the NxTech AL3 Codes tag now shows a warning when IVANS downloads are enabled and a Line or Policy Type in the live or a future effective date has no AL3 code. The warning gives a total and a count for each effective date, and it clears once the code is set. Previously, transactions for Lines and Policy Types without a code were skipped from IVANS downloads with no indication. The warning is informational only and does not block copying or publishing an effective date.
Vehicle Loss Payees Available to Personal Auto Documents (BC-28189)
Additional interests attached to an individual vehicle, such as a loss payee, are now available to Carbone document templates. Personal Auto declarations and lienholder notices can print the loss payee for each vehicle instead of leaving it blank
Property Item Detail Report Corrections (BC-25461)
The Property Item Detail report now lists the Item column before Limit, and in-force policies whose revision has no property row are no longer dropped from the report. The report description was also updated to describe what the sheet contains.
Terminated Policies Report Matches Its Published Definition (BC-25469)
The Terminated Policies report's column names, filters and sorting are now consistent with its published report definition, including a single name for the Terminated Reason column on the Totals By Reason sheet.
Policy Change Requests Report Matches Its Published Definition (BC-25472)
The Policy Change Requests report no longer asks for an As Of Date that had no effect on the results, and its documented filters now describe which revisions it includes.
Report Definitions Updated for Six Standard Reports (BC-25475, BC-25476, BC-25479, BC-25494, BC-25495, BC-25498)
The published definitions for six standard reports now match how each report works, so you can trust that every column, filter and totals row means what its definition says. The updated reports are Claims by Closed Date, Write-Offs and Waives, Losses Incurred, Payoff Amounts, Accounting Detail and Premium Running. Depending on the report, the definition now explains how rows are chosen, which dates and locations are used, and how totals are calculated. Column names, sheet names and descriptions were aligned to match, and typos were corrected.
Consistent Row Order in the Property Item Detail Report (BC-26019)
Rows in the Property Item Detail report now appear in the same order on every run with the same data, which makes it easier to compare two runs or read an export by row position. The rows and values themselves are unchanged.
Incomplete Contacts Report Checks Aligned With the Classic Report (BC-26367)
The Incomplete Contacts report's address, phone and email checks were reviewed against the classic report, so it flags the same kinds of incomplete contacts carriers relied on before.
Return Payments Included in the Claims Payments Report (BC-27061)
The stock Claims Payments report now includes return payments, so the amount paid on a claim is shown net of funds returned. Previously the report showed gross payments, which did not match the claim's Accounting tab or the Open Loss Report..
Bug Fixes
Missing Columns Restored in the Inspections Due Report (BC-25474)
The Inspections Due report now includes the Next Inspection Date, Last Inspection Date and Policy Type columns described in its report definition, and its description has been updated.
Failed Lockbox Payments Retry on the Same Payment Record (BC-26457)
When a lockbox check failed to apply, the failed payment record was left behind, and posting the check again either created a duplicate record or was blocked. A retry now resumes the original payment record and completes it, so each check results in one payment and one credit. Imports and manual distributions of the same check are also processed one at a time, which prevents the same check from being credited twice.
Agents Can No Longer Backdate a Quote's Effective Date Outside the Application Date Bounds (BC-27589)
On the Setup page of an auto quote, an agent who reopened a saved quote could move its effective date outside the carrier's past and future application date bounds. The date is now checked when the quote is created and when the agent selects Continue, and a date outside the bounds is refused. The same check applies everywhere an agent can change the effective date of an application; Administrators and Underwriters are not restricted.
Long Waits Before Reports Start When Several Run at Once (BC-27316)
In Reports, a report that accessed tables already being accessed by an earlier run could wait a long time before it started when other reports were reading the same data, in some cases well over an hour. BriteCore removed the bookkeeping step that caused the wait, so these reports now start without queuing behind one another. As a result, prepared report data is no longer kept longer each time it is reused; it expires on its original date and is rebuilt the next time a report needs it.
BriteApps Bank Account Setup Showed Manual Entry in Place of Bank Login (BC-26796)
In BriteApps, under Payments > Payment Methods, adding a US bank account opened Stripe's manual form for routing and account numbers, so the account was added without verification. Adding a US bank account now opens Stripe Financial Connections, where the insured links the account by logging in to their bank, on both web and mobile.
Users with Multiple Roles Skipped the Role Picker After Signing In (BC-26706)
After signing in, users with more than one login role were sometimes taken straight to the dashboard without being shown the role picker, most often on the first sign-in after the browser had been closed. The pages loaded but no role was applied to the session, so the site was unusable until the user logged out and back in. BriteCore now restores the role the user last chose when they still hold it, and otherwise sends them to the role picker.
Attachments Named Form Were Left Out of the Print Queue (BC-26734)
When a user uploaded an attachment or photo whose file name was exactly Form and typed no label, the file was stored with a label BriteCore reserves for its own forms, so it was silently left out of the documents selected for printing. These uploads are now refused with a message explaining that the name is reserved, matching what already happens when a file is relabeled to Form.
Attachment Titles With Unsupported Characters No Longer Save Incorrectly (BC-27207)
In the Edit File dialog for an attachment, a title containing an emoji or a similar special character was saved with the title cut off at that character, while the page still reported that the file was edited successfully. BriteCore now refuses a title or new file name that contains characters it cannot store and shows a clear message, so the saved title always matches what the user entered.
Duplicate Named Insured on the Auto Quote Contacts Step (BC-27246)
On the Contacts step of the auto quote wizard, clicking Save twice in quick succession could show the same Named Insured twice, and deleting the extra card failed with the message Failed to delete Named Insured. Reason: not found. The second card was for a record that had not actually been saved. The page now ignores a second Save while the first is in progress, and a save that cannot be completed is reported as a failure instead of appearing to succeed.
Legal Entity Type No Longer Filled In When Tabbing Past It (BC-27295)
On the Named Insured form in the Contacts step of the quote wizard, pressing Tab to move past the empty Legal Entity Type dropdown selected the first option in the list, such as Estate, without the user choosing it. Tab now only moves to the next field and leaves Legal Entity Type empty. Clicking an option or pressing Enter on a highlighted option still selects it, and the change applies wherever Legal Entity Type appears on a contact form.
All Tasks View on the Tasks Workbench Showed Only the User's Own Tasks (BC-27353)
On the Tasks Workbench, the All Tasks view and its assignee filter listed only the signed-in user's tasks and those of the people who report to them, where they previously listed every task on the site. A recent change intended for the Underwriting Workbench task queue had also been applied to the Tasks Workbench. All Tasks on the Tasks Workbench again follows the existing tasks access permission, while the Underwriting Workbench queue continues to show all tasks only to users with the Supervisor role.
PDF Attachments Did Not Load in the PDF Viewer (BC-27671)
In Attachments on policies, claims and other pages, opening a PDF with the built-in PDF viewer enabled showed an empty viewer for some files, depending on where the file was stored. These PDF files now load in the viewer as expected. When the PDF viewer is turned off, PDF files continue to open in a new browser tab.
Claim Property Type Is Now a Configurable Lookup List (BC-17826)
On a claim's Damaged Properties tab, the Property Type dropdown offered a fixed set of 12 values that carriers could not change. Property Type is now a lookup list managed in Settings > Lookups Configuration, so carriers can add their own values such as Home, Roof or Kitchen, and rename or deactivate the original ones. The dropdown is searchable, shows the active values in the list's order, and starts a new property on the list's default value when one is set; existing properties keep the value they already have.
Claim Payment Method Hidden on the Agent Portal When Its Setting Is Off (BC-17828)
On the agent portal's claim Accounting page, the Payment History table always showed a Payment Method column, even when the claims setting that controls whether the payment method is shown on claim transactions was turned off. When that setting is off, the Payment Method column is now hidden and the payment method is no longer sent to the agent's browser. Payment History shows the Date, Payee(s) and Amount columns only.
New Actions Menu With New Dispute on the Claim Information Card (BC-18149)
On the claim page, there was no visible way to start logging a dispute: a user had to open the Claim Information Edit dialog, check Disputed Claim, and then find the new Disputes tab. The Bifurcate Claim button in the Claim Information card header is now an Actions menu, next to Edit, with two items: New Dispute and Bifurcate Claim. Each item appears only for users who have access to it, and Bifurcate Claim works as before.
Quick Search Keyboard Shortcuts Now Work on the New Search Pages (BC-18150)
On the Claims Search, Policy Search and Contacts List pages, the quick search keyboard shortcuts, such as g then c for Claim Quick Search, did nothing when the page first opened. The cursor was placed in the page's search box on load, so the keys were typed into the box instead. These pages now open without the cursor in the search box, so the shortcuts work right away; to search the page, click the search box, type, and press Enter. The agent portal search pages are unchanged.
Claim Payments Can Now Be Listed, Searched and Tagged on the System Tags Page (BC-18886)
On the Settings > System Wide > System Tags page, the Claim Payments section of a tag always reported that no claim payments had been tagged, even when payments carried the tag, and Tag New Items > Claim Payments returned no results for any search. The section now lists every tagged payment with its Claim Number, Transaction Date, Exposures, Payees, Status, Amount and tag value, and Tag New Items finds payments by claim number or payee name so their tag values can be edited and saved. Every change to a payment's tag is also recorded as a note on its claim.
Claim Payments Can No Longer Be Saved Without Their Required System Tags (BC-18887)
On the claim page, the Make Payment and Edit Payment dialogs could save a payment without a required system tag when the tags failed to load or were still loading at the moment the payment was submitted. The dialogs now refuse to submit until the system tags have loaded, with a message explaining why. If the tags cannot be loaded, the dialog shows the alert The system tags could not be loaded. with a Try again button that reloads them.
Claim Parties List Failed to Load for a Contact With an Invalid Confirmation Email (BC-22715)
A claim's parties list could fail to load when one party's contact had a stored confirmation email address ending in a period, even though the address was not visible on the contact. The parties list now loads regardless of that stored value. Confirmation email addresses also have surrounding spaces and trailing periods removed whenever they are saved, so the invalid value can no longer be stored.
Claim Numbers Skipped Ahead When a Claim Was Submitted (BC-27378)
For carriers using the newer claim numbering option, where the claim sequence for a policy type uses the same format as the number a claim receives when it is first created, submitting a claim moved it to a higher number and left a gap in the sequence. The claim's own initial number was being treated as a duplicate. A claim now keeps its initial number on submission when no other claim holds it, and protection against true duplicate claim numbers is unchanged.
Required Field Message Stayed on a Filled Vehicle Type When Filing a Claim (BC-27421)
On the File a Claim page in the agent portal, and on the Vehicles tab of a claim and New FNOL for administrators, the add-vehicle form could show "This field is required" under Vehicle Type or Fault Percentage after the field had been filled, left over from an earlier attempt to save. The message now clears as soon as the field has a value and returns only if the field is emptied, and a new or reopened vehicle form starts with no messages. The vehicle itself always saved correctly.
Duplicate Claim Parties After Re-Saving a Policy or Adding an Existing Contact (BC-27498)
On the new claim page, saving a claim again with the same policy re-imported the policy's contacts and created a second party record for every named insured, agent, mortgagee and additional interest. Adding a contact that was already a party through New Party > Search for Existing Contact on the Parties tab could also create a second record. The Parties tab combined the duplicates on display, so later edits to party type, representative or contractor description were saved to only one record and could appear to be lost, while reports saw both. Re-saving the same policy now adds only contacts and roles that are missing, and adding an existing party updates that party.
SQL Editor Excel Export Now Handles Time Values Past 24 Hours and Negative Times (BC-25394)
In SQL Editor reports, a column formatted as Time exported to Excel as plain text whenever the value was 24 hours or more, or negative, so the cell showed text such as 1 day, 2:00:00 and could not be summed, sorted or charted. These values are now written as numbers with an elapsed-time format, so a value of 26 hours displays as 26:00:00 and matches the report preview. Times within a single day export as before.
Failed Documents No Longer Left as Empty Files in Policy Attachments (BC-24719)
In a policy's attachments, a document whose generation failed could remain listed as an empty file that spun for several seconds and then reported that it was not found. This happened when the document was created with a print state other than the two the cleanup looked for, such as Do Not Print on a custom report location, and the file could only be cleared with the Deliverable Recovery Tool. BriteCore now tracks the files each generation attempt creates and removes the empty ones when the attempt fails, whatever their print state.
Custom Deliverables That Check E-Signature Status Failed to Generate (BC-27336)
For custom deliverable templates that check whether e-signature is enabled, such as a Policy Application, the deliverable stopped generating after a recent release. Agents could not complete a submission because the application was not created, and administrators could not preview or create the deliverable. The e-signature check is available to templates again under its original name, so these deliverables generate as before.
Declaration Package Created an Empty Folder When a Form Had a Blank Page (BC-27357)
When a Declaration Package was generated from the Custom Deliverable option on a policy, a policy form containing a blank page caused the whole package to fail. An empty folder was added under Attachments, and the popup still reported "Deliverable created successfully." A form that has at least one page with content is now included in the package as before, and when a custom deliverable cannot be created the user is told that it failed instead of seeing a success message.
Two Payments Close Together No Longer Reinstate a Cancelled Term Twice (BC-26375)
With the billing engine enabled, two payments posted close together on a term cancelled for non-payment could each trigger a reinstatement. This could produce a second reinstatement and fee, or an error that discarded the second payment's processing. The second payment now checks the term's current status first, so the term is reinstated once and both payments are recorded.
Net Commission Counted Twice or Not Paid After a Bill To Change (BC-26664)
On policies using net commission, changing Bill To from the agency to the insured reversed the net commission on the policy's account but left it on the commission records. The Commission Report could then show double the commissionable amount and commission for that policy, some terms were never selected for payment, and changing Bill To back to the agency could credit the account a second time. A Bill To change now settles the commission once, so the commission records and statements show it a single time and it is paid once.
Readable Payment Error When eDatabase Is Unavailable (BC-26872)
When eDatabase returned an unreadable response during an outage, the public payment page displayed the vendor's raw error page next to the failed payment, and the back-office Payment Status window and the policy's Payment Processor Error note showed the same content as raw markup. Nothing told the user whether the charge had gone through. These places now show a plain message explaining that the failure is not a card or bank decline, that the charge may still have gone through, and to check the account balance before retrying.
Name and Email Missing When Adding a Stripe Payment Method from Billing Setup (BC-26926)
On a policy's Billing > Billing Setup page, the Add Payment Method window for Stripe did not include the Name and Email fields that appear when adding a payment method from a contact's Payments page, so the payment method was saved in Stripe without them. The window now includes both fields for staff on Billing Setup and for agents on the agent portal's Accounts Receivable page. Both are required and are saved on the payment method in Stripe.
eDatabase Payments With an Unknown Outcome No Longer Recorded as Failed (BC-27033)
When an eDatabase payment was sent to the processor but came back with an error instead of an approval or a decline, BriteCore recorded it as a failed payment and told the payor it had failed, even though the processor may have charged the account. A retry or the next automatic payment could then charge the same installment again. BriteCore now marks such a payment as having an unknown outcome, tells the payor not to resubmit, adds a Payment Outcome Unknown note to the policy with instructions for staff, and holds further website, phone, staff and automatic payments on that policy while the outcome is open.
Invoice Numbers Mismatched After a Backdated Endorsement (BC-27038)
When a backdated endorsement changed premium or fees, the later revisions that were updated only to carry that change forward each received a new revision invoice number. The invoice number on the billing statement could then differ from the one on the AR Feed report for the same premium change. Those later revisions now keep the invoice number of the revision that changed the premium, so statements and the AR Feed reference the same number. The fix applies to endorsements committed from this release forward.
Return Premium Off by Cents When Minimum Earned Premium Applies (BC-27042)
When a policy was cancelled and the Minimum Earned Premium (MEP) applied, the earned premium posted on the Accounting tab could end up one to three cents above or below the MEP. The return premium and the cancellation notices were off by the same amount. Earned premium now equals the MEP exactly on these cancellations, and cancellations where the MEP does not apply are unchanged.
Secure Checkout Showed the Wrong Current Payment Plan (BC-27117)
On the Secure Checkout payment page, when a policy's current payment plan was not set to show on the public payment page, the payment plan dropdown displayed the first available plan instead, so payors were shown a plan they were not on. If they then changed plans, they had no way to return to their original one. The dropdown now shows and selects the policy's actual current plan, and the payor can switch back to their original plan during the same visit; other hidden plans remain unavailable.
Secure Checkout No Longer Lets Unauthenticated Visitors Change the Payment Plan (BC-27118)
On the public Secure Checkout payment page, a visitor who had not signed in could change the payment plan on an existing policy without making a payment. The change was recorded in the policy notes only as made by the system, and because autopay stayed on, the next automatic payment could draw the full amount due under the new plan. Secure Checkout is now for payments only: payment plan changes on existing policies are limited to signed-in users, and each change is recorded against the user who made it.
Agent Batch Sweep Page Blocked When Batch Sweep Payments Are Disabled (BC-27199)
In the agent portal, an agent could open the batch sweep payments page by typing its address even when batch sweep payments were disabled and no sweep account existed. The Payment Method dropdown then offered the insured's own saved payment methods, and a submission created a sweep payment that could never be processed and stayed in the Payment Log as Pending until it was voided by hand. No charge was made and balances were not affected. The page now redirects to Schedule Sweep when batch sweep payments are disabled, only the agent's permitted sweep accounts are offered, and a request that uses any other payment method is refused before a payment is created.
Installment Invoice Regeneration No Longer Retires the Current Invoice Files Early (BC-27427)
When an installment invoice was regenerated, the check that cleans up older look-alike billing statement folders on the policy also swept the invoice's own current folder, so its pending files could be removed or marked do not print earlier than intended. The check now excludes the invoice's own folder and only cleans up the look-alike folders, leaving the current files to the normal regeneration process.
eDatabase Card Declines Recorded as Payment Processor Errors (BC-27585)
For carriers that process payments through eDatabase, some declined card payments, such as those returned for an exceeded withdrawal limit or an invalid service, were recorded with a Payment Processor Error note instead of as declines. Those payments were missing from the DECLINED section of the Electronic Payments Report, no Payment Declined note was written, and no Card Failure Notice printed. These gateway decline responses are now recorded as declined payments, as they were before.
Check and Cash Payments Could Not Be Recorded Without an Active Payment Vendor (BC-27638)
On Daily Cash Receipt, adding a check, cash or money order payment failed with the message No payment vendor is currently enabled, or with a message that the payment integration is not installed, when no electronic payment vendor was active. The same error blocked deposit receipts, the Payment Log, and voiding, deleting or transferring a check payment. Manual payments can now be recorded and managed without an active payment vendor, while card and ACH payments are still refused with the same message.
Process Commission Payments Acted on Rows That Were Not Selected (BC-27666)
On Payments > Commission Payments, selecting one row on the ACH tab and clicking Process Commission Payments also processed the same payee's other unreviewed commission payments, including manual payments shown only on the Manual tab, which were marked Reviewed without being selected. The result message then counted those rows and read as a failure even when the selected payment succeeded. Process Commission Payments now acts only on the rows selected on the current tab, the result message counts only those rows, and Select All applies to the current tab only.
Agencies with a Zero Commission Balance Stayed on the Delayed Commission Payments List (BC-27688)
On Policies > Agency Commissions, for carriers that delay negative commissions, an agency whose commission entries netted to exactly $0.00 was marked as delayed at month-end export. It then stayed in the delayed commission entries banner and on the Delayed Commission Payments list with nothing owed, unless it later earned new commission or was written off. A zero balance is now settled at export with a $0.00 commission payment, so these agencies no longer appear as delayed; negative balances are still delayed and carried forward.
Billing Schedule Auto-Switch Skipped for Staff and Agent Stripe Secure Checkout Payments (BC-27689)
On sites that use the built-in Stripe checkout, a Secure Checkout payment started from Accounts Receivable by a staff or agent user was recorded as an anonymous public payment. As a result, the policy's billing schedule did not switch automatically and no Billing Schedule Automatically Changed note was written. These payments are now attributed to the signed-in staff or agent user, so the automatic billing schedule change applies again, while payments made by anonymous visitors and insureds through Secure Checkout still do not change the schedule.
Mid-Term Policy Type Change Removing Policy Items and Earned Premium (BC-27753)
In the agent Quote Wizard and on the agent policy setup page, changing the policy type on a mid-term endorsement of a term that already had committed revisions removed all policy items from the revision. When the items were re-entered and the endorsement was committed, the premium earned before the endorsement was lost, which could produce an incorrect return premium or reduced remaining installments. BriteCore now refuses the policy type change in this case, shows a message, and leaves the items and policy type as they were; endorsements already affected are not corrected by this change.
Uploaded Commission Payments Marked Electronic for Agencies Paid by Check (BC-27792)
On Policies > Payments > Pending Commission Payments, Upload CSV marked every uploaded commission payment as electronic, even when the agency was set to be paid by check or had no commission account. Those payments could then fail electronic processing or need manual correction. An uploaded payment is now electronic only when the agency is paid electronically and has a commission account, matching how month-end commission payments are handled; otherwise it is created as a non-electronic payment.
Group Payment Receipt Links on Secure Checkout Now Open the Correct Receipt (BC-20093)
On secure checkout, after a Stripe group payment, some View Payment Confirmation links opened an empty page, and a link that did open could show another policy's receipt. Each row in the results now links to the receipt for that row's policy. The page waits up to about 30 seconds for every policy's receipt before showing the links, a row whose receipt is not ready shows a message that the confirmation is still being prepared, and the emailed group confirmation document no longer appears as an extra row.
Outdated CLUE Loss History After a Named Insured or Address Change (BC-21491)
In the agent Quote Wizard, the LexisNexis CLUE loss history retrieved on the Questions tab continued to be shown, rated and underwritten on after the agent replaced the named insured or changed the property address. BriteCore now detects that the report on file belongs to the previous insured or address and flags it as outdated. The outdated report is checked when the agent submits, when the policy is committed or bound through the API, and when an underwriter approves, so a quote no longer moves forward on another insured's loss history.
Timed-Out Stripe Payments Recorded With Their Original Details (BC-22694)
When a Stripe charge took longer than BriteCore's 60-second limit but still completed at Stripe, the late confirmation created a second payment record labeled Public Web Gateway, with the sweep and auto pay details missing. Reports and receipts could then classify a timed-out sweep or auto pay charge as a one-off public web payment. The late confirmation now completes the original payment record, so the payment keeps the way it was made and one charge has one record.
Add Payment Method Dialog Showed a Blank Stripe Form on Load Failure (BC-23900)
In the Add Payment Method dialog, when Stripe could not load the payment form, the dialog stayed open with a blank payment area and no explanation, and confirming produced an unclear error. The dialog now closes and an alert titled Unable to load payment form appears with the reason Stripe reported. This applies to both the Billing Setup dialog in Accounts Receivable and the dialog used on contacts and in quoting; adding a payment method otherwise works as before.
Automatic Retry When Creating a New Effective Date Hits a Database Conflict (BC-27055)
In Lines, when a new effective date was added and the background copy of line data collided with other database activity, the copy failed at once and the user received a failure email and had to start over. BriteCore now retries the copy once automatically before reporting a failure, so a brief conflict no longer requires the user to run the copy again.
Verisk Address Message Shown Inline on the Classic Property Page (BC-27058)
On the Classic Property page, when Verisk geolocation cannot place an address and the standard geocoder supplies the location instead, the message returned by Verisk now appears as an inline warning directly after the county fields, where it does not block the page. The warning clears when the address or ZIP code changes, a suggestion is picked, or a latitude and longitude are typed by hand. Latitude, longitude and county behavior are unchanged.
Address and Geolocation Corrections on the Classic Property Page (BC-27076)
On the Classic Property page with Verisk geolocation, several edge cases in address handling were corrected. Picking a second address suggestion before the first finished saving could leave the earlier address saved, and a failed ZIP code lookup after a successful address match could leave the previous county and map on screen. The latest pick is now the one saved, the county and map no longer carry over from a previous address, and Open Map and HazardHub wait for the location lookup and do not run when the property has no coordinates.
Claim Service Activity Errors No Longer Reported as Duplicates (BC-27241)
When a claim service vendor sent an activity that BriteCore could not save because of a data error, BriteCore told the vendor the activity was a duplicate. Because vendors do not resend duplicates, the activity was lost without any error being reported. Only an activity that was truly already recorded is now reported as a duplicate; any other failure is returned to the vendor as an error.
Overlong Vendor Identifiers Refused on Claim Service Calls (BC-27242)
Inbound claim service calls from vendors accepted financial, event and decision identifiers longer than 255 characters and stored them cut short. A repeat of the same call was then answered as a duplicate without a reference to the stored record, so duplicate detection did not work for those identifiers. BriteCore now refuses an identifier that is too long, or that is not text, with a validation error naming the field, and nothing is stored.
Loss History Report Number Kept on Out-of-Sequence Endorsements (BC-27450)
When an out-of-sequence endorsement was merged into later revisions, a property's stored loss history report number could be cleared on the future revision while the report content was kept. This happened on sites using only the Verisk loss history integration, when the claims major and minor setting was on, or when the stored report could not be read, and the property's report was then treated as corrupt. The merge now carries the report number and its content forward together from the same revision, so the stored report on the future revision reads correctly.
Vendor Event Times Shown Hours Late on the Claim Services Tab (BC-27502)
On the Services tab of a claim, event times received from claim service vendors such as Copart and CCC were displayed later than they actually occurred, by the difference between the site's time zone and UTC. An event could even appear to have happened after BriteCore received it. Vendor event times are now converted to the site's local time when they are stored, so the Services timeline shows when each event actually happened.
Rejected Policy Type Requests No Longer Save a Partial Policy Type (BC-16037)
The API endpoints that create and modify policy types could save part of a request they rejected. A request with duplicate sub line or line item references returned a validation error but still saved a partial policy type, and a request that repeated the same sub line or item ID was not validated at all. Both endpoints now reject these requests with a clear message that the Subline ID or Line Item ID must be unique, and nothing is saved when a request is rejected.
Related Coverages Dialog Skipped Mandatory Coverages When Closed With the X (BC-24371)
In the Quote Wizard for property policy types, closing the Related Coverages dialog for a Line Item Group with the X in its header did not add the group's mandatory coverages, so a quote could proceed without them. Mandatory coverages are now added however the dialog is closed: Cancel, the header X or the Escape key. When one addition triggers several Line Item Groups, the dialogs now open one at a time instead of stacking on top of each other.
Line Item Groups With Both Policy and Property Coverages in the Quote Wizard (BC-24372)
In the Quote Wizard, when a Line Item Group contained both policy-level and property-level coverages, adding one coverage tried to add the others to the same place. Some coverages were silently left off with no message to the agent, or a policy-level coverage appeared under a property until the page was refreshed. Each coverage in the group is now added at its own level, property-level coverages are not offered from the policy-wide section, and any coverage that cannot be added is listed in a single error message.
Related Coverages Dialog No Longer Opens When an Underwriting Rule Adds a Coverage (BC-24374)
In the Quote Wizard, when an Underwriting Rule with an Add Line Item effect added a coverage that belongs to a Line Item Group, the Related Coverages dialog opened while the rules were still running. The dialog could appear behind the processing overlay where the agent could not click it. Coverages added by a rule are now added without opening the dialog, as they were before Line Item Groups were supported in the Quote Wizard.
Auto Quotes Without a Driver Return a Clear Validation Message When Rated (BC-26570)
When an Auto quote with vehicles but no drivers was rated through the full-quote API endpoint, the response contained a raw system error instead of an explanation. That path now runs the same checks as interactive rating, so a quote with no driver, no vehicles, no quote coverages, or a vehicle with no coverages is refused with the same validation message. Other policy types are unaffected.
Rating Reports an Invalid Rating Combination Instead of a System Error (BC-26572)
During rating, if a factor in a rate calculation resolved to something other than a number for a particular combination of rating categories, the response contained a raw system error. Rating now returns the existing invalid combination of Rating Information message, naming the line item, the categories involved, and the calculation, so the configuration can be corrected.
Supplemental Questions in Lines Showing Outdated Values After a Save (BC-26573)
In Lines, after supplemental questions were saved on the Edit Line Item page, reloading the page could show the questions as they were before the save, with different reloads showing different versions. Saving from one of those outdated pages wrote the old questions back over the newer edits. Supplemental questions are now read fresh every time, so each load shows the saved values and a save no longer reverts earlier changes.
Warning When a Line Item Calculation Reads an Item Name Used on More Than One Sub-Line (BC-27488)
In Lines, two items on different sub-lines of a policy type can share the same name, and a calculation that reads that name receives one combined entry: custom variables come from the first item, while premium, limits and deductible are added together. Nothing told the person configuring the line, so an eligibility check could silently read the wrong item. The Edit Line Item screen now shows a warning on save that names the item, the sub-lines that use it and the items that read it; choosing OK saves and Cancel stops the save. A matching warning is also written to the rating log, and rating results are unchanged.
Configuration Promotion Failing for Policy Types With Category-Based Rating Steps (BC-27504)
In Configuration Promotion, some policy types could not be previewed or exported, and showed the message "This policy type cannot be previewed" with an unsupported cross-reference type error. This happened when an item's rating steps included a categories step, because category references were also being applied to unrelated steps in the same rate chain. Category references are now kept on the categories step only, so these policy types preview, export and import as expected.
Non-Premium-Bearing Endorsements Now Carry Forward to Renewal Terms on a New Lines Effective Date (BC-11786)
On policies that had already renewed for a future term under a newer lines effective date, a non-premium-bearing endorsement made on the current term, such as a mortgagee change, was not carried forward to the renewal revision and had to be keyed again by hand. These changes now carry forward to the renewal revision when the endorsement is committed, including when a same-date correcting endorsement replaces an earlier one.
Copy Builder Information Error When Moving an Agency-Billed Revision to a Newer Lines Effective Date (BC-18570)
On the policy page, reselecting the policy type with Copy Builder Information checked failed with an error and rolled Builder back when the revision's agency was on agency billing and the revision still carried items that do not apply to agency billing. The revision stayed on the older lines effective date and could not be committed. The revision now moves to the newer lines effective date, and Persistent Builder lists those items as removed with the reason Not Applicable for Agency Billing, so the policy can be rated and committed.
Attachments Can No Longer Be Relabeled as Form (BC-26073)
On sites that include forms as attachments when printing, the label Form is reserved, and files carrying it are left out of the print queue. An attachment such as a Declaration on an uncommitted revision could be relabeled to Form, which removed it from printing with no way to change it back. BriteCore now refuses that relabel, and the label editors for photos and attachments show the refusal message and restore the previous label instead of appearing to save.
Agent Endorsements Losing Coverages at the Quote Wizard Setup Step (BC-26462)
In the agent Quote Wizard, continuing past the Setup step on an endorsement could remove every coverage and item from the policy change. Agents then saw "There are no coverages or items on this policy. Add some to continue rating." on the Rating step, with a premium of $0. This happened on policies first written under an older lines effective date than their current term. Endorsements and renewals now keep the product they already hold unless the agent selects a different one. Suspend Quoting rules are also no longer applied to endorsements, since the policy is already in force.
Quote Creation No Longer Fails on Circular Rate Chain Dependencies (BC-26671)
When Lines contained items whose rate chains referred back to each other through two or more items, creating a quote through the API that added one of those items failed with a system error. Quote creation now detects the circular reference, skips the repeated step, and completes the quote.
Duplicate Policy Renewed Entry After Reinstating an Expired Policy (BC-27102)
In the Policy Changes history, reinstating an expired policy recorded two policy renewed entries, one of them attached to the previous term where it might not appear with the new term. A reinstatement now records a single policy renewed entry on the new term's revision. Duplicate entries created by earlier reinstatements are not changed.
Removing a Location Now Handles Its Bill Whom Mortgagee (BC-27236)
On a policy endorsement, removing an entire location did not behave the same way as deleting that location's mortgagee directly. When the mortgagee was the selected Bill Whom, it stayed listed in Accounts Receivable and remained the billing recipient, and the endorsement could be committed without any warning. Removing a location or a property group now records the mortgagee removal notes, removes the mortgagee from Accounts Receivable, resets the billing information, and shows the BILLING INFORMATION HAS BEEN RESET warning.
Slowness During Attachment Uploads, Builder Navigation and Reinstatements (BC-27365)
On policies, users could experience long delays, in some cases around 90 seconds, and an unresponsive interface while processing reinstatements, moving through the Builder tab, or attaching and uploading files. Attachment uploads and estimated quote calculations were holding a policy's records for the full length of the operation, which made other actions on the same policy wait. Both now release those records sooner, so other work on the policy is no longer blocked behind them.
Policies Could Not Be Opened When a Credit Score Matched No Credit Tier (BC-27406)
In the agent portal, a policy whose insured had a credit score outside every configured credit tier could not be opened: the page reported that the policy could not be loaded, which also blocked Accounts Receivable, Policy Setup and the attachments tab. These policies now open normally, with no credit class or credit restriction applied, and Policy Setup shows "Credit score fits no credit tier" under Credit so the agent can order credit again. Rating is unchanged.
Forms Added by an Endorsement or Renewal Not Attached to the Declaration (BC-27472)
When an endorsement or renewal added a coverage or other item that carries a form, the new Declaration could list the form but leave it out of the attached forms and the printed package. This happened when the same form had appeared on any earlier Declaration in the policy's history, even in a prior term, and on converted policies in their first term. BriteCore now compares each revision with the previous committed revision, so a form the revision brings in is attached and printed once, and forms that were already in place are not sent again.
Renewal Custom Deliverables Printed on Endorsements Dated on the Term Effective Date (BC-27684)
When an endorsement dated on the term effective date was committed over a revision already committed on that date, BriteCore generated every Custom Deliverable marked Print on Renewal Declarations and set it to print, even on a new business term. Insureds could therefore receive renewal documents, such as a renewal cover letter, with an endorsement. These endorsements now behave like any other mid-term endorsement and produce the Amended Declaration without the custom deliverables.
Subjectivity Popup Now Shows the Specific Reason a Save Failed (BC-19128)
On the policy page, the Add/Modify Subjectivity popup showed only a generic failure message when a subjectivity could not be saved, for example because of an invalid due date, so the user could not tell what to correct. The popup now shows the specific reason for the failure, and the Mark as Satisfied icon in the revision header does the same. The generic message remains only when no specific reason is available.
Home Page No Longer Loads Blank When Wizard Text Contains a Quotation Mark (BC-20162)
The home page loaded blank when a configured quote wizard label or placeholder contained an apostrophe or a quotation mark, such as the word Insured's. The page now handles this text correctly and loads as expected, with the punctuation shown as written.
Clear Rating Message When a Property Address Cannot Be Located (BC-21490)
When rating a quote, a property whose address could not be placed on the map was saved without a location, and rating that depends on location factors then failed with a technical error that gave the agent no way forward. Rating now returns a readable message that names the property and asks the user to verify the property address and save it again, or to contact underwriting if the address is correct. The same message is returned for quotes rated through the ACORD API endpoint.
Agent Application Submission Left Incomplete When Document Generation Failed (BC-24345)
On the Finalize step of the quote, clicking Submit Policy Application could fail partway when generating the Policy Application document ran into a database conflict. The policy received a number and appeared as Submitted to administrators, while the agent remained on the Finalize step with a message to contact support and no submission documents were stored. Document generation is now retried automatically when this conflict occurs, so the submission completes.
Removed Endorsements Reappeared in the Agent Quote Wizard (BC-26743)
In the agent Quote Wizard, underwriting rules that add line items ran again each time the agent opened the Application Questions step. Endorsements the agent had removed on the Rating step were added back and the rate was cleared, so submitting the quote failed with a message that it must be rated. Items an agent removes now stay removed as they move between steps, the rate is kept, and a rule adds its items again only when one of its triggers changes; mandatory items are still added.
Full Question Text Shown in Extra Information on Auto Quotes (BC-27309)
In the Extra Information section for vehicles, watercraft and drivers on an auto quote, long underwriting questions were cut off with an ellipsis, so users had to answer without being able to read the whole question. Each question now appears on its own full-width row, with the complete question text on the left and the answer control on the right, and the text wraps onto as many lines as it needs. On narrow screens the answer control moves below the question. Questions shown on coverage cards keep their existing layout and are no longer cut off.
Extra Unexpected Error Popup on Agent Quote Submission (BC-27339)
On the Policy Setup page in the agent portal, when a submission was stopped by validation, for example the message listing the actions that must be completed before submitting an application, a second popup reading "An unexpected error occurred during submission" opened on top of it. Only the validation message now appears, so agents can see exactly what needs to be completed.
Rate & Save Re-Adding Optional Coverages the User Removed (BC-27780)
In the Classic Builder, in both the back office and the agent portal, Rate & Save added back an optional coverage that an underwriting rule had added and the user had then removed. Users could not proceed without keeping the coverage, and it was included in the rated premium. Rate & Save now runs these rules on save only for Auto and Umbrella policy types, as it did before, so a removed optional coverage stays removed on other policy types.
Generated Forms Could Be Relabeled Back Into the Print Queue (BC-27075)
On attachments, a generated form is identified by its Form label and is protected from being relabeled. When the stored label differed only in capitalization, accents or trailing spaces, that protection did not apply, and relabeling the attachment could put the form back into print selection and cause a duplicate print. These variants are now recognized as the Form label, so generated forms can no longer be relabeled this way.
Required Report Parameters Now Validated by the buildXLSReport API Endpoint (BC-27473)
When a SQL Editor report was launched through the version 1 buildXLSReport API endpoint without a required parameter, such as an as-of date, the API endpoint returned a success response and the report run failed later. The API endpoint now returns an error naming the missing required parameters before anything is launched, and parameters that have a default value are filled in automatically, matching the version 2 run_report API endpoint. Requests that already supply their parameters, and reports delivered as a saved file, work as before.
Rule-Added Line Items Placed on the Wrong Sub Line Instance (BC-24387)
When an Underwriting Rule with an Add Line Item effect ran on a policy with two or more instances of the same sub line, the added item could be attached to a different instance than the one whose item triggered the rule, and the result could vary between runs. The added item is now placed on the sub line instance that triggered the rule. Policies with a single instance of the sub line were not affected.
Note Text Always Displays as Plain Text in Policy Change Popups (BC-27192)
In the Endorsement Review and Show Policy Changes popups on policy pages, the title, author and contents of a note were displayed without being treated strictly as text. A note containing markup, such as one created from an uploaded property photo with a specially crafted file name, could therefore be interpreted by the browser instead of shown as written. These values are now always displayed as literal text, and line breaks in notes continue to display correctly.
Account History Description Displayed Entered Markup (BC-27397)
In Accounts Receivable, the Description shown under Details when an account history row is expanded displayed free text, such as a return premium reason, exactly as it was stored, including any HTML markup typed into it. The description is now cleaned before it is displayed, so entered markup is removed and only the text is shown. Line breaks that BriteCore adds before notices in the description are kept.
Workflows Buttons No Longer Rotate While Loading (BC-27442)
In the Workflows module, a button in its loading state rotated as a whole instead of showing only its spinner icon. This affected Refresh on the Execution Log, the Refresh, Resume, Retry and Restart buttons on Run Detail, and Revert, Publish and Delete on Workflow Detail. Loading buttons now stay still while only the spinner icon turns, and the standalone loading indicators in Workflows turn at the same speed as loaders elsewhere in BriteCore.
Credit Pulls Refused for Agencies the User Cannot Act For (BC-26049)
When a credit report is ordered for a contact through the API endpoint with a specific policy revision, the agency on that revision is billed for it. BriteCore did not check that the caller was allowed to act for that agency, so a caller could cause a different agency to be billed. The revision now decides billing only for carrier users, the agency itself, its agents, an agency group that contains it, or the agent who created or is assigned to that revision; any other request is refused with a message explaining why, no report is ordered and nobody is billed. The response also now states which agency was billed.
IVANS Policy Change Downloads Reported Full Term Premium for Non-Premium Changes (BC-26907)
In the IVANS download, a policy change transaction caused by an edit that does not change premium, such as an insured name or address change or a mortgagee update, reported the policy's full term premium as the premium change amount. Agency management systems then booked premium that had not changed. These transactions now report a premium change of 0.00 while still carrying the current term premium, and policy changes with a real premium change continue to report the actual difference.
360 Value Valuation Failed When a Different Home Type Was Selected (BC-26910)
When starting a 360 Value valuation on a property that already had a valuation under a different home type, for example choosing Manufactured/Mobile after a 1 to 4 Family valuation, BriteCore tried to reopen the existing valuation and 360 Value returned an ERR04 error. BriteCore now reopens an existing valuation only when it matches the selected home type and otherwise starts a new one. Valuations completed before this change are treated as 1 to 4 Family.
LexisNexis Property CLUE Alerts and Consumer Statements on Secure Internet Connections (BC-27313)
When the LexisNexis Property CLUE vendor was set up for a Secure Internet connection, BriteCore did not read the consumer alerts and consumer or record statements returned with a report, such as an identity theft alert, fraud alert, legal hold or security freeze. Users saw no warning when they retrieved loss history, and a report that LexisNexis withheld because of an alert appeared as an empty loss history with no explanation. BriteCore now reads these alerts and statements on Secure Internet connections and shows them on the loss history screens, as it already did for the older VPN connection.
Resending Selected Policy Transactions to IVANS (BC-27383)
For the IVANS download, the process BriteCore support uses to resend past policy transactions for a chosen list of policies was too slow to cover a long date range and could silently leave out policies whose numbers were entered with or without the term suffix. It now selects the requested policies before building the transactions, accepts either form of the policy number, and stops with a clear message when a policy number is not found. Errors raised while building IVANS transactions also now report the actual cause.
Saved Motor Vehicle and Credit Report PDFs Were Removed After Viewing (BC-27417)
On the Contacts tab of a policy, opening a saved motor vehicle report or credit report with the magnifying glass removed the stored PDF after it was displayed. The next attempt showed an error, and for reports older than 100 days the message "This report is older than 100 days and cannot be viewed. Please pull a new report." appeared on every attempt. Saved vendor report PDFs are now kept when viewed, so they can be opened repeatedly.
PNC PayerExpress Nightly Payment Status Check Failing Silently (BC-27494)
For carriers using PNC PayerExpress, the nightly Transaction Search Report that updates pending payments to approved or declined could fail for every payment without leaving any record on the payment or in the logs. In addition, one payment with incomplete transaction details stopped the check for all payments after it, and payments older than one month, including agent sweep payments, were never checked again and could stay pending indefinitely. Failed lookups are now recorded against the payment, a single problem payment no longer stops the run, and older pending payments are included in the check.
Aged Accounts Receivable Report No Longer Lists Paid Terms (BC-25255)
The Aged Accounts Receivable report could leave out older payments whose original revision no longer existed, so fully paid terms appeared with an open balance. These payments are now included, and paid terms no longer appear on the report.
Correct Deferred Premium in Monthly Payoff Amounts Runs (BC-26392)
When the Payoff Amounts report was run for a single month, terms with no accounting activity in that month showed $0 Deferred Premium and their whole unbilled balance as Premium In Course Of Collection. Monthly runs now show the same deferred premium as longer date ranges.
Standard Fire Quotes Rate With $0 Coverage B in the Quote Wizard (BC-26470)
In the Quote Wizard, a Standard Fire quote could not be rated unless Coverage B for private structures had a scheduled row worth more than $0, which blocked most dwellings with no outbuildings. These quotes now rate with Coverage B at $0, as they do in classic quoting.
Quote Wizard Setup Keeps the Policy Type the Agent Chose (BC-26473)
On the Quote Wizard Setup step, the policy type the agent selected could silently switch back to the line's first policy type when the list of available policy types changed. The chosen policy type now stays selected.
Quote Wizard Rates Quotes With Categories Left on Their Default (BC-26475)
In the Quote Wizard, leaving a visible rating category on its placeholder, such as Please Select an Answer, stopped the quote from rating, and the error could appear on a different field. These quotes now rate the same way they do in classic quoting.
Accounting Detail Report Reverses Deferred Premium Once on Cancellation (BC-26628)
In the Accounting Detail Report, a cancellation that voided invoices billed before it reversed Change In Deferred Premium a second time, leaving a negative deferred premium on a fully reversed term. The cancellation now reverses only the amount actually booked, so balances end at $0.
System Tags Can Be Added to Claims (BC-27852)
Users with the right permissions could not add system tags when creating a claim or editing an existing one. System tags can now be added to new and existing claims.
Synced Rating Categories No Longer Overwrite Other Items in the Quote Wizard (BC-27899)
In the Quote Wizard, a rating category set to sync across line items was copied to every other item each time it changed, so items such as Coverage A and Coverage C could not keep different values, for example different construction types. Items now keep their own values, as they do in classic quoting, and the quote rates correctly.
Quote Wizard Setup Keeps Underwriting Answers After an Effective Date Change (BC-27929)
On the Quote Wizard Setup step, underwriting answers saved for a replacement product could be removed when a later change to the effective date made that product unavailable. These answers are now kept.
Bound or Unbound Message Shown on the Quote Wizard Application Step (BC-27993)
When bound submission was turned on but not allowed for a quote, the Application step of the Quote Wizard showed neither the Submit Application Bound checkbox nor the message that the application will be submitted unbound. Agents now see the message, so they know the application is going in unbound.
New Features and Enhancements — In Testing
Vehicle Condition at Time of Loss and Repossession Loss Payee on Auto Claims (BC-26213)
On auto claims, each vehicle can now carry a Vehicle Condition at Time of Loss of None, Parked / Unoccupied or Auto Repossessed. Choosing either no-driver condition hides the vehicle's Driver field and clears its driver after a confirmation, and Auto Repossessed opens an optional Loss payee block where the user can pick a loss payee from the policy in force on the loss date or find, import or create a contact. The payee appears under Parties as Loss Payee, and history notes record each change. The feature sits behind a new claims setting that is off by default, so claims are unchanged until it is turned on.
Shared Review Instructions for Automated Code Review (BC-27649)
BriteCore added a shared set of review instructions to its code repository for use by its internal automated code review. No application code uses it, so nothing changes for users.
Packages Page Under Lines > Forms Library (BC-26683)
A new Packages page is available under Lines > Forms Library, where an administrator selects a policy type and sees every part of its Declaration Package in the order it will print. Customize Order opens the priority fields for editing, deliverables can be added to or removed from the package, Reset to Default Order clears every saved priority after a confirmation, and Preview Package lists the parts that will print, including edits not yet saved. Users without write access to Lines see the page as read-only.
Nightly Runner for Billing Engine Timers (BC-25641)
In nightly processing, BriteCore added a runner that picks up billing engine timers due on or before the processing date and fires each one once, after confirming the policy term is still in the state the timer was set for. A timer whose term has moved on is cancelled without firing. No timer group is enabled in this release, so nightly processing output is unchanged on every site.
Nightly Billing Ledger Consistency Checks (BC-27155)
BriteCore added five read-only nightly checks to its internal quality assurance runs for billing. They confirm that each term's balance matches its ledger entries, that billed premium matches written premium, that no invoice remains after a cancellation date, that a cancellation produces no duplicate adjustment or refund, and that each due date carries at most one late fee. The checks do not change billing behavior.
Safeguards to Keep the Configuration Promotion Package Format Current (BC-27730)
For promoting product configuration between environments, BriteCore added internal checks that keep the configuration package format in step with changes to the system, such as database changes and new settings. A change that would leave the package format outdated, or that alters the format without a new package version, is now caught before it is released. This helps packages continue to carry the complete configuration from one environment to another.
Rebuilt Permissions Page with Review Before Save (BC-27569)
The Settings > System Wide > Permissions page has been rebuilt with Permission Levels, Role Assignments, User Group Assignments and Options tabs, and it loads one permission level at a time instead of everything at once. Changes are no longer saved on every click: edits are staged, marked as added, changed or removed, and saved only after the user confirms them in Review and Save. A locked rule can no longer be edited or removed until it is unlocked, and the path field for a rule now offers autocomplete and refuses empty or invalid paths.