7.0.183.x Release Notes
Release Date |
|
|---|
Table of contents
Features
AVOB-100 – Agency Search for Account Submission
When submitting an account, the Branch/Agency drop down selection on the “Initial Account Information” screen has been adjusted for easier access and search.
This workflow has been updated as follows:
When the user clicks the "Submit an Account" link from the left navigation they will be taken to "Find Agency" screen.
Find Agency Screen will have only the Search Type drop down presented with the following options:
Agency Code
Agency Name
Agency State
Once a "Search Type" has been selected and the "Next" button is clicked, the user will be presented with any results that matched the selected search criteria on the “Choose Agency” list screen.
"Choose Agency" link will advance the user to the “Initial Account Information” screen.
If all information is validated and entered correctly, user will continue through the existing “Submit an Account” workflow as it exists today.
FUEL-2563 – Restriction of Credit Score in TransSync
Carriers may have internal practices that disallow receiving of the credit score via the TransSync process. As a result, Tinubu has added an option located at: All>Settings>ImportExport>CreditScoreToTransSync.
A system administrator will be able to update the setting, which will be delivered as True. If the Value is set False, the credit score information will not be passed in TransSync. Please ensure that if any system settings are changed, they are saved, and the Clear Cache is selected.
FUEL-2739 – Addition of Account Purpose Type Code to Experian API
In Sprint 180, the ability to use the Experian FICO 10 credit reporting API was added. This API has been updated to now include the Permissible Purpose Type within the Personal Credit Reporting configuration. This is part of the API requirements to allow the use of the FICO 10 credit scoring model. For carriers using the Experian FICO 10 subscription, 10 needs to be entered into this field.
Fixes
AEG-112 – Fixed Renewal Application when Required User-Created Generic Obligee Questions Asked on Application for Non-Generic Obligee Bond Configurations
When using additional user-defined questions in the generic obligee question group, and these questions are set to be required, renewal applications for bonds from generic obligee type bond configurations would refer due to unanswered required questions. However, as these questions would not apply for non-generic obligee configurations, this is now allowing the renewal application to process without considering these question requirements.
AMS-770 – Correction to Commission Calculation for Pro-Rated PBR when Calculated Premium is Below Minimum Premium
When using pro-rating and the premium calculation, due to a PBR adjustment, is lower than the minimum premium, the commission calculation was being set to the value calculated without the minimum premium. This has been corrected to have the proper commission calculation if the minimum premium is in effect.
AMS-771 – Correction of Commission Calculation for Pro-Rated Cancellation
When using pro-rating and cancelling a bond with return of premium for last segment of the bond term, the commission calculation was being set for the commission amount value for the entire duration of the bond term. This has been adjusted to calculate the commission based on the segments of the bond term which premium is being charged.
AVI-464/HAN-893 – Fixed Cancellations when a Premium Rate Definition Variable is not Answered Prior to Cancellation when using Rider/Cancellation Pro-Rating
When using pro-rating and cancelling a bond which uses a premium rate definition but the variables on the bond have not been answered, an error would occur. This has been corrected to allow for the cancellation to process, allowing the premium rate definition variable to be set during the cancellation transaction.
CIN-284 – Adjusted Auto Renewal Applications to Designated the Effective Date of Action to Match Bond Term’s Effective Date
When the Auto Renewal background job processes renewal applications, the effective date of action for the renewal application would be set to the date of the transaction. This has been adjusted to set the effective date of action to match the effective date of the renewal term.
NOTE: If manually renewing a bond, the effective date of action is already set to match the effective date of the renewal term.
FUEL-2595 – Corrected NPBR Email Triggers
If an NPBR was submitted on a bond application and its changes were pushed to a pending renewal, a Reject NPBR email notification was triggered and sent. This has been resolved. Now, when an NPBR’s changes are pushed to a pending renewal, the Reject NPBR email template is not triggered and sent.
1
I