7.0.227.x Release Preview 12/12/2024
Tinubu Surety For Carriers
Version Preliminary - Release date 1/02/2025
*This document reflects items which are targeted for the 0.0.000.x release. All items listed within are subject to final Product and Quality Assurance approval and are not guaranteed to be included in the final release stated above.
Features
BOND-89 – Auto Renew Background Job Improvement
This feature delays processing the documents being requested during the auto-renewal job. This will help jobs run faster as well as reduce the number of ‘Unable to Create Connection’ errors that interrupt the job process.
BOND-98 – SuretyQL Support for Multiple Schemas in the Warehouse
This allows for the ability to deploy using new methods that will minimize risk and downtime for future releases.
BOND-110 – Comparison Rules Do Not Need the Account Question Asked on the Bond
When using a comparison rule, the account question used in the rule does not need to be on the account application tied to the bond type. Instead, it only needs to have the question answered on the account directly (and the account may have a separate account application template).
BOND-124 – Add Limiter to BeginGetBondTransactions API Call
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. 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.
BOND-222 – Issue with Commission Rate Changed at Bond Level via PBR
When submitted the renewal, the quote does not reflect the agency default commission. The quote is holding the overridden commission until the renewal quote is fully submitted. This provides inaccurate information to the agent during the submittal of the renewal quote. The commission is correct once you submit renewal.
BOND-226 – TX Notary Fields Appearing when Editing Other Attachment Type
When editing an already uploaded file on Account/Bond attachments, the Driver License Number and Driver License State fields should not appear, except on Texas Notary Bonds.
BOND-231 – Producer of Record List is not Alphabetized
The list of available Producer of Records for bonds will now be alphabetized.
BOND-235 – User can enter a Commission Rate Greater than 100
This fix will prevent the user from being able to enter in a commission rate on a bond greater than 100.
CORE-280 – Additional Data for Associated Bond Types for Application Templates
The 'Associated Bond Types' pop-up for application templates is being 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.
Additionally, only active bond types will be listed, and inactive bond types will be excluded.
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-90 – Correct Styling and Behavior with Driver's License Number Question
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.
The second issue is that if the driver's license is left blank, there is currently no message indicating to the user that the field is required. This message should be appearing and is being corrected with this ticket.
UW-91 – Move Texas Notary Notification on Bond Submission Page
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 should be 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
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 due to a technical error on the TX Notary 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
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
Currently the success and error message text is hard coded. This ticket is to localize these messages to allow carriers to edit the display text.
UW-240 – Localization of Activity Dropdown for Account Menu
The values for the following options in the Activity dropdown in the account menu are being localized so that they can be relabeled to the wording needed:
Show All Bonds
Show All Commercial Bonds
Show All Contract Bonds
Buy Bond
Fixes
ADMIN-201 – Agent Profile Box Disappears when using Agency Dropdown
When you click the drop-down for the list of agencies on the user profile for a multi-agency user, if you click anywhere within that new box that shows up (outside of clicking an agency), the underlying box where you clicked the drop-down arrow disappears.
ADMIN-155 – PreviousVal(ApplicantFullName) Correction
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
The anonymous and payment portal users for the client are not appearing on the action list and throwing an error. This fix will allow these user roles to be opened for their allowed actions.
BOND-48 – Fix Applicant Section on Requote Action
If any additions made to People/Company at the Requote Action prior to or after Purchase that the Person/Company information was not being retained. This fix will retain any additions made.
BOND-205 – Error When Attempting to Purchase Bond after Bid Conversion Approval
There is a report of receiving an error when attempting to “Purchase Quote from New Bond Application” on a bond. Error populating is “There was a problem. Nullable object must have a value.” This fix will allow the bond to be purchased after it’s been converted from a bid bond.
BOND-210 – Fix Switch Agency Drop-Down Feature
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
When bond is cancelled and the system is using rider/cancellation pro-rating, the cancellation transaction in TransSync receives a duplicate record in the TransSyncPremiumTiers section of the BeginGetBondTransactions API call response. This is being corrected to not pass any duplicates for the commission records.
CORE-247 – Correction to ExpirePromote Job for Waiting on Payment Bond Status
When a bond is using the Waiting on Payment status for Direct Billed -- Invoice/Check billing type, the ExpirePromote job is being 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.
CORE-272 – Rounding Correction to TransSync Premium Tier Commission
The values passed in TransSync in the Premium Tiers section currently round the ProRatedTierAmount and ProRatedTierAmountDifference fields for commission records. This is being corrected to pass the proper amounts to the appropriate two decimal places for cents.
CORE-284 – Fix to Bond People and Companies with Matching Index Numbers
Scenarios have occurred where two (or more) companies or two (or more) people on a bond have 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 will stop the adjustments to these index numbers so that they maintain their proper numbering.
UW-184 – Improved Loading Time for Agents Page
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 is being 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
When using CyberSource as the payment method for a bond and the bond type includes a U.S. State type question, the payment transaction errors if purchasing from the bond page. This does not occur in the purchase is occurring directly from the Application Results page (in the case of an auto-approved bond application). This is being 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
When editing an ACH payment profile using CyberSource, an error occurs upon saving the change. This is being investigated to solve the issue and allow for edits to be done without error.
UW-201 – Issue Editing CyberSource Credit Card Payment Profile
When editing a Credit Card payment profile using CyberSource, the changes can be done and the user can submit the changes. The save appears to have been completed, but the prior information for the credit card profile is still retained. This is being investigated to solve the issue and allow for edits to be done and saved appropriately.