7.0.226.x Release Notes 12/10/2024
Tinubu Surety For Carriers
Version 7.0.226.x
Date 12/10/2024
Features
ADMIN-130 – Fix DeclineExpiredQuotes Performance Issue
1. The DeclinedExpiredQuotes background job has been updated to run more efficiently.
CORE-153 – Update to Underwriter Assignment on Auto-Renewals
When a bond's responsible underwriter is no longer valid (possibly inactivated or the user configuration has been changed), the auto renewal background job will reset the responsible underwriter to one of the following options for underwriters (in order of priority from top to bottom):
Account’s Underwriter
Agency’s Underwriter
If it is a contract bond, the underwriter from the agency's Contract Underwriter.
If it is a commercial bond, use the underwriter from the agency's Commercial Underwriter
The Branch Representative set on the branch for the bond's agency.
The top user in the Responsible Underwriter dropdown list, sorted alphabetically.
CORE-154 – Referral for Invalid AIF on Auto-Renewals
When an AIF that has been on bonds becomes invalid (ie. agent AIF user is inactivated, the carrier AIF is inactivated, or the agent AIF user is disabled from being an AIF), the renewal process needs to be able to accommodate for this situation without causing renewal errors. However, the bond does need to have the AIF re-selected to a currently valid AIF option. The AutoRenewals job will flag the renewal as referred so that a user can review the bond and determine the new AIF for the bond.
NOTE: This referral reason for auto-renewals will only apply if the system is configured to require the AIF. This is determined by the RequireAttorneyInFactCommercialBonds and RequireAttorneyInFactContractBonds settings, located at: All>Setup>Settings>User Interface.
UW-55 – TX Notary V2 Integration
The Texas Secretary of State (SOS) is modernizing the API they use for their Notary Portal. With the migration to a new API, Tinubu was required to update our integration with the TX SOS. Along with sending data to a new API, there is also a different workflow within the TSC application due to no longer sending over an attachment as required with the legacy connection. Therefore, there this epic also included UI/UX changes to capture all the necessary data in the database before sending the application using the REST API. Therefore, this epic also included UI/UX changes to accommodate the new workflow.
UW-153 – Failure Email when Date of Birth is not configured for Riders
This update was introduced to address a bug found during testing of the Texas Notary integration. It was discovered that the misconfiguration of the “Date of Birth” field will throw an application error during PBR and NPBR actions on TX Notary Bonds. To prevent the user receiving an application error, a fix was completed to allow the agent to proceed with the action but prompt the carrier via email if the bond failed to submit to the Texas Secretary of State due to a misconfigured date of birth field. An admin at the carrier will then be able to change bond configuration so that the application and future applications can be submitted without issue.
NOTE: To get Texas Notary V2 successfully setup, the Date of Birth has to be added as an Account question (for Bond Application lifecycle) and as a Bond Question (for PBR and Non-PBR lifecycles). The issue described in this ticket occurs when the mentioned Bond Question is not setup.
UW-154 – Update Residence State Only Applicable to TX, LA, NM, OK, and AR
The Texas Secretary of State only grants notary bonds to residents of Arkansas, Louisiana, New Mexico, Oklahoma, and Texas. This purpose of this ticket is to generate an email notification to the carrier if a bond application is submitted for an applicant whose address is outside of the allowed states.
UW-155 – Fix for Application to TX SOS when Purchasing Bond from Actions
This ticket is to address a bug that was preventing the bond information from being sent through the Texas Notary API when the user initiated the purchase action from the Action Menu -> 'Purchase Quote From new Bond Application'.
UW-180 – Correction of Error Received from Missing Escrow License Expiration Date
This ticket addressed an issue that caused an application error during the bond purchase flow if the escrow license expiration date was not filled in.
Fixes
CORE-212 – Correction for Last Day of Month Specified Expiration Date
Using a specified expiration date with the designation to expire of the Last Day of Month and the Minimum Term Days is greater than 0, the premium calculation for a bond cancellation, would pro-rate the term incorrectly lowering the base premium to the minimum premium. This is being corrected to maintain the base premium on the bond unless the rider/cancellation prorating is being used. If the rider/cancellation prorating is being used, the proper proration for the cancellation will be calculated according to the effective date of the cancellation action.
UW-5 – CyberSource Integration Correction for Adding Payment Profiles to Accounts
When using the CyberSource payment processor integration and adding a payment profile to an account, a validation message appears requiring an email address. This is being reviewed to implement the needed change for CyberSource. The page now requires a new field to capture the email address to be able to complete the creation of a new payment profile on accounts.
UW-85 – Fix for the Name on Account Not Saved Properly on ACH Payment Profile
When using Simulation payment processor, a saved ACH payment profile had not stored the 'Name on Account' field after submitting the entry. This has been updated to save the information to the payment profile.
When using Process One payment processor, a saved ACH payment profile stores the Bank Name field into the 'Name on Account' field. Since the 'Name on Account' field is not necessary for Process One, this has been changed to not ask the question on the ACH payment profile.
©2024 Tinubu® Square Confidential and Proprietary