Dynamic grids in the workflow have been enhanced to allow the editing of data within the grid itself, without having to open the detail window. Once configured, the user can double-click a cell for an editable column, add or edit the content, and then click on another row or click outside the grid to save the changes. Multiple cells in a single row can be edited, and the entire row is saved on clicking outside the row.
Two new options have been added to the Panel Management page.
•When working with a grid, the Enable Editing in Grid checkbox is available in the Grid Settings panel. This checkbox enables editing for the current grid.
•The Editable in Grid checkbox has been added to the Field panel of the detail window when configuring fields within the grid. This option is available when Enable Editing in Grid is enabled, the Display in Grid setting has been checked, and the current field type is supported.
The following field types are supported: Text Box, Textbox (Decimal), Textbox (Integer), and Checkbox. However, if the field configuration is set to Read-Only, this checkbox will not be available.
Note that any field or panel override conditions will not be applied, but the Required setting in the field configuration will be enforced if it is checked. In addition, data validations set for the grid will not be triggered, so any such validations should also be set for the parent page.
− For details on configuring panels, see the Managing Panels section.
Grids can now be configured to include a column of links leading to specific pages within the workflow. Other columns can be include as well to provide related information.
The Hyperlink Field option has been added to the Field Assignments panel in the Panel Management page. A Label or Textbox field can be selected.
Note that using this feature disables the Add and Export / Import features, as well as the ability to open a detail window by clicking a link in the first column. The grid can only be populated by an integration configuration, such as bringing in data from Insurity's Policy Decisions system. Once populated, certain fields can be edited directly in the grid if configured with the Editable in Grid setting.
− For details on configuring panels, see the Managing Panels section.
− For information on configuring integrations for use with this feature, please contact your Oceanwide Representative.
The Multiply() function has been added, taking a grid column or other set of fields containing numerical data and multiplying all values. The function returns the multiplied total.
− The Multiply() function is detailed in the Functions section.
A new row has been added to the template used for importing data into grids. It is hidden by default and contains the code of each field that defines a column in the grid. The data in this row should not be modified so as to not cause errors when importing the file.
− For details on importing grid data, see the Importing Grid Data section.
When selecting a policy from within a claim, a selection of system details from the policy are copied over into the claim. This feature can now be configured for dynamic fields as well.
A single field can be used in both the Policy workflow and Claims workflow, or two separate fields from Policy and Claims can be linked together. The link is created using the External Code field in the Field Management page. The code should be prefixed with "Bridge.Policy.", such as "Bridge.Policy.CoverageRegion", with the same code used in both fields when linking two fields.
Whenever a policy is selected for a claim, including changing or re-selecting a policy, the claims field will be populated with the data from the associated policy field. The claims field can then be used normally for features such as calculations, conditions, and generated documents.
Note that changes to the policy field will not automatically be copied to the claims field. The data will only be copied when selecting a policy in the claim.
In addition, any changes to the claims field will not be copied to the policy field, and will be replaced with the policy field data if the policy is re-selected.
− For details on managing field configurations, see the Managing Fields section.
The Automatic Cancellation Initiation feature introduced in version 2.4.78 can be configured to begin the cancellation of a policy. A new configuration is now available that can complete the cancellation process.
The Automatic Cancellation Finalization panel has been added to the Master Cover - Automatic Processing page. This feature allows cancellation transactions for a specific master cover to be confirmed according to a trigger. This applies to all cancellation transactions in Quoted status that are on or after their Effective Date, whether they were created manually or automatically.
Automatic rescission of a cancellation is currently in development, and will be available in a future release.
− For details on configuring automatic finalization settings, see the Automatic Processing section.
In Part 1 of this enhancement from version 2.4.81, configuration options were introduced to enable claim payment summary e-mails. This feature is now functional.
In addition to the configuration options introduced in the previous version, grid functionality has been added to the claims e-mails. These e-mail tables can pull in data from dynamic grids within the workflow, or special internal tables.
A new internal table, ClaimPayments, and a selection of payment detail placeholders, can be used in the claim payment summary e-mails. The system will automatically filter data from this table to only include payments to the party to whom the e-mail is being sent.
− For information on e-mail syntax for grids, see the Tables in Claims E-mails section.
− For information on the new placeholders, see the Claim Payments Information, Multiple Filtered Payments section.
− For information on managing e-mail configurations, see the Configuring Claims E-mails section.
− For information on managing general settings for e-mail scheduling, see the General Settings – Scheduled E-mails section.
The system can now automatically create claim payments in response to certain events in the claim workflow. This is managed through rule configurations that include the conditions when the payment will be created, and the details to be applied to the payments themselves.
The Payment Rules menu option under the Claims and Configurations menus has been expanded into a sub-menu. This sub-menu includes the existing Payment Integration feature and the new Automatic Claim Payments feature.
The new Automatic Claim Payment Rules page allows the creation of individual rules. The rules are associated to one or more workflow events and a trigger. If a selected event occurs, the trigger evaluates to true, and a policy has been selected for the claim, the rule will produce a new payment. The rule configuration defines the details of the payment, taking most of the settings from fields within the workflow.
− For information on managing claim payment rules, see the Automatic Claim Payment Rules section.
A system of control rules has been added to the system to manage which users can access which claims.
•Users have access to claims that they have submitted.
•Users can access a claim if they are attached to it as a claim party, or if they belong to a company that is attached.
•Users with the Adjuster Supervisor or System Admin roles have access to all claims in the system.
Note that these rules alone only provide potential access. User must still have the necessary security rights to work with claims.
In addition, when a user tries to attach a policy to a claim, they will only be able to select policies that they have access to within the policy module.
As an enhancement to both the transaction and full versions of the Event Tracking report, additional information has been made available for any integration events.
When viewing the details for the event, any failed integrations will display "Error" at the end of the header line.
A new Status column has been added to the event details page. This displays if the activity succeeded or failed, where applicable.
A new Operation Result column has been added to the event details page. This column includes links to the response XML files, where applicable.
− For details, see the Event Tracking Report section.