Bridge 2.4.87 Release Notes Addendum

Bridge
2.4.87 Release Notes Addendum

Version 2.4.85Bridge User Guide2.4.85 Release Notes

Table of Contents

Purpose of This Document

Core Enhancements

Setting a New Licensee HQ Company

Creating and Viewing Quote Versions

Minor Enhancements and Functionality Fixes

Enhancements

Fixes

Bridge User GuideRelease Notes Addendum

Purpose of This Document

Therelease notesdocument for each new version detailsnew features, enhancements, and fixes to be found in each release of the Bridge platform. Some changes are patched to previous versions, and are detailed in this Addendum document.

Bridge User GuideRelease Notes Addendum

Core Enhancements

Setting a New Licensee HQ Company

In order to customize the licensee company hierarchy, a new or existing licensee company can be set as the licensee HQ.

A new checkbox, Top Level, has been added to the Company panel of the Licensee Information screen. Saving a company with this setting will make it the new HQ company, and the previous HQ company will become a subsidiary of the new HQ.

Access to this checkbox is controlled by the new ChangeOwnership security right. This right has not been added to any security roles by default.

This feature was introduced in version 2.5.100.

For details on creating licensee companies, see the section on Creating a New Licensee Office in the User Guide -Reference and Administration document.

Creating and Viewing Quote Versions

In order to control access to the Create Quote Version and Create Quote Version List options in a transaction, two new security rights have been added.

The CreateQuoteVersion right controls the user's ability to view the Create Quote Version option in the Actions widget. The ViewQuoteVersionList right controls the user's ability to view the Quote Versions List option in the Common Screens widget.

The Allow Quote Versions setting in the master cover must also be checked in order for these options to be available.

The CreateQuoteVersion and ViewQuoteVersionList rights have been automatically added to any security roles that include the CreatePolicy or CreateSubmission security rights.

This feature was introduced in version 2.5.107.

For details on security rights, see the Security Rights section in the User Guide - Security Rights document.

Bridge User GuideRelease Notes Addendum

Minor Enhancements and Functionality Fixes

Enhancements

Previously, users that had access to the Cognos Reports tool could see all reporting data in the system, regardless of their user account. Moving forward, the information available to each user will be tailored to their account. This enhancement was introduced in version 2.4.89.
A new option list resource type named CustomWebService has been created. It is visible in the Resource Type field of the Data Source Properties panel on the Option List Management page when the Type field is set to Static. This is part of a larger feature that will allow custom web services to be used with Data Source Configurations. It is currently not in use and it is recommended to not create any option lists that use this resource type.

Fixes

Updates made to option list items in one environment would not appear when the product was imported into another environment. This was due to a problem with the import process and has been corrected. This fix was introduced in version 2.4.88.
Combo boxes that use grids as a data source would sometimes not display all records from the grid. This has been corrected. This fix was introduced in version 2.4.88.
Asynchronous integration calls would display an error even when they were completed successfully. This has been corrected. This was fixed in version 2.4.88.
A server error could occur when publishing a workflow. This occurred because the system was including deleted universal triggers in the publish process. This has been corrected. This fix was introduced in version 2.4.88.
When logged in as a distributor, an error could occur when saving a new client as part of creating a new submission. This has been corrected. This fix was introduced in version 2.4.88.
Documents added as attachments in the Documents field of Automatic E-mail Configurations would sometimes not be saved. This has been corrected. This fix was introduced in version 2.4.88.
Some rows belonging to child grids would sometimes be deleted during the Calculate Quote process. This has been corrected. This fix was introduced in version 2.4.88.
The CheckComplianceHit function would always return false and not output results to other fields. This has been corrected. This fix was introduced in version 2.4.88.
Data Validations configured to activate when saving changes made to detail windows for View Grids would not activate. This has been corrected. This fix was introduced in version 2.4.88.
Certain images and icons were missing from the workflow. These included combo box drop-down arrows, warning icons and pin images. This has been corrected. This fix was introduced in version 2.4.89.
Renewal transactions would not be able to be created due to a validation error stating that at least one term in the policy was not declined or bound. When the renewal was attempted, the system was associating Renewal - Incomplete transactions to the policy that could not be seen by the end user, which caused the validation error to occur. This has been corrected. This fix was introduced in version 2.4.89.
A validation error could occur when trying to import a product if it contained a Data Table or Data Source Configuration used in two workflows, where one of the workflows was a shared workflow of the other. The validation message would state that either a Data Table Definition or Data Source could not be imported since another Product had one with the same code. This has been corrected by removing this validation rule from the system. Since workflows can be shared, the rule is no longer necessary. This fix was introduced in version 2.4.89.
The thousands separator and rounding precision of a Textbox Decimal field would not be correctly applied after entering a value and then either tabbing out of the field or clicking outside of it. This has been corrected. This fix was introduced in version 2.4.88.
The system would add a value of zero to a Textbox Decimal or Textbox Integer field if the user placed the curser in the field and then removed it without entering a value, and no other settings were configured to populate the field with a zero-value. This has been corrected. This fix was introduced in version 2.4.88.
When the Modern Large Font or Modern Small Font skins were used, the comma, currency symbol and separators in the Premiumwidget would be partially or completely cut-off. This has been corrected. This fix was introduced in version 2.4.89.
A server error could occur when clicking on the Issue Quote action, the Next button or on a link in the Submission Screens widget. The error log would contain messages stating that fields referenced by triggers did not exist in the Product Library, and that calculated fields weren’t added to the Product Library. This has been corrected. This fix was introduced in version 2.4.89.

A server error would occur when clicking on Endorse, Adjust, Reinstate, Renew or Copy in the Actions widget for a bound transaction. This would occur in workflows containing checkboxes where Default was chosen to be the initial value for the control in the Field Initial Value Settings panel on the Field Management page. This has been corrected. The fix was introduced in version 2.4.90.
An error could occur when performing the Get Quote, Bind, or Endorse actions. This error was most likely to occur when the system was simultaneously processing a high number of submissions. This has been corrected.This fix was introduced in version 2.4.90.
The LookupDataSource function was case-sensitive, and would not work if the case did not match exactly. This has been corrected so that case does not affect the functionality. This fix was introduced in version 2.4.90.
A server error would occur when the system had to copy a transaction that contained a checkbox field whose initial value was set to Default in its Field Initial Value Settings panel and whose Apply Default field was set to None. This has been corrected. This fix was introduced in version 2.4.90.
A server error could occur when trying to view the Data Source Configuration Management page for a configuration that used a Web Service as the Data Source Type. The error would occur in a system withtwo option lists having a Resource Type ofWeb Service that both contained an item with the same Code. To correct the issue, the licensee must delete one of the items that uses the shared Code.
Correlated option lists in tab workflows would be empty when configured to auto-populate according to the default selection of their parent list. Changing the selected item in the parent and then reselecting the default item would cause the child list to populate correctly. This has been corrected. This fix was introduced in version 2.4.90.
A server error could occur when saving changes made to a child tab workflow. This fix was introduced in version 2.4.90.
The SmartView dashboard would sometimes fail to load. This has been corrected. This fix was introduced in version 2.4.90.
The thousands separator and rounding precision of a Textbox Decimal field would not be correctly applied after entering a value and then either tabbing out of the field or clicking outside of it. This has been corrected. This fix was introduced in version 2.4.90.
The system would add a value of zero to a Textbox Decimal or Textbox Integer field if the user placed the curser in the field and then removed it without entering a value, and no other settings were configured to populate the field with a zero-value. This has been corrected. This fix was introduced in version 2.4.90.
Combo boxes with data source configurations whose Key Column Rule was set to Specify Alternate Key Column wouldcause a server error when the search was activated. This has been corrected. This fix was introduced in version 2.4.90.
The system would not renew all policies set to be automatically renewed. This has been corrected. This fix was introduced in version 2.4.90.
When quoting an incomplete transaction, an error could be displayed about not being able to preview the payment schedule. This error would occur when a quote validation was triggered in a configuration with just a single quote option and a single payment plan. This has been corrected. This fix was introduced in version 2.4.90.
Multi-select control types, such as Checkbox Group, Include Exclude List, and Multi Select,in tab workflows would not save their values.This has been corrected. This fix was introduced in version 2.4.90.
In some cases, clicking Next in a claims workflow would fail to activate validations and would not save changes to the screen. This would occur when a validation should have triggered, but failed. This has been corrected. This fix was introduced in version 2.4.90.
The page numbers for generated documents would reset at various intervals. This has been corrected. This fix was introduced in version 2.4.90.
Data Validations would activate at incorrect times when using a browser whose language was not set to English. The validations were associated to Textbox (Decimal) fields where periods were used as the thousands separator, and commas were used as the decimal separator. This has been corrected. This fix was introduced in version 2.4.91.
Calculated field formulas would produce incorrect results when the web browser language was not set to English. This has been corrected. This fix was introduced in version 2.4.91.
Premium Adjustmentsmade in a transaction would not be considered for other rate calculations applied to the same Premium Type. This has been corrected. This fix was introduced in version 2.4.91.
A validation error related to invalid currency codes would occur during the activation of Integration Configurations. This has been corrected. This fix was introduced in version 2.4.91.
A server error would occur when exporting a product. This has been corrected. This fix was introduced in version 2.4.91.
When a quote would be calculated, the premium would be incorrect when the web browser language was not set to English. This has been corrected. This fix was introduced in version 2.4.91.
Actions in the workflow that were dependent on large formulas would sometimes fail to occur. An example of such an action would be the populating of a grid following the system’s evaluation of a formula. This would occur whenever the system needed more than ten seconds to evaluate the formula. Prior to this fix, the system would abandon the formula evaluation after ten seconds, causing any subsequent actions that needed the results of the evaluation to fail. To correct this problem, the system has been enhanced to evaluate formulas much more quickly, and the ten second limit has been increased to one minute. This fix was introduced in version 2.4.91.
A server error could occur when clicking on theE-mails link in the Common Screens widget. The error would occur if the e-mail history contained e-mails belonging to inactive E-mail Templates. This has been corrected. This fix was introduced in version 2.4.91.
A server error could occur when clicking on any link in the Policy Information widget while viewing a transaction belonging to a product that was imported. This has been corrected. This fix was introduced in version 2.4.91.
Following a product import, an incorrect province or state would appear for certain clients in the Client Information widget and the State/Province column in the Client List panel. This has been corrected. This fix was introduced in version 2.4.91.
The LookupDataSource function could fail and prevent any subsequent functions in the same formula from activating. This would occur when the LookupDataSource function activated a Data Source Configurationthat used a Data Table and where no results were found. This has been corrected. This fix was introduced in version 2.4.91.
Some users expected Field Evaluation Rules to activate when saving changes from within a Tab Workflowor Detail Window. Bridge does not currently support the activation of Field Evaluations Rules when saving changes from within these items.
Operation timeout errors would occur during the activation of certain Integration Configurations. The configurations that would experience the error were those whose message size exceeded 33 MB or which required more than ten minutes to process. To correct the issue, the system has been enhanced to allow a maximum message size of 200 MB and a maximum processing time of 120 minutes. This has been corrected. This fix was introduced in version 2.5.100.
A server error could occur after selecting a Product while starting a new submission. This would occur whenever the Distributor List panel was configured to show the Distributor Link column, which is no longer used by the system. To correct this, any existing configurations of the Distributor List panel that displayed the Distributor Link column have been updated so that the Distributor Link column is no longer displayed. This fix was introduced in version 2.5.100.
A server error could occur when accessing a policy. This was most likely to occur during periods of high server traffic. This has been corrected. This fix was introduced in version 2.5.100.

Description / Activity / Conditions / Correction / Fixed in Version
Rich Text Control was collapsed by default. / Responsively Disclosing a Panel with a Rich Text field. / A driver field discloses a panel in the submission screen. / This has been corrected. / 2.5.101
Bridge resources are deleted, such as Lookup Tables, Quotes, etc. / Deleting a transaction. / When a transaction has the same resource id as any existing bridge resource, deleting the transaction can also delete the resource. / This has been corrected. / 2.5.103
RowID SequenceNo is not working as expected. / Add Grid rows. / Deleting certain rows results in Row IDs (number) being reused instead of incrementing. / This has been corrected. / 2.5.103
A cancellation transaction was throwing an error when premium was zero. / Cancelling a policy with zero premium. / Premium must be zero. / This has been corrected. / 2.5.103
"Referral Accept". Integration service call failed. / Integration succeeds but a validation is thrown and no e-mail is sent out. / An integration fails to populate Bridge fields. / This has been corrected. / 2.5.108

Bridge User GuideRelease Notes Addendum

All material in this document and on this website are protected by copyright and intellectual property laws and are the property of Oceanwide Canada Inc.

No part of this document may be reproduced, stored in a retrieval system, or transmitted by any means, electronic, mechanical, photocopying, recording or otherwise, without prior written permission from the owner Oceanwide Canada Inc. Printed and published in Montreal, Quebec CANADA.

Trademarks

All trademarks, registered trademarks and service marks in this document are exclusive to Oceanwide Canada Inc.

Disclaimer

The publisher Oceanwide Canada Inc. and authors specifically disclaim any responsibility for any liability, loss, or risk; whether corporate, personal or otherwise in whole or in part of which; is incurred as a consequence directly or indirectly of the application use; or reliance on or any of the contents of this document (documentation).