7.0.190.x Release Notes
Release Date |
|
|---|
Table of contents
Features
AMS-949 – System Rules Add Person or Company at Rider or Renewal
Administrator users can create new system rules for “Add Person at Rider/Renewal” and “Add Company at Rider/Renewal.” The rule values should be set to True or False.
If rule is set to True, the following conditions are set:
If Add Person or Add Company was selected, the item WILL NOT refer.
If user changes info on existing entity tiles, item WILL NOT refer.
If user removes an existing entity, item WILL NOT refer.
If rule is set to False, the following conditions are set:
If Add Person or Add Company was selected, the item WILL refer.
If user changes info on existing entity tiles, item WILL refer.
If user removes an existing entity, item WILL refer.
FUEL-2726 – Enhancements to the Maintenance Premium Calculations
Additional flexibility is now provided on when maintenance premium starts. The previously hard coded value of 12 months has been changed to a setting that will allow the standard to be set to either 12 or 24 months. The setting can be found All>Setup>Settings>Premium>MaintenancePremiumOffsetMonths.
This setting will be delivered with a default of 12 months so as not to negatively impact bonds that have already been issued. Carriers are free to change this to their preferred option.
In addition to the setting, bond configurations can also be updated to have an option that would override this value from the setting. At All>Maintain Bond>Configure Bond>Term tab, users have the option to enter a Maintenance Time Offset Months that will override the system setting.
If this field is filled in, regardless of the setting, the maintenance calculation will not begin until that number of months have passed. It is suggested that for those carriers that allow differences, new bond configurations be created and titled with the alternative maintenance period for ease of use. It is expected that with the ability to have multiple options available for maintenance, carriers can reduce, or even eliminate, the need for manual calculations.
NOTE: There is an immediate and significant change in the entry of maintenance requirements during bond processing.
Maintenance Years has been changed to Maintenance Months. This change was made to allow for the alternate number of months entry if not full years as well as to prepare for a future development item that will also allow for partial year calculations.
In this example, the bond configuration is set to not calculate maintenance until after 18 months. Therefore, the user would enter a total of 30, which is the 18 months, plus the 12 months to be charged. In traditional circumstances, the user will just enter 12, 24, 36, etc. If no maintenance is applicable, regardless of the configuration, the user simply will not provide an entry in the field.
The code will be deployed to calculate the number of years entered at present by 12 for existing bonds. All current system users will need to be advised of this change for proper calculation going forward.
FUEL-2850 –Additional Options Added to the Change Commission Allowed Action
The allowed action of ‘Allow Commission Override’ has been enhanced to now include the Initiate Cancel and Flat Cancel bond actions. If wanting to restrict users from performing this action but allow for others, the system administrator can allow the use of the pertinent actions in the Additional Information field.
If the allowed action is True, enter the fields that you would like it to be allowed for. Fields not listed in that box would be unavailable for the user role. If True is selected but no additional details are entered, the user will be able process the commission on any transaction, without restriction.
Fixes
AVI-538/WEB-479 – Corrected Addition of Optional Question Group Entry with NPBR
When making additional entries to optional question groups with a NPBR, an error could occur. This has been corrected to allow for the previously unanswered question group to have entries made with a NPBR.
FCC-611 – Fixed Recording of Successful Login for Users using MFA
When a user signs into the application and is required to use multi-factor authentication (MFA) in the process, the system will record the successful login.
FCC-630/GRA-181 – Corrected Effective Date of Action Validation Message
When doing a transaction on a bond that included an override of the expiration date, a validation message was returned saying, "the Expiration date must be greater than effective date" even when the dates were properly set. This has been corrected to only display the validation message when it is needed.
HAN-1057 – Corrected Pushed to Renewal for People and Companies
People and company records that are added to the current bond during an NPBR and pushed to the renewal were not being copied to the renewal version of the bond. This has been addressed so that users can add or remove specific people or companies on the renewal bond if a NPBR is processed on the current bond.
HUD-900 – Corrected Effective Date of Action to Prevent Date from being Greater than Expiration Date
When editing the expiration date of the bond term to a date prior to the existing effective date of action, the effective date of action would not adjust and stay outside of the bond term dates if the transaction is submitted. This scenario has been corrected to adjust the effective date of action to match the expiration date of the bond term if the expiration date of the bond is changed to be prior to the current effective date of action.
OLR-531 – Fixed PBR Error when a Company is Pulled into the Transaction
Corrected issue with PBR transactions for company entities when the numbering of the company on the bond record is not sequentially, due to malformed data for the company record. This has been corrected to allow the PBR to process without error and properly set the numbering of the company on the bond.
OLR-534 – Corrected Background Job Error for Network Connection
On occasion, a background job would error due to a network connection issue. This has been adjusted to avoid the error.
WEB-496 – Fixed Account Show All Bonds Display when using Azure Search
When using the Azure Search option, the display of the bond list was missing the bond number (or tracking number if there is no bond number).
1
I