7.0.208.x Release Notes
Release Date |
|
|---|
Table of contents
Features
AVI-666 – Addition of Address to Change Obligee Display
The Address field is being added to the search results in the Change Obligee Pop-up.
NOTE: To enable this feature, edit the user role to have the Allow Change Obligee allowed action set to True: All>System Tables>Authority Levels>Actions.
FCCD2-2 –Account and Bond Claims Status
Bonds will have the ability to be marked if a bond has an active or historical claim associated with it. This status will be updated through an API call. Once this status is designated on a bond, any future bonds can use the claims status from any bonds on an account as underwriting rules for bond applications, renewals, or riders associated to the account.
FCCD2-20 – Claims Status Added to Account’s Show All Bonds
The Bond Claims Status is being added to the Show All Bonds page for account to identify any bonds with an Active or Historical claims status. An additional filter will be added at the top of the page to filter the contents of the page to bonds with active, historical, or no claims history.
FCCD2-22 – Addition of Active Claims System Rule
A new system rule is being added named ‘Active Account Claim Status’. The rule would evaluate if the account associated with the application has any bonds with an active claim status.
Rule value can be configured to = False or = True.
Rule can be set to be an auto-approval rule.
The business use case would be to configure the auto-approval rule to = False.
The bond would auto-approve if the account does not have an Active Claims status on any of its bonds (pending the evaluation of any other rules).
If the account does have an Active Claims status on any of its bonds, the application would refer.
Rule can be set to be an auto-rejection rule.
The business use case would be to configure the rejection rule to = True.
The bond would auto-reject if the account does have an Active Claims status on any of its bonds.
If the account does not have an Active Claims status on any of its bonds, the application would auto-approve (pending any other rules).
This rule can be applied to the New Bond Application, Renewal, NPBR, and/or PBR lifecycles on the application it is set on.
FCCD2-27 – Deprecation of Submit Claim and Edit Claim Bond Actions
The Submit Claim and Edit Claim bond actions are being deprecated as the Claims Status API will be the new way of tracking claim statuses on bonds and accounts. These will no longer be available to be used on any bonds as of this release.
FCCD2-3 – States and Branches to User APIs
The states and branches assigned to a user are being added to various user based APIs to further assist in user management and maintenance.
FCCD2-24 – Addition of States and Branches to GetUsers API
A new version of the Tinubu Surety Carrier API is being implemented as version 2. This will have a new URL endpoint:
https://[environmenturlprefix]svc.e-surety.net/esuretyservice2.svc/rest/GetUsers
Note the update to the end of the URL with ‘…esuretyservice2.svc”
The prior version (1) will continue to be offered and no changes have been made to it.
In version 2, the branches and states associated with a user are being added to the response of the GetUsers API. The response will contain an array for each in the following format:
"UserBranches": [
{"BranchCode": "SE",
“BranchId”: 500000,
"BranchName": "Southeast",
"IsPrimaryBranch": true},
{"BranchCode": "NW",
“BranchId”: 1000000,
"BranchName": "Northwest",
"IsPrimaryBranch": false}]
"UserStates": [
{"StateAbbreviation": "SC",
"StateName": "South Carolina"},
{"StateAbbreviation": "FL",
"StateName": "Florida"}]
FCCD2-25 – Addition of States and Branches to GetUserByUsername API
A new version of the Tinubu Surety Carrier API is being implemented as version 2. This will have a new URL endpoint:
https://[environmenturlprefix]svc.e-surety.net/esuretyservice2.svc/rest/GetUsers
Note the update to the end of the URL with ‘…esuretyservice2.svc”
The prior version (1) will continue to be offered and no changes have been made to it.
In version 2, the branches and states associated with a user are being added to the response of the GetUserByUsername API. The response will contain an array for each in the following format:
"UserBranches": [
{"BranchCode": "SE",
“BranchId”: 500000,
"BranchName": "Southeast",
"IsPrimaryBranch": true},
{"BranchCode": "NW",
“BranchId”: 1000000,
"BranchName": "Northwest",
"IsPrimaryBranch": false}]
"UserStates": [
{"StateAbbreviation": "SC",
"StateName": "South Carolina"},
{"StateAbbreviation": "FL",
"StateName": "Florida"}]
FCCD2-26 – Addition of States and Branches to Add and/or Update Users API
A new version of the Tinubu Surety Carrier API is being implemented as version 2. This will have a new URL endpoint:
https://[environmenturlprefix]svc.e-surety.net/esuretyservice2.svc/rest/GetUsers
Note the update to the end of the URL with ‘…esuretyservice2.svc”
The prior version (1) will continue to be offered and no changes have been made to it.
In version 2, the AddUser, UpdateUser, and AddUpdateUser APIs have been updated to allow for states and branches to be passed in the request.
Here is a sample portion for the request:
"UserBranches": [
{"BranchCode": "SE",
"IsPrimaryBranch": true},
{"BranchCode": "NW",
"IsPrimaryBranch": false}]
"UserStates": [
{"StateAbbreviation": "SC"},
{"StateAbbreviation": "FL"}]
When updating a user record, if the request does not include the UserBranches and/or UserStates objects in the call, there will be no update to the existing branches and/or states. If one of the objects is sent but empty, then the branches or states would be removed.
Error messages:
If an invalid state abbreviation is sent, an error message would be returned: "Invalid state abbreviation sent in the request. Please review the state abbreviations."
If an invalid branch code is sent, an error message would be returned: "Invalid branch code sent in the request. Please review the branch codes."
Additional Notes:
The AddUser API is only for adding new users. If the Username already exists, proper messaging is in place to alert the user exists.
The UpdateUser API is only for updating existing users. If the Username does not exist, proper messaging is in place to alert the user does not exist.
The AddUpdateUser API is for either adding or updating users. If the Username already exists, the data sent will update the user. If the Username does not exist, the user will be added.
HUD-1185 – Change Agency Able to Search by Agency Code
When a user was changing the agency on a bond, the search for the new agency was only reviewing agency names. This has been expanded to include agency code as searchable criteria.
Fixes
AMS-413/FCC-332/WFOB-271 – Correction to Bond View after Agency Change
When a bond changes agency, the view of the bond is adjusted to allow the prior agency to only access the bond transactions associated to that agency. For the current agency, agent users will be able to only view transactions associated with the current agency. The search features are also being adjusted to include bonds in the search results for both agencies. When navigating to the bond, the agent user will be directed to only the transactions associated with its agency.
AVI-469 – Fix to Change Obligee Adjustment of Obligee Location
When changing the obligee on a bond (contract bonds only) and the obligee has multiple locations to be selected, the obligee locations would not update after selecting a new obligee. This is fixed to have the obligee location dropdown updated to reflect the locations for the newly selected obligee during the transaction.
If an obligee has only one location added, the dropdown will default to that location as the new selection. If an obligee has multiple locations, the dropdown will be blank, and the user will be prompted to select a location.
1
I