Bridge 2.5.100 Release Noteshelpdocs.oceanwide.com/ow_files/bridge_docs/release_… · Web...

0Table of Contents

Version 2.5.100 Bridge User Guide 2.5.100 Release Notes

Bridge

2.5.100 Release Notes

Version 2.5.100

iTable of Contents

Table of Contents

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

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

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

Logarithm Functions Have Been Added..................................................................2

Setting a New Licensee HQ Company.....................................................................3

Selecting or Creating Clients From a Custom Screen in the Workflow................3

New Cross-Policy Search Functions to Return Detailed Results.........................4

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

2.5.100 MINOR ENHANCEMENTS AND FUNCTIONALITY FIXES....................6

Enhancements............................................................................................................6

Fixes............................................................................................................................6

INDEX....................................................................................................................8


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.5.100 Core Enhancements

Logarithm Functions Have Been Added

The following functions can now be used to calculate the logarithm and natural logarithm of a number.

Log(p0, p1)Calculates the logarithm of a number in relation to a base value.

P0 (numeric): The number whose logarithm should be calculated. This can be a placeholder, function, formula or literal value.P1 (numeric, optional): The base value. If no value is provided, the system will use a base value of 10.Returns (numeric): Returns the logarithm of p0 in relation to the base value.

Exceptions: Any value of p0 or p1 that is less than or equal to 0 will cause the function to return a null value, which will be treated as 0 by the system.

eg.Log(10) will return 1.Log(10,2) will return 3.321928.Log([[FieldA]]*[[FieldB]],2) where [[FieldA]] = 3 and [[FieldB]] = 2 will be evaluated as Log(3*2,2) and will return 2.584962.5 + Log(0) will return 5.

Ln(p0)Calculates the natural logarithm of a number.

P0 (numeric): The number whose natural logarithm should be calculated. This can be a placeholder, function, formula or literal value.Returns (numeric): Returns the natural logarithm of p0.

Exceptions: Any value of p0 that is less than or equal to 0 will return a null value, which will be treated as 0 by the system.eg.Ln(10) will return 2.302585.Ln([[FieldA]]*[[FieldB]]) where [[FieldA]] = 3 and [[FieldB]] = 2 will be evaluated as Ln(3*2) and will return 1.791759.5 + Ln(0) will return 5.

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


3Index

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.

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

Selecting or Creating Clients From a Custom Screen in the Workflow

The client for a submission can now be selected or created through custom fields in the workflow. These can be used in place of the standard select/create client pages, or as an additional method of handling the client data.

To start, a new setting is now available in the master cover. The Client Selection in New Submission Workflow field now has an option for Within the Workflow. Selecting this option bypasses the select/create client pages, allowing client management to be handled through the workflow.

A set of resources have been created to support this new approach. A built-in screen can be added to the workflow, or the component panels, fields, and lookups can be used in a custom screen.

For more information on these built-in resources, see the Appendix C - Built-In Client Management Components section of the User Guide – Product Design document.


4Index

The Assured Lookup web service has also been updated as part of this enhancement. In order for it to work with any data source configuration, the following two hidden fields must be added to the workflow, and two Output to Fields configurations must be implemented.

The AssuredUserId and InsuredCompanyId fields must be added to the screen containing the Assured Lookup.

Output to Field configurations must be created to save the Assured User Id to the AssuredUserId field and the Insured Company Id to the InsuredCompanyId field.

For more information on the Assured Lookup, see the Web Service List for Data Sources section of the User Guide – Product Design document.

New Cross-Policy Search Functions to Return Detailed Results

Two new versions of the $CrossPolicyExactMatch and $CrossPolicyFuzzyMatch functions have been created. While the original functions just returned a boolean true/false value if a match was found, the new functions can return a customized list of values from the matching transactions. The returned list of values can be used with the NewGrid or SaveToGrid functions to populate a grid with the search results.

The two new functions are the $CrossPolicyExactMatchList function and the $CrossPolicyFuzzyMatchList function. The parameters are similar to the existing functions, with some changes to define the returned values.

For details and examples, see the Searching Across Policies section in the User Guide - Calculated Fields document.

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.


5Index

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.

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


6Index

2.5.100 Minor Enhancements and Functionality Fixes

Enhancements

When adding a Field Behavior Override to a panel, a Panel/Grid field has been added to the top of the page to identify the current panel.

Fixes

A server error could occur when trying to create a new claim (FNOL). This would occur when the claims workflow did not include any triggers. This has been corrected.

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 and patched back to version 2.4.87.

A server error would occur when publishing a workflow containing an Option List that was Correlated to another Option List that was not present in the system. This would typically occur following a faulty product import process where an Option List would be erroneously left out. This has been addressed with the addition of a new validation error that will occur during the publish process to prevent the system from crashing. The validation message will indicate the Name and Code of both the Field and Option List present in the system and a statement saying that the field’s option list has an invalid parent Code.

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 and patched back to versions 2.4.86, 2.4.89, 2.4.90, and 2.4.91.

A server error would occur when publishing a workflow that made use of a Shared Workflow. This has been corrected and patched back to version 2.4.91.

The Calculate Refund link would not be visible in the Actions widget when viewing certain cancellation transactions. This would happen when the cancellation belonged to a master cover that used the Rule Evaluation coverage calculation method for cancellations, and whose Set Transaction Status to Incomplete if Quoted Submission is Modified checkbox was checked. This has been corrected and patched back to version 2.4.90.


7Index

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 and patched back to version 2.4.87.

When trying to make an online payment, the payment amount could appear as zero and it would not be possible to complete the payment. This has been corrected and patched back to versions 2.4.90 and 2.4.91.

When trying to make an online payment on a transaction that had been in referral, and the Payment Plan Summary had not been refreshed, the payment amount could appear as zero and it would not be possible to complete the payment. This has been corrected.

Taxes and fees were not being included in the amount due when using the Pay Now feature. This has been corrected.

A server error could occur when clicking Save or Save & Close from the Rate Rule window. This has been corrected and patched back to versions 2.4.89, 2.4.90 and 2.4.91.


8Index

Index

22.5.100 Core Enhancements 22.5.100 Minor Enhancements and Functionality Fixes 6BBreak Text function 5BreakText() function 5EEnhancements 6Enhancements and New Functions for Copying Data to Grids 4FFixes 6LLogarithm Functions Have Been Added 2NNew Cross-Policy Search Functions to Return Detailed Results 4New Grid function 4New List function 5NewGrid() function 4NewList() function 5PPurpose of This Document 1SSave To Grid function 4SaveToGrid() function 4Selecting or Creating Clients From a Custom Screen in the Workflow 3Setting a New Licensee HQ Company 3


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

Bridge 2.5.100 Release Noteshelpdocs.oceanwide.com/ow_files/bridge_docs/release_… · Web...

Documents

Transcript of Bridge 2.5.100 Release Noteshelpdocs.oceanwide.com/ow_files/bridge_docs/release_… · Web...