Fixed Issues for Version 19.1.0.3 Server Patch 3
This Encompass 19.1 Critical Patch 1 includes updates to users' Encompass client machines and a Server Patch (server patch 3) that is applied to the Encompass Server.
Why we fixed these issues: 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 Server (i.e., Server Patch 3)
These are the updates in the Server Patch that is 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.
Issue With Loading Encompass Plugins Resolved
When a user logs into Encompass there are plug-ins that are loaded as the system starts. Some users were receiving timeout errors related to these plug-ins that prevented them from logging in. Updates have been made to the system’s plug-in registration process to help ensure that this error no longer occurs when users are logging in.
Account Executive Role Can Now Be Changed in Encompass TPO Connect Loans in Environments Migrated from Encompass TPO WebCenter to Encompass TPO Connect
An issue occurred for Encompass clients who migrated from Encompass TPO WebCenter to Encompass TPO Connect. When a user manually assigned an Account Executive file contact to their Encompass TPO Connect loan, and then saved and closed the loan, Encompass reassigned the Sales Rep/AE assigned to the user profile of the TPO loan officer file contact assigned to the loan when the loan was reopened. This issue has been resolved and the loan now retains the manually assigned Account Executive.
Issue Resolved: SDK ‘Invalid Object Name ‘#loanFolders’’ Exception Error Triggered for LoanFolder.GetContents() Call
Certain Encompass SDK (Software Development Kit) users trying to execute the LoanFolder.GetContents() call received the following error:
Invalid object name '#loanFolders'
The cause of this error was identified and addressed. SDK users can now execute this call without encountering this error.
NICE-21777
Updates to the Encompass Client Machines
The Encompass 19.1 Critical Patch 1 includes the following item, which is a client-side update that is 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.
Rollback of a Fix For an eConsent Acceptance Issue
An issue occurs in Encompass when a loan has a borrower and co-borrower that share the same first and last names and there is a non-borrowing owner file contact (NBO) user associated with this borrower pair. Once all three people accept the eConsent Agreement, the eConsent Not Yet Received alert is still displayed in the Pipeline and Loan Log. When viewing the alert details, the eConsent Status for the co-borrower is not reflecting that they have accepted eConsent yet. The eConsent Status for the borrower and NBO is accurately reflecting that they have accepted eConsent.
A fix for this issue was introduced in Encompass 19.1. However, this fix had side effects that resulted in new issues. Therefore, this original fix has been rolled back and removed from this 19.1.0.3 release. An updated fix will be provided in a future Encompass release.
NICE-12267, NICE-21772
Issue Resolved: Encompass SDK Users Receiving Version Mismatch Exception Error When Trying to Commit Changes to Loan Files
An issue in the Encompass SDK occurred for some users where they could use the SDK to open a loan (Loan,Open method), make changes and commit the updated loan (Loan.commit), and then refresh the loan (Loan.refresh), but then they would receive an Exception error related to an Encompass version mismatch when they tried to commit the loan again (Loan.commit). This issue has been resolved.
