bridge 2.4.86 release notes -...

0Table of Contents

Version 2.4.85 Bridge User Guide 2.4.85 Release Notes

Bridge

2.4.85 Release Notes Addendum

iTable of Contents

Table of Contents

TABLE OF CONTENTS.........................................................................................I

PURPOSE OF THIS DOCUMENT........................................................................1

CORE ENHANCEMENTS.....................................................................................2

Policy Terms Can No Longer Be Manually Locked................................................2

Enhancements and New Functions for Copying Data to Grids.............................2

MINOR ENHANCEMENTS AND FUNCTIONALITY FIXES.................................4

Enhancements............................................................................................................4

Fixes............................................................................................................................4

Bridge User Guide 2.4.85 Release Notes Addendum

1Minor Enhancements and Functionality Fixes

Purpose of This Document

The release notes document for each new version details new 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.



Core Enhancements

Policy Terms Can No Longer Be Manually Locked

The ability to manually lock a policy term was removed from the system. The system would often lock a policy term in the background, however the Lock action would often still be available to end users. In this scenario, if users were to click on the Lock action, an error would occur.

Notes:

The system will continue to automatically lock policy terms as it does currently.

Users with the LockUnlockPolicy security right will still be able to manually unlock policies, but they will no longer be able to lock them.

The Lock action will no longer be available in the Actions Widget.

This was introduced in version 2.4.88.

Enhancements and New Functions for Copying Data to Grids

The NewGrid and SaveToGrid functions have been enhanced with a new optional parameter that allows each row to be duplicated as many times as needed.

The copies parameter and associated p5 parameter (to specify the number of copies) can be included at the end of each function.

NewGrid(p0, p1_SequenceNo, p2, p3, p4, p3, p4, copies, p5)SaveToGrid(p0, p1_SequenceNo, p2, p3, p4, p3, p4, …, copies, p5)



These are optional parameters. If they are not included, the functions will process normally and produce one instance of each row according to the configuration of the function. If the parameters are included, each row will process normally according to the configuration of the function, but will be added to the target grid multiple times. If the p5 parameter is 1, then one duplicate of each row is created, resulting in two identical rows. A parameter of 3 will produce four identical rows.

A new function, NewList, has been added. This function takes a comma-separated list and returns a list of the values, formatted to be used in other functions such as NewGrid and SaveToGrid.

NewList(p0,…)P0 (text): List of all values, separated by commas. These can be placeholders, functions, formulas, or literal values.Returns (): A list of all provided values, formatted for use in other functions.

Another new function, BreakText, has been added. This function takes a large string value and splits it into smaller string values with a specified maximum length. This produces a list of strings, formatted to be used in other functions such as NewGrid and SaveToGrid.

BreakText(p0,p1)P0 (text): This identifies the text to be split. This can be a placeholder, function, formula, or literal value.P1(integer): The maximum number of characters in the sub-strings. If the character number falls in the middle of a word, the system will move back to the nearest whitespace, such as a space, tab, or line break character. If a single word exceeds the maximum number of characters, the word will be split at the character limit.Returns (text): Returns the resulting sub-strings as a list of strings, formatted for use in other functions.

These enhancements were introduced in version 2.5.100.

For details, see the Full Function Reference List section in the User Guide - Calculated Fields document.



Minor Enhancements and Functionality Fixes

Enhancements

Previously, buttons in the Screen Button Bar could be missing from view. This would occur when too many buttons were configured to appear within the bar’s available space, if users increased the zoom-level above a certain amount, or if the screen was resized. A new internal setting has been added to prevent this. When it is enabled, the system will add extra rows so that all buttons are displayed. When it is disabled, any buttons that cannot fit in the first row will be hidden from view. The internal setting is disabled by default. To enable it, contact your Oceanwide Representative. This was introduced in version 2.4.89.

The automatic processing of cancellation finalizations has been updated. Previously, checking the Enable Automatic Cancellation Finalization checkbox would cause the system to wait for a cancellation’s Effective Date before deciding whether or not to rescind or confirm the cancellation. Following this update, the system will now also make this decision during every automated review of all policies in Cancellation - Quoted status. During each review, the system will evaluate the trigger specified in the Automatic Cancellation Finalization panel. If it evaluates to true, the system will confirm the cancellation if the cancellation’s Effective Date is earlier than or equal to the current date. If it evaluates to false, the cancellation will be rescinded immediately.

This new functionality is particularly useful when you want the system to decide whether or not to rescind a cancellation before the cancellation’s Effective Date, such as when a payment is made on a policy that is nearing cancellation.

This was introduced in version 2.4.89.

When an advanced lookup that is activated by a combo box returns no results, a message will indicate so at the bottom of the combo box dropdown. This was introduced in version 2.4.90.

When a transaction has multiple Quote Versions, the most recently created version appears in the Submission/Policy List panel. Following this enhancement, once a quote version is Bound, that version will appear instead. This was introduced in version 2.4.90.

Fixes



When accessing the Audit Trail for a claim, a system error could appear with a message similar to "Value cannot be null". This was caused by an error in a recent update that did not properly check for null data. This has been corrected. This fix was introduced in version 2.4.87.

Advanced lookups in the Claims module would sometimes not return any results. This was due to a recent enhancement that erroneously affected the module. This has been corrected. This fix was introduced in version 2.4.87.

The web service to import claim payments could fail when then amount was missing. This issues was introduced by a previous fix that incorrectly assumed the amount would always be provided. This has been corrected. This fix was introduced in version 2.4.87.

An error could occur when publishing a workflow containing the LookupDataSource function. This occurred when the function referenced a data source configuration that used fields whose Calculated Field Formula field was empty. This has been corrected. This fix was introduced in version 2.4.87.

An error could occur when importing a product. This would occur when the import file exceeded 33 MB, which previously was the maximum allowable file size. This has been corrected by increasing the maximum allowable file size to 2048 MB. 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 quoting a transaction in Referral status, a message would appear about being unable to preview the payment schedule, This has been corrected. This fix was introduced in version 2.4.88.

A server error could occur when creating a Quote Version for certain workflows. These workflows were those containing grids with records that had files as attachments. After entering a quote version in the Create Quote Version window and clicking Confirm, the error would occur. This has been corrected. This fix was introduced in version 2.4.88.

A server error could occur when trying to reverse a receipt. This would occur when the post would fail due to validations, but the system was still trying to generate and post billing adjustments. This has been corrected to not generate adjustments if the post is not successful. This fix was introduced in version 2.4.87.

Navigating through a claims workflow would not respect the sequence order of the screens, instead using the order they were added to the workflow configuration. This has been corrected. This fix was introduced in version 2.4.88.

In a claims workflow, panel overrides to make a panel read only were not working. This has been corrected. This fix was introduced in version 2.4.88.



A server error could occur when trying to reverse a receipt. This would occur when the post would fail due to validations, but the system was still trying to generate and post billing adjustments. This has been corrected to not generate adjustments if the post is not successful. This fix was introduced in version 2.4.87.

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 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 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.

A server error could occur when attempting to log into the system. This was due to a faulty database query that would launch during the login process, which has been corrected. This fix was introduced in version 2.4.87.

When reversing a receipt, an incorrect error message would appear about the allocation amounts. 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.

A server error could occur when trying to access a policy. This was due to versioning issue with internal components, which has been corrected. This fix was introduced in version 2.4.89.

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.89.

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.89.



The LookupDataSource function would not display any results or output to any fields when used with a Data Source Configuration that used Grid as its Data Source Type. An error referring to an invalid cast exception would also appear in the Event Tracking report. This has been corrected. This fix was introduced in version 2.4.89.

When the same grid repeater trigger was used in two or more documents being printed together (using multiple templates in a configuration), the trigger would not be evaluated again after the first instance. This would produce incorrect results for the remaining instances. 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.

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.

The Driver Field in the Rate Rule window would sometimes not show any fields. This was most likely to happen in workflows containing a large number of fields. 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.

Cancellations in Quoted status would be confirmed before their cancellation Effective Date. This would occur for cancellations belonging to master covers that used the features in the Automatic Cancellation Finalization panel, where the Enable Automatic Cancellation Finalization checkbox was checked, and the Trigger evaluated to true. 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 Adjustments made 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.

Posted payment amounts were being doubled before being added to the Billing.TermTotalCollectedAmount integration field. 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 would occur when attempting to Bind a policy where the payment plan was automatically selected by the system. This has been corrected. This fix was introduced in version 2.4.91.

Users would have to click more than once on the search icon of combo boxes that used the Address Lookup web service in order to activate the search. This occurred when the lookup was placed in a Detail Window. 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 Configuration that used a Data Table and where no results were found. This has been corrected. This fix was introduced in version 2.4.91.

The Policy Term Outstanding Amount placeholder could return the wrong amount. This would occur when traces of duplicate invoices were found in the system. This has been corrected. This fix was introduced in version 2.5.100.

Description Activity Conditions Correction Fixed in Version

Job execution was failing.

ExportBillingInfo daily scheduled job.

Some expected validations from policy were being considered errors.

This has been corrected.

2.5.102

ImportPolicy was failing as part of ExportBillingInfo job.

ImportPolicy web service was failing for some transactions.

The earliest overdue invoice date was NULL.


2.5.102

Billing only sends New Business and Renewal data to Policy.However, in order to be able to cancel or rescind quoted cancellations, Billing has to send data about quoted

Execution of Export Billing Info Job.

Information for Quoted Cancellation transactions are sent from Billing module to Policy.


2.5.102



Cancellations as well.

EHO when importing a product.

Import a product from the UI.

The import file does not contain IsSysResource attributes.


2.5.102

Latency experienced Setting the Master Cover from Test to Live.

When licensees have many submissions (>100 K).


2.5.103

Parent-Child grids do not work in modals.

Click a link from a parent grid to display a child grid inside a modal.

The parent grid should have a child grid.


2.5.103

When no value was found for "Term Earliest Overdue Invoice Due Date", the Billing system was sending Date.MinValue to Policy. This date is "01/01/0001" which was not expected.

Code modified on Policy and Billing so that "null" can be accepted by Policy for a date.

When importing Billing info into Policy, the Billing system sends the "null" value when no invoice is found.


2.5.103

Mapped values are in PD XML but not in PD.

Running the extraction tool. This has been corrected.

2.5.103

Entered line-breaks were being ignored and replaced by spaces when PD forms were saved in Bridge.

Saving a value containing a line-break in a text field on a PD form.


2.5.103


Copyright Notice

Copyright © 1998 - 2018 Oceanwide Canada Inc. All Rights Reserved.

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).