Fixed Issues for Version 22.1.0.2 Server Patch 2 (Banker Edition)
This section describes the issues that have been fixed in this release.
Why we fixed this issue: This issue was fixed to improve usability and to help ensure Encompass is operating as expected. This issue was chosen to be fixed based on the severity of its impact to clients and client feedback.
Updates to the Encompass Client Machines
The Encompass 22.1 Critical Patch 2 release includes the following items, which are client-side updates that are applied to users' Encompass client machines (22.1.0.2). This client update can be controlled manually via the Encompass Version Manager tool. If the tool has been configured to always apply new releases to users’ computers automatically, users will receive this update upon their initial log in of Encompass following the release.
An issue was resolved that affected the Green Check Mark, Blue Flag, or Red Flag icons that display for the Price Limit indicator (field ID QM.X384) in the General Qualified Mortgage column on the ATR/QM Eligibility tab on the ATR/QM Management input form.
This issue occurred because the logic for populate the Price Limit indicator icon was not updated when the other calculations in Encompass were adjusted for the 2022 thresholds. This resulted in an incorrect icon displaying for some loans that fell in a range between the 2021 and 2022 thresholds. This issue has been resolved and the following logic is now being used to populate the icons:
-
To determine the Consummation Date:
-
The Document Signing Date (field ID 1887) is used if it has a value.
-
If the Document Signing Date is blank, the Closing Date (field ID 748) is used.
-
If the Closing Date is blank, the Estimated Closing Date (field ID Field 763) is used.
-
-
If the Consummation Date is on or after 1/1/2022, then 2022 thresholds are used, otherwise apply 2021 thresholds are used.
If you are utilizing the Encompass SDK, upgrading to the new SDK package for 22.1.0.2 Server Patch 2 is required to receive this update.
Some Encompass SDK users experienced issues with launching the new SDK provided for Encompass 22.1. The cause of this issue was related to the System.Runtime.CompilerServices.Unsafe DLL and it has been addressed. Upgrade to the new SDK package provided with this 22.1.0.2 Server Patch 2 release (after upgrading to Encompass 22.1.0.2 Server Patch 2) to start utilizing the SDK application.
An issue occurred where if an existing loan with one or more confirmed lock snapshot (LOCKRATE.CONFIRMATIONCOUNT virtual field greater than “0”) was updated, and then that loan was saved, the LOCKRATE.CONFIRMATIONCOUNT was reset to “0”. This issue has been resolved and the LOCKRATE.CONFIRMATIONCOUNT is no longer reset to “0” when a change is made to a loan with one or more confirmed lock snapshots and then saved.
Update to the Encompass Server (i.e., Server Patch 2)
Below are updates in the Server Patch (server patch 2) that are applied to the Encompass Server. The Server Patch contains the relevant Encompass code that applies to the following fixed issues. The Server Patch included with this release will be applied to the Encompass Server automatically and cannot be controlled manually via the Encompass Version Manager tool.
An issue was introduced in Encompass 22.1 where an Application Error was triggered when administrators attempted to edit a condition form. After navigating, to Encompass Settings > Loan Setup > Condition Forms and opening a form, the following Application Error was triggered when clicking the New icon to select a Starting Page or Ending Page.
This issue has been resolved and this error message is no longer triggered when working with condition forms and the starting/ending pages options.
NICE-40517
Next Section: Change Log | ||
Previous Section: New Features & Forms |