The Assured Lookup web service has been added for Data Source Configurations. It allows users to search for individual clients and client companies based on the supported client types specified in the master cover. This feature is primarily intended to be used with future features which will allow client information to be collected at custom points in the workflow, instead of at the very beginning.
Note: In order for this web service to function, the following two filters must be configured in the Filters panel of the data source configuration.
•For the first filter: Select Assured Type in the Column field, select Field in the Filter By field, and select MasterCoverAssuredType for the Field or Constant Value field.
•For the second filter: Select Country in the Column field, select Field in the Filter By field, and select MasterCoverCountryOptionListCode in the Field or Constant Value field.
These filters will ensure that the web service only returns information that corresponds to the supported client types and countries of the master cover, which are specified in the Supported Client Type and Supported Client Countries fields in the Client Configuration Settings panel of the Master Cover - General Information page.
− For more information, see the Web Service List for Data Sources section.
Various settings that control how a user creates or selects a client before starting a submission have been updated.
•On the Master Cover - General Settings page, the following label changes have been made to the Supported Clients panel.
o The Supported Clients panel has been renamed to the Client Configuration Settings panel.
o The Type field has been renamed to the Supported Client Type field.
o The Countries field has been renamed to the Supported Client Countries field.
•The Client Screen in New Submission Workflow field has been moved from the Miscellaneous Settings panel on the Master Cover - Policy Settings page to the Client Configuration Settings panel on the Master Cover - General Settings page. The field has also been renamed to the Client Selection in New Submission Workflow field.
•The Skip button that allows users to bypass the creation or selection of a client before starting a submission can now be hidden. This is useful when you want to require users to create or select a client before they begin the submission process.
To support this feature, the Skip Button field has been added to the Client Configuration Settings panel. Select Display so that the Skip button is available to users. Select Hide so that the Skip button will be hidden, thus requiring users to select or create a client before starting a submission.
− For more information, see the General Information section.
Licensees can now use their own custom web services with Data Source Configurations. This is especially useful when workflows need access to data that can only be provided by web services that do not come with Bridge.
To support this feature, Bridge will now come with a built-in option list. Its Code is DataSourcesWebServicesOptionList and its Name is DataSources WebServices OptionList. It is used to customize the list of web services available for data source configurations on the Data Source Configuration Management page. This is useful when you want to change the label of existing web services, or to remove unused web services from the list.
•The Code of the option list items, as well as the Name and Code of the option list itself, should not be changed. Doing so could cause data source configurations to stop working.
•This option list uses a new kind of Resource Type, which is Web Service. No further option lists that use this resource type should be created. If any are, they should be deactivated.
The option list can be customized by navigating to its Option List Management page and making modifications to the option list items in the Option List Items panel. The option list comes pre-populated with the option list items necessary to support the web services that come with Bridge.
•To modify the label of a web service, change the Label of its option list item and then save your changes.
•To remove a web service from the list, delete its option list item and then save your changes. Use caution when doing so, as there can be data source configurations that depend on it.
•Existing items that are deleted from this list can be restored. As long as their original Code is used, they will resume working as they did before they were deleted.
•Changing the Sequence of the items for this specific option list will not change the order in which the items appear.
•Adding a new item to this list for a custom web service requires coordination with Oceanwide. Contact your Oceanwide Representative.
− For more information on Data Source Configurations, see the Creating a Data Source Configuration section.
Payments can now be made toward policies that have been quoted, but not yet bound. This is particularly useful for products where the binding of a policy is contingent on receipt of a payment.
To enable this feature, the Allow Online Payment on Quoted Transactions checkbox was added to the Billing Settings panel on the Master Cover - Policy Settings page. When it is checked, the Pay Now option will be available in the Premium widget after a quote is calculated and a Payment Plan is selected. This applies if the transaction type is New Business, Endorsement, Renewal or Adjustment. It will allow the user to make online payments directly from the transaction.
To match the new checkbox, the Allow Online Payment checkbox has been renamed to Allow Online Payment on Bound Transactions.
Following the online payment, the system can supply a custom field in the workflow with the total cumulative payment amount made on the transaction. This is particularly useful in cases where the cumulative payment amount needs to be used with triggers or referenced by calculated field formulas. In order for a custom field to receive the payment amount, it must have the following characteristics:
•Its Code must be BillingTotalTransactionPaymentAmount. To ensure that the Code becomes this value, enter BillingTotalTransactionPaymentAmount as its Name. Once the proper Code has been generated on saving the field, the Name can be modified.
•Its Control Type must be Textbox (Decimal).
•When using the Import feature to import a transaction for a product that allows online payments, the field must be included along with the other fields in the Fields XML node within the CustomInfo XML node. For information on the Import feature, see the Import section.
Note:
•Once the payment is processed, the system will automatically bind the transaction. Bind Validations must be configured if other conditions must be verified before the transaction is bound.
− For more information, see the Policy Settings section.
Previously, the system required that a client be explicitly linked to a distributor. This link was made in the Distributor Owner panel on both the Individual Client Information page and the Client Company Information page. When managing a submission, the user could only select from clients that were linked to the selected distributor.
This link has been removed from the system. Now, when a user is managing a submission, they can select from all clients made available by the system, regardless of the distributor that was selected. Clients can now have multiple policies where each policy can have a different distributor.
To implement this change, the following modifications have been made:
•The Distributor Owner panel and Distributor Change History panel were removed from the Individual Client Information page and the Client Company Information page.
•The Distributor column was removed from the Client List panel on the Clients page.
•Specifying a distributor owner is no longer required when using the Data Import feature to import transactions. The distributor owner used to be specified in the Owner Code element of the ResourceInfo node of the XML structure of the import file. The entire ResourceInfo node is no longer required.
•The ManageAssuredOwner security right is no longer in use, and has been removed from the system. It was used to allow a user to change the distributor company listed as the owner of a particular client.
The distributor associated to a policy term can now be changed. Previously this was done indirectly, by changing the distributor associated to the client of the policy. This was often not ideal, since doing so would transfer all the client’s policies to the new distributor.
Certain users can now change the distributor associated to a policy term from within the submission workflow. This allows the distributor to be changed on a term-by-term basis, and allows clients to have policies with more than one distributor.
The distributor can be changed on New Business, Endorsement, Adjustment or Renewal transactions that are in Incomplete, Quoted, Underwriting Required or Referred status. Users must also have the new ChangePolicyDistributor security right, which was created as part of this enhancement. It is recommended to give this security right to users that can see other distributors, such as Licensee users. By default, the security right is given to all users that had the ManageAssuredOwner security right. As of this version of Bridge, the ManageAssuredOwner security right has been removed.
Changing the distributor is done at the transaction level using the Policy Information widget. Permitted users can change the distributor by selecting the new one from the Distributor field. The new distributor gains access to all transactions in the term. The. former distributor retains read-only access to transactions on which it is the distributor.
When a distributor is changed for a transaction in Quoted, Underwriting Required or Referred status, the transaction will be set to Incomplete.
•Any related Quote Versions will have their distributor changed to the new distributor.
•Any related Quote Versions in Quoted, Underwriting Required or Referred status will be set to Incomplete.
•Following the distributor change, any of the above transactions and Quote Versions that had quotes will have to be re-quoted. Some of these transactions and quote versions may be re-quoted automatically, depending on product settings.
− For more information, see the Changing the Distributor on a Policy Term section.