Enhancements
New Claims experience | Claims Notes Content Field Improvements (BC-20568)
Claims adjusters needed more flexibility in how claim note content was captured. BriteCore no longer requires content in the note, only the title.
Report Retrieval API Enhancements (BC-20884)
Machine users authenticated via BriteAuth can now successfully access the /api/v2/reports/retrieve_reports endpoint. This change restores API-based report retrieval, enabling automated workflows and faster access to reporting data.
Adding an Additional Interest Type for STP Configurations (BC-20913)
This change is specific to Straight-Through Processing (STP) rules and adds the ability to expose and reference an Additional Interest type within STP configurations. As a result, the STP engine can apply automation rules based on the presence and classification of Additional Interests, improving control over eligibility, routing, and automated decisioning while increasing transparency into how Additional Interest details influence processing outcomes.
Remove Read-Only Notification Icon for BriteData Reports (BC-21108)
The read-only icon for BriteData reports has been removed from the report list. This change reduces visual clutter and makes the report list easier to scan and use.
Changing Privacy Settings to Attachment Folders and Contents (BC-20820)
In Claims, when a folder’s privacy setting is changed to Public, the system will now automatically apply that same Public setting to the items contained within the folder. This helps ensure visibility is consistent and reduces the need to manually update privacy on individual items after making a folder public.
SQL Editor – Date Formatter Time Zone Changes (BC-21098)
In the SQL Editor table preview, date formatters were incorrectly applying a time zone offset, causing dates to appear as the previous day for users in GMT-X time zones. This has been corrected, so dates now display accurately and consistently with the underlying query results.
DocuSign Anchor String Support (BC-19897)
Document signatures required a more precise placement of the anchor strings. This enhancement improves signing accuracy and reduces document rework.
E-Signature Support for Dynamic Document Templates (BC-20554)
This enhancement supports DocuSign e‑signatures for Dynamic Documents by adding signature anchor metadata to the template context, enabling templates to control where signatures are placed. It also supports multiple agents and insureds by generating anchors in sequence for all required signers.
Separate Min/Max Payment Enforcement (BC-20760)
This enhancement splits payment amount enforcement so minimum and maximum payment rules can be managed independently for Secure Online Payment and Accounts Receivable. Previously, a single configuration applied the same enforcement across both channels, which constrained internal servicing scenarios that required more flexible payment entry. The change preserves existing behavior by defaulting the new settings to match the prior single-setting configuration unless explicitly adjusted.
New Revision History User Interface (BC-20816)
The Revision History screen has been updated with a cleaner layout that makes it easier to review policy changes over time, including an expand option to see coverage-level premium changes and a more visible Declarations Generated indicator.
To use the expand option:
- Open a policy and select Show Revision History.
- Review each revision’s effective date, policy status, endorsement date, revision state, and premium before and after the change (including the difference).
- Select a row to see which coverages drove the change.
To allow agents to view revision history through the Accounts Receivable screen, enable the display_revision_history_ar_agent advanced setting.
Tagging Policy Attachments to use in Straight Through Processing
Policy attachments uploaded in the Quote Wizard for New Business, Endorsements, and Renewals can now be tagged with a File Type selected from a dropdown at upload time. This File Type is a business document category (not the file’s technical format like PDF/JPG), making it easier to identify what was submitted and enabling more reliable Straight-Through Processing (STP) validation and routing based on required document tags. The available File Types come from the configurable lookup table, which includes default values and can be extended to support customers’ use cases. In addition, the policy’s attachment page has a new look and feel.
Updated Policy Attachments Experience
The Policy Attachments screen has been refreshed to align with the Claims Attachments experience, delivering a more consistent and streamlined way to upload, organize, and manage documents across BriteCore. Users can now tag attachments with a searchable Type, add optional Descriptions, and view this information directly in the attachment list and file details. Enhanced search by Type makes it easier to find documents on policies with large attachment volumes, while updated edit functionality allows existing files to be renamed or reclassified without losing prior data.
Defects
SQL Editor – Text Report Delimiter Fix (BC-20785)
Text reports generated with the delimiter set to None no longer default to tab-delimited output. Selecting None now produces output with no delimiter between columns, while all other delimiter options continue to behave as expected.
New Written Premium Commission Algorithm (BC-19559)
Multiple issues were corrected in the written premium commission calculation. Flat cancellations were incorrectly producing a small commission (e.g., $0.01) instead of zero, and commissions after mid-term rate changes were not using the original rate as expected. Users can expect more reliable commission processing with greater reliability for premium commission calculations.
NSF Cancellation Processing (BC-16066)
BriteCore fixed an issue where an NSF payment on a policy that had previously been placed into Cancellation Pending – Non-Payment could incorrectly generate a second non-pay entry, assess an additional non-pay fee for the same invoice, and reset/extend the policy’s cancellation date. With this update, when the NSF is processed using the Allow policy to cancel option, BriteCore reactivates the original non-pay so the original cancellation date is honored and duplicate non-pay fees are not charged.
Credit Score Not Found Error (BC-20874)
When a credit score could not be retrieved, the system returned an error instead of handling the situation gracefully. The issue has been resolved, so users can continue their workflow without interruption.
Duplicate Payments (BC-18184)
BriteCore fixed an issue where manual payments submitted from the Daily Cash Receipt (DCR) screen could be unintentionally submitted twice, resulting in duplicated (doubled) payments—sometimes showing auto-filled details instead of the values entered by the user. The update adds a submission lock to prevent duplicate submissions triggered by rapid or overlapping user actions (e.g., double-clicking Add or pressing Enter and clicking Add).
Delayed Commission Dialog (BC-18970)
BriteCore fixed an issue where users had to write off delayed commissions one entry at a time by letting them write off all delayed commission entries for an agency in a single action. The update also requires users to select a reason (Collected from Agency or Forgiven) and record an explanation.
Task Age Display Error (BC-20886)
Task date handling has been improved to ensure accurate and consistent displays across the Task Workbench and Task Detail views: task age no longer appears as NaN, task creation dates no longer default to 1/1/1970, and task due dates no longer shift based on the user’s time zone, ensuring the same due date is shown everywhere.
Restore Delete Button in BriteData (BC-21020)
The Delete button has been restored for BriteData reports. This allows users to delete reports as needed, supporting normal data cleanup and corrections.
Fix for E2Value Page Load Failure (BC-19516)
BriteCore fixed an issue where sometimes the E2Value Replacement Cost Value screen would error out instead of rendering when Dynamic Documents was enabled. The fix ensures the E2Value callback screen is rendered without invoking Dynamic Documents for this workflow, avoiding template resolution failures and allowing the E2Value submission to complete normally.
SQL Editor Output Filename Preservation (BC-21039)
Custom output filenames are now reliably preserved when loading and exporting reports. Previously, filenames could be overwritten during report initialization, causing names set in SQL Editor to revert unexpectedly. This has been corrected to prevent unintended changes.
Base Policy Number Retrieval (BC-21073)
BriteCore fixed an issue where policy lookups could fail in environments using custom numbering configurations and prevent the system from finding an existing policy. With this update, policy number handling now only evaluates policy-specific numbering sequences, improving accuracy and restoring reliable policy retrieval in affected workflows (including document preview scenarios).