bridge 2.4.77 release notes - oceanwidehelpdocs.oceanwide.com/ow_files/bridge_docs/release... ·...

0Table of Contents

Version 2.4.77 Bridge User Guide 2.4.77 Release Notes

Bridge

2.4.77 Release Notes

Version 2.4.77

iTable of Contents

Table of Contents

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

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

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

Using Dynamic Grids and Web Services as Data Sources....................................2

Locking Policy Terms................................................................................................2

Single Sign-On Enabled Between Bridge and Insurity Systems...........................3

Defining What Fields to Evaluate Before and After an Integration.......................3

Managing Formulas in Generated Documents.......................................................4

Paying Invoices Using On-Account Receipt Balances..........................................4

Offset Feature Using Credit Invoices to Pay Debit Invoices..................................5

Reversing Claim Payments.......................................................................................6

Modifications to the Custom Labels Feature..........................................................6

New Billing Placeholder for Selected Payment Plan..............................................7

2.4.77 MINOR ENHANCEMENTS AND FUNCTIONALITY FIXES......................8

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

Fixes............................................................................................................................9

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

Using Dynamic Grids and Web Services as Data Sources

In the existing functionality, data source configurations are linked to advanced lookup tables pre-set within the product model. This feature has been enhanced to allow data sources to be linked to dynamic grids within the submission workflow or web services that retrieve data from other systems.

For dynamic grids, as rows are added they become available for search and selection within any combo box controls that use the associated data source.

For web services, when a search is triggered from the combo box control, the system retrieves the appropriate data.

When configuring a data source, the new Source Type field allows the selection of a Data Table, Grid or Web Service. On saving, the remaining configuration options become available, customized for the selected source.

In addition, the functionality has changed when the selection from one combo box field is output to another combo box. If the target field is configured for manual search, the output value will appear in the field, but the user must still activate the search. If the target field is configured for automatic search, the system will trigger the search and select the appropriate result. If more than one result matches the input value, no selection is made and the user must choose one of the options.

For details on configuring data sources, see the Data Source Configurations section of the User Guide – Product Design document.

Locking Policy Terms

New options have been added, allowing entire terms to be locked and unlocked. This can be used by web services to prevent changes during a lengthy integration process, or can be used manually to control changes.


3Index

With the necessary security right, the Lock and Unlock options become available in the Actions widget. The Lock option prevents any changes to the policy term and any transactions within that term. No changes can be made to the transaction, client, or billing details, as well as notes, documents, e-mails, or attachments. Users can still navigate through the transactions to review details, but navigation will not trigger any save or quote calculation actions. A locked transaction can still be copied to produce a new submission.

In the Submission/Policy List, locked transactions are marked with the (Locked) text displayed next to the Status. When viewing a locked transaction, a warning message is displayed at the top of the page.

If a user is working on a transaction and it becomes locked in the background, the next attempt to save changes will display a notification message and the changes will not be saved.

Access to the Lock and Unlock actions is controlled by the new LockUnlockPolicy security right, which is not included in any security roles by default.

Single Sign-On Enabled Between Bridge and Insurity Systems

In order to manage Single Sign-On (SSO) integrations between Bridge and Insurity systems, a new option has been added to the user account and individual client pages. The Authentication Settings panel allows the selection of either Bridge or Insurity as the system that will authenticate any attempts to login.

The new ConfigureUserAuthentication security right controls access to this new panel, and has not been included in any security roles by default.

For information on configuring user accounts, see the section on Managing User Accounts in the User Guide - Reference and Administration document.

Defining What Fields to Evaluate Before and After an Integration


4Index

When performing an integration between systems, the default behavior is to perform a full calculation pass before and after running the integration. New fields have been added to the Integration Specifications panel in the Integration Configuration Management page, allowing modifications to this behavior.

When configuring a backend integration, the Pre-Integration Evaluation field becomes available. The evaluations can be set to evaluate All necessary fields, evaluate None of the fields, or perform a User-Defined Rule. Selecting User Defined Field reveals an additional field, Pre-Integration Evaluation Rule, where a Field Evaluation Rule can be selected to provide a set of fields to be evaluated.

If the integration is Synchronous, the Post-Integration Evaluation field also becomes available, with similar options for evaluating fields after the integration is complete.

For details on configuring integrations, see the section on Integration Configurations in the User Guide – Product Design document.

Managing Formulas in Generated Documents

Previously, certain conditions and calculations would be passed through into generated Word documents. This information is hidden within the document and could result in the loss of manual changes made to the document.

The generation process for Word documents has been enhanced to remove any hidden content related to placeholders, conditions, and calculations originating from the Bridge system. This process is called flattening. Only the final result will be included in the document as text. This enhancement does not affect any functionality of the Word document itself, such as the table of contents, page numbering, etc.

There is a known issue where the flattening process is incompatible with some Word templates, which can cause the document generation to fail. A new Validate All button has been added to the Document Templates page, which will check all active templates and report any that are incompatible. Note that some incompatible documents may still generate properly as PDF files, just not as Word documents.

The flattening feature can be disabled in the system configuration. Please contact your Oceanwide Representative for details.

For details on managing document templates, see the section on Managing Document Templates for Policies in the User Guide – Product Design document.


5Index

Paying Invoices Using On-Account Receipt Balances

A new option is available in the batch receipts feature, allowing on-account balances from existing receipts to be used to pay outstanding invoices.

1. When creating a new Batch Receipt, the Type can be set as Account Balance Allocation. The available fields adjust to the appropriate options.

2. Receipts are added to the batch, each assigned to a specific Bill to Party.

3. Invoices are then assigned to the receipt, along with one or more receipts with on-account balances belonging to the selected Bill to Party.

4. The allocation of the available funds is then managed directly in the invoices list.

5. When the batch is posted, all appropriate account changes are made.

For information on entering batch receipts, see the section on Managing Receipts by Batch in the User Guide - Billing document.

Offset Feature Using Credit Invoices to Pay Debit Invoices

When a bill to party has accumulated multiple debit and credit invoices, a receipt can be manually created to offset the positive and negative values.

The new Offset feature automates this process. When viewing the Outstanding Invoices page for a bill to party, select multiple invoices with debit and credit balances, and click Offset. The system assigns the remaining amounts according to the Due Date from oldest to newest, and presents a preview of the allocations for approval.


6Index

When the offset transaction is completed, the system automatically generates and posts a receipt batch and receipt with the appropriate allocations.

The new OffsetOutstandingInvoices security right controls access to this new feature, and has not been included in any security roles by default.

For information on using the offset feature, see the section on Offset Invoices in the User Guide - Billing document.

Reversing Claim Payments

If a claim payment was made in error or is otherwise invalid, it can now be reversed. A special reversal payment can be created from the detail window of the original payment. On confirming the reversal, all tracking and accounting values from the original payment are reversed.

When viewing a payment in Paid status, the Reverse Payment button is available. This creates a new payment with similar information to the original payment. Some new information is required, including a Reversal Reason, and then the reversal can be confirmed. When viewing the original payment or reversal payment, a link is available to the associated payment.

The new ReverseClaimPayment security right controls access to create reversals, and has not been included in any security roles by default.

The options for the Reversal Reason field can be customized. They should be included in a custom Option List with the name ClaimPaymentReversalReasons.

Known Issues: When viewing a saved reversal, the Reversal Reason field displays the Code of the option instead of the Label. This has

been logged for correction. The Reserve/Estimate panel is not displaying proper details for some payment statuses. Until this is corrected, the

Reserve/Estimate panel will not be displayed when viewing saved payments in the Paid, Error, or Void statuses.

For information on managing claim payments, see the section on Managing Claim Payments in the User Guide - Claims document.


7Index

Modifications to the Custom Labels Feature

Changes have been made to the Excel file used in managing custom labels within the system. These changes simplify the structure of the data, and provide better references when translating to other languages.

The Standard (language) column did not provide useful information, and has been removed.

The (English) column has been renamed to Default Text (English). This column displays the original English text from the system. For all language files other than English, any Custom (en) text from the English language file will be displayed instead. This allows translators to see the customized English terms instead of the base default terms, resulting in a more accurate translation.

For details on customizing labels, see the section on Custom Labels in the User Guide – Reference and Administration document.

New Billing Placeholder for Selected Payment Plan

A new placeholder has been added to identify the selected payment plan in billing documents and e-mails.

Document E-mail Field

Policy Term Payment Plan Word Ribbon Policy Information / Policy Term Payment Plan

E-mail [[Billing_PolicyTerm_PaymentPlan]]

This information is available in the Oceanwide Word Ribbon. A new Word Ribbon definition file can be downloaded in the Export / Import page. Select the Billing Invoice option in the Workflow list, and the new placeholder will be included in the Policy Information section.

For details on using placeholders, see the Placeholders section of the User Guide – Calculated Fields document.


8Index


9Index

2.4.77 Minor Enhancements and Functionality Fixes

Enhancements

Automatic e-mail configurations set for the Add - Attachment option as the Workflow Event will now also activate when files are attached using the File Upload field type.

Additional information has been made available for certain grids in the Billing module.

When viewing invoice details, the Invoice Line Items includes a new column for Net Premium. The net premium values do not include commission or taxes.

The Charge List grid in the Charges Report and the Billable Charges grid in the On Demand Invoicing page have two new available columns, Claim Number and Claim Payment Type. These fields are hidden by default, and can be added to the grid by right-clicking the header, opening the Select Columns menu, clicking the fields, and clicking Apply Changes.

A new security right has been added, ViewEventHistory, to be used for a new feature currently in development.

Previously, publishing a workflow could result in multiple warnings about the absence of fields used in universal triggers, even if those triggers are not used in the workflow. A new option can be enabled in the system configuration, allowing the publishing process to find missing fields in "Shared Workflows". When enabled, only one warning will appear, listing the referenced shared workflows.

When using universal triggers in a workflow or in configurations related to a workflow, please ensure that all necessary fields are included. The absence of those fields will not be reported when publishing, and the triggers will not function properly.

The Account History page in the Bill to Party has been modified so that the Reporting Period fields no longer default to show the last month. The original plans to allow configuration of the default dates for all reports have been postponed.

The Billing menu has been reorganized to group related features. The following changes have been made.

o The Billing Adjustments, On Demand Invoicing, Batch Receipts, Receipt Corrections, and Write-Offs features are now under the new Transactions menu item.

o The Distributor Payables, Insurer Payables, and Tax Payables features are now under the new Payables menu item.

o The Reports menu has been reordered, with the Receipts and Online Payments reports now available under the new Collections sub-menu.


10Index

o The Earned Premium report has been renamed to Earnings.

Fixes

Corrected timeout issue that could prevent workflows from publishing.

Corrected issue that could prevent data validations from triggering in grid modal windows.

Corrected issue where adding more than 13 rows to a workflow grid could prevent the activation of an associated integration configuration.

Corrected issue where some internal fields were not set properly when exporting a product, resulting in an error when importing the product.

Corrected missing data that could cause an error when sending emails.

Corrected issue where using custom fields to set effective policy dates would not always be recognized when creating endorsements.

Corrected a string length limitation that could prevent an integration from correctly populating fields.

Corrected a rendering issue where scrolling within a combo box field would cause the dropdown portion to separate from the field.

Corrected issue that could occur when the Billing module is active, causing a failure in a policy import that includes a new individual assured.

Corrected issue in endorsements where premium from premium grids would be added to the transaction premium twice.

Corrected issue where child grid fields would not be available for trigger configurations.

Corrected issue where external codes would not be updated when re-importing a product.

Corrected issue in Firefox only where data would not be kept in fields that are configured as both filter and output for an advanced lookup.

Corrected issue where claim payment details did not include the full charge description information when passed to the Billing module.

Corrected issue in the Insurer Payables report where the Payment Date displayed the current date instead of the proper payment date.


11Index


12Index

Index

22.4.77 Core Enhancements 22.4.77 Minor Enhancements and Functionality Fixes 8DDefining What Fields to Evaluate Before and After an Integration 3EEnhancements 8FFixes 9LLocking Policy Terms 2MManaging Formulas in Generated Documents 4Modifications to the Custom Labels Feature 6NNew Billing Placeholder for Selected Payment Plan 7OOffset Feature Using Credit Invoices to Pay Debit Invoices 5PPaying Invoices Using On-Account Receipt Balances 5Policy Term Policy Number placeholder 7Purpose of This Document 1RReversing Claim Payments 6SSingle Sign-On Enabled Between Bridge and Insurity Systems 3UUsing Dynamic Grids and Web Services as Data Sources 2


Copyright Notice

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