•Previously, the Submission/Policy Screen field in the Screen Selection panel on the Master Cover - General Information page displayed all published active workflows, filtered by line of business. It now no longer filters by line of business and shows all active published workflows of type Steps.
•A Data Source Configuration can now pull data from a grid within a shared workflow.
•The following updates have been made to the Domain / Rate Table Management page:
o A Name field and a Code field have been added. If the user does not enter a code, the system will create one automatically.
o The Culture and Effective Date fields of existing domain / rate tables can now be modified.
o The Import button has been removed. If a file is selected to be imported, the import process will occur when the page is saved.
•The Address Lookup web service now returns a Country Code field.
•For Textbox (Integer) fields, the visibility of the thousands separator will be updated when the fields lose focus. Previously, these updates were only made when the page was saved and refreshed. Note that if the Textbox (Integer) field has its Hide Thousands Separator checkbox checked, the separator will not show.
•For Textbox (Decimal) fields, the decimal formatting will be updated when the fields lose focus. Previously, these updates were only made when the page was saved and refreshed.
•Data tables now support up to one-hundred columns.
•“.0001” would sometimes get appended to the Code field of a product every time it was saved. This has been corrected.
•When importing claims, the system would allow multiple parties to be attached with the same Party Role. The validations have been corrected to prevent multiple parties per party role, with the exception of Additional Named Assureds.
•A server error could occur when endorsing transactions whose Endorsement Effective Date is set to Field Value on the Master Cover - Policy Settings page and the current date is outside the transaction’s policy term. This was because the code’s sequence of operations that handled the dates had an error which caused the wrong dates to be assigned to the endorsement. This has been corrected.
•A server error could occur when attempting to login to Bridge. This would occur on certain versions of Bridge where an incorrect username or password was entered. These versions were configured to return an error page instead of the normal message that informs the user that incorrect login information was entered. They have been updated to ensure that the normal message is returned instead.
•The Category field in a claim payment would display the code of the category options instead of the labels. This has been corrected.
•Pre-integration field evaluation rules would sometimes not be triggered. An upgrade to the system code for improving its performance was causing it to skip over the evaluation of these rules. This has been corrected.
•When warning or error messages appear in the Bill to Parties Scheduled Payments list, they could stay on the page when navigating back to the Bill to Parties list. This has been corrected.
•A grey horizontal line could appear across the login page, passing just below the Logon button. The system can now be configured to display this line or hide it. Please contact your Oceanwide Representative to request any changes to the configuration.
•A system error could occur when trying to retrieve tax information using placeholders. This would occur when the value being returned by the system was not a number. The system has been updated to ensure that it can parse data of multiple types including text, numbers, dates and boolean values.
•Within a claims workflow, using a combo box linked to a data table would not return any results. This has been corrected.
•Printing a document with the same grid that appears multiple times on the same page could cause the application to crash. This occurred because a necessary operation that would update the field values before generating the document was not running. The code has been updated to ensure that the update is made before the document is generated.
•Certain fields using nested triggers would sometimes be missing or sometimes visible when they should have been hidden. This occurred because the system wasn’t updating these field values at a specific time that was necessary for processing the result of nested triggers. The code has since been updated to ensure that all field values are updated prior to nested trigger evaluations.
•The results of trigger evaluations would sometimes appear in their field values. This occurred due to a bug with a recent upgrade of built-in third-party software that manages various user-interface elements. Where this issue has occurred, an older version of the third-party software has been re-implemented until the newer version is fixed.
•Some grids that were supposed to be cleared for cancellation and reinstatements were not cleared as expected. This occurred because code from a recent enhancement to Bridge was causing the grid data to be copied forward instead of being cleared. This has been corrected.
•When importing a file, the system would sometimes allow duplicate tracking numbers. A recent update to Bridge disabled part of a web service that could detect them. The web service has since been updated to ensure that it will catch duplicate tracking numbers and prevent them from existing in the system.
•The following validation error could occur: “Cannot publish workflow since the following Source Transaction Fields are using Source Transaction Fields to set their initial value.” The system has been updated to now allow source transaction fields to use other source transaction fields to set their initial values.
•A spinner would appear when clicking on a hyperlink to download a file from a grid. This caused the application to become unusable until the download was complete. This has been corrected.
•A server error could occur when importing a workflow. This occurred because the system was erroneously producing duplicate system identifiers for fields being imported. The code has been fixed to prevent such duplicates from being created.
•If a communication error occurred with the Billing module while confirming a cancellation, an error code would be displayed without any message. The error has been corrected to display a proper message.
•When creating Rate Rules, users were able to select grid fields for use as driver fields. Although these fields were selectable, the system was not programmed to actually use them properly for Rate Rules. This has been corrected so that only form fields can be selected.
•An error could occur when the system would call the QueryPolicyHeader web service. This service would make use a file containing stored-procedures that has recently expanded significantly. Certain SQL keywords needed to be added in between the stored procedures in this file to ensure that all of them would be called when necessary; these keywords were missing from the file. The file has since been updated with these keywords.
•The Security Roles field in the Assignable Security Roles panel on the User Information page would sometimes be disabled. This occurred due to a recent update to third-party software that is used to display many of the user-interface controls. An aspect of the update did not integrate well with existing Bridge code, which caused the field to become disabled. The Bridge code has since been fixed to correct this.
•An incorrect error message could be displayed when re-scheduling a payment plan that was no longer included in the Master Cover. This has been corrected.
•A server error could occur when uploading an attachment. This was caused by an error with the code that analyzed the file’s size. It often overestimated the file size and then prevented it from being attached. This part of the code has been corrected.
•A server error could occur when printing a document. This would occur for documents that referenced top-level fields from within a grid. An internal prefix required by the system parser was missing from these fields. This has been corrected.
•The NewGrid function would not clear a target grid when combining fields from multiple grids and using a Where clause. This has been corrected.
•When the Billing module was enabled, importing a policy without billing information would cause an import error. This has been corrected to make the billing information optional.
•Multi-currency workflows could experience a server error when calculating a quote or viewing the Quote Summary screen. This was due to a flaw in the code that could not adequately handle certain currency symbols and formatting rules. This has been corrected.
•A server error could occur when indexed fields were displayed in the Claims Search list, but a user did not have the necessary roles to view that information. This has been corrected to display the proper information.
•In some cases, triggers were no longer working in the Claims module. This was affecting features such as field behavior overrides, adjuster auto-assignment, documents, and e-mails. This has been corrected.
•Unexpected validations could occur after importing a document template, stating that certain codes are already in use. This was occurring because the system was not creating unique internal codes for each new template. The system code has been updated to ensure that new internal codes are created.
•Once the Billing and Claims modules had been enabled for a site, they would not disappear when disabled. This has been corrected.
•When assigning claims adjusters, calculated fields referencing the adjuster would not be updated immediately. This has been corrected. Reported issues for this bug include automatic emails sent on adjuster assignment having the incorrect adjuster information.
•A server error could occur when trying to open a product from the Product List panel on the Products page. This occurred for products created in the Product Model section. Products created in the Product Model section do not require a Product Group specified. Since this field is required when opening a product from the Product List on the Products page, the error would occur. The Product Management page has been updated to handle opening products that do not have any Product Group specified.