• When an advanced lookup that is activated by a combo box returns no results, a message will indicate so at the bottom of the combo box dropdown. This has been patched back to version 2.4.86.
• When a transaction has multiple Quote Versions, the most recently created version appears in the Submission/Policy List panel. Following this enhancement, once a quote version is Bound, that version will appear instead. This has been patched back to version 2.4.86.
• A server error could occur when saving changes made to a child tab workflow. This has been corrected and patched back to version 2.4.87.
• A server error would occur when trying to post a receipt batch that did not contain any receipts. A validation has been added to prevent posting of empty batches.
• When viewing the Account History for a Bill to Party, the list would initially only display data for the last month. Performing a search would display the appropriate results. This has been corrected to show the appropriate data when loading the Account History.
• The system would not renew all policies set to be automatically renewed. This has been corrected and patched back to version 2.4.87.
• Combo boxes with data source configurations whose Key Column Rule was set to Specify Alternate Key Column would cause a server error when the search was activated. This has been corrected and patched back to version 2.4.87.
• A server error would occur when clicking on Endorse, Adjust, Reinstate, Renew or Copy in the Actions widget for a bound transaction. This would occur in workflows containing checkboxes where Default was chosen to be the initial value for the control in the Field Initial Value Settings panel on the Field Management page. This has been corrected and patched back to versions 2.4.87 and 2.4.88.
• When automatic billing was disabled, some validations related to fields required for automatic billing would still occur. These have been corrected.
• A server error would occur when the system had to copy a transaction that contained a checkbox field whose initial value was set to Default in its Field Initial Value Settings panel and whose Apply Default field was set to None. This has been corrected and patched back to versions 2.4.87, 2.4.88 and 2.4.89.
• In some cases, clicking Next in a claims workflow would fail to activate validations and would not save changes to the screen. This would occur when a validation should have triggered, but failed. This has been corrected and patched back to version 2.4.87.
• A server error would occur when exporting a workflow while the Include All Universal Triggers checkbox was not checked. This has been corrected.
• The page numbers for generated documents would reset at various intervals. This has been corrected and patched back to versions 2.4.85, 2.4.86, and 2.4.87.
• The LookupDataSource function was case-sensitive, and would not work if the case did not match exactly. This has been corrected so that case does not affect the functionality. This has been patched back to versions 2.4.86, 2.4.87, 2.4.88, and 2.4.89.
• The Driver Field in the Rate Rule window would sometimes not show any fields. This was most likely to happen in workflows containing a large number of fields. This has been corrected and patched back to version 2.4.86.
• The Screen Button Bar would sometimes unnecessarily display extra rows below its buttons. This would typically occur after resizing the screen or collapsing a widget when the Screen Button Bar initially needed more than one row to display all of the buttons. This has been corrected and patched back to version 2.4.89.
• A server error would occur when trying to access the Earnings report when no earnings had ever previously been posted. This has been corrected.
• Fields configured to become populated following the activation of an Integration Configuration would not be populated. This occurred when Shared Workflows would be used and where one of the shared workflows contained a field that used an Option List. This has been corrected and patched back to version 2.4.83.
• Correlated option lists in tab workflows would be empty when configured to auto-populate according to the default selection of their parent list. Changing the selected item in the parent and then reselecting the default item would cause the child list to populate correctly. This has been corrected and patched back to version 2.4.87.
• When using a screen behavior override in a Claims workflow, the trigger in the override configuration would not be evaluated properly. This has been corrected and patched back to version 2.4.88.
• Some data would not be saved when reallocating a receipt. This has been corrected.
• Multi-select control types, such as Checkbox Group, Include Exclude List, and Multi Select, in tab workflows would not save their values. This has been corrected and patched back to versions 2.4.87, 2.4.88 and 2.4.89.
• Cancellations in Quoted status would be confirmed before their cancellation Effective Date. This would occur for cancellations belonging to master covers that used the features in the Automatic Cancellation Finalization panel, where the Enable Automatic Cancellation Finalization checkbox was checked, and the Trigger evaluated to true. This has been corrected and patched back to versions 2.4.86 and 2.4.89.