Skip to main content
Skip table of contents

7.0.215.x Release Notes

Release Date

Table of contents

Features

AVOB-300 – Modal Pop-up for Details Concerning CARM Error Queue

With the queue being added for failed CARM integration calls for bonds (see AVOB-322 below), a modal pop-up has been added to display the logged records for the attempted calls to the CARM integration.

AVOB-322 – New Queue for Bonds with CARM Integration Errors

A new queue has been added for environments configured with a CARM integration. This queue presents any CARM bonds issued in the system that have a failed call to the CARM integration. Once a bond has been re-submitted to CARM successfully, the queue would remove the bond from the queue.

BS-13 – Bond Archive Legal Hold Button

This is a continuation of laying the bond archive legal hold groundwork for future functionality. This ticket allows a legal hold button to appear in the standard bond view based on user permissions. It will be turned off when deployed until the functionality is fully complete.

FCCD2-19 – Payment Status API

  1. This is a one-way interface between client payment applications and Tinubu Surety for Carriers (TSC). When a payment is submitted on a bond in the client’s payment application, an action will be triggered via the Payment Status API to Submit Payment or Submit Renewal Payment in TSC. TSC will display the updated payment status and complete actions configured for each billing type. Optional settings will be available to configure the environment to retain new bond and/or renewal documents until payment has been made.

    1. When a Payment is made in the clients’ payment application, a “PaymentStatus” message is triggered in near real time.

    2. When a "PaymentStatus” update message is received by the Payment Status API, TSC will:

      1. Trigger “Submit Payment” action for New Bonds, and the Bond Action Status is set to Completed.

      2. Trigger “Submit Renewal Payment” action for renewal purchases, and the Bond Action Status is set to Completed.

      3. Trigger specific behaviors based upon the configuration of billing types that are set for each billing type during interface configurations. Billing Types are unique to each Agency and entered into the system during configuration:

        1. Billing codes below are the current codes configured for each billing type as part of the onboarding process:

          1. Existing Tinubu Billing Type Require Payment Values:

          2. 0 = Do not Withhold Documents, no Waiting on Payment.

          3. 1 = Withhold Documents at New and Renewal and show Waiting on Payment.

          4. 2 = Withhold Documents only at Renewal and show Waiting on Payment.

          5. 3 = Do not withhold Documents, but show Waiting on Payment for New Bonds and Renewals.

          6. 4 = Do not withhold Documents, but show Waiting on Payment for Renewals Only.

        2. Please contact the TSC support team for assistance in configuring your billing types for these options.

FUEL-3966 – People and Company Details on Load Selected Acct. Parties on Bonds

The address, phone, and email fields has been added to people or companies when loading account parties on a bond transaction for additional reference when selecting these to be added to a bond.

MAOB-163 – ACH Payments for CyberSource Payment Integration

  1. This is an update to the payment options for the CyberSource Payment integration. This ticket will be adding ACH as a payment option:

    1. TSC contacts “CyberSource Payment Processor” API when:

      1. “Direct Bill – ACH” is selected during the purchase of a bond and/or Renewal:

        1. Tokenized method used to create customer profile.

          1. A Customer is created via a Payment Authorization, this can be for a zero amount.

          2. A Customer will be created with a Payment Instrument

            1. A Customer Payment Instrument represents tokenized customer payment information.

            2. A Customer can have one or more Payment Instruments, with one allocated as the Customers default for use in payments.

            3. A Payment Instrument token does not store the account and routing numbers.

      2. No refunds will be processed in TSC, refunds will be processed directly in CyberSource.

      3. Renewal bond with ACH account information automatically process payment via CyberSource based on bond renewal configuration settings.

MAOB-190 – Saving of Reference Number for CyberSource Payments

This is an update to the CyberSource payment processor. The Client Reference Information Code will be stored in TSC for bond payments made through the CyberSource payment processor so that the number can be used in data feeds for SuretyQL.

WFOB-313 – Municipal Tax-Exempt Bonds

For clients using municipal tax integrations from a external service provider, this feature is adding the ability to designate obligees and/or applicants (principals) as exempt from the municipal tax calculation. The following stories are associated with this feature, and additional stories will be added in subsequent releases for the full implementation of the feature:

WFOB-487/WFOB489 – Flag for Obligees Exempt of Municipal Taxes

An additional field has been added to obligees to mark them as exempt of municipal taxes (city and county). This would apply only if using a tax system integration. Further functionality will be added in an upcoming sprint for this exemption to be implemented. This field is only for reference until later development is completed.

WFOB-488 – Flag to Allow States to Consider Municipal Tax Exemption

An additional field has been added to states to mark them as eligible for municipal tax exemption for bonds associated to that state. Further functionality will be added in an upcoming sprint for this exemption to be implemented. This field is only for reference until later development is completed.

WFOB-318 – Multi-Agency Agents Feature

Agents have been previously tied to a single agency. This feature is expanding that capability to allow an agent to be associated with multiple agencies configured in the system. The following stories are associated with this feature, and additional stories will be added in subsequent releases for the full implementation of the feature:

WFOB-426 – Addition of User Switching for Agents with Multiple Agencies

For agents configured to have multiple agencies, a user switch has been added to the user profile in the top right corner of the application. This allows the user to toggle between their assigned agencies. This dropdown will only appear for agents that are linked to multiple agencies.

WFOB-428 – Update to Agent APIs to Include Multiple Agencies Linked to the Agent

  1. This update will offer the ability to specify linked agencies for an agent when using the Agent based APIs.

  2. The agent APIs are being updated to support the additional functionality for multi-agency agent users:

    1. AddAgent

    2. AddUpdateAgent

    3. UpdateAgent

    4. GetAgentByUserName

    5. GetAgentByProducerCode

  3. Users will now be able to:

    1. Create new agents in Tinubu (with first name, middle name, last name, initials, email, producer code, is producer of record or not, security role, agency code, additional agency codes, inactive=false).

    2. Update agent in Tinubu (could be any combination of changes to first name, middle name, last name, initials, email, producer code, is producer of record or not, agency code, additional agency codes).

      1. Examples: the agent has agencies removed, the agent has agencies added, the agent has changes to name/email/producer code, etc.

    3. Inactivate existing agent in Tinubu, because they're no longer an agent in relationship with the carrier.

    4. Re-activate agent in Tinubu that was previously active, restoring the agent (the same attributes would be involved: first name, middle name, last name, initials, email, producer code, is producer of record or not, security role, agency code, additional agency codes, inactive=false).

WFOB-504 – Removal of Credit Pull Authorization for Exempted Accounts

  1. As an extension of underwriting exempt designation on accounts, when the account is set to be “Underwriting Exempt”, the “Pull Credit Authorize” feature which appears at the end of the bond application summary page will be hidden and skipped, unless the bond type also uses a credit score range for the premium rate definition.

    1. When “Underwriting Exempt” is selected on account page:

      1. Pull Credit Authorize acknowledgment feature must be skipped if selected for the bond type.

Exception: If the bond type’s rate requires a credit score to determine the premium rate, the field will continue to be displayed.


Fixes

AMS-1908 – Correction to Recalculate Button for Pro-Rated Riders

When performing a PBR using rider pro-rating, the recalculate button would not display the pro-rating breakdown of the premium. However, the calculation after submitting the PBR does the proper calculation. This has been corrected to show the pro-rating breakdown prior to submitting the PBR.

AVI-694 – Adjustment for Document Sets to be Available on Renewal Transactions

  1. When an optional document set is selected on a renewal application, the document set would not continue to be associated with the renewal application if performing any of these bond actions:

    1. Submit Renewal Application

    2. Edit Info for Renewal Application

    3. Requote Renewal

    4. Purchase Quote for Renewal Application

  2. This has been corrected to ensure the selected document set is preserved on the renewal application through these bond transactions.

FCC-399 – Fix to Custom Company Credit Reporting when editing the Password

When editing a custom company credit reporting configuration, the Change Password button would not open the password fields to make a new entry. This has been fixed to open the Password and Confirm Password fields.

FCC-760 – Correction to WIPs when Adding a Project Errors

When adding a project record to a WIP statement and that process fails, incomplete data is saved to the statement causing an error on the WIP page. This scenario is being corrected to save the project information appropriately and to have appropriate rollback procedures if there was an issue with saving the project.

FUEL-3952 – Fix for People and Companies Search During Bond Application

When searching for people or companies in the new tables when applying a bond and hitting the Enter key, the page triggers a validation for the applicant selection. This has been corrected to only trigger the search criteria entered.

FUEL-3963 – Correction for Credit Report Fields Layout on Account People

The credit report information displayed on account people records is being displayed in six columns instead of two. This has been corrected to display in two columns providing consistency for account and bond people.

FUEL-3968 – Visibility of the Attorney-In-Fact on the Bond Page

The Attorney-In-Fact (AIF) field had inadvertently been moved to be seen only after expanding the Bond Information section on the bond page. This has been corrected to be on the collapsed view of the Bond Information section.

FUEL-3971 – Fix for Saving Entries on User-Defined People and Companies Questions

For people and company records on accounts that have user-defined questions, the answers given on the account were not saving the data in the account person or company. This has been corrected to have the data saved appropriately for the user-defined questions on the account people and companies.

GRA-393 – Correction for Penalty Increases for Tiered Commission Changes

When using tiered commission with more than four tiers, commission is calculating incorrectly if changing the bond penalty (Contract Amount) to an amount that would trigger a higher tier of commission. This has been occurring on Recalculate and/or actions like PBR.

HAN-512 – Removal of Retainage Amount when Suppressed

When the SuppressRetainageAmount is set to True, the Retainage Amount field would still appear in the expanded fields of the Bond Information section of the bond page. This has been removed and will no longer be visible when the setting is configured to True.

HAN-1288 – Fix to Tiered Commission when Maintenance Penalty is Below Bond Penalty

When a bond’s maintenance penalty is lower than the bond penalty and as a result, the maintenance tiers are different from the tiers on the commission rate; the commission from the maintenance premium was being calculated as if the maintenance penalty was equal to the bond penalty. This has been corrected to calculate the commission coming from the maintenance premium properly.

UFS-373 – Adjustment to Inactive Responsible Underwriter Behavior

  1. When an underwriter user is no longer eligible to be the Responsible Underwriter on a bond, previously, the field would be displayed as the Id number for the user. This is being adjusted to continue to display the underwriter’s name with the addition of a (Inactive) note next to the name.

  2. In addition, the underwriter will be adjusted automatically on the next bond transaction to the default underwriter for the bond. The default underwriter is determined by the following criteria and in this order:

    1. The underwriter assigned to the account.

    2. The agency’s default underwriter.

    3. The agency’s branch representative.

    4. The first underwriter is available in the Responsible Underwriter list by alphabetical order.

WFOB-377 – Fix for Cancellation Premium Coming from Pro-Rated Rider

An issue was found when cancelling a bond with a previously pro-rated premium bearing rider when the effective date of action for the cancellation was equal to the bond’s expiration date. The system was calculating the cancellation return premium only based the base premium from the penalty amount after the rider instead of the pro-rated premium amount, resulting in a changed premium calculated for the cancellation. This has been corrected to properly maintain the pro-rated premium through the cancellation in the case of the cancellation effective date of action being equal to the bond’s expiration date.

WFOB-438 – Fix for Secondary Pro-Rated PBR when Adding a Day to Expiration

Prorated bonds with multiple mid-term PBRs were calculating 367-day terms when using the AddDaysToExpiration system setting set to 1. This has been corrected to use the proper number of days for the bond term in the pro-ration calculation.

WFOB-525 – Extension of the Bond Number Validation API on Application Summary

When using a bond number validation API integration, the validation has been extended to cover the Existing Bond Number field on the application summary page prior to submitting the bond application.

WFOB-527 – Adjustment to TransSync Premium Tiers Section for Unused Tiers

  1. Two additional fields have been added to the TransSync Premium Tiers section of the API response:

    1. PreviousTierAmount

      1. This value represents the tier amount given for the previous transaction.

    2. PreviousTierUnused

      1. Indicates if the previous transaction was using this tier of premium.

1

I

JavaScript errors detected

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

If this problem persists, please contact our support.

Contact Support Close