•Drop Down control types are now supported for use with the Editable in Grid feature.
•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.
•Placeholders in the Policy module that referenced certain data from the Billing module were not being populated. This was caused by a limitation that only allowed such placeholders to return numerical values. The placeholders have been enhanced, and can now return all data types.
•A server error could occur when trying to publish an imported workflow. This would occur when the system did not successfully match fields to their codes during import, producing Null values. This has been corrected to identify and correct missing information during import.
•When viewing the list of claims e-mail configurations, the Recipients column was displaying internal codes instead of recipient names. This was due to the system reading the data from the wrong internal resource. This has been corrected, and the recipients are now displayed correctly.
•When confirming a cancellation transaction, a server error could occur. This was due to the fact that the text supplied for the Cancellation Reason exceeded five-hundred characters. To correct this problem, the system will now accommodate the maximum number of characters that can be stored within two gigabytes of memory.
•When viewing a claim, the screen resolution or a significant amount of content in the widgets could cause one or more widgets to extend off the bottom of the screen. When this occurred, there would be no scrollbar to allow access to the hidden areas of the widgets. The scrollbar has been enabled.
•The validation that would warn users that they were trying to save an older version of the submission would not occur when necessary. A recent update of the code disabled this validation. The code has been further updated to ensure that it will occur when necessary.
•A system error could occur when a transaction entered quoted status following an accepted compliance referral. This would occur due to the system performing a calculation on an outdated version of the data. The system now uses the correct version.
•When importing a product, the process would sometimes abort with a system error. This can occur whenever the product file being imported has identifiers containing upper-case characters. The system will now ensure that all product files contain identifiers that use only lower-case characters.
•A validation error would occur when publishing a workflow, referring to fields missing from shared workflows. This would occur if the formula in a calculated field referenced a field code without exactly matching the case of the code. This has been corrected to ignore case when referencing field codes.
•When trying to upload a data file to a Domain / Rate Table configuration, an error would appear about the "type initializer" throwing an exception. This was caused by an incorrect setting in the internal component used to import the file. This setting has been corrected.
•When adding claim payments, clicking Add & New or Save & New then clicking Close would close the window but not refresh the payments list until the entire page was refreshed. This was due to the Close button not being set to refresh the page. This has been corrected so that the Close button will now refresh the page.
•An error would occur on Calculate Quote due to a related OFAC Compliance Scan integration service call failing. This occurred because Bridge received a code update that made it incompatible with the Compliance Scan service. A further update to the code has been made to ensure that Bridge and the service are compatible.
•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.
•When printing documents, the currency information would sometimes be missing and replaced with: “()”. This would occur when the system mistakenly overwrote the existing values. The system has been corrected so that the currency data will not be overwritten.
•Some calculated fields would sometimes display quote option values without a quote option having been selected. This occurred due to system operations that would prematurely populate these fields. The system will now populate these fields only after a quote option has been selected.
•When using the SaveToField() function within a grid, data would be saved to the first row instead of the current row. This was due to the system incorrectly tracking the rows. This has been corrected, and the function will now save to the same row where the function is being calculated.
•A server error would occur in a Data Source Configuration when saving a Filter set to a Constant Value. This was introduced by a recent enhancement that mistakenly inserted a 0 for the unused Field selection in the filter. This has been corrected to save the Field selection as null when no field is selected.
•When creating or modifying a document template, the Document Template List would not update. This was due to an error in the code that would prevent the list from displaying the change. The code has since been fixed to ensure that any newly created or modified document templates get displayed.
•When trying to reset a password, the expected password-reset email would not be delivered. This occurred because a recent Bridge update temporarily disabled this feature. The code has since been updated to ensure that the email is delivered.
•A server error would occur when creating a new FNOL in certain environments. This was caused by an old system file interfering with the application. This file has been removed.