Skip to main content
Skip table of contents

7.0.213.x Release Notes

Release Date

Table of contents


Features

AVI-663 – User Who Initiated Bond Lifecycle Email Recipient

  1. A new recipient designation is available on bond email templates to be sent to the original user who submitted the bond lifecycle. This would be for the New Bond, Renewal, NPBR, and PBR lifecycles:

    1. New Bond: An email will be sent to the user who submitted the original application for that bond (the user which submitted the Submit New Bond Application transaction).

    2. Renewal: An email will be sent to the user who submitted the most recent Submit Renewal Application transaction. This needs to be the most recent, since a renewal could be declined, rejected, or cancelled, and then the renewal application can be re-submitted.

    3. PBR or NPBR: An email will be sent to the user who submitted the most recent Submit PBR or Submit NPBR transaction. This needs to be the most recent, since a rider could be rejected, or prior riders could have been performed on the same bond.

  2. For the Cancellation, Reinstatement, Lost Bid, Payment and Premium Credit lifecycles, the email would not be applicable as these lifecycles are not able to be referred or quoted.

AVOB-352 – Adjustments to CARM Integration

  1. The CBSA’s Bond API provides surety companies direct connection to CBSA systems to perform non-cash bond related activities. With this API, surety companies will be able to interact with the bonds to which they act as a guarantor on behalf of Trade Chain Partners (TCPs). The following API updates are made within Tinubu Surety Carrier to reflect the latest updates from the CBSA:

    1. Create eBond API:

      1. Tinubu Surety Carrier’s create eBond API will be updated so that the ‘BondValidTo’ date will default to “9999-12-31T00:00:00”.

    2. Update eBond API:

      1. As of October 2023, the following properties have been removed from the CBSA’s update eBond specification. Tinubu Surety Carrier is updating our XML payload to reflect these changes:

        1. TCPProgramNumber

        2. GuarantorBN9

        3. ProgramID

        4. BondValidFrom

        5. LegislativeAuthority

      2. Tinubu Surety Carrier’s update eBond API will be updated so that the ‘BondValidTo’ date will default to “9999-12-31T00:00:00”.

BS-14 – Bond Archive Permissions

This feature lays the groundwork for new bond archive functionality within the system. This includes database changes to create allowed actions for control over who can use these new features. These are located at the user role allowed actions: All>System Tables>Authority Levels>User Roles>Actions.

These permissions are not in effect yet and will be leveraged by further development in upcoming releases.

BS-19 – Bond Purge Permissions

This feature lays the groundwork for new bond purge functionality within the system. This includes database changes to create allowed actions for control over who can use these new features. These are located at the user role allowed actions: All>System Tables>Authority Levels>User Roles>Actions.

These permissions are not in effect yet and will be leveraged by further development in upcoming releases.

BS-24 – Legal Hold Permissions

This feature lays the groundwork for new legal hold functionality for archived bonds within the system. This includes database changes to create allowed actions for control over who can use these new features. These are located at the user role allowed actions: All>System Tables>Authority Levels>User Roles>Actions.

These permissions are not in effect yet and will be leveraged by further development in upcoming releases.

FCC-807 – New Tables and Columns to the Reporting Database

  1. The following tables have been added to the reporting database for future use with SuretyQL and Power BI reports:

    1. Base.AccountRateModifiers

    2. Base.LogRecords

    3. Base.FinancialTypes

    4. Base.MaintenanceRates

    5. Base.MaintenanceRateEffectiveDates

    6. Base.MaintenanceRateItems

    7. Base.SecuredActionsSecurityGroups

    8. Base.SecuredActions

    9. Base.SecuredActionCategories

    10. Base.SecuredActionsSecurityRoles

FUEL-3935 – Adjustment to People and Companies to Auto-Size Grids

  1. The following changes have been made to the People and Companies grid heights:

    1. The height of each grid is determined dynamically in relation to the number of rows (or entities) in each grid with the minimum grid height being 1 row and the maximum grid height being 5 rows.

    2. If the number of rows in each grid exceeds 5, the grid displays with a scroll bar so the user can scroll to rows which are beyond the max visible row limit of 5.

FUEL-3948 – Account People and Companies List Functionality

The People and Companies lists default sort order will be updated so that each list is sorted by the ‘Name’ column in ascending, alphabetical order.

FUEL-3949 – Bond People and Companies List Functionality

The People and Companies lists default sort order will be updated so that each list is sorted in ascending, alphabetical order by the ‘Name’ column.

When a person or company is selected to be named on the bond application, the person or company details screen will no longer auto open when the checkbox is selected. The checkbox will be marked and only opened if there are unanswered required fields for that entity.

MAOB-20 – CyberSource as Payment Processor Integration Option

  1. CyberSource has been added as another payment processor option for credit card billing. The integration will require a CyberSource account from the carrier to be used in processing payments.

  2. For configuration, go to: All>Setup>Payment Processor Configurations. The payment processor configuration is added by selecting CyberSource as the provider.

Subsequently, the credentials and setup fields are entered.

Once configured, the configuration can be selected to be used by the system at: All>Setup>Payment Processor Assignments.

MAOB-22 – ImageRight Document Integration

Client custom integration has been built for document and attachment storage.

SKY-336 – Addition of Tracking Number to Custom Bond Links

  1. The Custom Bond Links setting has been expanded to allow for tracking numbers from the bond to be populated into the URL being added in the setting.

    1. This setting allows clients to have links added to the bond page, which include variables coming from the bond’s information. This allows the tracking number to be passed through into the URL with #TrackingNumber# added (see sample in screenshot below).

    2. This setting is located at: All>Setup>Settings>User Interface>CustomBondLinks.

WFOB-434 – Login Types Allowed Added for Agents

  1. The Login Types Allowed field has been added to the agents create and edit pages. This field allows the agent to be configured to allow only SSO login, only traditional login, or both types.

    1. NOTE: Users are configured by default to use both types.

WFOB-467/ WFOB-468/ WFOB-469 - Bond Number Validation API

  1. A web service integration has been added that will validate bond numbers and agency code to validate manually entered bond numbers.

  2. A system validation has been created that will warn the user when an assigned bond number does not already exist in the system for the current agency.

  3. The service provides the bond number, the agency code, and the bond class bond number code. The client’s provided service can then return a response of ‘Valid’ or ‘Not Valid’.

    1. If the response is ‘Valid’, the user will be able to proceed with the bond application.

    2. If the response is ‘Not Valid’, the user will be stopped and would need to make changes to the number so that they can proceed.

  4. Bond Number validation is complete when bonds that are issued outside of the system can call the Bond Number Validation API to verify that the bond number and the agency code match.


Fixes

FCC-815 – Fix Permissions for Historic PBR and Cancellations

When navigating to a historical transaction from the bond’s History Details pop-up, the Historic PBR and Historical Cancellation bond actions were still available, even if the user’s role disallowed this access. This access has adjusted to only allow access to these bond actions if the user’s role allowed this.

NOTE: The access for these historical transactions is controlled by the “Allow Historical Term Transactions,” located at: All>System Tables>Authority Levels>User Roles>Actions.

FUEL-3962/GRA-371 – Correction to Direct Bill Number Display

When using an integration to provide a direct bill number for bonds, the number would not display on the bond page when the number is first pulled into the system from an external API. This has been corrected to ensure that the number displays properly the first time the page loads after pulling in a number for this field.

RREX-395 – Correction for Inactive Users Accessing Web Service APIs

When a user has been updated to be inactive, but the user role is enabled to access the Tinubu web service APIs, the user would still be able to access the services. This has been adjusted to disallow access to the web services if the user has been inactivated.

WEB-700/UFS-395 – Fix for Update Index Documents Background Jobs

When not using the Azure Search feature, account and bond actions could trigger the UpdateAccountIndexDocument and UpdateBondIndexDocument background jobs. These jobs would not be necessary, and this has been fixed so they are not triggered when they are not needed.

WFOB-379 – Cancellation Pro-Rating Correction for Multi-Year Prepaid Bonds

When performing a cancellation for a multi-year annual bond and the cancellation was effective during the second year or greater, the first year’s premium would be included in the proration. This has been corrected to not pro-rate the first year.

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