No minor enhancements are included in this release.
•The system was allowing a cash batch receipt to be posted when it contained an invoice with allocation of zero. The check for a zero-allocation invoice was only being performed for Account Balance Allocation batch types. This has been corrected to apply to all batch types.
•Policy transactions showing in the Common Screens widget could sometimes display the wrong policy status. This bug was introduced during a recent fix that improved the performance of the formula evaluator. The code has since been updated to ensure that the correct status will be displayed.
•Corrected issue where the Payment Category, Payment Description, and Payment Coverage placeholders were not being populated.
•The Distributor Code would sometimes not populate fields that used it as part of a calculated field formula. This was because the system was taking the Distributor Code from a part of the system code that no longer contained it at the moment when calculated fields are evaluated. The system has been updated to ensure that the Distributor Code is taken from the correct part of the code base.
•Certain events were not included in the Event Tracking reports. The following events have been added.
− General: Create new policy.
− Tab workflow: Load Row, Create Row, Save Row, Save and New, Save and Close, Close, Copy Row, Delete Row, Next Screen, and Tab Select.
− Form Grids: Create Row, Load Row, Save Row, Delete Row, and Copy Row.
•Policy transactions showing in the Common Screens widget could sometimes display the wrong policy status. This bug was introduced during a recent fix that improved the performance of the formula evaluator. The code has since been updated to ensure that the correct status will be displayed.
•When using triggers in calculated fields within a grid, the triggers would evaluate the same for every row. This was caused by the triggers not receiving the row identifiers, and therefore trying to evaluate the entire column. This has been corrected to allow triggers to properly evaluate for each row.
•The Application Logs Viewer window would take a very long time to load. This was due to the system loading all data at once. The system now loads the data one page at a time for better performance.
•Corrected error that would appear when trying to export data from the Application Logs Viewer window. This feature was not configured properly. This has been corrected, allowing exports.
•Some calculated fields would not resolve when creating a new row in a grid after clicking on the Save & New button. This occurred because the system was incorrectly assigning two identifiers to the new row item, which would cause it to be unable to resolve the calculated field’s value at a later time. The code has been updated to prevent two identifiers from being created for a given row item.
•A server error could occur when trying to access a policy transaction using the Common Screens widget. This would occur in scenarios where a Custom Status was necessary to display based on result of a calculated field, but the system had not yet made the formula evaluator available to compute this result. The system has since been updated to ensure that the formula evaluator would be available in these scenarios.
•A timeout server error could occur when accessing the Earned Premiums report. This was caused by the system using default timeout settings. This was corrected to use custom system settings. If this error occurs, please contact your Oceanwide Representative to modify the custom timeout settings.
•A server error could occur when trying to access specific policies in the system. This would occur in workflows where the user would open an existing child grid’s row item, click Save & New, then Save & Close. This caused the system to generate two identifiers for a single row item, which would cause it to crash the next time it had to retrieve that row item from the database. The code has been updated to prevent two identifiers from being created for a given row item.
•Compliance acceptance reasons would sometimes not populate calculated fields. This is because the system has more than one identifier for these reasons and was using the wrong one in these cases. The system has been updated to use the correct one.
•Compliance rejection reasons would sometimes not populate calculated fields. This would happen in some scenarios where the system would not operate in a mode that considered the Compliance Referred status of the transaction. The system has been updated in so that this status is considered by the system in these cases.
•The system error message produced when using the same field in multiple grids was not clear. The message has been improved to provide more information.
•When a validation error would occur while editing a grid in-line, it would sometimes be possible to edit cells in other rows. This was caused by a bug within an older version of the user-interface tools that display the grid. The code for the tools has since been updated so that only the row that has caused the validation error can be edited. Once the cause of the validation error is fixed, the other rows can be edited.
•A server error could occur when trying send automatic emails with attachments. This is because certain versions of Bridge had a bug that caused the system to crash when evaluating triggers for email attachments. A fix for version 75 has currently been implemented to correct the issue.
•When printing documents that contained premium grids, the Transaction Premium and Term Premium columns would be empty. This was caused by the system incorrectly storing the premium values. Values are now being stored properly, and are available for documents.
•Watermarks would sometimes not appear on generated documents for master covers in test mode. This occurred because the code responsible for generating the document’s watermark was not configured to consider master covers in test mode. The code has since been updated to consider master covers in this mode.
•Certain printed documents would contain numeric values with incorrect formatting. This occurred because the system was ignoring recently refactored code that applied the correct formatting. The system has been updated to include the correct formatting produced by the refactored code.
•Documents generated in the Billing module would not populate placeholders for data from the Policy module. This was caused by mismatched versions of the document management code between the modules. The versions have been updated to the same code.
•A system error could occur when accessing a screen for a claim that had been imported through the Bordereaux feature. This occurred because a recent change to the import feature was using the label of option list items instead of the codes, and would convert the labels to lowercase. This has been corrected to use the codes for option list items.
•A server error could occur when attempting to view a grid page beyond the first. This was due to a bug in the code that incorrectly referenced the property in the grid that was supposed to show the column data. This code has been corrected to use the correct reference term for the column data.
•Requesting a quote could cause a server error. Certain policies with one distributor and multiple coverages had two different Code values for the distributor where there should have only been one. This caused the system to crash when trying to select the proper commission value for the quote. The system has been updated so that only the correct Code value is used for any given distributor.
•Users would sometimes be able to enter more characters into a textbox than specified by its Maximum Length. This is because some older versions of Bridge did not support this feature. The code has since been updated to ensure that this feature is fully supported.
•A server error can occur when trying to save a document template in the Claims module that was created in the Policy module. The cause of the error has been previously corrected, but some bad data may remain. If you are experiencing this error, please contact your Oceanwide Representative to have it corrected.
•A server error could occur during the calculate quote process in a tab workflow. This occurred because the code was removing a required identifier for a grid row’s parent item that was needed by the formula evaluator to calculate the premium. The code has since been updated to ensure that this identifier is available to the formula evaluator.
•Opening a document template could cause a system error or the wrong template to open. This was due to a recent database script that produced incorrect associations between templates and their associated documents. A new script has been run to ensure that all document templates have been associated to the correct document.
•Corrected a server error that could occur when trying to send manual emails associated to a claim.
•The Adjuster Auto-Assignment functionality was mistakenly disabled by a related enhancement. This has been corrected.
•Screen and Panel override configurations were not working in the Claims module. This was caused by the Claims module identifying triggers differently than the Policy module. While this issue has not been completely corrected yet, a workaround is available through system configuration. If you are encountering this issue, please contact your Oceanwide Representative for assistance.
•When binding a transaction, an error message may appear about an integration service failing. This could be caused by delays when transferring data to the Billing module. The timeout period has been increased to the system standard, allowing time to complete the process.
•Clicking on the Export button in the Export Product panel on the Export / Import page could cause a server error. This would occur in cases where the file size necessary to perform the export operation exceeded certain built-in system limits. The code has since been updated to ensure that large file sizes can be properly accommodated during the export process.
•Corrected issue where indexed field data was not being pulled into the claims module. The issue was linked to errors such as detection of duplicate claims and being unable to add custom fields to the claims list.