Fixed Issues for Version 19.3.0.5
This Encompass 19.3 September Service Pack Critical Patch 1 includes updates to users' Encompass client machines (19.3.0.5).
Why we fixed these issues: These issues were fixed to improve usability and to help ensure Encompass is operating as expected. These issues were chosen to be fixed based on the severity of its impact to clients and client feedback.
Updates to the Encompass Client Machines
The Encompass 19.3 September Service Pack Critical Patch 1 includes the following items, which are client-side update that are applied to users' Encompass client machines. 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.
Fixed Issues
High Encompass Memory Issue Resolved
An issue with high Encompass memory usage has been resolved. Memory usage gradually increased as users navigated from the Borrower Summary - Origination input form to the 1003 Page 3 input form to the 2015 Itemization input form. As this workflow was repeated, the memory usage continued to increase until a system error was triggered and users were required to exit Encompass. This cause of this "memory leak" was identified and the relevant code has been updated to prevent this issue from recurring. The reduction of this memory leak also results in improved Encompass system performance.
Secondary Registration/Snapshot List Now Updates Correctly After Loan is Saved
An issue occurred where rate lock entries in the Secondary Registration/Snapshot List were being erroneously cleared. If a lock request was confirmed for a new request, extension, or relock, and then the loan was saved, the lock snapshot in Secondary Registration was cleared for a new lock or the Lock Expiration Date. The Fulfilled On, Fulfilled By, Investor, etc. columns were cleared for lock extensions or relocks. This only occurred if any new fields were added to the Key Pricing Alert Field Triggers. This issue has been resolved and the Secondary Registration/Snapshot List is now updated correctly.
