Google Analytics ID updated to work with Google Analytics 4(GA4) version
Google is currently transitioning from Universal Analytics (UA) to Google Analytics 4 (GA4) and as part of this change, we needed to update the ID associated with our existing properties. These properties include <client>.britecore.com and <client>.britecorepro.com.(BC-11463)
HazardHub service enhanced to include caching
In this update, we have made enhancements and validations to the HazardHub integration. The key improvements include the implementation of caching, allowing us to store HazardHub data for a customizable duration and with a default duration of 14 days. Caching is enabled by default but can be enabled or disabled based on user preference. We have also optimized HazardHub calls during rate calculations, ensuring the use of up-to-date information in policy building. By default, triggering on rate and save is enabled, but it is disabled if caching is disabled. Additionally, we have provided control over HazardHub visibility, disabling it for admins and agents. Admins can choose to disable visibility entirely, while the checkbox for agent visibility is automatically disabled if the overall visibility is disabled. Furthermore, we have conducted thorough validation to ensure proper spacing and sizing of HazardHub display on the policies page within the new user interface. These updates enhance caching, offer visibility control, and ensure accurate HazardHub presentation. (BC-9592)
Enhanced builder to improve response time
Carriers with multiple properties were experiencing a lag in reviewing the builder sections for each property. The back-end processes that support this user interface have been optimized from more than 12 seconds to respond to 4 seconds, resulting in improved responsiveness and experience in the interface. Improve the performance of the API endpoint in a few seconds. (BC-11497, BC-11522 & BC-11504)
Vendor Returned Distance to Coast as Rating Factor
In order to enhance flexibility and enable the usage of the distance to coast data in rating with other integrations, we decoupled the distance-to-coast data from Air Worldwide/HazardHub and make it accessible for rating calculations across other integrations including ISO protection Class. (TS-1177).
Additional factors available in Rating Engine
In this release, we have added factors to our rating engine to enable specific calculations based on policy details. These additions to the rating engine enable precise and customized calculations based on the policy's household composition, insured ages, and timing of the quote creation, enhancing the accuracy and flexibility of our rating system. The following have been introduced:
- Household Composition Factor: The evaluation of the number of insureds on the policy is now possible using: this.revision.named_insureds. This change allows the Household Composition Factor to accurately consider the number of insured individuals covered by the policy.
- Age of Insured Discount: To calculate the discount based on the age of the eldest insured, utilize: insured.age for insured in this.revision.named_insureds. If the date of birth is not provided, the value returned will be None. This calculation ensures that no personally identifiable information (PII) is exposed directly to the rating engine, and the age is inferred relative to the policy term's effective date.
- Advanced Shopper Discount: The Advanced Shopper Discount calculation involves comparing the Quote Create Date to the Requested Effective Date. This discount can be utilized in an evaluation using: this.revision.effective_date - this.revision.create_date.. This allows for the accurate calculation of the discount based on the time difference between the quote creation and requested effective dates. (BC-11582)
'Information is Missing’ error on policy types without supplemental questions
When agents clicked “Save Information” on the Rating tab of a Farmowners quote, they were getting an error message that stated, “It looks like some information that is required for this form is missing,” even though all required fields had been filled out. It was identified that when supplemental questions do not exist within the line of business, the code identified it as empty resulting in the error message. This has now been corrected. (BC-11492)
Ivans Edocs timeout issues
The issue revolves around timeouts occurring in the IVANS/NxTech eDocs integration, specifically related to the submission of a master XML file and numerous associated PDF files. To address this, we have optimized file handling, enhancing transmission efficiency and managing flags to prevent duplicate submissions. By implementing these improvements, the timeouts are resolved, and the IVANS/NxTech eDocs integration operates more effectively. (BC-11424 & BC-11541).
Issue with "Prevent Creation of Multiple Open Revisions Simultaneously" Setting
This release addresses an issue related to the "prevent-creation-of-multiple-open-revisions-simultaneously" advanced setting in the policy management system. When enabled, the setting should restrict users from creating a second open revision on a policy with an existing open revision. However, the issue allowed agencies/agents to create a second open revision through quoting a change, while internal users were unable to do so. Conversely, when the setting was disabled, users could create a second open revision with the same date, replacing the existing one without warning. The resolution includes implementing pop-up error messages to block users from creating multiple open revisions simultaneously and providing clear instructions to commit or delete existing open revisions before proceeding. These changes improve the functionality and data integrity of the policy management system. (BC-11546)
Issue with New Premium Written Earned/Unearned report type
We have resolved an issue with a file type mismatch on the New Premium Written Earned/Unearned report. An alert was appearing in BriteCore indicated a file type mismatch. The new report was being saved as an xls instead of an xlsx file. This issue has been resolved and the error no longer displays in BriteCore. (BC-11418)