Enhancements
Added “Date Inspected” Field in the Claims Record (TS-2426)
Within a claim, a new field labeled “Inspected” has been added under the Information tab. It is located with the Dates section.
Added Ability to Set Default Answers for Supplemental Questions (BC-19288)
When setting up supplemental questions within Lines, BriteCore added the ability to set default answers for supplemental questions to streamline data entry.
Exposed Scheduled Item Details to STP Engine (BC-19379)
Exposed scheduled item details to the STP engine to enable rule-based triggers through advanced triggers.
for item in schedule_items:
print(item["Test"], item["Test2"], item["Test3"], item["Test4"])
Introduced Logic for Using Existing Credit Score to Quote Wizard (BC-19391)
In the Wizard, if a contact already has a valid credit score, the system will reuse it as long as it falls within the configured validity period. A new credit score will only be pulled if the existing one has expired or if key contact details (date of birth, SSN, or name) have been modified.
Added STP Events for Analysis and Underwriting Referrals (BC-19888)
Added two new STP-related system events for analysis and underwriting referrals. Within the payload, Britecore included the policy ID, Revision ID, and Contact ID.
Retrieve Deleted Quotes (BC-20372)
The retrieve_full_quote API now returns revisions even if they are soft-deleted.
Rewrote Existing Stock Reports using SQL Views (BC-18506) (BC-19200) (BC-19204)
BriteCore redesigned the following reports to use the SQL Views and made the source code available to BriteCore carrier clients
- Reinsurance Received Recovered Report
- Incomplete Contacts Report
- Policy Term Expirations Report
By rewriting these reports, they are more accurate, performant, and allow the SQL code to be used as a basis for further customization in the SQL Editor. Full documentation as to changes can be found in BriteCore’s new inline report documentation.
Added v_report_docs view to SQL Editor Views (BC-19931)
A new view has been added to SQL Editor in order to display the report documentation within the tool. The report documentation view will include the report description, version number, changelog, report granularity, and formatting data.
Defects
Honor is_renewal Flag on create_quote_extended API (BC-20035)
The create_quote_extended endpoint is currently not honoring the is_renewal flag. As a result, STP checks are applying new business rules instead of the intended renewal rules.
Email Address Suggestions Limited to Relevant Policy Contacts (BC-19463)
BrieCore is now limiting email address suggestions to relevant policy contacts to prevent data exposure. Previously, emails were suggested that aren't related to the agency or the policyholders they represent in the Email Policy Information pop-up
Corrected Logic to Print Optional Forms Based on Category Selection (BC-18814)
Restored printing logic for optional forms to depend correctly on category selection based on setting enabled “Document Printing depends on selected category values.”
Ensuring Claim-related Line Items follow Billing and Configuration rules (BC-19268)
Added validation through Quote_full API to ensure claim-related line items follow billing and configuration rules. Agencies configured for Agency Bill were incorrectly being charged rate chain items, even though these items were marked as “Does not apply if policy is on Agency Billing.” This behavior resulted in inaccurate premium and invoice calculations, as taxes and fees should not be computed or collected for agency-billed policies.
Corrected Issue in Reapplying Underwriting Rules when Toggling Optional Coverages (BC-19542)
The fix ensures that Underwriting rules are correctly reapplied to items that are re-added to a policy in BriteCore. Previously, the rules were not triggered when an item was removed and then re-added, potentially causing issues with policy validation. This update addresses that gap by making sure that all relevant rules are automatically re-executed for reintroduced items.
Subjectivity Not Always Applying (BC-19945)
Subjectivity requirements were not being applied to policies as expected due to a defect in the logic that processes and enforces subjectivities. This resulted in cases where subjectivity conditions were either not recognized or not enforced during policy handling. The fix ensures that subjectivity logic is now correctly executed and subjectivity requirements are properly applied to all relevant policies