7.0.223.x Release Notes
Release Date |
|
|---|
Table of Contents
Features
7.0.225.x_Release_Notes (1).pdf
AVOB-80 –Bond Workflow and Override Enhancements
The workflow for bonds is being enhanced for additional underwriting rules, bond approval conditions, and premium value overrides, including a re-design for the premium section of the bond page. The following stories are associated with this feature, and additional stories will be added in subsequent releases for the full implementation of the feature:
AVOB-381 – Implementation of Month Warranty Approval for Bond Applications
As previously added in prior releases, there is a projects question "Project Warranty Months" available to be asked on contract bonds as part of the question group (see AVOB-379 on release 220). On contract authority levels, a value can be captured for Project Warranty Approval (see AVOB-95 on release 220).
When a value for project warranty approval is added to the user's authority level and the project warranty months question is asked on a bond application, these two value are compared:
If the Warranty Approval for the user’s contract authority level is equal or greater than the answer to the question, the user will have the approval bond action available.
The approval is still subject to other system checks and could still not be approved due to those other limits.
If the Warranty Approval for the user’s contract authority level is less than the answer to the question, the approval will not be able to be completed.
AVOB-390 – Implementation of Answer Contains Rules
When configuring Answer Contains rules (see AVOB-388 in prior release 221) on a bond application, these rules are being implemented to affect bond lifecycles where these rules are configured.
The Answer Contains rule compares the answers to a bond question and an account question. The account question can only be a multi-select dropdown question type. If the answer to the bond question matches one of the options selected for the account question, the rule will pass. If the answer to the bond question does not any of the selections for the account question, the lifecycle will be referred.
BS-2 – Bond Archive
Bond Archive will allow users to remove bonds from the transactional database as well as purge them completely. This feature will enable users to clean up unused or unwanted records, improving efficiency in the system and in business operations.
BS-78 – Update for Bond Archive Logs
This feature allows for the new Bond Archive table created as part of BS-77 to populate with the archive/purge/legal hold actions. This data will be used to as part of the audit reports in a future feature.
FCCD2-35 – Addition of BondId to Claim Status API
The BondId field has been added to the BondClaimStatus API endpoint. The field is optional and can be used to update a bond if the bond number passed in the call has more than one matching record in the system.
FUEL-4111 – Permission to Hide Account Commissions
An allowed action has been added to hide the account commission section of the account page, disallowing the users from viewing and/or editing the fields. The functionality from this section will continue to operate. This only removes the access for certain user roles.
MAOB-25 – Enhanced Search by Account Name to Contains Instead of Starting With
When searching for accounts with the Find Account search option by Account Name, the search entry was required to be the beginning of the name. This has been updated to allow entries where they match any part of the account name.
Fixes
AMS-2057 – Fix for Bond Execution when Billing Types Switch
When a billing type is changed during a purchase quote (i.e. Agency Bill to Direct Billed), an error was received, and the bond cannot be processed. This will allow for billing types to be changed and bonds to be processed with the new changes.
FUEL-4039 – Fix for Tax Exempt Generic Obligee with an Invalid Address
For the situation where an environment is using a tax integration and a bond uses a generic obligee and the address entered for the generic obligee is not a validated address, attempts to correct the generic obligee address to a validated address would trigger an error. This is resolved to allow for this type of correction or change without an error.
FUEL-4104 – Correction for Account Approval Authorization for Authority Levels
Authority levels have the option to set each authority level to authorize the users from that authority level to approve referred accounts. This is controlled by the UseAccountApproval setting. There is an issue when the setting is off, the enforcement of the authority level approval option is enforced. This ticket adjusts this to only enforce this option if the setting is set to True.
GRA-441 – Fix for ClearTestAgencies Background Job
An error for the ClearTestAgencies background job is being resolved.
GRA-451 – Multi-Agency Agent Switch for Other Agent Type User Roles
When using an additional agent type user role besides the original agent user role, the user was not able to switch to different agencies, if the agent is configured to have multiple agencies. This has been corrected to allow the user to appropriately switch agencies.
GRA-469 – Billing Number Integration Correction for Longer Company Names
When a company name on an account exceeded 60 characters, the billing number integration would not generate a billing number. This is being corrected to allow the longer company name length.
GRA-474 – Rounding Fix on Cancellations and Reinstates on Overridden Expiration Date
When performing cancellations and reinstatements with an overridden expiration date, the calculated premium from the adjusted term dates does not round to the nearest dollar. This is being fixed to implement the rounding of the base premium in this scenario.
MAOB-408 – Cancellation Error with Project Duration Months
When using the Projects question group including the Project Duration Months question and processing the initiate cancellation action, an error would occur when the project questions had been added to the application, removed, and then re-added. This scenario has been corrected to be handled without causing an error.
MAOB-521 – UI Correction for Changing Billing Types from Credit Card to ACH
When switching the billing type from Credit Card to ACH, the fields for the ACH entry do not load to capture the information needed for processing the ACH payment. This is corrected so that the ACH fields show when the billing type is switched to ACH.
MAOB-546 – Extension of Account Name Character Limit for New Account Applications
When applying for a new account, the account name was limited to only 80 characters. This has been expanded to be 500 characters.
STG-123 – Fix for SureLYNX Account Registration on Renewal Applications
When attempting to create an account for a SureLYNX consumer from a renewal quote, the create account link errors. This has been solved to allow for the account creation without error.
UFS-468 – Correction to Push Changes to Renewal for Penalty Amount
When a user submits a PBR after a renewal, and the new penalty is higher, the displayed amount after submission remains unchanged. This fix displays the new penalty amount, rather than the original penalty.
WFOB-351 – Correction to TransSync Duplicate Commission Tier Records
When using rider/cancellation prorating, and cancelling a bond with proration dates, the TransSyncPremiumTiers data would create 2 commission records for each commission tier. This fix creates only a single record for each commission tier.
WFOB-687 – Error Message Adjustment for Mandatory Fields
When saving an nPBR and not completing the required fields, the pop-ups for Push Changes to Account and Print Rider Documents appear before the error message. When saving an nPBR and not completing the required fields, these pop-ups will now appear after the required fields have been resolved.
WFOB-754 – Correction to Flat Cancel for Out of Sequence Proration
When using rider/cancellation prorating, the Out of Sequence message meant for Initiate Cancellation and PBR would display for Flat Cancels. With Flat Cancels overriding and zeroing the premium, this message is not needed. This message is being removed for Flat Cancel.
