•A Field Evaluation Rule can now be configured to have the system evaluate a calculated field in the event that a transaction is bound. This event can be included in a field evaluation rule by selecting Bind from the Events field in the Triggering Conditions panel on the Field Evaluation Rule Management page.
•When viewing the submission Search/List page, taxes would be visible in the Taxes (Last Transaction) column without any corresponding value in the Premium (Last Transaction) column. This occurred because the source code was configured to show tax information in this column as long as any existed for the transaction, but would only show premium information if the transaction status was Quoted, Bound or Bind Requested. This has been corrected so that both taxes and premium will appear based on whether the transaction is in Quoted, Bound or Bind Requested status.
•When making an online payment, the First Name and Last Name fields would be displayed with both first and last names in the First Name field, and the user’s e-mail address in the Last Name field. These fields are no longer being automatically populated, so the user will need to enter the information.
•When the Billing Frequency was set to Daily, an internal date mismatch could result in the invoicing being run a day late. This has been corrected.
•Individual assured users would sometimes not be able to print documents. Printable documents would be visible in the New Document window, but clicking the Print button would not generate them. This has been corrected.
•When editing the charge for a payment schedule in a transaction, the payment plan summary would not be immediately refreshed to reflect the changes. This has been corrected.
•The Print Document button would sometimes not be visible for cancellation transactions, where the Confirm Cancellation action had been clicked and the master cover had the Set Transaction Status to Incomplete if Quoted Submission is Modified checkbox unchecked. This has been corrected and patched back to version 2.4.83.
•Updates made to option list items in one environment would not appear when the product was imported into another environment. This was due to a problem with the import process and has been corrected. This has been patched back to version 2.4.87.
•An error could occur when importing a product. This would occur when the import file exceeded 33 MB, which previously was the maximum allowable file size. This has been corrected by increasing the maximum allowable file size to 2048 MB.
•A server error could occur when creating a Quote Version for certain workflows. These workflows were those containing grids with records that had files as attachments. After entering a quote version in the Create Quote Version window and clicking Confirm, the error would occur. This has been corrected and patched back to version 2.4.86.
•When trying to access a billing or claims page with a link or bookmark, without an active session (timed out or not logged in), a system error would appear instead of the login page. This has been corrected.
•A warning message would not appear to notify the user of a failed integration configuration after the user clicked on the Next button. More specifically, this would occur for Post-Action integration configurations configured to activate on the Save action. This was because the system was designed to only show such warnings on the same page that activated the integration configuration. The system has been updated so that these warnings will now appear on the next page. This has been patched back to version 2.4.83.
o Note: the warning will only appear on the next page immediately following the failed integration. If the user leaves the page and then returns, the warning will no longer be visible.
•An error could occur when importing a product. This would occur when the import file exceeded 33 MB, which previously was the maximum allowable file size. This has been corrected by increasing the maximum allowable file size to 2048 MB. This has been patched back to version 2.4.86.
•Checkbox columns in grids would sometimes not be visible after exporting a grid and refreshing the page. This has been corrected.
•The system would automatically add eight numbers after the decimal of a premium value specified in the Premium Override Window. This caused a validation error to occur when the Save button was clicked. This has been corrected.
•When logged in as a distributor, an error could occur when saving a new client as part of creating a new submission. This has been corrected and has been patched back to versions 2.4.84 and 2.4.87.
•Combo boxes that use grids as a data source would sometimes not display all records from the grid. This has been corrected. This has been patched back to versions 2.4.86 and 2.4.87.
•A server error could occur when publishing a workflow. This occurred because the system was including deleted universal triggers in the publish process. This has been corrected and has been patched back to versions 2.4.85, 2.4.86 and 2.4.87.
•When reversing a receipt, an incorrect error message would appear about the allocation amounts. This has been corrected and patched back to version 2.4.86.
•Automatically generated documents would sometimes not be attached to automatic e-mails that were configured to be sent when a policy was cancelled. This has been corrected and patched back to version 2.4.83.
•When quoting a transaction in Referral status, a message would appear about being unable to preview the payment schedule, This has been corrected, and the fix has been patched back to version 2.4.86.
•Asynchronous integration calls would display an error even when they were completed successfully. This has been corrected. This was patched back to versions 2.4.86 and 2.4.87.
•Records of e-mails sent by automatic e-mail configurations would not be visible in the E-mails window for certain recipients. These recipients were those whose e-mail address was included by using the value from a calculated field. Records were also not visible to recipients intended to be included because the Include Submission Creator or Include Client or Include Distributor checkbox was checked in the configuration. This has been corrected, and has also been patched back to version 2.4.71.
•A server error could occur when saving a claims payment for a newly initialized environment. This has been corrected for any environments created from here on. If this bug appears in any other recently created environments, please report the issue to your Oceanwide Representative for correction.
•Some larger automatic reports were not being generated. This was caused by the reports taking longer than the allowed timeout period. The timeout periods have been increased, and an internal setting has been added to allow the periods to be increased again if necessary.
•Some rows belonging to child grids would sometimes be deleted during the Calculate Quote process. This has been corrected and patched back to version 2.4.87.
•Navigating through a claims workflow would not respect the sequence order of the screens, instead using the order they were added to the workflow configuration. This has been corrected and patched back to version 2.4.86.
•In a claims workflow, panel overrides to make a panel read only were not working. This has been corrected and patched back to version 2.4.86.
•The SmartView dashboard would sometimes fail to load. This has been corrected.
•The CheckComplianceHit function would always return false and not output results to other fields. This has been corrected and patched back to version 2.4.87.
•Documents added as attachments in the Documents field of Automatic E-mail Configurations would sometimes not be saved. This has been corrected and patched back to versions 2.4.86 and 2.4.87.
•The thousands separator and rounding precision of a Textbox Decimal field would not be correctly applied after entering a value and then either tabbing out of the field or clicking outside of it. This has been corrected and patched back to version 2.4.86.
•The system would add a value of zero to a Textbox Decimal or Textbox Integer field if the user placed the curser in the field and then removed it without entering a value, and no other settings were configured to populate the field with a zero-value. This has been corrected and patched back to version 2.4.86.
•Data Validations configured to activate when saving changes made to detail windows for View Grids would not activate. This has been corrected and patched back to version 2.4.87.