•When a user clicks on the up or down arrows of a grid’s detail window or tab workflow, the system will now automatically save any unsaved changes before navigating to the next record. Note that this only applies to grids in workflows, and not those found on configuration pages. Saving changes to a submission could disable certain actions until a new quote is calculated.
•The Full Publish button has been removed from the Workflow Management page.
•The [[ReferralRejectionReason]] placeholder has been created, allowing the Reject Reason to be used in generated documents, e-mails, and calculated fields. The Reject Reason may be provided when declining transactions in Referred status (including compliance referrals), Special Quote Requested status, and Bind Requested status. For details on placeholders, see the Placeholders section.
•A server error could occur when clicking on Endorse, Adjustment, Renew or Copy while viewing a Bound transaction. The error would occur in workflows containing a Correlated field where the parent field appeared in two or more panels. This has been corrected.
•A server error could occur when clicking on Issue Quote while viewing a transaction in Referred status. The error would occur if the transaction belonged to a Master Cover whose Allow Quote Versions checkbox was checked. This has been corrected.
•A server error could occur when clicking on the E-mails link in the Common Screens widget. The error would occur if the e-mail history contained e-mails belonging to inactive E-mail Templates. This has been corrected and patched back to version 2.4.87.
•A server error could occur when clicking on any link in the Policy Information widget while viewing a transaction belonging to a product that was imported. This has been corrected and patched back to versions 2.4.87, 2.4.88, 2.4.89 and 2.4.90.
•Following a product import, an incorrect province or state would appear for certain clients in the Client Information widget and the State/Province column in the Client List panel. This has been corrected and patched back to versions 2.4.87, 2.4.88, 2.4.89 and 2.4.90.
•Saving a claim payment would produce an error message when the payment amount and the associated general ledger account had different currency types. The claim payment window will now only allow the selection of general ledger accounts that match the selected currency.
•Actions in the workflow that were dependent on large formulas would sometimes fail to occur. An example of such an action would be the populating of a grid following the system’s evaluation of a formula. This would occur whenever the system needed more than ten seconds to evaluate the formula. Prior to this fix, the system would abandon the formula evaluation after ten seconds, causing any subsequent actions that needed the results of the evaluation to fail. To correct this problem, the system has been enhanced to evaluate formulas much more quickly, and the ten second limit has been increased to one minute. This has been patched back to versions 2.4.86 and 2.4.87.
•A validation error related to invalid currency codes would occur during the activation of Integration Configurations. This has been corrected and patched back to versions 2.4.87, 2.4.88, 2.4.89 and 2.4.90.
•Calculated field formulas would produce incorrect results when the web browser language was not set to English. This has been corrected and patched back to versions 2.4.86 and 2.4.87.
•Premium Adjustments made in a transaction would not be considered for other rate calculations applied to the same Premium Type. This has been corrected and patched back to versions 2.4.86, 2.4.87, 2.4.88, 2.4.89 and 2.4.90.
•Data Validations would activate at incorrect times when using a browser whose language was not set to English. The validations were associated to Textbox (Decimal) fields where periods were used as the thousands separator, and commas were used as the decimal separator. This has been corrected and patched back to versions 2.4.86, 2.4.87 and 2.4.90.
•A server error would occur when exporting a product. This has been corrected and patched back to versions 2.4.86, 2.4.87 and 2.4.90.
•A server error would occur when attempting to Bind a policy where the payment plan was automatically selected by the system. This has been corrected and patched back to versions 2.4.86 and 2.4.90.
•A server error would occur when saving changes made to a child grid that uses Tabs as its Management Style. This has been corrected and patched back to version 2.4.89.
•When a product is configured to start a new submission with the New Client Company screen, the new client screen should open as a full page. However, if a user navigated to the Select or Create Client page, then tried to return to the New Client Company screen, the client screen would open in a detail window instead of a full page. This has been corrected and patched back to version 2.4.90.
•When a quote would be calculated, the premium would be incorrect when the web browser language was not set to English. This has been corrected and patched back to versions 2.4.86, 2.4.87 and 2.4.90.
•The LookupDataSource function could fail and prevent any subsequent functions in the same formula from activating. This would occur when the LookupDataSource function activated a Data Source Configuration that used a Data Table and where no results were found. This has been corrected and patched back to versions 2.4.86, 2.4.87, 2.4.88, 2.4.89 and 2.4.90.