helpdocs.oceanwide.comhelpdocs.oceanwide.com/ow_files/bridge_docs/release_… · Web viewEnhancements. A . Sequence Number. can now be assigned when selecting . Integration Configurations

0Table of Contents

Version 2.4.71 Bridge User Guide 2.4.1 Release Notes

Oceanwide Bridge

2.4.1 Release Notes

Version 2.4.71

iTable of Contents

Table of Contents

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

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

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

Integrated Billing System..........................................................................................2Configuration...................................................................................................................... 2Workflow Changes.............................................................................................................4Billing Features.................................................................................................................. 4

Integrated Claims System.........................................................................................7Configuration...................................................................................................................... 7

Enhanced Product Design Features........................................................................8Risks.................................................................................................................................. 8Data Tables........................................................................................................................ 8Data Sources..................................................................................................................... 8Layers................................................................................................................................ 8Field Evaluation Rules.......................................................................................................9

Advanced Lookup Tables..........................................................................................9

New Control Type: Combo Box.............................................................................10

Enhancements for Calculated Field Formulas......................................................10

Account Control for Single-Sign-On Users...........................................................11

Allowing Users to Assign Additional Security Roles...........................................12

New Report for Users & Roles................................................................................13

Controlled Access for Files Attached to Policies.................................................13

Taxes & Fees Based On Dynamic Fields...............................................................14


iiTable of Contents

Sharing Data Across Transactions........................................................................14

Data Validations on Grid Detail Windows..............................................................16

Alternate Language Labels and Help Text for Workflow Components..............17

Custom Transaction Statuses in the Workflow....................................................17

New Security Rights to Control Workflow Widgets..............................................18

New Dynamic Field Type for File Uploads.............................................................18

Parent and Child Grids Changed to Cascading Structure...................................19

New Panel Layout Options......................................................................................19

Additional Grid Controls for Height and Filtering.................................................20

Digital Signatures for Transaction Documents.....................................................21

E-mails Drawing Additional Recipients From Workflow Fields...........................22

New Integration Point and Report for Compliance Scans...................................22

New Integration Point for Request Quote Action.................................................24

Integrations Leading to External Websites...........................................................25

Deleting Bound Transactions.................................................................................25

New Functions for Modifying Date and Time Values...........................................26

New Functions for Detecting Changes to Fields..................................................27

New Placeholders for Calling Client, Distributor, and Insurer Details................28

New Placeholder for Tracking Integration Run Times.........................................30

New Placeholder for the Last Modified Date and Time of a Transaction...........30

New Placeholders for Calling Quote Option Details.............................................31

Enhancements to the Product Export / Import Feature.......................................32


iiiTable of Contents

2.4.71 MINOR ENHANCEMENTS AND FUNCTIONALITY FIXES....................34

Enhancements..........................................................................................................34

Fixes..........................................................................................................................36

INDEX..................................................................................................................38


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

Integrated Billing System

A full-scale Billing system has been added to the Bridge system.

Allows users to select payment plans when creating submissions, and make online payments. Charges are tracked and available for automated or manual invoicing. Adjustment charges can be created for inclusion in

invoicing. Receipts can be entered and matched to invoices. Accounts are tracked per Bill To Party, and can be integrated with external accounting systems. Integrated with the new Claims module.

Configuration

Most configuration options are found under the new Billing menu, while others have been incorporated into existing areas of the Bridge system.

Adjustment Types can be set up under the Billing, Configuration, Adjustment Types menu option. These are used to categorize adjustments and link them to general ledger accounts.

Access to this feature is controlled by the ViewAdjustmentType, CreateAdjustmentType, and EditAdjustmentType security rights.

Bank Accounts can be set up under the Billing, Configuration, Bank Accounts menu option. These are used as reference data for account numbers and currency types when working with receipts.

Access to this feature is controlled by the ViewBankAccount, CreateBankAccount, and EditBankAccount security rights.


3Index

Document Configurations can be set up under the Billing, Configuration, Billing Documents menu option. Using Word templates uploaded in the template management section, invoice and statement documents can be configured for automatic generation.

Access to this feature is controlled by the ViewBillingDocument, CreateBillingDocument, and EditBillingDocument security rights.

Document Templates can be set up under the Billing, Configuration, Document Templates menu option. Word templates are uploaded for use in the Document Configurations.

Access to this feature is controlled by the ViewDocumentTemplate security right.

General Settings for the Billing system are access under the Billing, Configuration, General Settings menu option. This page is used to configure options throughout the billing system, including default billing settings, invoice numbering, receipt matching, generating statements, accounting and fiscal years, and reporting.

Access to this feature is controlled by the ViewBillingGeneralSettings and EditBillingGeneralSettings security rights.

General Ledger Accounts can be set up under the Billing, Configuration, General Ledger Accounts menu option. This feature allows internal accounts to be created and mapped to external accounting systems.

Access to manage general ledger accounts is controlled by the ViewGeneralLedgerAccount, CreateGeneralLedgerAccount, and EditGeneralLedgerAccount security rights.

Payment Plans can be set up under the Billing, Configuration, Payment Plans menu option. Payment plans define the distribution, frequency, and scheduling of payments. Multiple payment plans can be attached to each Quote Option defined in the Master Covers, with optional triggers to control availability.

Access to manage payment plans is controlled by the ViewPaymentPlan, CreatePaymentPlan, and EditPaymentPlan security rights.

Assigning payment plans to quote options is controlled by the ViewMasterCoverPaymentPlans and EditMasterCoverPaymentPlans security rights.

Payment Providers can be configured for online payments.


4Index

Access to manage payment provider configurations is controlled by the ViewPaymentProviderConfiguration, CreatePaymentProviderConfiguration, EditPaymentProviderConfiguration, and DeletePaymentProviderConfiguration security rights.

For each Distributor attached to a master cover, billing can be set to either invoice the client directly (the default option) or can be set as agency billing so that invoices go to the distributor instead.

A range of billing information is available for use in generated documents, e-mails, and calculated fields.

Workflow Changes

Once Payment Plans have been configured and attached to Quote Options in the Master Cover, they become available within the workflow. When users select a quote option within a transaction, they can select one of the available payment plans immediately, or defer the selection until later. The SelectPaymentPlan security right is required to view and select payment plans.

Users with the EditPaymentSchedule security right can alter the details and scheduling of the selected payment plan.

Once a payment plan has been selected, it is displayed in the Policy Information detail page.

If a Payment Provider has been configured, users with the CreatePayment security right can make immediate payments directly from the policy. The UseOnAccountBalance right allows the user to use on-account funds when making payments.

Billing Features

Existing Client and Distributor companies can be defined as Bill To Parties, while new clients created with a new submission are automatically added. Bill To Parties can be viewed and edited under the Billing, Bill To Parties menu option. This page provides party details, allows custom billing options to be applied to just the selected bill to party, tracks any on-account balance and transaction history, and lists outstanding invoices with the option to make online payments.

Access to this feature is controlled by the ViewBillToParty and EditBillToParty security rights, while the DesignateBillToParty right is needed to define an existing company as a bill to party.

The CreatePayment security right is needed to make online payments.


5Index

Most charges are generated automatically according to the payment plans and other features. The Billing Adjustments feature allows individual, one-time charges to be created for discounts, additional fees, or any other purpose that requires an adjustment.

Bill to Party adjustments are scheduled as charges within the system, and will be available for automatic or manual invoice generation. Insurer adjustments create the appropriate General Ledger entries for accounts related to the selected adjustment type.

Access to view and manage adjustments requires the ViewBillingAdjustment, CreateBillingAdjustment, EditBillingAdjustment, DeleteBillingAdjustment, and PostBillingAdjustment security rights.

As transactions are bound, charges are generated in the system according to the selected Payment Plan. The billing process can be configured to run automatically, using the default settings in the General Settings page or the custom settings defined in individual Bill To Parties, or invoices can be generated manually using the On Demand Invoicing feature.

Access to On Demand Invoicing is controlled by the CreateInvoice security right.

As payments are received and deposited, the bank receipts can be entered into the system and matched with recorded invoices. This is done through the Billing, Receipts, Batch Receipts menu option. Receipts can be entered manually, or uploaded in Excel files. Receipts for known bill to parties can be matched to invoices or put on account, while amounts for unknown bill to parties are recorded in a suspense account.

All allocations can be edited until the batch is posted. Once a batch has been posted, individual receipts can be reversed or reallocated through the Receipt Corrections feature.

If an invoice is not expected to be paid in full, the outstanding balance can be written off. This produces a new write-off batch and standard receipt to cancel-out the outstanding balance. The receipt can be reversed if payment is received or it is decided to pursue the collection

Access to view and manage receipt batches is controlled by the ViewBatchReceipt, CreateBatchReceipt, EditBatchReceipt, DeleteBatchReceipt, and PostBatchReceipt security rights.

Access to view and manage receipts within a batch also requires the ViewReceipt, CreateReceipt, EditReceipt, and DeleteReceipt security rights.


6Index

The Receipt Corrections feature requires the ViewReceiptCorrections, ReverseReceipt, and ReallocateReceipt security rights. In addition, the ViewReceiptCorrectionDetails right gives access to a panel with correction information when viewing receipt details.

Access to write-off invoices is controlled by the WriteOffInvoices security right.

The Reports menu provides access to detailed information and controls.

Account History Provides invoice and receipt details. Access is controlled by the ViewAccountHistoryReport right.

Aged Receivables Provides a list of receivable transactions, grouped by age range, with access to view transaction details. Access is controlled by the ViewAgedReceivablesReport right.

Charges Provides a list of charges generated within the system. Access is controlled by the ViewChargesReport right.

Distributor Payables Provides a list of all commissions owed to distributors. Access is controlled by the ViewDistributorPayablesReport right, with the CreateDistributorPayablePayment right allowing transactions to be marked as paid and ViewDistributorPayablePayment allowing access to view the payment details.

Earned Premium Provides a list of all premium charges, broken down by individual transactions, and the earned amount of each charge. Access is controlled by the ViewEarnedPremiumReport right, with the PostEarnedPremiumReport right allowing earned premium to be posted.The AllowBillingBackdate right allows the user to backdate the Period Ending date in the report.

General Ledger Entries Provides a list of all general ledger entries generated from financial transactions. Access is controlled by the ViewGeneralLedgerEntriesReport right.

Insurers Payable Provides a list of all premium and adjustments owed to insurers. Access is controlled by the ViewInsurersPayableReport right, with the CreateInsurerPayablePayment right allowing transactions to be marked as paid and ViewInsurerPayablePayment allowing access to view the payment details.

Invoices Provides a list of invoices generated automatically or manually. Access is controlled by the ViewInvoicesReport right, with the ViewInvoice right controlling access to view individual invoices.

Online Payments Provides a list of online payments with statuses and tracking details. Access is controlled by the ViewOnlinePaymentReport right.


7Index

The Online Payments report includes two columns that are hidden by default and can be added using the Select Columns feature. Request ID and Authorization Number can be selected to provide additional details about the payment.

Report Repository Lists all reports that have been generated automatically by the system. Access is controlled by the ViewBillingReportRepository right.

Integrated Claims System

An integrated claims system has been added to the Bridge system.

Features: Claims are entered through a workflow similar to the policy submission workflow. The workflows are created using the same

tools and process as the policy workflows. The claims workflow has some of the same widgets as the claims workflow, but also some new widgets specific to working

with claims. A common screen is included in the workflow for tracking payments, reserves, and estimates related to the claim. Like the policy submission workflow, the claims workflow supports notes and follow-ups, generating documents and e-mails

with data from the claim, and attaching files. Once enough information has been provided in the claim, it can be attached to a policy through the claim workflow. The

system validates the date of loss and finds the suitable policies and terms.

Configuration

Most configuration options are found under the new Claims menu, while others have been incorporated into existing areas of the Bridge system.

Adjuster users can be defined in the system using the new Adjuster and Adjuster Supervisor security roles. These roles will be recognized even if they are renamed. These adjusters can be assigned to a claim manually, or Adjuster Auto-Assignment rules can be created to assign specific adjusters when the claim is submitted. If multiple adjusters rules apply, the system automatically assigns the claim to the adjuster with the least number of active claims.


8Index

Claims includes its own configuration features for e-mails and generated documents.

Validation Rules can be created and applied to the claims workflow.

Custom Workflow Events can be created based on action and changes in the workflow. These events can drive automated actions such as sending e-mails and generating documents.

Professional Service Companies can be entered into the system and attached to a claim for use in tracking payments.

Claims payments can be integrated with the new Billing module, generating invoices and/or tracking payments in the General Ledger feature.

Enhanced Product Design Features

To centralize the creation and maintenance of workflow components and similar features, a new product configuration section has been added. The Product Model feature has been added to the Product Design menu, although it is currently only available to Oceanwide administrative users.

The Product Model section will gradually receive updated versions of the management pages for workflow components, plus new features related to products.

Opening the new feature provides a list of products. Selecting a product opens the Product Management page and a Product Menu widget to the left of the page. This new widget is used to navigate between features and resources, and changes context within each section to show different pages of settings and deeper levels of configuration.

The new features are introduced below.

Risks

This feature is not in use at this time.


9Index

Data Tables

This section defines the base configuration for advanced lookup tables.

Data Sources

This section defines how advanced lookup tables are used.

Layers

This section defines the data structure for advanced lookup tables, and is used to upload the data itself.

Field Evaluation Rules

This section allows the evaluation (calculation) of specific calculated fields in response to certain events. This is in addition to the normal calculation of fields that occurs at various points.

Rules can be created with a selection of fields from a specific master cover and workflow, with conditions on when the fields will be evaluated. The conditions include an optional trigger, and three events.

Import Policy Evaluates when a bound transaction is imported from an external source, either through an integration or through the Data Import feature.

Save on non-Bound Status

Evaluates when an unbound transaction is saved. The transaction is saved at various points, such as the user clicking Save & Refresh or Next, or when changes are made to grid data, the transaction dates, or the client.

Save on Bound Status

Evaluates when a bound transaction is saved. The transaction is saved at various points, such as the user clicking Save & Refresh or Next, or when changes are made to grid data.

For details on using these rules, see the section on Field Evaluation Rules in the User Guide - Product Design document.


10Index

Advanced Lookup Tables

A new version of the Lookup Tables feature has been created within the new Product Model section. This is now a multi-stage process that allows the creation of simple lookups, or complex lookups with multiple hierarchical layers, versions based on date ranges, and multiple distinct tables.

The construction of an advanced lookup table begins with the Data Table. This defines how the data will be sorted and indexed when the Excel sheet is uploaded.

Next is to define the layers. Layers of data can be constructed in a hierarchy, where a layer can be selected when retrieving data.

Layers can be divided into Layer Versions. This creates distinct versions of the data based on time periods, allowing data to be retrieved for a specific date.

The final step is to create one or more Domain / Rate Tables, and upload the Excel files containing the actual data. Multiple Domain / Rate Table entries can be created, each with different data or the same data with a different Data Table.

Once the full lookup structure has been completed, it can be used for a variety of features that access the data in different ways and for different purposes. Any requirements or restrictions will be detailed in the descriptions for those features.

For more information on configuring advanced lookup tables, please see the Product Model section of the Product Design user guide.

New Control Type: Combo Box

A new control type has been introduced for use in workflows. The Combo Box is an advanced version of the Drop Down control, providing significantly more functionality. The Combo Box retrieves data from an Advanced Lookup Table, displaying multiple columns of data that can be filtered and searched, with the selected option populating multiple fields within the workflow screen.


11Index

The Combo Box is linked to a Data Source entry, which in turn is linked to an Advanced Lookup Table. The Data Source entry is used to configure the various options, such as selecting the data to be displayed, apply filtering to the available data, and mapping columns to be output to other fields.

The advanced lookup table must be defined first. For more information on configuring advanced lookup tables, please see the Product Model section of the Product Design user guide.

The combo box control can then be added to the workflow.

For details on configuring fields, see the section on Managing Fields in the User Guide – Product Design document.

Enhancements for Calculated Field Formulas

Several enhancements have been made to how Bridge evaluates formulas in calculated fields. These changes improve performance, make formulas easier to read and write, and provide more control over the data and conditions.

All previous functionality is still supported, so any existing calculated fields will continue to work as normal.

Enhancements:

Quotes can now be used to define literal text. Any text within quotes will be treated as raw text, and will not be evaluated for calculations, placeholders, or any other processing. Note that angled quotes “ ”, or “Smart Quotes” will not be recognized, and must be replaced with straight quotes ".

Spaces and line-breaks can be included in formulas to make them easier to read and write. All spaces and line-breaks will be ignored, unless they are enclosed in quotes.

The dollar sign before a function name is no longer required, but may be included to make it easier to identify functions in a


12Index

complex formula. When defining a range of fields for use in a function, commas can now be used to separate items. A new version of the IF function has been introduced. Instead of using a trigger defined within the system, the new IF

function has all conditions defined within the function itself. For details on working with If functions, see the section on Conditional Results in the User Guide – Calculated

Fields document.

New Function:

The SaveToField() function has been added to allow specific data to be saved to a specific field in the workflow.

SaveToField(p0, p1)P0 (text): The code of the target field to receive the data. The code can be entered directly, retrieved from a field by a placeholder, or calculated with conditional logic. Any method must return the code of the target field as straight text.P1 (any): The value to be saved in the target field. This can be a literal value, a placeholder, or a calculated value.Returns (any): The calculated field itself will display the last value that was saved to the target field.

Account Control for Single-Sign-On Users

When a user accesses Bridge through a direct link with another system, known as single-sign-on access, they will generally have no need for account controls such as passwords or profile information. These are handled internally through the link configured between the systems.

A new option has been added when viewing a user account. The Single Sign-On Settings panel is accessible to users with the new ConfigureSingleSignOnUser security right, which has not been added to any security roles by default. This panel contains settings to define the user account as a single-sign-on user, and provide the user ID from the external system, if necessary.

When single-sign-on is enabled with default settings, a user can login through the external system or through the standard login page. When a user account is defined as a Single Sign-On Only user, the following changes will be applied.

Login is handled through an internal configuration, so the user's password is deleted and the user will not be sent any emails related to the password.

The user will not have access to the Profile page.


13Index

The external system can integrate with Bridge using the e-mail address provided in the user account, which enables both SSO and manual login. If the external system uses a user ID other than the e-mail address, it can be defined in the user account to allow SSO to match to the account. Note that defining an alternate ID or checking the Single Sign-On Only option will disable manual login.

These changes streamline the transition between systems, allowing Bridge to appear as an extension of the external system.

Allowing Users to Assign Additional Security Roles

Previously, any user who tried to create or modify a user account could only assign security roles that they had themselves. Now, users can be given the ability to assign specific roles to other users, referred to as Assignable Security Roles. A user who can assign a role, but does not have the role themselves, will not have access to the features or resources controlled by that role.

In the User Information page, the Assignable Security Roles panel has been added below the Security Roles panel. This panel displays any assignable roles available to the current user. The new ViewAssignableSecurityRoles right allows users to view the new panel, and is not included in any security roles by default.

To make roles available for assignment, please contact your Oceanwide Representative.

New Report for Users & Roles

When an organization has a large number of users with a variety of roles, it can be time-consuming to review individual user accounts. The new Users & Roles Report provides a full list of users and their associated security roles.

When viewing the User List, the Users & Roles Report button is available at the bottom of the page. This generates a report in Excel format, listing all users in the system. Each security role associated to each account is listed, with details on whether the role is assigned directly to the user or if the user can assign the role to accounts.


14Index

The new ViewUsersAndRolesReport security right allows users to generate this report, and is not included in any security roles by default.

Controlled Access for Files Attached to Policies

Previously, a list of attachment types could be created and selected within the master cover, and a type could be selected when attaching a file to a policy transaction. This type did not have any effect on the attachment, and was used primarily for information purposes.

This feature has been enhanced to allow security roles to be assigned to each attachment type. Only users with at least one of the necessary roles can select a particular type when attaching a file, and access the file once it has been attached. If no roles are assigned to an attachment type, any attachments linked to that type will be accessible by all users. If no type is selected for an attachment, it will also be accessible to all users. However, user will still need the appropriate rights to view and create attachments, regardless of type.

To apply the new settings, a new panel has been added to the Policy Settings page in the master covers. The Attachment Type Settings panel includes all options defined in the current list. Clicking each option opens a details window where the security roles can be assigned.

If the selected Attachments list is changed and the page is saved, the new options will be displayed in the Attachment Type Settings panel. Any previous options that have been assigned security roles will remain in the panel for reference, but cannot be selected for new attachments, while previous options that have no security roles will be deleted. Any remaining options from old lists can be manually deleted using the Delete button in the details window.

For details on configuring lists and attachment types, see the section on Policy Settings in the User Guide – Master Covers document.

For details on attaching files to policy transactions, see the section on Attaching Files to a Submission or Policy in the User Guide – Workflow document.

Taxes & Fees Based On Dynamic Fields


15Index

The Taxes & Fees page in the Master Covers section has been enhanced to allow taxes and fees to use values from fields within the workflow.

In the Master Covers - Taxes & Fees page, a new column has been added to the Taxes & Fees grid. The Driver Field column can be used to select a numerical field from the workflow. The value of this field, which will commonly be a calculated field, will be used as the full value of the tax or fee instead of the default rate.

The tax or fee will be a flat value equal the field value, and will not be adjusted or prorated. If the tax or fee is configured for all premium types, the flat value will be applied for each premium type included in the master cover, even if that premium does not have any value in a particular transaction.

This flat value will not be applied in Cancellation or Reinstatement transactions, as the premium is based on the existing premium from the policy.

For details on configuring taxes and fees, see the section on Taxes & Fees in the User Guide – Master Covers document.

Sharing Data Across Transactions

Previously, policy data was isolated to a single policy and its associated transactions. Documents, e-mails, and calculated fields could only access information from the current policy, plus common system information.

The Cross-Policy Data Configurations feature creates repositories for data from selected fields across policies, and even across products. This data becomes available for use in calculated fields within individual transactions, and can be used to perform comparisons or searches.

When a transaction contains data marked for collection, any time that transaction is imported, bound (including confirming Cancellations and Reinstatements), quoted (calculated quotes or issued quotes), or saved while in Bound status, the relevant data is collected and stored in the repository. If the transaction is deleted or set to Lost status, the stored data for that transaction is removed. Functions within calculated fields can access the most recent data for processing.

Access to this feature is controlled by the CreateCrossPolicyDataConfigurations, DeleteCrossPolicyDataConfigurations, EditCrossPolicyDataConfigurations, and ViewCrossPolicyDataConfigurations security rights, which have been added to the Product Designer security role by default.


16Index

For details on managing these configurations, see the section on Cross-Policy Data Configurations in the User Guide – Product Design document.

Once a Cross-Policy Data Configuration has been created and data has been stored, two new functions can be used to search the stored data and compare it to a source value to determine if there is a match.

$CrossPolicyExactMatch(p0,p1,p3,p3,p3,...)$CrossPolicyFuzzyMatch(p0,p1,p2,p3,p3,p3,...)

These functions evaluate to true if they find an exact match ($CrossPolicyExactMatch) within the stored data or data that is similar within a certain tolerance ($CrossPolicyFuzzyMatch).

P0 (text): This identifies the field containing the source value that the function will search for. The field Code should be provided, enclosed in square brackets.P1 (text): This identifies the resource containing the stored data. The Code of the Cross-Policy Data Configuration should be provided, without any brackets.P2 (numeric): This is the tolerance, ranging from 0 to 100, and is only used for the $CrossPolicyFuzzyMatch function. As the function compares the source value to the stored data, it calculates a percentage match score from 0 (no similarity at all) to 100 (exact match). The percentage must be equal to or greater than the tolerance value for the function to consider it a positive match.P3 (text): These are optional filters to control what data will be searched within the Cross-Policy Data Configuration. The source value will only be compared against data that fits within all of the selected filters.Each filter should be formatted as Filter=Value, and only one filter of each type can be used in each instance of the function, except where noted.

Filter ValuesProduct All, Current, Other Searches through data related to All products, the Current

product, or all products Other than the current product.

Policy All, Current, Other Searches through data related to All policies, the Current policy, or all policies Other than the current policy. If this filter is not specified, it will be applied with the default value of Other.

Assured All, Current, Other Searches through data related to All clients, the Current client, or all clients Other than the current client.

Distributor All, Current, Other Searches through data related to All distributors, the Current distributor, or all distributors Other than the current distributor.


17Index

PolicyTransaction All, Current, Other Searches through data related to All transactions, the Current transaction, or all transactions Other than the current transaction. If this filter is not specified, it will be applied with the default value of Other.

PolicyTransactionStatus

Quoted, Referred, Bound, UnderwritingRequired, Incomplete

Searches through data related to transactions in the selected status. This filter can be applied multiple times with different statuses.

Returns (text): $CrossPolicyExactMatch returns "1" if an exact match is found within the stored data. Returns "0" if no match is found.$CrossPolicyFuzzyMatch returns "1" if data is found that has a percentage match score that equals or exceeds the tolerance. Returns "0" if no data matches closely enough.

For details on using functions, see the section on Functions in the User Guide – Calculated Fields document.

Data Validations on Grid Detail Windows

When creating a data validation, it can now be applied to specific grids within a screen. This checks the validations whenever the user tries to save an entry in the grid detail window. When a data validation is triggered, the validation message is displayed within the detail window and the Save & New and Save & Close buttons will not allow the user to leave the current entry until the data has been corrected.

When creating or editing a validation rule in the master cover, the Screens field has been renamed to Screens and Grids and enhanced to display grids within each screen. Grids are presented as the screen name followed by the grid name.

Note that the data is still saved when a data validation is triggered, and the user can close the window. Validations applied to a grid can also be applied to the parent screen to ensure that the user cannot proceed in the workflow with invalid data.

For details on configuring Validations, see the section on Validation & Workflow Actions in the User Guide – Master Covers document.


18Index

Alternate Language Labels and Help Text for Workflow Components

When the Custom Labels feature was introduced, it allowed users to upload translated versions of all system labels. These alternate labels would display according to the user's browser language settings. This feature has been enhanced to allow custom labels and help text for fields, panels, screens, integration configurations, and workflow steps.

When any of the above resources are saved, it is added to the labels list with its Code as the Resource Key. The labels and help text are added to the default (English) column for the resource, and can be customized for other languages as needed.

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

Custom Transaction Statuses in the Workflow

By default, the core transaction statuses are displayed in the workflow, made up of the transaction type (not counting New Business) followed by the status of the transaction. A new option has been introduced, allowing custom status labels to be displayed in the workflow.

In the Miscellaneous Settings panel of the Master Cover – Policy Settings page, the new Custom Status Field drop down list has been added. The list includes all Textbox and Label fields from Form panels in the attached workflow.

The value of the chosen field, either entered manually or calculated, will be displayed in the Status fields of the Policy Information widget (without the color coding) and the Policy Information window, as well as the Status column of the Policy Transactions list. If the field does not have a value or if the value is blank, the status will revert back to the core system statuses.

This only affects the display of the status fields in the workflow. The core system statuses still apply, and still control all aspects of the transaction. Features such as available Actions, workflow overrides, and other resources associated to transaction statuses will not be affected. For reference, the transaction types are still displayed in the Type column of the Policy Transactions list.

For details on configuring Miscellaneous Settings, see the section on Policy Settings in the User Guide – Master Covers document.


19Index

New Security Rights to Control Workflow Widgets

All widgets in the workflow screen now have associated security rights, allowing them to be displayed or hidden depending on the security roles of the user.

The ViewActionsWidget, ViewClientWidget, ViewCommonScreensWidget, ViewPolicyWidget, and ViewPremiumWidget security rights each control their respective widgets. These rights have been added to the Client, Client Risk Manager, Compliance Manager, Distributor, Distributor Supervisor, Underwriter, and Underwriter Supervisor roles by default, as well as any custom roles that include either the ViewSubmission or ViewPolicy rights.

Note that the ViewPolicyWidget right controls the entire widget, while the ViewPolicyInformationWidget right still controls specific details within the widget.

The ViewSubmissionScreensWidget security right has also been added, and replaces the ViewPolicyMenuWidget right. This right has been added to any roles that included the ViewPolicyMenuWidget right.

New Dynamic Field Type for File Uploads

In addition to the Attachments feature in the Common Screens widget, files can now be uploaded to a field directly into the submission workflow. This allows files to be attached in context related to a specific screen or panel, allows instructions to be provided in the field label or help text, and allows the field to be controlled by overrides.

The File Upload control type has been added to the Field Management page. The field can be Read-Only, or Hidden. It can be set as Available for Triggers, checking the field to determine if it Equals nothing (no file attached) or Not Equals nothing (file is attached). The field can be made Available for Reports, where it will display a blank if no files is attached, or an internal identifier if a file is attached.

The Field Initial Value Settings can be set to copy an attached file to a new transaction, revert to the default (no attachment), or copy the attachment from another File Upload field.


20Index

When using the File Upload field within a workflow, the user can click the Select or Drop File to Upload button to open a standard file selection window, or drag and drop a file onto the field. Once the file has been uploaded, it can be viewed by clicking the link or deleted with the Delete button.

For details on configuring fields, see the section on Managing Fields in the User Guide – Product Design document.

Parent and Child Grids Changed to Cascading Structure

Introduced in version 2.3.0, child grids could be defined to contain data related to each row in the parent grid. These child grids would be accessed using a Manage link in each row of the parent grid, and would open as a window on the page.

With this release, child grids will now appear in the workflow screen, directly below the parent grid. On loading or refreshing the screen, only the parent grid will be displayed. When any row in the parent grid is selected, the child grids will appear below the parent, displaying the data related to the selected row in the parent (if any). If a different row is selected in the parent, the child grids will refresh to display the data related to that row.

Child grids may have child grids of their own, which will display below their parent when a row is selected.

Adding data to a child grid is the same as the parent, using the Add button or the Export / Import button (if enabled).

The grid configurations do not need to be changed to support this enhancement, however the workflows will need to be republished.

New Panel Layout Options

Two new settings have been added to the General Information panel of the Panel Management page. These settings can be used separately, or combined in the same panel.

Layout can be set to Horizontal (the original layout and the default setting) or the new Vertical layout with the labels above the field. This is useful for fields with long labels, such as detailed questions.


21Index

Column Layout controls the number of columns, and can be set to Single (the original layout and the default setting) or the new Double column layout. This can save a significant amount of space for large groups of small fields.

The settings can be used together, resulting in a double-column layout with labels above the fields.

There are some restrictions to the Double column layout, as some field types are too large to fit. These are listed in the full description in the documentation.

For details on configuring panels, see the Managing Panels section of the User Guide – Product Design document.

Additional Grid Controls for Height and Filtering

The Panel Management page has been reorganized to group all settings exclusive to grids in a new panel, Grid Settings. This new panel is displayed when the Control Type for the panel is set to Grid or Premium Grid.


22Index

Two new settings have been introduced in the new Grid Settings panel.

Grid Height As rows are added to a grid, it expands and takes up more space on the screen. When it reaches the maximum height, it adds pages which can be navigated using the page controls in the bottom-right of the grid.

The options are Small (10 rows), Medium (25 rows), and Large (50 rows).Enable Filtering This option enables the filter row in the grid, giving users greater control in finding and

organizing data.

For details on configuring panels, please see the Managing Panels section of the User Guide – Product Design document.

Digital Signatures for Transaction Documents

Documents generated within a transaction can now be digitally signed through integration with a certification service.

A new placeholder, Signature Placeholder, has been added to the Word Ribbon in the Signature group. This will be replaced by a certified signature in the final generated PDF.

Once the document is saved with the placeholders, it is uploaded as a template and attached to a document configuration in a master cover. The document can then be generated manually from the submission workflow, but will not include the digital signature. For the signing process, a custom integration must be configured and attached to the workflow.

A new Integration Type, E-Signature, has been added to the Integration Configuration Management page. This is a custom integration that adds a new action to the Actions widget.

When the user clicks the custom action, the document is generated as a PDF and saved in the Document/Forms list, then the signing window opens. The user must first accept a consent document. The full document is then displayed with marked boxes for each required signature. The user can review the document and accept each signature as required. When the last signature is accepted, a confirmation message appears and the user must click Ok.

This completes the signature process. The signed version of the document replaces the unsigned version stored in the Documents/Forms list. The user can also download a copy of the document from the signature window.


23Index

The document status is stored in the system and can be used for such purposes as tracking, display, and validations.

For details on configuring the document template with the new placeholder, see the Configuring Digital Signatures section of the User Guide – Document Configuration document.

For details on configuring the signature integration, see the Integration Configurations section of the User Guide – Product Design document.

For details on the signature process, see the Digitally Signing Documents section of the User Guide – Workflow document.

E-mails Drawing Additional Recipients From Workflow Fields

E-mails can now be configured to pull additional recipient e-mail addresses from a dynamic field in the workflow.

When creating an e-mail configuration, either automatic or manual, the new Recipient Groups panel becomes available once the configuration is saved. Multiple groups can be created, each referring to a single field from the associated workflow. An optional trigger can be chosen to control if each group will be included in the e-mail.

The selected fields can be Textbox, Text Area, Textbox (Email), or Label types, and can be predefined or provided by the user.

When the user initiates the e-mail or the system generates the e-mail automatically, the triggers are evaluated and the appropriate groups are added to the Additional To field. For automatic e-mails, any invalid addresses will be left out. For manual e-mails, if the user can edit the recipients list, they can remove or correct invalid addresses themselves. If the recipients cannot be edited, the user will need to contact their administrator to have the addresses corrected in the workflow.

For details on configuring e-mails, see the E-mail Configurations section of the User Guide - Master Covers document.

New Integration Point and Report for Compliance Scans

A workflow integration point can now be configured to perform compliance scans on selected transaction data. This feature includes new placeholders for compliance details and a report to view detailed scan history results.


24Index

When configuring the integration point, the new Integration Type is Compliance Scan. On saving the integration, new panels are displayed to define the settings for the compliance scan.

The Client and Distributor can be checked for scanning.

The selected data is compared to one or more sanction lists defined in the integration configuration. As each list is included, the threshold for that list is defined, determining how close the data must match before failing compliance.

For details on configuring integration points, see the Integration Configurations section of the User Guide – Product Design document.

With this new feature, additional information is now available for use in generated documents, e-mails, and calculated fields.

Placeholder Word Ribbon E-mail / Calculated Field Placeholder

Compliance Successful Compliance Information / Compliance Successful [[ComplianceSuccessful]]

Compliance Message Compliance Information / Compliance Message [[ComplianceMessage]]

Compliance Detailed Message Compliance Information / Compliance Detailed Message [[ComplianceDetailedMessage]]

Compliance Executed On Compliance Information / Compliance Executed On [[ComplianceExecutedOn]]

Compliance Referral Requested By First Name

Compliance Information / Compliance Request User First Name

[[ComplianceRequestUserFirstName]]

Compliance Referral Requested By Last Name

Compliance Information / Compliance Request User Last Name

[[ComplianceRequestUserLastName]]

Compliance Referral Requested On Date Compliance Information / Compliance Request Date [[ComplianceRequestDate]]

Compliance Acceptance Reason Compliance Information / Compliance Acceptance Reason [[ComplianceAcceptanceReason]]

Compliance Accepted By First Name Compliance Information / Compliance Acceptance User First Name

[[ComplianceAcceptanceUserFirstName]]

Compliance Accepted By Last Name Compliance Information / Compliance Acceptance User Last Name

[[ComplianceAcceptanceUserLastName]]

Compliance Accepted On Date Compliance Information / Compliance Acceptance Date [[ComplianceAcceptanceDate]]


25Index

Compliance Accepted N/A [[ComplianceAccepted]](calculated fields only)

Compliance Rejection Reason Compliance Information / Compliance Rejection Reason [[ComplianceRejectionReason]]

Compliance Rejected By First Name Compliance Information / Compliance Rejection User First Name

[[ComplianceRejectionUserFirstName]]

Compliance Rejected By Last Name Compliance Information / Compliance Rejection User Last Name

[[ComplianceRejectionUserLastName]]

Compliance Rejected On Date Compliance Information / Compliance Rejection Date [[ComplianceRejectionDate]]

These placeholders are only available once a Compliance Scan integration has run, and are populated when the appropriate event occurs, such as compliance referral requests, compliance acceptance, or compliance rejection.

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

Once a Compliance Scan integration has run, a new option becomes available in the Common Screens widget. The Compliance Scan History option opens the Compliance Scan History window.

The first panel lists all scans that have been performed for the current transaction, and provides a summary of the scan results.

Selecting a scan in the first panel displays a second panel listing the elements of the scan and whether that portion of the scan passed or failed.

Selecting an element in the second panel displays the third panel, identifying all lists where the scans failed. This identifies the scores and necessary thresholds, and provides detailed scan results.

Access to this feature is controlled by the new ViewComplianceScanHistory security right, which has been added to the Compliance Manager security role by default.

For details on the report, see the Compliance Scan History Report section of the User Guide – Workflow document.

New Integration Point for Request Quote Action


26Index

When viewing a transaction in Underwriting Required status, clicking Request Quote will send the transaction into Referral status. A workflow integration point can now be configured for the Request Quote action.

This option is available for Policy integrations, and the standard settings are available including pre or post-action, synchronous or asynchronous communication, and conditional activation.

Note that some users, commonly underwriters, will bypass Underwriting Required status and go directly to Referred status. This integration will not activate in those circumstances.


Integrations Leading to External Websites

A new option has been added to the Integration Configuration Management page, allowing an integration to redirect the user to an external website. The integration can include system and transaction data, allowing the destination website to adjust according to the origin transaction in Bridge. The Bridge session is maintained (up to the set timeout period), allowing the user to return to Bridge without needing to login again.

When configuring a Custom integration, the Integration Level can now be set to Frontend. This Reveals the Link URL field.

In the Link URL field, enter the full URL of the destination website. This can be a simple, static URL, or it can contain placeholders to pull in system and transaction information for use by the destination website.

As with Backend integrations (integrations using Bridge services), Frontend integrations add an action to the Actions widget. This action can also be set for Emphasize Action, which adds a button at the bottom of the screen.



27Index

Deleting Bound Transactions

The Delete action within the policy workflow has been extended to include Bound transactions.

As the deletion of bound transactions is generally more significant than deleting transactions still in progress, a new security right has been added. The DeleteBoundPolicyTransaction right controls this action for bound transactions, and has not been included in any security roles by default. The DeletePolicyTransaction right still controls the action for non-bound transactions.

Some additional notes and conditions apply: New Business transactions cannot be deleted. Bound transactions can only be deleted from the last term of the policy. A bound transaction cannot be deleted if there are any unbound transactions within the policy, or if there have been any

transactions bound after the transaction to be deleted. All such transactions must be deleted first. No Declaration transactions can be associated to the policy for any term. The Billing and Claims modules cannot be active. Deleting a Renewal transaction also deletes the term. Deleting a Reinstatement transaction also deletes the associated Cancellation transaction. The bound Cancellation

transaction (Cancelled status) cannot be deleted directly.

New Functions for Modifying Date and Time Values

New functions have been added for use in calculated fields.

Functions exist to adjust date values by days, months, or years. The new $AddHours() function can add or subtract hours.

$AddHours(p0,p1)Takes a provided date and adds or subtracts a specified number of hours.

P0 (date): Date field. The date must be in the system format, such as from a date picker field, the $TodayXml function, or any system dates.P1 (integer): Number of hours to add (positive values) or subtract (negative values). Decimal values are not supported.Returns (date): New date with adjusted time. The date itself will change if the hours cross into the next or previous days.


28Index

Functions exist to convert system dates into long or short formats. The new $DateTimeLong() and $DateTimeShort() functions include the time element as well.

$DateTimeLong(p0)Converts a provided date and time into the long date and time format.

P0 (date): Date field. The date must be in the system format, such as from a date picker field, the $TodayXml function, or any system dates.Returns (text): Date p0 in long date and time format.eg. If p0 = 2014-12-19T14:45:00.0000000-04:00, returns Friday, December 19, 2014 2:45:00 PM. The output may display differently due to regional settings.

$DateTimeShort(p0)Converts a provided date and time into the short date and time format.

P0 (date): Date field. The date must be in the system format, such as from a date picker field, the $TodayXml function, or any system dates.Returns (text): Date p0 in short date and time format.eg. If p0 = 2014-12-19T14:45:00.0000000-04:00, returns 12/19/2014 2:45 PM. The output may display differently due to regional settings.


New Functions for Detecting Changes to Fields

While the submission process will generally require that a quote be recalculated when changes have been made, the validations cannot cover all possible changes. New functions have been introduced to detect any changes at all in one or more fields. The $Hash function records the date and time the changes were detected, and the $IsDateGreaterThan function can be used to determine if the changes were made after a specific reference date and time.

$HashAndModifiedOn(p0,p0,p0,...,p1,p2)The first time this function runs, it combines the content of all P0 fields, calculates a hash value (a unique value derived from the content), stores the hash value in the P1 field, and stores the date and time of the calculation in the P2 field.


29Index

Each time the function runs after the first time, it calculates the hash value for all fields then compares it to the previous hash value stored in P1. If the hash value has changed, meaning that at least one of the fields was changed since the last time the function ran, the function stores the new hash value in the P1 field and updates the date and time stored in the P2 field.The date stored in the P2 field can be compared to another date to determine if any of the fields changed within a certain time period. The $IsDateGreaterThan() function is useful for making the comparison.Note: The date stored in the P2 field indicates the last time the function identified the changes. It does not reflect when the changes were made.

P0 (text): All fields to be included in the hash calculation should be provided, separated by commas.P1 (Text Area): The Code of the field to contain the hash value. This will be an alphanumeric value with no meaning outside of this function, so the field should most likely be hidden. This condition is literal and must contain the Code of the field without any square brackets, no placeholders or functions can be used here.P2 (text): The Code of the field to contain the last date and time that changes were detected. This condition is literal and must contain the Code of the field without any square brackets, no placeholders or functions can be used here. This should be a text field to ensure the full date and time are stored.Returns (text): Returns the same hash value stored in P1.

$IsDateGreaterThan(p0,p1,p2)Checks the first provided date to determine if it is greater than the second provided date. A tolerance can be set to account for minor differences.

P0 (date): First date field.P1 (date): Second date field.P2 (integer): Tolerance in milliseconds. The system date/time format is accurate to a ten-millionth of a second. Even dates that seem to be calculated at the same time will have a small difference. If the P0 date is only greater than the P1 date by less than the provided tolerance, it will not be considered a difference and the function will return false.Returns (text): Returns "1" if the P0 date is greater than the P1 date by more than the P2 tolerance, if any. Returns "0" if the P0 date is less than or equal to the P1 date, or if it is greater but within the P2 tolerance.

eg. If P0 is 2014-10-28T18:16:12.001-04:00, P1 is 2014-10-28T18:16:12.002-04:00, and no tolerance is specified, returns "0" since P0 is less than P1.If P0 is 2014-10-28T18:16:12.005-04:00, P1 is 2014-10-28T18:16:12.002-04:00, and no tolerance is specified, returns "1" since P0 is greater than P1.If P0 is 2014-10-28T18:16:12.005-04:00, P1 is 2014-10-28T18:16:12.002-04:00, and the P2 tolerance is set to 10, returns "0" since P0 is greater than P1, but only by 3 milliseconds when the tolerance is 10 milliseconds.



30Index

New Placeholders for Calling Client, Distributor, and Insurer Details

New placeholders have been added to pull a range of company details from Client, Distributor, and Insurer companies into generated documents, e-mails, and calculated fields.

Placeholder Word Ribbon E-mail / Calculated Field Placeholder

Client Company Contact Employee Number Company Client / Client Contact Employee Number [[InsuredContactEmployeeNumber]]

Client Company Contact Email Company Client / Client Contact Email [[InsuredContactEmail]]

Client Company Code Company Client / Client Code [[InsuredCode]]

Individual Client First Name Individual Client / Client First Name [[InsuredContactFirstName]]

Individual Client Last Name Individual Client / Client Last Name [[InsuredContactLastName]]

Individual Client Address Individual Client / Client Address [[InsuredAddress]]

Individual Client City Individual Client / Client City [[InsuredCity]]

Individual Client Country Individual Client / Client Country [[InsuredCountry]]

Individual Client State/Province Individual Client / Client State [[InsuredState]]

Individual Client Zip Individual Client / Client Zip/Postal Code [[InsuredZip]]

Individual Client Email Individual Client / Client Email [[InsuredEmail]]

Individual Client Phone Individual Client / Client Phone [[InsuredPhone]]

Individual Client Code Individual Client / Client Code [[InsuredCode]]

Distributor Primary Contact First Name Distributor / Distributor Contact First Name [[DistributorContactFirstName]]

Distributor Primary Contact Last Name Distributor / Distributor Contact Last Name [[DistributorContactLastName]]

Distributor Primary Contact Employee Number Distributor / Distributor Contact Employee Number [[DistributorContactEmployeeNumber]]

Distributor Primary Contact Email Distributor / Distributor Contact Email [[DistributorContactEmail]]

Distributor Primary Contact Phone Distributor / Distributor Contact Phone [[DistributorContactPhone]]


31Index

Insurer Primary Contact First Name Insurer / Insurer Contact First Name [[InsurerContactFirstName]]

Insurer Primary Contact Last Name Insurer / Insurer Contact Last Name [[InsurerContactLastName]]

Insurer Primary Contact Employee Number Insurer / Insurer Contact Employee Number [[InsurerContactEmployeeNumber]]

Insurer Primary Contact Email Insurer / Insurer Contact Email [[InsurerContactEmail]]

Insurer Primary Contact Phone Insurer / Insurer Contact Phone [[InsurerContactPhone]]


New Placeholder for Tracking Integration Run Times

When a workflow contains an integration to an outside system, there may not be a noticeable change within a transaction. The system now tracks the last time each different integration is successfully completed, and this date and time information can be retrieved using a calculated field.

The placeholder syntax is as follows: [[Integrations/Integration[Code='code']/StartTime]]

The code should be the code of the integration configuration defined for the workflow.

If the resulting date and time are to be used for date comparisons, the field containing this placeholder should be a text field. If a date picker field is used, it will lose the time component.


New Placeholder for the Last Modified Date and Time of a Transaction

The system tracks the last date and time changes were made to a transaction. This information is now available for use in e-mails and calculated fields.


32Index

The placeholder syntax is as follows: [[ModifiedDate]]

Note that the following actions will not update this value: Clicking the Previous button. Clicking the Next or Save & Refresh buttons without making any changes to the transaction. Generating documents, uploading attachments (either through the Attachments feature or a File Upload field), or sending

emails.

The date and time are saved in the full system format, such as "2015-10-28T18:16:12.3313239-04:00". Formatting placeholders and functions can be used to modify the value for presentation. Also, if the date and time are to be used for date comparisons, any calculated field containing this placeholder should be a text field. If a date picker field is used, it will lose the time component.


New Placeholders for Calling Quote Option Details

New placeholders have been added to pull details from each quote option into calculated fields. The calculated fields can be displayed in the workflow, and used as placeholders in documents and emails. The quote details are not available before the quotes have been calculated, or if the quote is in Open status (having failed quote validation).

The QuoteCode parameters identify the Code of the appropriate quote option, the PremiumTypeCode parameters identify the Code of the appropriate premium type within the quote. Any additional parameters are noted below.

Insurer Name by Quote Option

[[QuoteInfoArray/QuoteInfo[QuoteCode='code']/InsurerName]]

Premium Amount by Quote Option and Premium Type

[[QuotePremiumInfoArray/QuotePremiumInfo[QuoteCode='code' and PremiumTypeCode='code']/Amount]]

Total Premium by Quote Option

[[QuoteInfoArray/QuoteInfo[QuoteCode='code']/TotalPremium]]


33Index

Tax Amount by Quote Option, Premium Type, and Tax Type

[[QuoteTaxInfoArray/QuoteTaxInfo[QuoteCode='code' and PremiumTypeCode='code' and TaxCode='code']/Amount]]

Note: TaxCode should contain the Code of the tax type.

Total Tax by Quote Option

[[QuoteInfoArray/QuoteInfo[QuoteCode='code']/TotalTax]]

Commission Amount by Quote Option and Premium Type

[[QuoteCommissionInfoArray/QuoteCommissionInfo[QuoteCode='code' and PremiumTypeCode='code']/Amount]]

Total Commission by Quote Option

[[QuoteInfoArray/QuoteInfo[QuoteCode='code']/TotalCommission]]

Limit Amount by Quote Option, Premium Type, and Limit Type

[[QuoteLimitInfoArray/QuoteLimitInfo[QuoteCode='code' and PremiumTypeCode='code' and LimitTypeCode='code']/Amount]]

Note: LimitTypeCode should contain the Limit Type.

Deductible Amount by Quote Option, Premium Type, and Deductible Type

[[QuoteDeductibleInfoArray/QuoteDeductibleInfo[QuoteCode='code' and PremiumTypeCode='code' and DeductibleTypeCode='code']/Amount]]

Note: DeductibleTypeCode should contain the Deductible Type.

Insuring Conditions by Quote Option

[[QuoteInsuringConditionInfoArray/QuoteInsuringConditionInfo[QuoteCode='code']/Text]]


Enhancements to the Product Export / Import Feature


34Index

The Export / Import feature is used to copy master covers and related resources from one Bridge site to another. This feature has received multiple enhancement to provide better control and improve performance.

A large portion of the export file is made up of the documents and triggers associated to a master cover. A new Export Product option has been added to only include documents and triggers that have been modified as of a specific date. The Export Documents and Triggers Modified as of field in the Export Product panel can be used to select the date. The reduced file size will speed up both the export and import processes.

Note: When using this option, the export file should only be imported on top of a previous import. Importing to a new location may result in missing documents and triggers.

Two new Import Product options have been added:

Keep Distributor Association: If unchecked, importing a product on top of an existing product will overwrite the distributor configurations associated to the master cover. Checking this box keeps the current distributor configuration in the destination product.

Perform GUID check: If unchecked, any imported workflow resources will overwrite any resources of the same type that have the same code. If checked, resources will only be overwritten if both the code and internal GUID identifier both match.

The ability to export and import lookup tables has been added as two new panels, Export Lookup Tables and Import Lookup Tables. With functionality similar to the product export and import, the new options can export all lookup tables in the system, or a selection of tables. This produces a ZIP file that can be imported into a different site.

For details on using the Export / Import features, see the Export / Import section of the User Guide – Product Design document.


35Index

2.4.71 Minor Enhancements and Functionality Fixes

Enhancements

A Sequence Number can now be assigned when selecting Integration Configurations within the Workflow Management page. If multiple integration configurations are set to activate on the same Event with the same Perform setting, the sequence number will define what order they activate. This allows later integrations to depend on the results of earlier integrations, including evaluating the trigger to determine if the integration activates at all.

A new placeholder has been added to identify the selected language of the user's browser. The [[UserCultureCode]] placeholder can be used in calculated fields to pull in the browser language code when the fields are updated. The placeholder returns the language in the short code, such as en-us. Some uses for this information include triggers and filters on combo boxes.

A new email event type has been added to send emails when a transaction goes into Underwriting Required status. The Get Quote / Recalculate Quote – To Underwriting Required event is now available when creating an email configuration. Note that if the user has the ConfirmMaxReferralLimit1 security right, the transaction will go straight to Referred status instead of Underwriting Required, and emails for this event will not be sent.

A Trigger option has been added to the Master Cover - Quote Option screen, allowing quote options to be included or excluded based on transaction details when the quotes are calculated.

To ensure that users from insurer companies do not see quote information from other insurers, the Premium Widget has been modified. Whenever more than one insurer is attached to a master cover, even across quote options, then users from those insurer companies will not be able to see the premium value in the Premium Widget. They can still use the Quote Summary to see the premiums for individual quote options to which they have access.

If only one insurer company is attached to a master cover, then users from that company will be able to view the premium. This change does not affect client or distributor users.

The Emphasize Actions feature from the Screen Management page has been extended to custom integrations. When configuring a Custom integration, the Emphasize Action checkbox can be selected to add a button at the bottom of the screen with the same label as the custom option in the Actions widget. If the option in the Actions widget is unavailable, the button will not be displayed.


36Index

The label on the Code field for client companies can now be customized separately from other Code fields throughout the system. The Label_AssuredCode entry has been added to the language file in the Custom Labels page. Any changes to this label will apply wherever the code for a client company is displayed.

The Bind action for integration configurations now applies to binding Cancellation and Reinstatement transactions as well.

Automatic e-mails are now included in the E-mails list within the submission. The Type column has been added to the E-mails list, displaying whether the e-mail was generated automatically or manually.

Previously, e-mails attached to a transaction were only visible to the sender and recipients. The Master Cover – E-mail Configurations page now has a new panel, E-mail History View Criteria, which allows the selection of security roles. Users with at least one of the selected security roles will be able to view the generated e-mails.

The Enable Data Import feature, allowing users to import data directly into a grid, has now been enabled for View Grids.

When creating or viewing a client company, either through the Client menu or within a submission, the Code field is now displayed. When creating a new client company, the code can be provided or the system will automatically generate the code on saving.

When viewing a client company created before this update, if a code does not already exist it must be provided before saving the company. If the code for an existing company contains invalid characters, they will need to be corrected before the company can be saved.

The Custom Columns in Submission/Policy Grid panel in the Master Cover – Policy Settings page contains additional columns that can be customized and included in the submission list. The number of text columns has been increased from three to ten.

The Allow Insurers to Edit Clients checkbox in the Miscellaneous Settings panel of the Master Cover – Policy Settings page has been changed to Allow Insurers to Create / Edit Clients. This setting now allows insurer users to create new clients within a submission in addition to editing existing clients.

Note that this only applies to new submissions created after activating this option. It will not allow changes to pre-existing submissions.

When using the Accept Compliance action on a transaction, an Acceptance Reason must now be provided. The reason will be available in the Policy Information window, accessed through the Policy Information widget, and can be pulled into documents, e-mails, and fields.

The Field Initial Value Settings panel in the field configuration page and the Policy Settings panel in the panel configuration page have been expanded to include Cancellation and Reinstatement transactions.

The ability to view, create, edit, or delete Distributor configurations in a master cover no longer requires create or edit rights for the master cover itself. The ViewMasterCover right is required to access the master cover, but then the ViewMasterCoverDistributors, CreateMasterCoverDistributors, EditMasterCoverDistributors, and DeleteMasterCoverDistributors rights control the management of distributors within the master cover.


37Index

Whenever sidebars are available, containing widgets or additional content, they can be pinned or unpinned using hidden icons at the top-right of the sidebars (the icons appear when the mouse pointer passes near them). When a sidebar is pinned, it remains open and the main screen adjusts to fit. When a sidebar is unpinned, it collapses to the side and the main screen fills the space. The unpinned sidebars can be expanded or collapsed as needed, overlapping the main screen when expanded. This feature can be disabled in the system configuration, managed by your Oceanwide Representative.

The Reject Cancellation option, available when viewing Cancellation – Quoted transactions, has been replaced with the standard Delete option. This does not change the results, as both actions deleted the cancellation transaction, leaving the policy in effect.

Note that the Reject Cancellation option was associated to the CancelPolicy security right, while Delete is associated to the DeletePolicyTransaction security right. Users who had the ability to reject cancellations may not have the ability to delete them.

The main menu bar at the top of the page can now be hidden. The ViewTopMenu security right has been created and added to all existing security roles by default.

Without this right, the menu bar is blank, even if the user has the rights to view other features within the system. Features can only be accessed through direct links, such as bookmarks or the policy links that can be included in emails. The menu bar may be turned off to control access when using the Single-Sign-On (SSO) feature.

An optional configuration has been added to the core system settings. When enabled, completing a custom integration will automatically recalculate the quote if the current screen is set to recalculate in the master cover. For information on this setting, please contact your Oceanwide Representative. This does not apply to E-Signature integration types.

When Policy Number Source in the Master Cover is set to Manual, any Renewal transactions will now take their policy number from the selected field. If the field value changes from one term to the next, the policy number will change.

Fixes

Corrected error that could occur on calculating quotes for two submissions received simultaneously through a web service.

When importing transactions to update existing transactions, any fields with the default Read-Only setting will not be updated. Importing new transactions will still update these fields.

Corrected error that would occur when importing policies for a master cover in Test mode.

Corrected issue where the technical coverage would not match the effective coverage.

Corrected issue that could occur if no taxes were applied to the New Business transaction, but were applied in an Endorsement. The endorsement taxes would not be counted in the term, affecting cancellation transactions.


38Index

Corrected error that would occur when trying to auto-expire a quote on a deleted transaction.

Corrected issue where setting a master cover to live without making any changes would not be recognized.

Corrected error that could occur when exporting a master cover that included a tax code with more than 50 characters.

Corrected error that could occur when publishing a workflow.

Corrected issue where scheduled jobs might not run if a related insurer was removed from the master cover.


39Index

Index

22.4.71 Core Enhancements 22.4.71 Minor Enhancements and Functionality Fixes 34AAccount Control for Single-Sign-On Users 11Additional Grid Controls for Height and Filtering 20Advanced Lookup Tables 9Allowing Users to Assign Additional Security Roles 12Alternate Language Labels and Help Text for Workflow Components 17BBilling Features 4CConfiguration 2, 7ConfigureSingleSignOnUser security right 12Controlled Access for Files Attached to Policies 13Custom Transaction Statuses in the Workflow 17DData Sources 8Data Tables 8Data Validations on Grid Detail Windows 16Deleting Bound Transactions 25Digital Signatures for Transaction Documents 21EE-mails Drawing Additional Recipients From Workflow Fields 22Enhanced Product Design Features 8Enhancements 34Enhancements for Calculated Field Formulas 11Enhancements to the Product Export / Import Feature 32FField Evaluation Rules 9Fixes 36IIntegrated Billing System 2


40Index

Integrated Claims System 7Integrations Leading to External Websites 25LLayers 8NNew Control Type: Combo Box 10New Dynamic Field Type for File Uploads 18New Functions for Detecting Changes to Fields 27New Functions for Modifying Date and Time Values 26New Integration Point and Report for Compliance Scans 22New Integration Point for Request Quote Action 24New Panel Layout Options 19New Placeholder for the Last Modified Date and Time of a Transaction 30New Placeholder for Tracking Integration Run Times 30New Placeholders for Calling Client, Distributor, and Insurer Details 28New Placeholders for Calling Quote Option Details 31New Report for Users & Roles 13New Security Rights to Control Workflow Widgets 18PParent and Child Grids Changed to Cascading Structure 19Profile page 12Purpose of This Document 1RRate Driver fields 17Risks 8SSetMax() function 11Sharing Data Across Transactions 14Single Sign-On Settings panel 12TTaxes & Fees Based On Dynamic Fields 14WWorkflow Changes 4


Copyright Notice

Copyright © 1998 - 2015 Oceanwide 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 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 Inc.®™ Printed and published in Montreal, Quebec CANADA.

Trademarks

All trademarks, registered trademarks and service marks in this document are exclusive to Oceanwide Inc. ®™.

Disclaimer

The publisher Oceanwide 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).