Enhancements
Announcing the General Availability of SQL Editor (BC-18629)
BriteCore’s SQL Editor custom reporting environment has been promoted to General Release, making advanced SQL-based custom reporting and analytics broadly available. This general release signifies that this custom reporting solution is now production-ready for BriteCore users. Product documentation, including a curated list of pre-built SQL reports, is available on BriteCore’s help site.
Automatic cover page for Excel reports in SQL Editor (BC-18724)
Excel report generation in BriteCore’s SQL Editor custom report environment was enhanced to include an automatically generated cover page for all exported reports. This feature provides a professional and consistent front page, which can be used to display summary information, report metadata, or custom branding. The addition of a cover page improves the usability and appearance of new custom reports, streamlining communication with stakeholders who rely on these documents for analysis or regulatory submissions.
Validate sheet name in SQL Editor (BC-18681)
The BriteCore SQL Editor custom reporting environment now validates Excel sheet names to prevent the use of invalid characters such as [], :, *, ?, /, and , which are not supported by Excel. This validation helps avoid report generation errors and ensures compatibility with downstream tools that consume these Excel files. When users attempt to generate a report within SQL Editor with an invalid spreadsheet name, BriteCore provides an error message, prompting correction before proceeding.
Add claim transaction system tags in SQL Editor (BC-18671)
Claim transaction system tags are now available within the SQL Editor, enhancing the ability to filter, report, and analyze claims data for advanced reporting needs, including regulatory reporting. This addition allows users to classify and extract claim transaction information with greater precision, supporting compliance and operational analysis.
Delivering dynamic fields to generate custom deliverables for policies in legacy claims UI (BC-18461)
The BriteCore Platform now supports the generation of custom deliverables with dynamic fields for policies, including both the admin and legacy claims user interfaces. New pop-up dialogs were introduced for entering dynamic field values, allowing users to create custom letters and communications directly from the BriteCore Platform.
Defects
Improved process to create, publish, delete, rename, and re-create when re-using names for reports in SQL Editor" (BC-18630)
When reusing report names, the process for creating, publishing, deleting, renaming, and re-creating SQL Editor reports now works seamlessly when it hadn’t before. Previously, deletion logic prevented users from re-using the same report name, causing workflow disruptions. This latest update ensures that the full report lifecycle is user-friendly and robust.
Resolved issue with "Print to Deposit" on Daily Cash Receipt page (BC-18742)
An issue was resolved where the "Print to Deposit" functionality on the Daily Cash Receipt page was not working as intended and users saw a message "Please resolve all payments for policies". The defect was corrected, restoring the ability for users to print deposit documentation directly from the page.
Resolved issue with fees appearing incorrectly on Daily Cash Receipt PDF (BC-18706)
A defect was fixed where fees were incorrectly appearing on the Daily Cash Receipt PDF, even for payment types such as cash or cheque where fees should not be displayed. This occurred because the fee calculation logic did not properly filter out certain payment instruments, resulting in misleading receipt documentation. This issue has been resolved.
Resolved issue with Secure Payment appearing on Daily Cash Receipt page (BC-18705)
An issue was corrected in which electronic payments made via the Secure Payment page were appearing on the Daily Cash Receipt (DCR) page, even though the DCR is intended only for cash, check, and money order payments. The logic now filters payment instruments appropriately, excluding electronic and ACH payments from DCR calculations.
Resolved issue with empty radio buttons appearing on Quote Wizard Billing Page (BC-18694)
A visual defect was resolved on the Quote Wizard Billing page, where radio buttons appeared blank or unpopulated, resulting in user confusion. Now all required radio button options are populated and selectable, restoring normal billing workflow.
Underwriting Rules - Displaying pop up message missing from effects option (BC-18608)
A user interface defect was resolved where the option to display a pop-up message as an effect in Underwriting Rules was no longer available after a recent screen update. The option to display a pop-up message has been restored in the effects list.
Correcting renewal error when first revision was not committed (BC-18555)
A renewal processing error was fixed where attempting to renew a policy with an uncommitted first revision would cause the process to fail, particularly when accident and violation integrations were enabled. This latest update ensures that available dates are used where present, allowing renewals to proceed smoothly.
Corrected inability to add claim notes (BC-18262)
A defect was fixed where the “New Note” button in the Claims module’s Notes tab was non-functional, preventing users from adding claim notes. The update restored note creation capability, supporting better claim documentation and communication.
SQL Editor v_recoveries missing Reinsurance values (BC-18034)
A defect was corrected where recoveries related to reinsurance were not properly reflected in financial reports generated in BriteCore’s SQL Editor due to a typo in the logic extracting reinsurance change data. The update ensures an accurate population of reinsurance values, improving financial transparency and reporting reliability.
Resolving issue where agent quoting bypassed mandatory re-rating (BC-17946)
A defect was fixed where agents could bypass mandatory re-rating checks and print quote summaries before a quote had been properly rated. The corrected logic ensures that the quote summary is only available after a successful rating, preventing incomplete or inaccurate summaries and improving rating integrity.
"Use eDelivery" checkbox not tracked correctly(BC-17683)
An issue was fixed where, after adding an email for the insured, selecting the “Use EDelivery” checkbox failed to correctly send the e-delivery invitation. The UI previously did not transmit the correct value for the checkbox after adding a missing email, causing silent failures. The fix ensures that the checkbox state is always sent correctly, so that invitations are reliably issued when the user intends to use e-delivery, reducing friction and errors in digital document workflows.
Declaration didn't generate after revision was committed (BC-17186)
A defect was remediated where committing a policy revision did not always result in generation of the corresponding declaration document, even though the folder for the declaration was created. The update added retry logic and additional error handling to ensure that declaration documents are reliably generated and attached, resolving inconsistencies and preventing missing documentation for completed policy changes.
OFAC reporting down - 504 error (BC-15904)
A defect was resolved when running the Financial Anti-Terrorism Cross-Reference (OFAC - Office of Foreign Assets Control) report which resulted in a 504 error due to long processing times as the policyholder base grew larger. The report logic was reimplemented to run as a background job, with new UI messaging and email notifications for completion or errors.
Unable to request credit score again even after No-Hit (BC-15518)
A defect was corrected where agents were unable to re-pull a credit report after receiving a “No Hit” result, even after updating contact information. The system previously considered “No Hit” as a valid credit score, which triggered the report validity counter and prevented further pulls. The recent update ensures that “No Hit” responses do not start the counter, and that a re-pull is allowed if contact data is corrected. Resolving this issue reduces the need for underwriting intervention and supports more accurate quoting.