Skip to main content
Skip table of contents

7.0.228.1 Release Notes 1/28/2025

Logo-tinubu-Color.png

Tinubu Surety For Carriers

Version 7.0.228.1

Features

ADMIN-214 – Previous Agencies Not Showing on “Updating Assigned Agency List” 

  1. On the Edit Agent page when you click Assign Agencies, the "Updating Assigned Agency List" popup does not allow you to add back agencies that the agent previously had because they won't show up in the Available list. 

A screenshot of a computer  Description automatically generated

ADMIN-299 – Commission Rate Limit to Maximum Value of 100 

  1. Validation has been added to the commission rate field on the bond page to be a value between 0 and 100 when the commission rate is being overridden.

A screenshot of a computer screen  Description automatically generated

CORE-319 – Failed Credit Report Pull Messaging for Client Integration 

  1. When using a client specific credit reporting integration, messaging has been added for specific codes returned from the client integration to display due to valid reasons for the credit report not being able to be retrieved.

CORE-392 – Error Handling for RunETL Background Job

  1. The RunETL background job, which pushes data to the data warehouse for Power BI reports and SuretyQL, has been improved to avoid failures during the job process to ensure the job completes successfully.

CORE-401 – Performance Improvement for Account Rate Load

  1. The application performance has been improved to load the data efficiently on the account page when an account rate is used on the account. 

A screenshot of a computer  Description automatically generated

CORE-440 – Performance Improvement for Companies Load

  1. The application performance has been improved to load the company data efficiently.

DAT-111 – Refactor API Call to TSC Help Articles 

  1. Updates to the TSC Help Articles API have been made to improve performance. Calls will only be made when the ‘help’ button is clicked on the application page as well as only relevant help articles will display.  The number for the count of articles associated the page in the application loaded has been removed from the display as part of this adjustment.

A white background with a black border  Description automatically generated

UW-28 – Account and Bond Read-Only Access 

  1. For users accessing bonds and accounts, functionality to turn a user into a read-only type user is needed.  This will be accomplished through user role permissions (allowed actions).  This feature is to enhance the user role permissions to have read-only roles within account and bond access.

UW-18 – Implementation of Edit Diary Note Permissions 

  1. When the permissions for editing bond or account diary notes is disabled, users from the role will not have access to the Edit button on the diary notes pop-up for either bonds or accounts.

A screenshot of a computer  Description automatically generated

UW-19 – Implementation of Add Diary Note Permissions

  1. When the permissions for creating bond or account diary notes is disabled, users from the role will not have access to the Add button on the diary notes pop-up nor the Add button on the diary notes menu for either bonds or accounts.

A screenshot of a computer  Description automatically generated
A screenshot of a computer  Description automatically generated

UW-229 – Disallow Removed Accounts from Selection on Change Account Bond Action

  1. The options displayed for Change Account on a bond allows for all accounts to be available for selection.  Removed accounts are being hidden from the selectable options.

A screenshot of a search account  Description automatically generated

Fixes

CORE-354 – Error Troubleshooting for Client Billing Number Integration 

  1. A client billing number integration had not been able to complete and save the billing number from the external source.  This has been corrected to pull in the billing number at the correct times for the integration.

CORE-396 – Troubleshooting Client Submission Provider Web Service Error

  1. A client submission provider had not consistently completed and saved the submission number from the external source.  This has been corrected to pull in the submission number at the correct times for the integration.

UW-299 – TX Notary API Error when Date of Birth Question is not Configured

  1. An error had occurred when using the 'TX Notary Date of Birth Not Configured' email template trigger, and the date of birth question is asked but not required, and the question is not answered.  This ticket resolves the situation so that the error is not triggered, and the email is sent when the date of birth question is asked but not answered.

A screenshot of a computer  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.