•The Integration Configurations panel now contains a Code column and a Description column. They display each configuration’s code and description, respectively.
•When creating an integration configuration, the integration’s Code can now be entered by the user. If no code is provided, the system generates one when the configuration is saved. When the save process is complete, this field becomes read-only.
•The Calculated On and Time to Calculate Quote fields have been removed from the Quote Report Header panel. The Rates panel has also been removed from the Quote Report.
•Two currencies belonging to the system currency list have had their currency codes updated:
o The Venezuelan Bolivar currency code is now VEF. The old currency code was VEB.
o The Zambian Kwacha currency code is now ZMW. The old currency code was ZMK.
•A server error could occur when trying to cancel a policy that had been reinstated. This has been corrected.
•A server error could occur when calculating a quote. This occurred due to a problem with how calculation trace information was being stored in the database. This has been corrected.
•The default values of checkboxes in grid rows would not be applied after copying the row or the entire transaction. Previously, the system was evaluating default values using a case-sensitive method. Default values with certain combinations of upper and lower case letters would be improperly assessed, which prevented them from being applied correctly when the transaction was copied. This has been corrected via the implementation of a case-insensitive method of assessing the default values.
•A server error could occur when the system would send an e-mail based on an automatic e-mail configuration that used a trigger. This would happen when the system contained another trigger with the same name that was inactive. The system was erroneously selecting the inactive trigger for use with the e-mail, which caused the error. This has been corrected. This has been patched back to versions 2.4.83 and 2.4.85.
•The result of grid field evaluations would sometimes be incorrect. This also caused dependent workflow elements such as reports and transaction statuses to display incorrect information. This occurred due to a problem with how the system was using internal memory to perform the evaluations. This has been corrected. This has been patched back to version 2.4.83.
•Field override behaviors would sometimes not activate following a page refresh. This was due to a problem with how the system was managing field properties when refreshing the page. This has been corrected. This has been patched back to version 2.4.85.
•A server error could occur when importing a claim containing payment information. This has been corrected.
•A server error could occur when trying to reverse a receipt. This would occur when the post would fail due to validations, but the system was still trying to generate and post billing adjustments. This has been corrected to not generate adjustments if the post is not successful.
•The Add button disappeared from the Invoice Allocations panel in the batch receipts section. This has been corrected.
•When using the SaveToGrid function to copy a grid, the error log would sometimes display a message similar to “Merge calculated fields for Grid- unable to merge row, - no key is associated”. This is an internal tracking message, and does not indicate an actual error. These messages are no longer displayed in the error log.
•A server error could occur when creating a new submission while event tracking was disabled. This was due to incorrect settings in the system code that handles event tracking. This has been corrected.
•A system error would occur when changing the sequence number of a template in a claims document configuration. This has been corrected.
•A server error could occur when performing the Calculate Quote action from a tab workflow. This was due to a problem with the system code which was creating duplicate identifiers for option list items. This has been corrected.
•When importing a product, the system would sometimes create duplicate codes for data source configurations. This was due to a problem with the import process, which has been corrected. This has been patched back to version 2.4.84.
•When pressing the tab button to remove the cursor from a numeric field, the field value would revert to its default value. An internal field property that is managed by the source code was using an improper value, and has been corrected.
•When using the DateTimeShort function, the system would return the correct date but erroneously display 12 AM as the time. This occurred because the system was defaulting the time-portion to 12 AM. This has been corrected.
•The values in certain workflow fields would be lost following an integration with another system. This was because the web service handling this process was using an incorrect file-path to retrieve a needed internal file. Since it could not find the file, it caused default values to appear in the workflow fields. This has been corrected.
•The web service to import claim payments could fail when then amount was missing. This issues was introduced by a previous fix that incorrectly assumed the amount would always be provided. This has been corrected. This has been patched back to versions 2.4.83 and 2.4.86.
•An error could occur where optional Policy Decisions forms would be selected in Bridge, but would not be selected in Policy Decisions. This was caused by an internal configuration error, and has been corrected.
•When accessing the Audit Trail for a claim, a system error could appear with a message similar to "Value cannot be null". This was caused by an error in a recent update that did not properly check for null data. This has been corrected. This has been patched back to version 2.4.86.
•A server error could occur when attempting to log into the system. This was due to a faulty database query that would launch during the login process, which has been corrected. This has been patched back to versions 2.4.81, 2.4.83 and 2.4.85.
•Advanced lookups in the Claims module would sometimes not return any results. This was due to a recent enhancement that erroneously affected the module. This has been corrected. This has been patched back to version 2.4.86.
•An error could occur when publishing a workflow containing the LookupDataSource function. This occurred when the function referenced a data source configuration that used a field whose Calculated Field Formula field was empty. This has been corrected and has been patched back to version 2.4.86.
•The following items would sometimes not appear on screen when they should have:
o The message that confirms when a workflow has been published successfully.
o The message that lists missing required settings when setting a master cover to live mode.
o Error messages relating to the Effective Date and Valid Until Date.
This occurred because the internal components that display these items had to be updated to a newer version. This update has been completed.
•When importing document templates using the Import Document Templates feature, re-importing existing templates with new or modified placeholders would cause those placeholders to not be populated on generating the documents. This was caused by the system not detecting the changes. This has been corrected. This has been patched back to version 2.4.83.
•A server error could occur when generating a document. This would occur when the document template contained two or more tables referencing the same workflow grid, but at least one table also referenced a top-level field. This has been corrected.
•In some cases, optional forms in a Policy Decisions workflow could not be selected. This was caused by missing default values in the configurations. This has been corrected.
•The panel that displays validation errors and warnings would sometimes not be visible. This was the due to a recent enhancement to support Internet Explorer 11. This has been corrected.