•An Outlook File column has been added to the E-mails List window. It is hidden by default and is part of an enhancement that will allow users to import e-mails from Microsoft Outlook into Bridge. This feature is not yet finished and is not currently intended for use.
•The Claims module now supports the use of the SaveToGrid, NewGrid and ClearGrid functions.
•The following currencies have been added to the system’s currency list:
o Angola Kwanza (AOA)
o Azerbaijan New Manat (AZN)
o Belarusian Ruble (BYN)
o CFP Franc (XPF)
o Nicaraguan Cordoba (NIO)
o Rwandan Franc (RWF)
o Serbian Dinar (RSD)
o Ugandan Shilling (UGX)
o Yemeni Rial (YER)
This has been patched back to version 2.4.75.
•View Grids can now be created for grids whose Management Style is Tabs. This has been patched back to version 2.4.83.
•Removing a field containing a default commission override value and then publishing its workflow would not trigger the necessary publish validation. The system was not verifying if these fields were in the workflow during publishing. To correct this, the system will now be checking for them every time a workflow is published.
•A server error could occur when trying to import a workflow that was just exported from another environment. This occurred when the serialization process used by the exporting environment was not compatible with the deserialization process used by the importing environment. Both processes have been refined to ensure that they are fully compatible. This has been patched back to version 2.4.85.
•A server error could occur when trying to import a product. This was due to a recent enhancement that caused the system country list, currency list, state list and some option lists to become inaccessible to the code that handles the import process. This was largely because of how the lists were formatted when stored in the database. This has been corrected so that the formatting is fully compatible with the import process. This has been patched back to versions 2.4.84 and 2.4.85.
•A server error could occur when trying to publish a workflow for a product that was just imported. This was due to a problem with the system’s parsing of the triggers belonging to the imported product. This has been corrected.
•A server error could occur when trying to publish a workflow containing a field whose control type was changed from Textbox to Textbox (Integer). This would occur for workflows that were recently imported. The import process was not creating references to certain field properties that were needed by the system when publishing. This has been corrected.
•When creating a document template, certain products were not available in the Product field. The process for retrieving the product list was only configured to service a single default user account. This has been corrected so that the appropriate product list will be returned for each authenticated user.
•An error could occur when trying publish an imported workflow. This would occur for workflows that were exported with shared workflow settings enabled. The system was incorrectly associating triggers and workflows in the export file, and these associations were then being imported into the new environment. This has been corrected. This has been patched back to version 2.4.83.
•Data source configurations whose Data Source Type was set to Grid would not be preserved when imported with a workflow. This occurred because the import process was not correctly handling the primary display columns belonging to the configurations. This has been corrected.
•When the Replace function was used with all three parameters, but the text to be replaced was not found, the function would replace the default separators instead (| and +). This has been corrected so that when the text to be replaced cannot be found, no replacement will occur.
•A server error could occur when trying to publish a workflow. This would happen when the system was trying to publish a screen that did not contain any panels. To correct this, a publish validation has been created to prevent publishing screens that do not contain any panels.
•A system error could occur when importing a product that was just exported. The import process was creating duplicate system identifiers for the product elements. This has been corrected. This has been patched back to versions 2.4.83, 2.4.84, and 2.4.85.
•Automatically generated documents would sometimes not be attached to automatic e-mails. The system was not creating an important document identifier that was required to attach each document to its e-mail. This has been corrected. This has been patched back to versions 2.4.83, 2.4.84, and 2.4.85.
•Effective dates for New Business transactions configured to be populated by custom fields would sometimes be incorrectly replaced by the submission’s creation date. This occurred because rules meant for Endorsements, Declarations and Adjustments were being erroneously applied to New Business transactions. This has been corrected.
•When using the NewGrid and SaveToGrid functions in sequence, with the same target grid, conflicting internal settings could prevent rows from being saved properly. This has been corrected.
•A server error could occur when the system tried to retrieve field information when evaluating a trigger. This occurred for transactions that were created or updated concurrently with other transactions using the same workflow. These transactions were sharing system information that wasn’t configured to handle more than one transaction simultaneously. As a result, incorrect trigger information was assigned, causing the error. This has been corrected so that the system information can be shared concurrently between transactions. This has been patched back to versions 2.4.83, 2.4.84, and 2.4.85.
•The read-only property of grid rows would sometimes not behave as configured. This occurred for grids containing calculated fields that made multiple calls to the SaveToGrid function. An optimization for the system code in charge of saving grid data was not properly handling these chained function calls. As a result, incorrect data was computed and then passed to triggers that would determine if grid cells would be editable or not. This has been corrected.
•Field evaluation rules configured for when a submission is created would sometimes not work. This was due to a recent code change that caused the system to skip the evaluation of these rules. This has been corrected.
•An internal error could occur when integrating charges between the Policy and Billing modules. This was caused by missing information in the policy details. Validations have been added to ensure the data is saved properly with the policy.
•When the Billing module was not enabled, some Billing information would still be saved and could interfere with other data. This has been corrected.
•A server error could occur on publishing a policy workflow after importing it into the system. This was caused by a missing script that was part of a previous enhancement. This has been corrected.