•The automatic processing of cancellation finalizations has been updated. Previously, checking the Enable Automatic Cancellation Finalization checkbox would cause the system to wait for a cancellation’s Effective Date before deciding whether or not to rescind or confirm the cancellation. Following this update, the system will now also make this decision during every automated review of all policies in Cancellation - Quoted status. During each review, the system will evaluate the trigger specified in the Automatic Cancellation Finalization panel. If it evaluates to true, the system will confirm the cancellation if the cancellation’s Effective Date is earlier than or equal to the current date. If it evaluates to false, the cancellation will be rescinded immediately.
This new functionality is particularly useful when you want the system to decide whether or not to rescind a cancellation before the cancellation’s Effective Date, such as when a payment is made on a policy that is nearing cancellation.
This has been patched back to version 2.4.86.
− For more information, see the Automatic Processing section.
•Previously, users that had access to the Cognos Reports tool could see all reporting data in the system, regardless of their user account. Moving forward, the information available to each user will be tailored to their account. This has been patched back to version 2.4.87. For more information, see the Cognos Reports section.
•When creating a claim payment, the Type and Status fields in the Payment window are no longer defaulted to any option.
•A new option list resource type named CustomWebService has been created. It is visible in the Resource Type field of the Data Source Properties panel on the Option List Management page when the Type field is set to Static. This is part of a larger feature that will allow custom web services to be used with Data Source Configurations. It is currently not in use and it is recommended to not create any option lists that use this resource type.
•Previously, buttons in the Screen Button Bar could be missing from view. This would occur when too many buttons were configured to appear within the bar’s available space, if users increased the zoom-level above a certain amount, or if the screen was resized. A new internal setting has been added to prevent this. When it is enabled, the system will add extra rows so that all buttons are displayed. When it is disabled, any buttons that cannot fit in the first row will be hidden from view. The internal setting is disabled by default. To enable it, contact your Oceanwide Representative. This has been patched back to versions 2.4.86 and 2.4.88.
•To prepare for an enhancement that is still in development, some changes have been made to the Billing Settings panel in the Master Cover – Policy Settings page. A new checkbox has been added for Allow Online Payment on Quoted Transactions and the existing Allow Online Payment checkbox has been renamed to Allow Online Payment on Bound Transactions. Note that the new checkbox for quoted transactions will make the Pay Now option available for quoted transactions, but it will not be functional. The functionality for bound transactions has not changed.
•When trying to load a page that contained a grid while using the Safari web browser, the system would display a blank page instead. This has been corrected.
•A server error would occur when clicking on Calculate Quote. This would only occur in workflows that had two or more taxes that shared the same internal reference but had a different Name. This has been corrected and patched back to version 2.4.83.
•The Event Tracking report would not mention if an invalid user account was used to attempt to complete an operation in the system. This typically occurs when the account is specified in the communication between two system components. Invalid user accounts include those with an expired password, an incorrect password, an incorrect username or set to inactive status. The report will now display an error message when this occurs. This has been patched back to version 2.4.83.
•An error could occur when performing the Get Quote, Bind, or Endorse actions. This error was most likely to occur when the system was simultaneously processing a high number of submissions. This has been corrected and patched back to versions 2.4.83 and 2.4.86.
•The DateOverlap() function would return any leading spaces that were included in the true or false return values, which could result in incorrect processing of those values. This has been corrected so that leading and trailing spaces are ignored.
•When the Modern Large Font or Modern Small Font skins were used, the comma, currency symbol and separators in the Premium widget would be partially or completely cut-off. This has been corrected and patched back to version 2.4.87.
•The Save and Delete buttons would still be available when viewing a posted receipt reallocation. This has been corrected.
•An error could occur when loading an option list containing the province list for the country of Bermuda. This has been corrected.
•The TotalGrossPremiumAmount function would return a value of 0 instead of the premium shown in the Premium widget when a quote was calculated. This has been corrected and patched back to version 2.4.83.
•Placeholders that used PremiumInfo would not return a value when a quote was calculated. This has been corrected and patched back to version 2.4.83.
•Screen behavior overrides would not work for screens configured to appear in tab workflows. This has been corrected and patched back to version 2.4.88.
•Renewal transactions would not be able to be created due to a validation error stating that at least one term in the policy was not declined or bound. When the renewal was attempted, the system was associating Renewal - Incomplete transactions to the policy that could not be seen by the end user, which caused the validation error to occur. This has been corrected and patched back to versions 2.4.86, 2.4.87 and 2.4.88.
•Certain images and icons were missing from the workflow. These included combo box drop-down arrows, warning icons and pin images. This issue was present and corrected in versions 2.4.83, 2.4.84, 2.4.85, 2.4.86 and 2.4.87.
•A server error could occur when trying to access a policy. This was due to a versioning issue with internal components, which has been corrected. This has been patched back to version 2.4.86.
•A validation error could occur when trying to import a product if it contained a Data Table or Data Source Configuration used in two workflows, where one of the workflows was a shared workflow of the other. The validation message would state that either a Data Table Definition or Data Source could not be imported since another Product had one with the same code. This has been corrected by removing this validation rule from the system. Since workflows can be shared, the rule is no longer necessary. This has been patched back to versions 2.4.85, 2.4.86, 2.4.87 and 2.4.88.
•When quoting an incomplete transaction, an error could be displayed about not being able to preview the payment schedule. This error would occur when a quote validation was triggered in a configuration with just a single quote option and a single payment plan. This has been corrected and patched back to version 2.4.86.
•A server error could occur when clicking on the Issue Quote action, the Next button or on a link in the Submission Screens widget. The error log would contain messages stating that fields referenced by triggers did not exist in the Product Library, and that calculated fields weren’t added to the Product Library. This has been corrected and patched back to versions 2.4.81, 2.4.83, 2.4.84, 2.4.85, 2.4.86, 2.4.87 and 2.4.88.
•The LookupDataSource function would not display any results or output to any fields when used with a Data Source Configuration that used Grid as its Data Source Type. An error referring to an invalid cast exception would also appear in the Event Tracking report. This has been corrected and patched back to version 2.4.86.
•When the same grid repeater trigger was used in two or more documents being printed together (using multiple templates in a configuration), the trigger would not be evaluated again after the first instance. This would produce incorrect results for the remaining instances. This has been corrected and patched back to version 2.4.86.