7.0.210.x Release Notes
Release Date |
|
|---|
Table of contents
Features
FCCD2-28 – New Allowed Action for Changing Expiration Date
A new allowed action has been added to permit the editing of the expiration date of the bond. This allows system administrators to change bond expiration date at specific actions.
If True, this rule can be enforced for specific actions in the additional info field. If additional info is blank, all actions will be allowed.
The available actions are: Submit PBR(6), Initiate Cancellation(19), Cancel Bond (20), Reinstate After Cancel (55), Submit Renewal Application(14), Submit Renewal PBR (41), Requote Renewal Application (40), Cancel Renewal (56), Purchase Renewal Quote (17), Edit Info for New Bond Application (61), Purchase Quote for New Bond Application (4), Requote (39), Flat Cancel (47).
If False, no actions will be allowed to edit the expiration date.
FCCD2-29 – Update to Change Effective Date Allowed Action to Include Flat Cancel
The ‘Allow User to Change Bond Effective Date’ allowed action is being updated to allow for Flat Cancel to be added to the Additional Info to allow or disallow the editing of the effective date of the bond.
FCCD2-30 – Updated Description of Change Risk State Allowed Action
The description of the ‘Allow Edit Risk State’ has been updated to include Purchase Renewal Quote (17), Cancel Renewal (56), Initiate Cancellation (19), Cancel Bond (20), Flat Cancel (47), Reinstate (21), and Reinstate After Cancel (55). This allowed action currently restricts or allows changes to the risk state for these actions. The description is being updated to match the functionality.
WEB-690 – Addition of Cancellation Reason to Initiate Cancellation API
The ‘Reason’ field for cancellations is being added to the TriggerInitiateCancel API as an optional field to be sent as part of the request in the API call. This will populate the cancellation reason question for the cancellation question group (reference the Cancellations_Reason overlay) as part of the cancellation transaction.
Sample API request body:
{ "BondNumber": "Bond-1234567",
"EDOA": "\/Date(928149600000+0000)\/",
"EDOAAsString": "1/25/2024",
"Reason": "Non-Payment of Premium"
}
WFOB-395 – Addition of Login Type to User APIs
The LoginTypeAllowed field has been added to the following APIs:
AddUser, UpdateUser, and AddUpdateUser
GetUserByUsername and GetUsers
The options to be sent and are retrieved for users for the login type are:
BothSuretyAppSso – users will be able to sign into the application with username and password or SSO integration.
SuretyAppOnly – users will only be able to log in via an SSO integration configured.
SsoOnly – users will only be able to sign into the application with username and password.
If the field is not sent in the API call, the field will remain unaltered.
Fixes
FUEL-3933 – Fix to People and Companies Address Validation
When editing a person or company within a bond, changes made to the Address 2 field do not trigger the address verification functionality. The expected behavior is that when you edit an existing address, the address is verified before saving and closing the window. This functionality should extend to include Address 2 when it is used.
FUEL-3934 – Correction to Applicant Filter for People and Companies
The system is no longer defaulting “Choose Who Will Be Named on the Bond” when entering a person or company on the bond application. The expected behavior is that either a person or company will be selected in the “Choose Who Will Be Named on the Bond” drop-down per the bond configuration’s details or per the CommercialDefaultApplicantType and ContractDefaultApplicantType system settings.
FUEL-3937 – Fix to Non-Bonded People and Companies from Being Available on Bonds
When using the “Bonded” entity question on an application, entities who are answered as “No” should not display in the available list of People and Companies when selecting the “Load Selected Acct. Parties” button.
HUD-1320 – Sorting of TransSync API Payload to be Explicitly Ordered by Action Log
When calling the BeginGetBondTransactions API call for TransSync, the order of the transactions in the response is now set to ensure they are delivered in the response in the order of when the transactions occurred in the system.
RREX-373 –Correction to the Return to Bond Button for Agent Users
When a bond is changed from one agency to another during a renewal application, the ‘Return to Bond’ button is available for the new agency’s users. The intention of ‘Return to Bond’ is to return to the current version of the bond. As this is not applicable for this scenario, agents from the new agency would not have the button unless the current version of the bond is also under the same agency.
RREX-374 – Alert for People and Companies for Referral Reasons
When a person or company record is the cause of a referral, likely due to a credit score rule or other factors, an exclamation point has been added next to the name of the entity as an indicator for which record is the cause of the referral.
RREX-376 – Correction to the Renewal Button for Agent Users
When a bond is changed from one agency to another during a renewal application, the ‘Renewal’ button is available for the old agency’s users. The intention of ‘Renewal’ is to navigate to the future renewal version of the bond. As this is not applicable for this scenario, agents from the old agency would not have the button unless the renewal version of the bond is also under the same agency.
RREX-382 – Correction to Account Credit Report View
When a credit report was pulled on an account, the report would be viewable while the user remained on the page. However, if the user were to navigate away and return to the account, the report would no longer be available, and the user would need to re-pull a new report. This has been corrected to continue to have the report on the person on the account for later reference.
SCT-2048 – Search Adjustment to Allow Wholesaler Users View Child Agency Records
As a wholesaler type user from a parent agency, when searching for bonds from assigned child agencies, the bonds would not appear in the search results. This has been updated to ensure the child agency’s bonds are available for wholesaler users if the child agency is assigned to the wholesaler agency.
1
I