7.0.227.2 Release Notes 1/15/2025

Tinubu Surety For Carriers

Version 7.0.227.2

Features

ADMIN-222 – Implementation of Bond Type Descriptions for Contract Bonds 

1. The bond type description that appears below the bond type selection has been implemented to show for contract bond type.  Previously, only commercial bond types had the implementation of the description.

ADMIN-230 – Alphabetization of Application Templates when Assigning to a Bond Type

1. When assigning an application template (either root, class, category, or account) to a bond type, the list of application templates has been alphabetized.

ADMIN-234 – Removal of Inactive States from Copy Bond

1. When processing a copy for a bond type, inactivated states have been removed from the available selections in the States dropdown.

ADMIN-238 – Removal of Inactive Question Groups from Question Assignments 

1. When assigning questions to an application template, inactive question groups have been removed from the available options to select.  

ADMIN-246 – Text Correction for Credit Score Rule Option

1. When using a credit score rule including an option for a penalty threshold, the description text has been updated to accurately reflect the scenario.  The text was updated from '…over…' to '…equal to or over…'.

BOND-124 – Add Limiter to BeginGetBondTransactions API Call

1. As part of the TransSync job, the customer uses the BeginGetBondTransactions API endpoint to retrieve the transaction records produced by the TransSync job. There is a table, GetTransSyncHistory, that is used to record the transactions that a particular customer user (the user authenticated for the API), has retrieved. This allows them to get the new ones that have been added since the last time the API was called. 

2. However, there are certain situations where the number of transactions a user will be allocated to download is larger than the system can process in a reasonable time, and the API request will time out. To prevent this, a limit is needed to cap the number of transactions returned. The remaining transactions will still be there the next time the API is called. 

3. The BeginGetBondTrxLimit setting will be delivered as on by default with the value of 7000.  The setting can be overridden by passing through a specific transaction limit at the end of the URL in the API call. For example: https://{{serviceURL}}/esuretyservice.svc/rest/BeginGetBondTransactions/4000

   1. This setting is located at: All>Setup>Settings>ImportExport>BeginGetBondTrxLimit.  

BOND-226 – License Number Fields Appearing when Editing Other Attachment Type

1. When editing an already uploaded file on Account/Bond attachments, the Driver License Number and Driver License State fields should not appear.

BOND-231 – Producer of Record List is not Alphabetized

1. The list of available Producer of Records for bonds will now be alphabetized.

BOND-270 – People and Company Account Grid Performance 

1. The calls to load people and companies on accounts have been improved based on stress testing of high volume of data and users. 

CORE-276 – Client Custom Bond Number Integration Adjustment for Test Mode Bonds 

1. A client specific bond number integration is being modified to not utilize the bond number integration if the bond type for a bond is configured to Test Mode.  Test Mode allows for bonds to be applied for and issued without using live bond number blocks, production credit reporting, and payment processors.  

CORE-280 – Additional Data for Associated Bond Types for Application Templates

1. The 'Associated Bond Types' pop-up for application templates expanded to include not only the titles of the bond types associated with the application templates, but also the State (if Commercial), Bond Class, Bond Category, Obligee (if Commercial), and Carrier.

2. Additionally, only active bond types will be listed, and inactive bond types are excluded.

   1. A bond type is considered inactive if:

      1. The bond type is inactive.

      2. The bond type's class is inactive.

      3. The bond type's category is inactive.

      4. The bond type's carrier is inactive.

      5. The bond type's obligee (commercial bonds only) is inactive.

CORE-293 – Auto Renewal Failed Message Adjustment 

1. When a bond fails to auto renew due to missing or incomplete information on the bond, a message displays on the bond to notate the failure of the automatic process.  The message currently continues to display after the renewal application is processed (including the input of missing information).  The message is being adjusted to discontinue the display of the message after the renewal has been handled.

CORE-315 – Adjustments to Client Color and Branding 

1. Adjustments made the clients color scheme for their needed styling of the TSC platform.

CORE-327 – Expansion of Client Integration for Credit Report Pulls on an Account

1. A client specific credit reporting integration is being expanded to allow for credit report pulls from an account directly.  Previously, the integration was limited to only on bonds.

UW-55 – TX Notary V2 Integration

1. 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-90 – Correct Styling for Driver's License Number Question

1. This ticket cleans up a few bugs that occur on the bond application when the Driver’s Licenses Number question is added. The first is an unwanted colon that appears on the application. 

UW-91 – Move Texas Notary Notification on Bond Submission Page

1. When a user purchases a bond that is part of the TX Notary configuration, a message indicating the success or failure of the submission to TX Notary is displayed on the purchases screen. The section in which the message is currently displayed is not visible on other bond actions, such as riders. Therefore, the messaging has been moved from its current location to one that is visible on all bond actions that would be submitted to the Texas Secretary of State. 

UW-215 – TX Notary V2 - API Application Resubmission

1. Currently, bonds can be submitted to the Texas Notary Secretary of State portal during purchase actions or rider actions. However, there are circumstances in which a user may need to submit an application without initiating a bond purchase or rider. An example would be resubmitting an application that was purchased successfully in TSC but failed the send to the Texas Secretary of State due to a technical error on their system. This ticket creates a button that allows underwriters and administrators to submit an application to Texas Notary for a bond if there has not already been a successful submission. 

UW-220 – Add Email Templates for Texas Notary Application Success and Failures

1. Currently the email that is sent out for successful or failed applications is hard coded. This ticket is to add the ability for a carrier to create an email template for Texas Notary V2 success and failure emails that can be configured.

UW-224 – Allow Localization of Texas Notary Success and Error Messages

1. Currently the success and error message texts are hard coded. This ticket is to localize these messages to allow carriers to edit the display text.

UW-254 – Prefix Question Names With "TXv2Notary_"

1. The question overlay names for Texas Notary V2 have been updated to have the prefix “TXv2Notary_” preceding the question's specific field name.

UW-219 –Expansion of Search Criteria for Find Account

1. When using the Find Account search, the options of Agency Code, Agency Name, Company Name, and Person Name have been expanded to allow for a "Contains" search criteria instead of the prior "Starts with" search criteria.

UW-233 – Localization of Authority Level Exceeded

1. The message displayed on bonds when an authority level has been exceeded  has been localized so that each environment can adjust the wording of the message.

UW-240 – Localization of Activity Dropdown for Account Menu

1. The values for the following options in the Activity dropdown in the account menu are localized so that they can be relabeled to the wording needed:

   1. Show All Bonds

   2. Show All Commercial Bonds

   3. Show All Contract Bonds

   4. Buy Bond

Fixes

ADMIN-155 – PreviousVal(ApplicantFullName) Correction 

1. The document overlay formula =PreviousVal(ApplicantFullName) is no longer showing the prior principal name on printed documents. This fix will correct this issue.

ADMIN-183 – Unable to Access "Actions" on two User Roles

1. The anonymous and payment portal users for the client are not appearing on the action list and throwing an error. This fix allows these user roles to be opened for their allowed actions.

ADMIN-201 – Agent Profile Box Disappears when using Agency Dropdown 

1. When you click the drop-down for the list of agencies on the user profile for a multi-agency user and click anywhere within that new box that displays (outside of clicking an agency), the underlying box where you clicked the drop-down arrow disappears.  This has been corrected to maintain the display.

ADMIN-218 – Auto Renewal Penalty Threshold Values Copied with Copy Bond Feature

1. When copying a configuration, the Auto Renew Penalty Threshold and Penalty Threshold values had not been copied over to the new configuration.  This is being corrected to copy the values from the prior bond configuration to the newly created one.  

ADMIN-242 – Removal of Other Users from Branch Representative 

1. The branch representative dropdown has been altered to only allow users from the CSR or Admin type user roles.  This includes all user roles associated with the CSR and Admin security groups.

BOND-48 – Fix Applicant Section on Requote Action

1. If any additions had been made to people or companies at the Requote action prior to purchase, the person or company information was not being retained. This fix will retain any additions made.

BOND-210 – Fix Switch Agency Drop-Down Feature 

1. The drop-down feature when switching an agency is only working intermittently. Sometimes when the multi-agency user clicks the drop down all the agencies are displayed. Other times they are not. This fix is to make sure the drop down works consistently.

CORE-242 – TransSync Commission Tier Record Duplication

1. When a bond is cancelled and the system is using rider/cancellation pro-rating, the cancellation transaction in TransSync would receive a duplicate record in the TransSyncPremiumTiers section of the BeginGetBondTransactions API call response.  This has been corrected to not pass any duplicates for the commission records.

CORE-247 – Correction to ExpirePromote Job for Waiting on Payment Bond Status

1. When a bond is using the Waiting on Payment status for Direct Billed -- Invoice/Check billing type, the ExpirePromote job has been adjusted to handle a renewal that is still waiting on payment.  Bonds with renewals with payment completed will promote appropriately, while the Waiting on Payment renewals will continue to hold until payment is managed first.  Then once payment is received, the renewal promotion will continue the following time the ExpirePromote job is run.

CORE-268 – Term Bond Premium Correction in TransSync Premium Tiers

1. When processing a term type bond with premium tiers, the values in the TransSync Premium Tiers section had inaccurate values in the ProRatedTierAmount and ProRatedTierAmountDifference.  This has been corrected to bring in the appropriate premium values.

CORE-272 – Rounding Correction to TransSync Premium Tier Commission 

1. The values passed in TransSync in the Premium Tiers section had rounded the ProRatedTierAmount and ProRatedTierAmountDifference fields for commission records.  This has been corrected to pass the proper amounts to the appropriate two decimal places for cents in the case of commissions.

CORE-284 – Fix to Bond People and Companies with Matching Index Numbers

1. Scenarios have occurred where two (or more) companies or two (or more) people on a bond had their index number, which indicates the order in which the company or person was added to the bond, adjusted incorrectly.  This incorrect adjustment then causes errors when loading the bond page.  This fix stops the adjustments to these index numbers so that they maintain their proper numbering.  

CORE-288 – Premium Prorating Correction at Cancellation for Pre-Paid Annual Bonds 

1. A correction is being made to the premium prorating calculation for the initiate cancellation process for annual bonds with a pre-paid years selection and a specified expiration date.

UW-184 – Improved Loading Time for Agents Page 

1. When loading the agents page for all agents across all agencies, the page loading time was extensive when the volume of agents loading on the page is high.  This has been adjusted to perform the loading of the agent data into the page quickly.

UW-193 – Error when using CyberSource and Bond Contains a U.S. State Question 

1. When using CyberSource as the payment method for a bond and the bond type includes a U.S. State type question, the payment transaction would error if purchasing from the bond page.  This does not occur if the purchase is occurring directly from the Application Results page (in the case of an auto-approved bond application).  This has been corrected to allow for the payment transaction and the purchase of the bond to be completed without error.

UW-197 – Error Editing CyberSource ACH Payment Profile

1. When editing an ACH payment profile using CyberSource, an error occurred upon saving the change.  This has been investigated to solve the issue and allow for edits to be done without error.

UW-201 – Issue Editing CyberSource Credit Card Payment Profile

1. When editing a Credit Card payment profile using CyberSource, the changes could be done, and the user could submit the changes.  The save appeared to have been completed, but the prior information for the credit card profile was still retained.  This has been investigated to solve the issue and allow for edits to be done and saved appropriately.

UW-237 – Correction to User Bond Approval Authority

1. When approving a commercial bond and the account is using Global or Both authority type (not bond class limits only), the user would be stopped from approving the bond due to account and/or user authority.  This has been corrected to allow for the approval if the user's authority limits (both single and aggregate) are sufficient.

©2025 Tinubu® Square Confidential and Proprietary