2.4.77 Core Enhancements

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.

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.

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.

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 Managing User Accounts section.

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 Integration Configurations section.

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 Managing Document Templates section.

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 Managing Receipts by Batch section.

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.

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 Offset Invoices section.

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 Managing Claim Payments section.

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 Custom Labels section.

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

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.