Bridge 2.4.87 Release Notes - helpdocs.oceanwide.comhelpdocs.oceanwide.com/ow_files/bridge_docs/release... · Web viewThe release notes detail new features, enhancements, and fixes

0Table of Contents

Version 2.4.87 Bridge User Guide 2.4.87 Release Notes

Bridge

2.4.87 Release Notes

Version 2.4.87

iTable of Contents

Table of Contents

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

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

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

New Function for Lookups Using Data Source Configurations............................2

Formulas Can Be Used For Field Default Values....................................................2

New Functions to Pad Text With Leading and Ending Characters.......................4

New Setting for Controlling E-mail Copies..............................................................5

Rescission of Cancellation Transactions................................................................5

New Web Service for Data Source Configurations.................................................6

New Functions to Search for Values Across Fields...............................................7

2.4.87 MINOR ENHANCEMENTS AND FUNCTIONALITY FIXES......................8

Enhancements............................................................................................................8

Fixes............................................................................................................................8

INDEX..................................................................................................................11


1Index

Purpose of This Document

The release notes detail new features, enhancements, and fixes to be found in each release of the Bridge platform.


2Index

2.4.87 Core Enhancements

New Function for Lookups Using Data Source Configurations

A new function has been created allowing calculated fields to perform lookups using data source configurations. This is useful for obtaining a configuration’s lookup result for use as part of a calculated field’s formula. This also allows data source configurations to be used without having to use a combo box to initiate the lookup.

The LookupDataSource function takes the Code of a data source configuration and performs a lookup using the filters from its Filters panel. It returns the Primary Display Column value and populates workflow fields as specified in the configuration’s Output To Fields panel.

For more details on functions and placeholders, see the Full Function Reference List section in the User Guide - Calculated Fields document.

For more details on data source configurations, see the Data Source Configurations section in the User Guide - Product Design document.

Formulas Can Be Used For Field Default Values

Formulas can now be used to generate the default values of fields in a workflow. Previously, only constant values could be used.

To support this feature, the following changes have been made to the Field Management page:

An Apply Default field has been added. It allows you to specify how the system will generate a default value. It is visible when the Calculated checkbox is unchecked. It has the following three options:

o Select None so that no default value is generated for the field.


3Index

o Select Constant so that a specific default value is generated for the field.

o Select Formula so that the default value is generated according to a formula.

The Default field is now hidden unless Constant is selected for the Apply Default field.

A Default Formula field has been added. It is used to specify the formula to be used to generate the default value. It is visible when Formula is selected for the Apply Default field.

The fields have been adjusted so that the Always Calculate and Calculated Field Formula fields will only be available when the Calculated box is checked. The Apply Default, Default, and Default Formula fields will only be available when the Calculated box is unchecked.

Calculated and default settings are now mutually exclusive. Until they are modified, existing field configurations will be set by the system to use either their default settings or their calculated field settings based on the following criteria:

o If a Calculated Field Formula exists, the Calculated box will be checked. On saving with the Calculated box checked, any default configurations will be deleted. If a Default value exists and should be kept instead of the Calculated Field Formula, unchecking the Calculated box and saving will keep the Default value and delete the Calculated Field Formula instead.Note that any pre-existing field with both a Calculated Field Formula and a Default value will be treated as a calculated field until the configuration is saved as one or the other.

o If a Default value exists and the Calculated Field Formula field is empty, the Calculated box will be unchecked and the Apply Default field will be set to Constant.

o If the Calculated Field Formula and Default fields are both empty, the Calculated box will be unchecked and the Apply Default field will be set to None.

The settings above can be verified, and modified if necessary, on the Field Management page. Saving the page will make the settings permanent.

While making the changes for this feature, some additional changes have been made to the Field Management page. The Mapping panel and ACORD field have been removed, as well as the System Library checkbox.

Notes:


4Index

The formula in the Default Formula field is only evaluated when the field’s screen is loaded. If the system has not evaluated the formula, the value of the field will be null. This is especially important to consider if other fields depend on the result of the formula evaluation. This also applies to fields in tab workflow screens.

When the formula is evaluated, the result is not automatically saved. To save the result, the page must be saved.

A user can delete or replace the default value if the field is not read-only. This can be done by clearing the default value from the field, entering a new value if necessary, and then saving the page.

For details on managing fields, see the section on Creating a New Field in the User Guide – Product Design document.

New Functions to Pad Text With Leading and Ending Characters

Two functions have been created to add a specific character a number of times to a text value so that the text becomes a certain length. They are especially useful for altering field values so that they conform to certain business rules, such as when a field must have a minimum number of leading zeroes.

PadLeft (p0, p1, "p2")Adds a specified character a number of times to the beginning of a string value, returning a string of a specified length.

P0 (text): Identifies the text to which the specified character will be added. This can be a placeholder, function, formula or literal value.P1 (positive integer): The length of the resulting string. It must be greater than or equal to the length of the original string or an error will be displayed. The Length() function can be used to verify the length of the original string.P2 (text): The specified character to be added, enclosed in quotes. This can be a letter, number or symbol. Only one character should be specified. Specifying more than one character will cause an error.Returns (string): The resulting string of the specified length using the specified added character.

eg. PadLeft(123, 6, "0") will return 000123.PadLeft([[PolicyId]], 6, "0") where [[PolicyId]] is 123456 will return 123456.

PadRight (p0, p1, "p2")Adds a specified character a number of times to the end of a string value, returning a string of a specified length.

P0 (text): Identifies the text to which the specified character will be added. This can be a placeholder, function, formula or literal value.


5Index

P1 (positive integer): The length of the resulting string. It must be greater than or equal to the length of the original string or an error will be displayed. The Length() function can be used to verify the length of the original string.P2 (text): The specified character to be added, enclosed in quotes. This can be a letter, number or symbol. Only one character should be specified. Specifying more than one character will cause an error.Returns (string): The resulting string of the specified length using the specified added character.

eg. PadRight(123, 6, "0") will return 123000.PadRight([[PolicyId]], 6, "0") where [[PolicyId]] is 123456 will return 123456.

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

New Setting for Controlling E-mail Copies

Previously, whenever the system would send an e-mail, it would automatically create and send individual copies of the e-mail for every recipient in the To and Additional To fields in the New E-mail window. Each individual e-mail would be sent to the recipients in the Cc and Bcc fields, causing those recipients to receive multiple copies. A new setting has been added to select between this existing functionality, or send one e-mail to all recipients.

The E-mail Sending field has been added to the Miscellaneous Settings panel on the Master Cover - Policy Settings page. It has two options:

When the Create Copies for Recipients option is selected, individual copies of the e-mail will be created and sent for each recipient in the To and Additional To fields. This option can cause recipients in the Cc and Bcc fields to receive multiple copies of the e-mail. Each recipient in the To and Additional To fields will not be able to see the other recipients in these fields. This option corresponds to the pre-existing behavior of the system.

When the Send One E-mail option is selected, a single e-mail is created and sent to all recipients. Each recipient in the To and Additional To fields will be able to see the other recipients in these fields.

For information on sending e-mails, see the Sending E-mails section of the User Guide - Workflow document.


6Index

Rescission of Cancellation Transactions

Previously, the only way to remove a Cancellation transaction that was no longer needed was to delete it. This would remove all data and any associated documents, e-mails, and notes. In order to keep track of historical data, Cancellation - Quoted transactions can now be Rescinded. This rejects the cancellation while keeping the transaction and all associated data.

When viewing a Cancellation - Quoted transaction, the Rescind Cancellation action is available in the Actions widget. This action changes the transaction to Cancellation - Rescinded status. The Policy Information widget displays the new Rescinded On field, and the Policy Information detail window displays the new Rescission Date field.

Two new security rights have been added for this feature:

RescindCancellation: This right allows the user to rescind the cancellation. This right has not been added to any security roles by default.

DeleteRescindedPolicyTransaction: This right allows the user to delete a rescinded cancellation transaction. The transaction can only be deleted if it is the latest transaction in the policy, all other transactions in the policy are either Bound or Rescinded, no Declaration transaction have been created for the policy, and the Billing and Claims modules are not enabled.

This new Rescinded status is available for selection in fields where transactions statuses can be used as conditions.

In addition to quoting and binding, Rescind Cancellation will trigger the automatic generation of documents with applicable configurations.

The rescission date is available for use in generated documents, e-mails, and calculated fields. The Rescission Date placeholder is available for documents in the Policy Information section of the Word Ribbon, while the [[TransactionRescissionDate]] placeholder can be used in e-mails and calculated fields.

The Automatic Cancellation Finalization settings in the Master Cover - Automatic Processing page have been modified. If the selected trigger evaluates as False, the cancellation will now be rescinded instead of being left in Quoted status.

New Web Service for Data Source Configurations


7Index

A new Country Wide Indicator Lookup web service can now be used with Data Source Configurations. The service is used to determine data capture requirements, validation information, and rating rules for a given class code.

The web service can be selected for use in the Data Source field in the Attributes panel on the Data Source Configuration Management page.

Note: An Insurity security token is required to use this service. Contact your Oceanwide Representative for information on obtaining one.

For details on data source configurations, see the Creating a Data Source Configuration section of the User Guide – Product Design document.

New Functions to Search for Values Across Fields

Three new functions have been made available to search for a specific value across multiple fields.

ContainsItem() searches for whole values. The function checks a selection of fields to determine if any field contains an exact match for the search value, and returns True if a match is found.

Contains() searches for string fragments. The function checks a selection of fields to determine if the search string is included anywhere in the contents, including across concatenated fields, and returns True if the string is found.

DoesNotContain() is the negative version of the Contains() function. This works exactly the same way, but returns False if the string is found.

Known issues: Currently, if the ContainsItem() function is used to reference a grid field from outside that grid, it will return a separate True/False value for each row in the grid. In a future update, this will be corrected to only return a single True/False value.

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


8Index

2.4.87 Minor Enhancements and Functionality Fixes

Enhancements

The Integration Configurations panel now contains a Code column and a Description column. They display each configuration’s code and description, respectively.

When creating an integration configuration, the integration’s Code can now be entered by the user. If no code is provided, the system generates one when the configuration is saved. When the save process is complete, this field becomes read-only.

The Calculated On and Time to Calculate Quote fields have been removed from the Quote Report Header panel. The Rates panel has also been removed from the Quote Report.

Two currencies belonging to the system currency list have had their currency codes updated:

o The Venezuelan Bolivar currency code is now VEF. The old currency code was VEB.

o The Zambian Kwacha currency code is now ZMW. The old currency code was ZMK.

Fixes

A server error could occur when trying to cancel a policy that had been reinstated. This has been corrected.

A server error could occur when calculating a quote. This occurred due to a problem with how calculation trace information was being stored in the database. This has been corrected.

The default values of checkboxes in grid rows would not be applied after copying the row or the entire transaction. Previously, the system was evaluating default values using a case-sensitive method. Default values with certain combinations of upper and lower case letters would be improperly assessed, which prevented them from being applied correctly when the transaction was copied. This has been corrected via the implementation of a case-insensitive method of assessing the default values.

A server error could occur when the system would send an e-mail based on an automatic e-mail configuration that used a trigger. This would happen when the system contained another trigger with the same name that was inactive. The system was erroneously selecting the inactive trigger for use with the e-mail, which caused the error. This has been corrected. This has been patched back to versions 2.4.83 and 2.4.85.


9Index

The result of grid field evaluations would sometimes be incorrect. This also caused dependent workflow elements such as reports and transaction statuses to display incorrect information. This occurred due to a problem with how the system was using internal memory to perform the evaluations. This has been corrected. This has been patched back to version 2.4.83.

Field override behaviors would sometimes not activate following a page refresh. This was due to a problem with how the system was managing field properties when refreshing the page. This has been corrected. This has been patched back to version 2.4.85.

A server error could occur when importing a claim containing payment information. This has been corrected.

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.

The Add button disappeared from the Invoice Allocations panel in the batch receipts section. This has been corrected.

When using the SaveToGrid function to copy a grid, the error log would sometimes display a message similar to “Merge calculated fields for Grid- unable to merge row, - no key is associated”. This is an internal tracking message, and does not indicate an actual error. These messages are no longer displayed in the error log.

A server error could occur when creating a new submission while event tracking was disabled. This was due to incorrect settings in the system code that handles event tracking. This has been corrected.

A system error would occur when changing the sequence number of a template in a claims document configuration. This has been corrected.

A server error could occur when performing the Calculate Quote action from a tab workflow. This was due to a problem with the system code which was creating duplicate identifiers for option list items. This has been corrected.

When importing a product, the system would sometimes create duplicate codes for data source configurations. This was due to a problem with the import process, which has been corrected. This has been patched back to version 2.4.84.

When pressing the tab button to remove the cursor from a numeric field, the field value would revert to its default value. An internal field property that is managed by the source code was using an improper value, and has been corrected.

When using the DateTimeShort function, the system would return the correct date but erroneously display 12 AM as the time. This occurred because the system was defaulting the time-portion to 12 AM. This has been corrected.

The values in certain workflow fields would be lost following an integration with another system. This was because the web service handling this process was using an incorrect file-path to retrieve a needed internal file. Since it could not find the file, it caused default values to appear in the workflow fields. This has been corrected.

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 has been patched back to versions 2.4.83 and 2.4.86.


10Index

An error could occur where optional Policy Decisions forms would be selected in Bridge, but would not be selected in Policy Decisions. This was caused by an internal configuration error, and has been corrected.

The Panel window on the Screen Management page would sometimes take a long time to load. This was due to an inefficient database query, which has been corrected.

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 has been patched back to version 2.4.86.

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 has been patched back to versions 2.4.81, 2.4.83 and 2.4.85.

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 has been patched back to version 2.4.86.

An error could occur when publishing a workflow containing the LookupDataSource function. This occurred when the function referenced a data source configuration that used a field whose Calculated Field Formula field was empty. This has been corrected and has been patched back to version 2.4.86.

The following items would sometimes not appear on screen when they should have:o The message that confirms when a workflow has been published successfully.o The message that lists missing required settings when setting a master cover to live mode.o Error messages relating to the Effective Date and Valid Until Date.

This occurred because the internal components that display these items had to be updated to a newer version. This update has been completed.

When importing document templates using the Import Document Templates feature, re-importing existing templates with new or modified placeholders would cause those placeholders to not be populated on generating the documents. This was caused by the system not detecting the changes. This has been corrected. This has been patched back to version 2.4.83.

A server error could occur when generating a document. This would occur when the document template contained two or more tables referencing the same workflow grid, but at least one table also referenced a top-level field. This has been corrected.

In some cases, optional forms in a Policy Decisions workflow could not be selected. This was caused by missing default values in the configurations. This has been corrected.

The panel that displays validation errors and warnings would sometimes not be visible. This was the due to a recent enhancement to support Internet Explorer 11. This has been corrected.


11Index

Index

22.4.87 Core Enhancements 22.4.87 Minor Enhancements and Functionality Fixes 8EEnhancements 8FFixes 8Formulas Can Be Used For Field Default Values 2NNew Function for Lookups Using Data Source Configurations 2New Functions to Pad Text With Leading and Ending Characters 4New Functions to Search for Values Across Fields 7New Setting for Controlling E-mail Copies 5New Web Service for Data Source Configurations 6PPurpose of This Document 1RRescission of Cancellation Transactions 5


Copyright Notice

Copyright © 1998 - 2017 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).

Documents

Bridge 2.4.87 Release Notes - helpdocs.oceanwide.comhelpdocs.oceanwide.com/ow_files/bridge_docs/release... · Web viewThe release notes detail new features, enhancements, and fixes