Skip to main content
Skip table of contents

7.0.229x Release Notes 00/00/0000

Logo-tinubu-Color.png

Tinubu Surety For Carriers

Version 7.0.229

Features

ADMIN-282 – Addition of Username Update in UpdateAgent API Endpoint 

  1. The 'UpdatedAgentUserName' field has been added to the UpdateAgent API endpoint.  When a value is passed in the field, the user, identified in the UserName field, will have the UserName field updated to the content of the UpdatedAgentUserName field.

ADMIN-295 – Addition of Send Approval Conditions Action after Referral Reassignment 

  1. The 'Send Approval Conditions' bond action has been added to be available after a Reassign Referral action on a new bond application.  Previously, this action was only available immediately after the new bond application submission.

A screenshot of a computer  Description automatically generated

BOND-301 – Newly Selected Applicant Does Not Save on PBR or NPBR

  1. When adding a person or company and switching the applicant (principal) to this new entity on a bond via a NPBR or PBR, the applicant change had not stayed, and the applicant reverted to the old applicant. This fix saves the applicant change.

A screenshot of a computer  Description automatically generated

BOND-381 – Update Applicant's Name Search for More Flexibility  

  1. When searching for a bond by the applicant's name, the exact result has needed to be entered, or else the bonds will not show in the search results. This can cause confusion in situations where there is not an exact match. For example, ‘The Test Account’ would not show up if ‘Test Account’ was entered.  This has been updated to allow for the search criteria to make partial matches for results.

BOND-392 – Performance Improvements on Bond/Accounts  

  1. For clients who have a high volume of people and/or companies, the bonds or accounts have been slow to load. This fix improves the backend calls to speed up this loading time.

CORE-370 – Client Tax Service Integration Address Adjustment

  1. For a client specific integration for tax calculation, the address sent in the request for the integration has been adjusted from the obligee address to the project address for contract bonds.

CORE-427 – Adjustment to Commission Values in TransSync Tiers to Two Decimals

  1. The TransSync Premium Tiers section has been adjusted to round the commission to two decimal places for the ProRatedTierAmount and ProRatedTierAmountDifference fields

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-323 – Message Adjustment on TX Notary DoB Email Template

  1. The message content for the 'TX Notary Date of Birth Not Configured' email trigger had referenced the lack of the PBR and/or nPBR lifecycles on the date of birth question.  The message content for the email trigger has been updated for the other scenarios for when the email would potentially be sent.

UW-386 – Adjustments to Client Color for Accounts Grid

  1. For the client specific color styling, the text for the headers on the accounts grid for underwriters has been adjusted to be easily visible due to other color changes in the client styling.

UW-391 – Additional Actions Able to Push People/Companies Changes to Accounts 

  1. Additional actions have had the 'Push Changes to Account' pop-up option added so that accounts can be updated when appropriate when a person or company change is being made on a bond.

A screenshot of a computer  Description automatically generated
  1. The following actions have had this added:

    1. Edit Info for New Bond Application

    2. Approve New Bond Application

    3. Requote (New Bonds)

    4. Submit Renewal Application

    5. Edit Info for Renewal Application

    6. Approve Referred Renewal Application

    7. Requote Renewal

  2. The exception in functionality is for the following actions for when they are referred.  If they are referred, the changes are kept on the referral and upon approval, the user is prompted again to push these changes to the account.  If the user accepts to push the changes to the account on the approval, then they will be completed on the account:

    1. Requote (New Bonds)

    2. Submit Renewal Application

Fixes

ADMIN-226 – Removal of Reinstate Renewal Action from Bond Type Document Actions 

  1. When adding a document template to a bond type on the reinstate lifecycle, there was an additional option for Reinstate Renewal.  This an errant bond action that is not functional and has been removed.

A screenshot of a document  Description automatically generated

ADMIN-311 – User Role Permission Change Error 

  1. When updating a user role's permission that contains more than 250 characters in the description, the user would receive an error upon saving their changes. The change is saved; however, it may not be evident to the user. The fix stopped the error message when these user role permissions have been updated.

A screenshot of a computer  Description automatically generated

BOND-205 – Error on Bond Transactions after Account Rate Assignment

  1. This ticket fixed an error correction when attempting certain bond transactions after an account rate has been assigned to the bond's account while the bond was issued prior to the assignment.

CORE-309 – Adjustment for Migrated Bonds for Backfilling Rating Structure

  1. When a bond has been migrated from an onboarding, the migration typically lacks rating structure data from the source data for the import.  This ticket handles the rating structure to be populated for these bonds upon a transaction on them.

UW-333 – Correction of Penalty Limits on Application Summary

  1. When a bond type limits the penalty amount between two amounts, the penalty cannot be outside of these limits on the 'Initial Bond Information' page and on subsequent transactions on a bond.  However, this limit was not enforced on the Application Summary page presented prior to the final submission of the bond application. This limit has been adjusted to enforce the limit on the Application Summary page.

A application form with text  Description automatically generated

©2025 Tinubu® Square Confidential and Proprietary

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.