2.5.144 Enhancements and Bugs

In This Topic...

Enhancements

  • The auto-cancellation job has been enhanced to use the latest bound transaction from the policy term when initiating an automatic cancellation. Previously, the system would create the cancellation from the New Business or Renewal transaction in the term as the source transaction. This occurred because the billing information used to calculate refunds associated to cancellations was stored in the New Business and Renewal transactions of the term. This enhancement was implemented in version 2.5.134 and the latest version of the Bridge Specialty Suite.

  • Billing data has now been made available to the latest transactions in a policy. Previously, billing data was only available for the New Business and Renewal transactions in a given policy term as these are the original transactions, however, this made it difficult for users working in subsequent transactions to retrieve this data without having to navigate to those original transactions, specifically when configuring auto cancellations.

    Now, the following core billing fields are available for the latest transactions in a policy:

    • BillingPolicyTermCollectedAmount
    • BillingPolicyTermOutstandingAmount
    • BillingPolicyTermEarliestOverdueInvoiceDueDate
    • BillingPolicyTermOverdueAmount
    • BillingPolicyOutstandingAmount
    • BillingPolicyRemainingUnpaidAmount
    • BillingTotalTransactionPaymentAmount

  • The Bridge system now stores the data from the Source and Source Reference columns in the General Ledger Entry Report, in the database. This change will make the data available for reporting in order to clearly distinguish between events that result in posting a Cash Receipt or moving the On Account Balance amounts within billing. This enhancement was implemented in version 2.5.141 and the latest version of the Bridge Specialty Suite.

  • A new function, ParentPolicyNumber(), has been introduced. When used, the function will return the top-most parent policy number. The function can be used in a calculated field, as a placeholder in an email, and in a Word document.

  • Previously, when using the ImportBatchReceipt web service to import batch receipts for policies that had an Effective Date set in the future, the settings for Receipt Detail Allocation were not being applied properly. The web service was missing a validation for the Apply when Policy Term is effective setting when set to active, and the cash amounts were being applied to the invoices instead of the amount being transferred to the On Account Balance of the Bill to Party. An enhancement has been added to validate if the policy term is effective in the future or not. If the policy term is effective with a future date, the system removes the receipt allocation data as per the billing setting. This enhancement was implemented in version 2.5.141 and the latest version of the Bridge Specialty Suite.

  • Previously, only users with the System Administrator or Adjuster Supervisor security roles could use the Claims data source to pull data from a claim into a policy, where the policy had been attached. An enhancement has been implemented where data from claims associated with the policy can be viewed by any user.

    The ability to implement viewing claim data in policy is a custom feature, additional view/hide rights can be implemented by a user with the Product Designer role. A service account must be enabled to use this feature. Please contact your Insurity Account Representative for details.

  • Previously, Bridge did not allow backdating when using the ImportBatchReceipt web service, so Cash Receipts with a Batch Date in the past could not be imported. The system has been updated to optionally allow any date for the Invoice date, and On Account Balance date. To enable this configuration, please contact your Insurity Account Representative.

  • Billing: Previously, for the creation of a Premium Refund, the General Ledger entry for the Premium Refund was created based on the Bind date of the policy. An enhancement will conditionally change the Entry Date for the Premium Refund General Ledger entry to be set to either the date of the policy transaction Effective Date or the transaction Bind date, whichever is greater.

Bug Fixes

  • An issue occurred when exporting a product from one environment to another, where the setting for Include Submission Creator checkbox was linked to the Include Distributor checkbox of the Master Cover - Email Configurations settings and was automatically being checked in the new environment. As a result, an additional manual step was required to uncheck the checkbox from the settings in order to avoid unnecessary emails being sent to the distributor. A code fix has been implemented, and this issue has been addressed in the latest version of the Bridge Specialty Suite.

  • For an integration call from Bridge to OMS, the Client Code would be returned, but it would not appear in the workflow submission. As a result, an error message would appear when updating the imported policy into Bridge Specialty Suite. A new custom control field for Bridge, UserID, has been added to a submission workflow as an additional input parameter, so when a policy is updated, the imported OMS policy UserID is not disturbed upon update. This issue was discovered and fixed in version 2.5.121, and the latest version of the Bridge Specialty Suite.

  • When initiating a Cancel Re-write, the premium and commission amounts would have the incorrect values in the Distributor Commission by Premium Type grid. This issue only occurred for direct bill policies when a user imported a policy via web service. A code fix has been implemented, and the proper premium and commission amounts now generate. This issue was discovered and fixed in version 2.5.141 and the and the latest version of the Bridge Specialty Suite.

  • Users reported that custom statuses were not being populated after binding a policy when there is at least one quote version available. The issue occurred due to a regression caused by a performance enhancement and it has been resolved by a code change.

  • On the Forms List screen in the Schedule of Forms workflow, a "Ready" message should appear beneath the Schedule of Forms grid when the data is saved, as per the standard functionality of other grids in the system. However, an issue occurred where, upon clicking Save and Refresh, the Schedule of Forms grid data would not load and a "Submitting all changes to server" message would appear instead. This issue has now been resolved.

  • When entering a Transaction Effective Date as search criteria to filter policies when using the GetPolicyInfo Web Service, the system was unable to retrieve an exact match for the Transaction Effective Date entered . An enhancement has been applied to retrieve policies using an exact date match to the date entered when using the Transaction Effective Date as the search parameter in the web service. This issue was discovered and fixed in version 2.5.141 and the latest version of the Bridge Specialty Suite.

  • The On Account Balance amounts were not being applied to policy invoices automatically when a cash receipt is linked to the Invoice and there are no Future Charges in the Booked status for the Policy Term. The issue has been resolved by a code change. This issue was discovered and fixed in version 2.5.141 and the latest version of the Bridge Specialty Suite.

  • Previously, values from a custom Client fields were not being saved in a quote or new transaction. This occurred when the Company Information was updated/changed for an Assured company. The process responsible for validating if there are changes to custom client fields was not running and therefore returned false, and replaced the new values with previously saved custom field values. A code update has been implemented that will now check for field modifications, and values for custom client fields are successfully saved. This bug has been fixed in version 2.5.141.

  • Previously, a replacement Endorsement would not have the changes applied from an Out-Of-Sequence transaction. This problem occurred because configurations were set to perform Auto Quote from only saved policies. As a result, a replacement Endorsement would not have the changes from the blocking transaction. A fix has been implemented in which changes for Out-Of-Sequence Endorsements merge with the replacement Endorsement.

  • Previously, for the ImportPolicy web service, if a policy contained a custom field with the Field Mapping Rule for Endorsement set to Copy From Source for a custom field, the default values from the custom field would not copy to the subsequent Endorsement. Instead, the subsequent Endorsement would contain incorrect or blank field values. This problem occurred because there was no logic in the code to copy Field Mapping Rules for the default values of custom fields. A code fix has been implemented so that policies with custom field default values now copy to subsequent transactions when importing via web service. This bug has been fixed in version 2.5.141.

  • Previously, when a user was assigned to a new company by an Administrative user, they were not able to use Single Sign-On(SSO) into Bridge. This issue occurred when deactivating an existing SSO account for the user, renaming the associated email address, and changing the account to a non-SSO account. Then when creating the user with a new SSO account and assigned a different company, SSO was not working upon logging in. A code fix has been implemented, and SSO can now be enabled for users who are assigned a new company.

  • Previously, when quoting and binding an Out-Of-Sequence Endorsement for a policy containing more than one endorsement between the New Business and OOSE transactions, the information from the first endorsement was not carried over to the replacement transaction (previous Endorsement prior to the OOSE). This issue occurred because the system was unable to correctly merge the changes from the blocking transaction to the replacement transaction. A code fix has been implemented so that when creating an OOSE, the information from the previous endorsements is carried forward to the replacement transaction accordingly.

  • Previously, an error message would appear when the Get Submission API was called. An enhancement has been made to the Submission API for all methods to ignore custom fields. Now, error messages will no longer appear when Get Submission API is called.

  • Previously, when users made an expense payment in the Claims module, the Claims History grid would not display the latest payment action. The issue was resolved by correcting the data being retrieved.

  • Previously, when a batch receipt was imported to the Bridge Specialty Suite for a policy that had multiple terms, the system did not allocate the On Account Balance (OAB) premium amount to the policy term. Instead, the system allocated the OAB to the Bill To Party. This occurred because the Web Service checked the Policy Number rather than the TermID. Since the policy number could be the same for different policy terms, the system could not allocate the charges to their respective terms. A new node for TermID has been added in the ImportBatchReceipt web service to check TermIDs when allocating OAB so that the imported policies will have their premium amount allocated to future charges accordingly. This bug has been fixed in versions 2.5.134 and 2.5.141.

  • Previously, when creating new transactions on a policy term, an Assured/Insured Company attached to the previous transaction would not carry forward into the new transaction if the company Code contained spaces. As a result, the company details in the Insured widget would appear empty after carrying forward the transaction. A code fix has been implemented to ensure a company is carried forward into new transactions, as expected. This issue was found and fixed in versions 2.5.136 and 2.5.141 of the Bridge Specialty Suite.

  • Claims: Previously, when users created a First Notice of Loss, the Claim created by field and CreatorLogonId were not being populated by the system. A fix has been implemented and the field values are now correctly populated and available for use on-screen and in documents. This issue was found and fixed in version 2.5.141 and the current release of the Bridge Specialty Suite.

  • Previously, when stepping through a submission, a server error message could appear instead of displaying the next screen in a submission workflow. This error occurred in a submission where a row had been added to a grid with formulas and then deleted. bug fix has been implemented to the Formula Evaluator so that users can proceed in the submission without an error message. This issue was found and fixed in versions 2.5.141 and the current release of the Bridge Specialty Suite.

  • Previously, in a grid with Enable Data Import selected, the Select Grid drop-down would appear empty in the Policy Grid Export/Import window. As a result, a server error would appear upon clicking Export Template or Download Template, and the programmed Excel spreadsheet would not download. A code fix has been implemented in which the method call for getting a workflow code has been updated. Now, the Select Grid drop-down will no longer appear empty for grids with Enable Data Import checked. As a result, the programmed Excel spreadsheet containing existing grid locations will now download.

  • Billing: Previously, when users canceled a policy, the General Ledger entries for cash receipts created a refund without checking the Bill To Party type. As a result, for the Bill To Party types of Direct Bill or Agency Bill, the following was created:

    • When the Bill To Party type was a Direct Bill, then a Debit entry was created for Premium Accounts Receivables.

    • When the Bill To Party type was an Agency Bill, the a Debit entry was created for Premium Accounts Receivables.

      A code update has been implemented that will create a Debit entry based on the Bill To Party type. The following will be created:

    • When the Bill To Party type is a Direct Bill, then a Debit entry is created for Premium Accounts Receivables.

    • When the Bill To Party type is an Agency Bill, then a Debit entry is created for Agency Bill Accounts Receivables.

  • Previously, in the Claims workflow, combo-box values in a grid row would not load after clicking Save, and the combo-box values could not be changed. This occurred because there was no existing ClaimID associated to the combo-box grids in the Claims workflow. As a result, the system could not retrieve ClaimIDs for combo-box grids, so the system returned Null. A ClaimID request has been added to the code, and combo-box values can now load and be changed.