7.0.231x Release Notes 3/11/2025
Tinubu Surety For Carriers
Version 7.0.231
Features
CORE-263 – Bond History Detail Enhancement
The bond history details pop-up has been enhanced to consolidate the information and improved display:
Removal of the Actions column, which contains the link to navigate to the bond transaction.
Addition of the hyperlink to navigate to the bond transaction to the bond action column.
Renaming of the ‘Name’ column to ‘Bond Action and Status’.
Addition of the bond action status to the Bond Action and Status column after the bond action and before the timestamp.
Removal of the Email column, which contains the ‘Email To’ link.
Addition of the ‘Email To’ link to the user’s name.
CORE-474 – Message AddUpdateAgent API for Updating Linked Agents
An error would occur with the AddUpdateAgent API when attempting an update to a linked agent record associated with a master agent user. This has been updated to provide an appropriate message that the linked agent user cannot be updated with these API endpoints. Alternatively, a new endpoint is being created to allow for updating linked agents (see CORE-558 below).
The message will show as “Agent user targeted cannot be updated since it is a linked agent. Use the UpdateLinkedAgent API endpoint to update linked agents."” in the response of the API call if the targeted username is a linked agent record.
CORE-558 – Addition of UpdateLinkedAgent API Endpoint
A new API endpoint (UpdateLinkedAgent) has been added to allow for updates to be made for linked agent users. This is only for agents who have been assigned to multiple agencies. This API can only update linked agents associated with a master agent.
Call can be made to https://{YourEnvironmentUrl}/EsuretyService.svc/rest/UpdateLinkedAgent
Sample body of the call:
{ "CommercialAuthType":"String content", "ContractAuthType":"String content", "DateCreated":"\/Date(928149600000+0000)\/", "Email":"String content", "FirstName":"String content", "Inactive":true, "Initials":"String content", "LastName":"String content", "LoginTypeAllowed":"String content", "MiddleName":"String content", "MobilePhone":"String content", "Password":"String content", "UserName":"String content", "WorkPhone":"String content", "WorkPhoneExtension":"String content", "AttorneyInFact":true, "IsAllAgent":true, "IsProducerOfRecord":true, "PcLicense":"String content", "ProducerCode":"String content", "SecurityRoleId":2147483647, "SecurityRoleName":"String content", "UpdatedAgentUsername":"String content"
}
The “UserName” field is to be used to target the linked agent user.
Data associated with the user is to be updated to the data included in the body of the call.
Fields not included in the call are to remain the same as prior to the call.
If sending the UpdatedAgentUsername field, the username for the user is to be updated.
If the UserName is not included in the call, the “Username is required” message will be returned.
If the AgencyCode or AgencyId is included in the call, the "Agency Code Or Agency ID is not needed. This API makes no Master Agency Changes.” message will be returned.
If the user found by the UserName is not a linked agent, the “This is not a Linked Agent - {UserName Used}, Please Use UpdateAgent API” message will be returned.
UW-31 – Inactivation of Account People and Companies
The people and companies on an account currently can only be removed. For keeping legacy data for an account, this is being adjusted so that it is a soft delete (inactivation). This will be added for account people and companies. Bond applications and subsequent bond transactions will also be limited to only active people and companies.
UW-32 – Inactivation Slider for Account People and Companies
An additional column has been added to people and companies on accounts to note their status for being active or inactive.
The active or inactive designation is editable while performing the Update People and Companies action.
Any person or company that is currently associated with an active bond is not able to be set to the Inactive status.
Records associated with an active bond will have a tooltip indicating the reason for it:
All existing records will be set to active upon delivery of the feature.
Any new records added will be initially set to active.
All records added as part of a new account application will be set to active.
UW-33 – Account People and Companies Filter for Inactive Records
The people and companies grids on accounts include a checkbox to show inactive people and companies.
By default, inactive records will not be shown in the grids unless the user checks the box to reveal these records.
UW-34 – Elimination of ‘Remove’ from Account People and Companies
When performing an Update People and Companies action on an account, the ‘Remove’ button will no longer display on the individual records. This removal feature has been replaced with the inactivation feature (see UW-32 above).
NOTE: The impact of inactive people and companies on bonds will be delivered in a subsequent release with ADMIN-470 and ADMIN-471. Until that delivery, inactive people and companies will still be available for use on new and existing bonds.
UW-437 – Account Update Setting for Users with Low Authority Level
The ‘AllowAccountUpdatesOverUserLimits’ setting has been added to allow for users with an authority level lower than the line of authority on an account to be able to update the account as long as they do not edit the line of authority. If the setting is set to True, users will be able to perform the Update Account Terms action on accounts that have a higher line of authority.
The setting is located at: All> Setup> Settings> Authentication> AllowAccountUpdatesOverUserLimits.
When the setting is configured to True and the user’s authority level is below the existing values for the account’s line of authority, the user will be able to complete the Update Account Terms as long as the line of authority fields are not altered.
One exception to this rule is if the TSC environment is using the DualAccountApproval setting, and the account is in a referred state. The user will still be able to update the line of authority above their limits while the account is in the referred state.
Fixes
ADMIN-452 – Rescinded Renewals Not to be Targeted by AutoRenewals Job
When a renewal is rescinded (rejected, declined or cancelled), the bond was still being accounted for in the AutoRenewal job, causing the job to trigger a false failure of the job. These bonds are now flagged, so that they will be bypassed in the AutoRenewal job.
BOND-110 – Comparison Rules Without the Account Question 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-464 - BeginGetBondTransactions Endpoint Failing
This fix was to the BeginGetBondTransactions Endpoint in production. Some clients had the endpoint set as https://{YourEnviromentUrl}/esuretyservice.svc/rest/BeginGetBondTransactions/. This was causing the call to the endpoint to fail due to an authentication error based on a new feature that allowed clients to limit the number of transactions in the database (by putting a number after the forward slash. This fix allows for the clients to have this additional forward slash without breaking the endpoint.
BOND-476 – Fix to Agency Change Push to Renewal from Approved PBR
When changing the agency with a PBR and pushing these changes to an existing renewal, but the PBR is referred, the agency change is not pushed to the renewal if the PBR is subsequently approved. This will save the changes of the new agency on the renewal.
CORE-468 – Prorating Correction for Initiate Cancel on Prepaid Bonds
When cancelling a bond multiple prepaid years and the cancellation is effective in the second or higher year, the premium proration was not calculated as needed. This has been corrected to properly adapt the prorating of the cancellation.
©2025 Tinubu® Square Confidential and Proprietary