Enhancements
Enhanced Claims Management with Policy/Claim Type Display
An enhancement has been implemented to streamline claims management. An existing configuration setting, "claims-header-type," now allows users to choose between displaying policy or claim type information in the Claims Search screen. The claims search screen has been upgraded to include an additional column for policy/claim type visibility in both agent and admin views. This improvement enables efficient filtering and searching by policy/claim types, enhancing usability and decision-making capabilities for insurance carriers. (BC-13923)
Hartford Steam Boiler Report FTP Transmission EOF Enhancement
BriteCore enhanced the connection to HSB to handle EOF errors returned by the HSB service FTP by catching and logging such events. Clients reported failures when sending reports to the Hartford Steam Boiler (HSB) service likely resulting from an access change by HSB that returned “end-of-file” errors when BriteCore attempted to transmit the reports. This enhancement ensures seamless operation with the HSB FTP service, improving the robustness and reliability of our application. (BC-14952)
Defects
Streamlining Vendor Call Handling in Policy Renewals
Policy renewals involve calling vendors. If a vendor call fails, it leaves a corrupted open revision requiring user intervention by an underwriter. To improve this, the system will now automatically initiate 2 retry attempts with a 15-minute interval after any initial failure. For overnight renewals, a failed vendor call will prompt deletion of the entire renewal, with the nightly renewal email specifying which vendor call(s) failed and why, allowing the system to retry overnight. During manual renewals, if a vendor call fails, the system will continue with old vendor data but will display a message detailing the failed vendor call(s). In both scenarios, a note will be added to the policy indicating which vendor call(s) failed and the reasons, alongside those that succeeded. (BC-14948)
Improved Transaction Handling in Authorize.net Integration
When using Authorize.net, our current implementation improperly handled the response code 4, which indicates payments under review (such as for fraud), by incorrectly treating it as a "declined" response. To address this issue, we have enhanced the code to pull out responseCode=4 into a separate condition branch where it will be correctly identified and logged. This adjustment ensures accurate processing of transactions flagged for review without misinterpreting them as declined payments. (BC-12546)
Ensuring Accurate Zip Code Handling in Persistent Builder
Currently,, when a client's property has a zip code outside the valid options defined in the Zip code category, Persistent Builder rejects the entire line item and displays an empty disabled drop-down on the UI. However, given that a carrier is already insuring the property, confirming the Zip code's validity, we must ensure the property's actual Zip code is used despite any configuration limitations. To address this, we have implemented a solution where the real Zip code of the property overrides any predefined options, ensuring accurate data representation in Persistent Builder and preventing unnecessary rejection of valid property details. (BC-14836)
Enhancing Visibility and Resolution in Persistent Builder
In Persistent Builder, a current issue arises where the system retains items even after the end-user marks them as resolved. This problem stems from the failure to highlight empty subline rows, which prevent proper resolution due to their absence from the front-end display. Consequently, the backend fails to receive the ID of these unresolved subline items.
To address this, an enhancement is ensuring that hidden items become visible when users select "display hidden items" in Persistent Builder. Conflicting lines configured to be hidden should still appear if they are in conflict, ensuring comprehensive visibility and resolution capabilities within the builder interface. (BC-14860)