•An Adjuster Assignment option has been added to the Action list for custom workflow events. This allows features such as automatic e-mails to be activated when an adjuster is assigned or re-assigned to a claim, either automatically or manually.
Note that this action occurs each time an adjuster is assigned, even if it is the same adjuster being re-assigned to the same claim. The triggers and other conditions should be carefully configured to avoid unnecessary repetition of events.
In order to avoid loops, custom workflow events based on adjuster assignment cannot be used for adjuster auto-assignment rules.
•The Claims SmartView dashboard has been updated so that any claims that do not have an adjuster assigned will show "Unspecified" in the Adjuster Name column of the Claims Ageing tile.
•A system error could occur when performing a lookup using the Commercial Lines Manual - Foot Note Lookup service. This would occur due to special characters in part of the response. This has been corrected to remove those special characters.
•A Responsive Disclosure configuration would fail to hide fields in a double-column layout if that layout included a Combo-Box field. This was caused by a difference in how the data was arranged between single-column and double-column layouts.
This has been corrected so that responsive disclosure now works properly for double-column layouts with combo-box fields. The exception is when the combo-box is read-only, which still causes this error. This will be corrected in a future release.
•When using Country/State correlated lists, the state could change on saving. This was caused by multiple states having the same code, and the system selected the first state with the appropriate code. This has been corrected so that the country is now properly evaluated to determine the correct state.
•Two validation errors would appear when trying to save and post receipts where the invoice total was less than the on-account amount. This occurred due to the system incorrectly validating the on account balance. The validation is now correct.
•Fields in double-column layouts were not receiving output values from combo-box fields. This has been corrected.
•A server error would occur when searching for charges in the Scheduled Payment page. This was due to missing payment plan details in old transactions. The system now correctly handles the payment that do not have a payment plan.
•A server error could occur when saving changes to a claim party. This was caused by an internal ID being saved incorrectly. This has been corrected.
•A system error would occur when creating an Adjustment transaction from a Reinstatement transaction. This was caused by the accepted quote option not being identified within the Cancellation or Reinstatement transactions. The system will now use the quote option from the last bound transaction in the term. Existing transactions will also be updated with the necessary information.
•Policy Parties attached to a claim were being deactivated when changes were saved through the Policy Information widget. This was due to the hidden Active checkbox being cleared on save. The checkbox is now ignored.
•Four internal placeholders, TransactionPremium, TermPremium, GridTransactionPremium, and GridTermPremium are no longer functional, and have been removed from the system.
•When using the SaveToField() function in a grid, it would only evaluate properly for the first row. This was caused by the row counter not returning the row number correctly, reverting to the first row. The row counter has been corrected.
•When the Initial Value On... settings were set to copy a value from a field, they were not performing the copy. This has been corrected and the settings now work properly.
•Custom translations for the Total Term Premium and Total Transaction Premium placeholders were no longer being applied. This occurred when the internal codes for the placeholders were modified, and no longer matched the value in the language file. The internal codes have been corrected, and the translations are now being applied properly.