7.0.196.x Release Notes
Release Date |
|
|---|
Table of contents
Features
AMS-1074 – Include Fee Rates in TransSync for NPBR Transactions
For NPBR transactions for bonds with a fee rate, the fee information would not be passed into TransSync. This has been adjusted within TransSync to deliver the fee rate information into TransSync.
AVOB-209 – Enhancements to Incomplete Account Applications Queue
The Incomplete Account Application Queue has received the following updates:
Top-of-page filters:
New filter has been added for “Created By”. The list will include all the “Created By” (displayed as Last Name, First Name) users which are returned in the incomplete account applications list.
New columns:
“Agency Code” is now displayed before the “Agency Name” column.
“Created By” is now displayed before the “Application Date” column.
Rename column(s)”
“Tracking Number” is now renamed to “Tracking #”
“Account Name” is now renamed to “Account.”
“Agency Name” is now renamed to “Agency.”
The following columns have been removed from this screen:
Actions: Edit action link is now available when clicking on the Tracking #.
FCC-285 – Addition of Risk State to Bond Page Display
The risk state for contract bonds has been added to the bond page inside of the bond information section of the page. This is only applicable for contract bonds.
NOTE: If the SuppressRiskState setting (located at: All>Setup>Settings>User Interface) is set to True, then the risk state will not be editable, as well as on the bond application or when performing bond transactions.
FUEL-3771 – Unlinking of Electronic Signature Requirement from SureLYNX
If a bond is made available via SureLYNX, e-Signature would be required and the wording for the e-Signature would be applied. Bond configurations can now be separated from requiring e-Signature while being available for SureLYNX. The wording for the e-Signature has been separated so separate verbiage can be set for SureLYNX and for the Tinubu application.
The items can be located and changed as follows:
All>Localization Tables>Categories>Item Text>ElectronicSignatureSureLynx.
Select Edit Value.
Update the wording and submit.
All>Localization Tables>Categories>Item Text>ElectronicSignatureWarningSureLynx.
Select Edit Value.
Update the wording and submit.
All>Localization Tables>Categories>Item Text>ElectronicSignatureTitleSureLynx.
Select Edit Value.
Update the wording and submit.
All>Localization Tables>Categories>Item Text>ElectronicSignatureWarningTitleSureLynx.
Select Edit Value.
Update the wording and submit.
Note: Be sure to Clear Localization Cache for changes to take place.
The default wording will be same as the platform verbiage and if that is acceptable, no changes are needed. You would only make the change(s) if you would like different verbiage on either.
FUEL-3829 – Allowed Actions for Security Groups and Security Roles Added to Audit Logs
The changes to security group and user role allowed actions have been added to the audit logs records. These would then be added to the information in the Audit Logs Power BI report to be able to track changes made to these records.
UFS-290 – Addition of Mobile Phone to Agent Users
The mobile phone field has been added for agent type users. This can be used as a means for multi-factor authentication if applicable for the user role.
WFOB-137 – Allow Agency to be Assigned to More than One Parent Agency
Adding agent users to the platform for bond and/or account submissions previously meant that only one agency code per agent user was allowed. That was subsequently expanded to allow use of the Wholesaler agent option as a method of allowing said user role to have one username but be able to transact for the wholesaler (parent) agency and the sub- (child) agencies assigned to the parent agency. We further improved that functionality by allowing a system administrator to select only specific child agencies within that parent, vs. an all or nothing option.
The functionality has been further improved to now allow the wholesaler agent to be assigned to multiple parent agencies as well as individual children of all assigned parents.
When assigning an agent as a wholesaler agent, you will now see:
Select Add to move the selections to the assigned column:
When next using the Assign Children option, the children of the assigned parent(s) will display for selection. Select Add in the same manner as for the Parent:
Scenario 1 – Agency is a stand-alone agency – it is not a parent nor a child.
Agent is assigned to this stand-alone agent as a wholesaler agent user.
Select Assign Additional Parents.
Parent and stand-alone agencies display for selection.
Select Assign Additional Parents.
Sub Agency selection list will display stand-alone and parent agencies for selection.
After Assign Additional Parents selected, select back to agent.
Now select Assign Children.
Only children for the selected parent(s) will display.
When wholesaler logs in, they will see the assigned parent(s) and children for selection.
Scenario 2 – Agent is set up as a wholesaler under a Child Agency.
Select Assign Additional Parents.
Parent and stand-alone agencies display for selection.
If no additional parents are added at this stage, and the user then selects Add Children:
No Children display.
When wholesaler logs in, they will only see the child agency for selection – user is assigned to the child agency only and would not have access to the Parent of the child, nor any additional children of that parent for selection.
Scenario 3 – Agent is set up as an agent user only, either in a parent or child agency.
No option for additional parent or children selection will be available.
When agent logs into system, no selection will be available as an agent user is logged in directly to the assigned agency code.
Fixes
GRA-169 – Corrected ClearTestAgencies Job Error
When an account did not have a bond record associated to it, the account would not be removed from the environment if it was associated to a test agency, and the clear test agencies background job would error. This has been corrected to allow for this scenario.
HAN-1203 – Fixed Omission of Final Tier in Commission Rate from Maintenance Premium
When using a tiered commission rate, and the final tier is reached by the maintenance penalty amount, the commission would not calculate from the maintenance premium from that final tier. This has been corrected to calculate commission from the maintenance premium for the final tier of the commission rate.
HUD-643 – Adjusted Display for Penalty Variable for Premium Rate Definitions
When using a premium rate definition on a bond configuration, and penalty is one of the variables used; the penalty on the bond page would display and be editable in two locations. This has been adjusted to only allow the penalty to be adjusted within the premium rate definition variable at the bottom of the premium section of the bond page. The penalty field at the top of the premium section is greyed out and will be adjusted according to the penalty dropdown for the premium rate definition.
RREX-331 – Added System API Web Services to Settings Clear Cache
When clearing the cache for system settings, the cache for the system API web services related to the system settings will also be cleared.
WFOB-97/WFOB-123/WFOB-125 – Corrected Cancellation with Effective Date of Action on the Effective Date or Expiration Date of the Bond Term
When performing the initiate cancellation on a bond and matching the effective date of action to the effective date or the expiration date of the bond term, the pro-rating calculation would leave out one day’s worth of premium from the premium total. This has been corrected to include the final day of the bond term in the premium proration.
NOTE: This is only applicable if using rider/cancellation pro-rating.
WFOB-108 – Fixed Cancellation Multiple Prepaid Year Bonds with Mid-Term Effective Date of Action and a Specified Expiration Date
When a bond has a specified expiration date and is purchased with two or more pre-paid years (Annual premium calculation bonds only) and a mid-term cancellation is processed during the period of year two or more, the return premium was not calculating properly. This has been adjusted to pro-rate the partial years correctly.
NOTE: This is only applicable if using rider/cancellation pro-rating and the ‘Add Days to Expiration’ setting is set to 1 (located at: All>Setup>Settings>Premium).
WFOB-122 –Corrected Expiration Date on 1/1 Specified Expiration Date Pre-paid Bonds
If a bond configuration was set to a specified expiration date of 1/1, a Minimum Term (Days) of 0, and the bond term is for 2 or more years, the expiration date was incorrectly displaying as 12/31. Other configurations with specified expiration dates have been working correctly if they are set to the end of the month. This issue has been resolved and specified expiration date with minimum term = 0 will generate the proper expiration date as per the configuration.
1
I