2.5.121 Minor Enhancements and Bug Fixes

Enhancements

  • An Event Tracking report is now available through the newly introduced Common Screens widget in the Workflow Container management page. This report provides a detailed overview of events directly relating to the Workflow Container from which it is accessed, including Workflow publishing history and Export and Import events. For details on the Event Tracking report, see the Full Event Tracking Report section.
  • The ability to send a copy of e-mails generated through the claims module to the claim creator is now supported. This feature can be enabled by checking the Send to Claim Creator checkbox in the E-mail Details panel of the Email Configuration page. Furthermore, five new placeholders have been introduced to capture e-mail recipient details for Documents and E-mails generated through the claims module. This has been patched back to 2.5.118. For additional information on the Send to Claim Creator option, see the Configuring Claims E-mails section. For additional information on the new placeholders, see the E-mail Recipient Placeholders section.
  • The Responsive Disclosure of grid fields is now supported in the claims module. This allows for fields to be displayed upon the selection of a Checkbox and/or Combo Box control field.
  • It was discovered that policy transactions in Quoted status transitioned to Incomplete status following certain custom integrations. In some cases, this resulted in users being unable to Bind a transaction. A new Web Site Configuration key called MaintainTransactionStatusAfterCustomIntegration has been introduced which, when set to "true", ensures that the most recent transaction status is maintained following all custom integrations. This has been patched back to 2.5.109, 2.5.112, 2.5.115, and 2.5.118.
  • Previously, when attaching a policy through the Select Policy action in the claims module the system only returned policy terms in effect on the Date of Loss. However, there are valid business scenarios where policy terms should also be available for selection based on the Date Reported. The system logic has now been updated to return all policy terms available for the Assured when the Date Reported criterion is specified. Note that the ability to attach a policy to a claim is governed by the SetClaimPolicy security right.
  • having these operations run concurrently risks data corruption. The following validation message will appear: " Only one operation can be done at once..." The error message will display the current import or export that is in progress.

Fixes

  • For an integration call from Bridge to OMS, the Client Code would be returned, but it would not appear in the workflow submission. As a result, an error message would appear when updating the imported policy into Bridge Specialty Suite. A new custom control field for Bridge, UserID, has been added to a submission workflow as an additional input parameter, so when a policy is updated, the imported OMS policy UserID is not disturbed upon update.

  • The system failed to Export / Import Claim Payments when this action was selected by users with the ViewClaimPayment and associated security rights. This has been corrected, and the Claim Payment records are now exporting and importing as expected. This has been patched back to 2.5.118.
  • Close Reserve Rules were not being deleted through the Close Reserve Rules grid in the General Settings - Reserves / Estimates page in the claims module for users with the appropriate security rights. This has been corrected, and selected rules are now being deleted. This has been patched back to 2.5.118.
  • The user is unable to Activate or Deactivate resources in the billing module by checking or unchecking the checkbox to the left of the resource(s) to be deleted. This has been corrected, and the user can now Activate or Deactivate these resources. This has been patched back to 2.5.115.
  • A server error occurs when the ImportConfigurations() web service is called and the configuration(s) are not imported. This has been corrected, and the configurations are now successfully imported.
  • A validation message prevented the user from unchecking the Enable Scheduled Emails checkbox in the Claim Payment Summary window when any of the required fields within the same panel were missing a value. This has been corrected, and this feature can now be disabled. This has been patched back to 2.5.118.
  • A server error occurs when deleting a grid row through the modal window in the claims module. This has been corrected, and grid rows can now be successfully deleted. This has been patched back to 2.5.118.
  • A server error occurs when exporting a claims product through the Export / Import feature. This has been corrected, and claims products can now be successfully exported. This has been patched back to 2.5.118.
  • Spaces between the DD, MM, and YYYY values are removed from Date and Time entries in grid fields. This has been corrected, and date values are being properly displayed. This has been patched back to 2.5.109, 2.5.112, 2.5.115, and 2.5.118.
  • It was discovered that user login passwords could be updated without having the necessary authentication in place. This has been corrected through an encrypted URL query string and security token validation. This has been patched back to 2.5.103, 2.5.109, 2.5.112, 2.5.115, and 2.5.118.
  • Values persisted in the optional fields of the Payment Management window of the claims module (Category, Check Number, Reference Number, etc.) even after the user accessed the window a second time to remove the value(s). This has been corrected. This has been patched back to 2.5.118.