Enhancements
Enhancing the Mail Merge Process to Include Form Sorting
The mail merge process in BriteCore has been enhanced to consider form sorting. When utilizing batch printing (Merged Mailing) functionality, the deliverables for a given contact on a policy are merged into a single PDF file. As configured in advanced settings, the Declaration should list forms alphanumerically, and these forms should be similarly sorted in the Merged Mailing PDF. While the Declaration displays forms in the correct alphanumeric order, the forms in the merged PDF now also align with this order, resolving previous workflow disruptions. For administrators, enabling policy merge via the advanced setting "merge_docs_by_recipient_and_pol" now considers the advanced setting "sort-forms-for-printing" when merging documents. (BC-13979)
Updated Link to BriteCore University
The link in Profile > Resources > BriteCore Training has been replaced by the term "BriteCore University." This minor wording change adds clarity for users seeking access to BriteCore University for product training information. (BC-14325)
Suspension Map is Now Available within Quotes
The integration of the Suspensions map within the BriteCore quotes module is now complete. After adding a suspension via agent portal > suspension, the suspension map displays on the setup page with all active suspensions associated with the current user's state and policy type selection. Upon entering a zip code, the map highlights areas with suspensions if the entered zip code corresponds to a restricted area. The map now renders all suspensions (by ZIP code and county) associated with the state of the policy type, leveraging the Google Maps API. Additionally, enhancements have been made to the zoom functionality, allowing users to zoom in on specific areas for restricted ZIP codes and zoom out for incomplete or non-restricted ZIP codes. This new Suspension Map capability is only available in the quote wizard and is enabled by administrators via the following quote wizard settings: setup_policy.form.suspensions_map to display the map and setup_policy.form.property_zip will highlight the counties or zip codes with suspension (BC-14108).
BriteCore Month-end Close Package (MECP)
The BriteCore “Month-End Close Package” (MECP) is a single master report, generated on the 1st of every month, which contains every key measure that an insurance carrier requires to complete their financial accounting entries, whether they use MTD or YTD booking, delivered at a grain and with sufficient and consistent dimensions available. The MECP consists of 5 primary datasets, which when delivered in an Excel Workbook, are each available as their own Worksheet within the Excel Workbook. Due to its large scale and scope of data, the MECP has the potential to replace nearly all other Stock Monthly-run Reports currently used by BriteCore clients. BriteCore will work together with our clients over the coming months to shorten the list of reports each carrier runs, simplifying the experience for all and providing the most efficient, accurate reports available.
Note that, while the MECP will eventually be enhanced even further to allow carriers to expand the report to include additional items chosen from their lines, this dynamic functionality is not being generally released today and is only available for Early Access Program customers. Today’s MECP report is comprehensive and contains a fixed set of contents.
Defects
Resolving Issue with Persistent Builder (PB) and Renewals
BriteCore has implemented a change to ensure the Persistent Builder (PB) feature triggers when adding new items on renewals. Previously, the Persistent Builder (PB) feature failed to trigger when adding new items on renewals, even when the item does not have the "skip PB on adding new" option selected. Additionally, the system neglected to mark items as conflicted when included in the renewal logic, leading to inconsistencies. As a result, not all sub-lines were marked as conflicted, resulting in the PB not being displayed on the UI, and users were unaware of the presence of some sub-lines from the previous policy type, hindering their ability to commit the revision. BriteCore has implemented a change to address this issue, ensuring that the clean-up logic only removes empty sub lines that are marked as conflicted. (BC-14106)
Resolving Issue with Renewal Process and User Inputs
BriteCore now initializes the user inputs field when a rate per item is included on an existing line item. Previously, a client encountered an issue with their renewal process, where they received daily emails indicating renewal failures due to 'user Inputs'. Subsequently, the client had to manually navigate to each renewal, rate, save, and commit the policy. The problem stems from the system failing to initialize the user inputs field when a rate per item is included on an existing line item. Consequently, when attempting to retrieve the value from the user input for rating, the system produced an error, even if it's not mandatory. To address this issue, new logic has been implemented to initialize the user inputs, resolving the issue and streamlining the renewal process for users. (BC-14185)
Resolving Issue with Manual Payment Method Reason Visibility
BriteCore now displays "reason for manual pay" field when an agent selects manual pay on the billing screen but fails to select the “first installment paid separately” checkbox within the blue banner. Previously, an issue was identified when creating a new quote and progressing to the billing step, where the visibility of the "reason for manual pay" field is affected. To ensure the field is displayed correctly, it is necessary to confirm that the settings allow_manual_override is set to true and the wizard flow setting policy_billing.form.checkbox_first_bill_paid is enabled. Now when an agent selects manual pay on the billing screen but fails to select the "first installment paid separately" checkbox within the blue banner, the "reason for manual pay" field will show. (BC-14037)
Resolving Issue with Policy Search Layout for Agents
An issue has been identified regarding the policy search functionality for agents when the settings show-agency-column and show-review-state-column are enabled. Previously, the layout would break when multiple columns (more than 9) were present in the policies list. However, a recent update was implemented to address this by adapting the columns to fit the screen when there are more than 9 columns (BC-14105).