7.0.182.x Release Notes
Release Date |
|
|---|
Table of contents
Features
Fuel-2194 – Localization of Add New Person/Company Labels
The labels within the display for adding a new company or adding new person to a bond or account have been localized. This allows carriers the option to change the wording to better suit their needs and process for submissions.
For Adjusting these values go to: All>Localization Tables>Categories>Headings>Keys. Find the AddNewCompany and/or AddNewPerson records to edit the text. Be sure to Clear the Localization Cache (left side menu) once changes are complete. If needed, please reach out to Tinubu Surety Support for additional assistance.
Fuel-2419 – Expansion of Data Available for Reporting on Warehouse Database
The following tables have been added to the reporting warehouse database
Base.ApplicationTemplates
Base.DecisionRuleExpressions
Base.DecisionRuleInputs
Base.DecisionRuleModifiers
Base.DecisionRules
Base.BondTypeDocuments
Base.CreditScoreRanges
Base.CreditScoreRangeItems
Base.DocumentTemplates
Base.DocumentTypes
Base.DropdownLists
Base.DropdownListItems
Base.LifeCycleEvents
Base.PremiumRateItems
Base.PremiumRateDefinitionDetails
Base.PremiumRateDefinitionItems
Base.PremiumRateEffectiveDates
Base.QuestionGroups
Base.QuestionGroupTemplates
Base.Questions
Base.QuestionTemplates
Base.QuestionTemplateLifeCycleEvents
Base.QuestionTexts
Base.TexasNotaryInfo
The following tables added the AddressId column:
Base.People.AddressId
Base.Companies.AddressId
Base.Agencies.AddressId
Fuel-2623 – Responsible Underwriter Primary Branch Code Available for TransSync Custom Field Mapping
The branch code value for a bond’s responsible underwriter’s primary branch is available to be sent in the TransSync custom fields. Please contact Tinubu Surety Support for assistance in mapping this your environment’s custom TransSync mapping.
Fixes
Fuel-2454 – Fixed Data Retainage when Rejecting a Referred PBR
When a PBR is referred and subsequently rejected, edited fields would retain the values for the fields. This has been corrected to return the fields to the values prior to the PBR transaction.
Fuel-2534 – Filter in SureLYNX for Inactive Bond Configurations
Filtering of the bond configurations in SureLYNX has been added to exclude any configurations where the bond configuration is inactive or if the bond class, bond category, obligee, or carrier of the bond configuration are inactive.
NOTE: The same already applies for bond configurations for agent and carrier users.
Fuel-2562 – Corrected Original New Bond Documents Generating when Rider is Referred
When selecting to reprint the original new bond documents on a rider transaction, and the rider is referred, the documents would be generated. This has been corrected so that the forms are only generated when the rider is auto-approved or approved after the rider has been first referred.
NOTE: this scenario was only created when the rider documents setting is enabled at: All>Setup>Settings>SystemDefault>EnableRiderDocumentGenerationOptions.
Fuel-2582 – Fixed Return of Premium with Direct Billed – Invoice/Check Billing Type when not able to Refund with a Credit Card Billing Type
Refunds are not allowed by certain payment processor providers. If a refund is attempted using the Credit Card billing type, the system allows for an alternative billing type to be used. This is determined by the BillingTypeForRefusedRefund setting located at: All>Setup>Settings>Payment>BillingTypeForRefusedRefund. An error would occur when using the Direct Billed – Invoice/Check option. This has been corrected to allow for credit card refunds to be processed with this billing type.
NOTE: Refunds using the Agency Billed billing type is not affected and is operating correctly.
Fuel-2680 – Adjusted Equifax Credit Report PDF Delivery
The Equifax credit reporting integration has been adjusted to allow for the Equifax service to have additional time to receive the credit report PDF so that the PDF can be generated from Equifax and be sent in the API call.
Fuel-2681 – Corrected Error for Bid Bond Conversions when Bid Bond is Configured to have an Expiration Date, and the Expiration Date is Overridden
When converting a bid bond to a final bond, and the bid bond configuration has been set to have an expiration date and that expiration date has been overridden on the bid bond, an error would occur during the conversion process. This has been adjusted to allow for the conversion regardless of the bid bond’s expiration date.