Fixed Issues for Version 24.1.0.3 Server Patch 3 (Banker Edition)
This section describes the updates provided 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.
Update to the Encompass Server (i.e., Server Patch 3)
The Encompass 24.1 Critical Patch 3 release includes the following update, which is applied to the Encompass Server only (server patch 3). The Server Patch included with this release is applied to the Encompass Server automatically and cannot be controlled manually via the Encompass Version Manager tool.
When attempting to move a loan file from one folder to another folder, the following error message was triggered if the destination folder's name included an apostrophe (for example, Robert's Files):
The loan [borrower last name, borrower first name (loan number)] could not be moved for the following reason: Loan has been moved back due to failed Loan Identity update.
This issue has been resolved. Loans can now be moved successfully to loan folders that use an apostrophe in their folder names.
Update to the Encompass Server (i.e., Server Patch 3) and Client Machines (24.1.0.3)
The Encompass 24.1 Critical Patch 3 release includes the following update. In order for this update to be fully integrated into your Encompass system, both the Server Patch and the client-side update provided with this release must be applied. The Server Patch included with this release is applied to the Encompass Server automatically and cannot be controlled manually via the Encompass Version Manager tool. The client-side update in this release can be controlled manually via the Encompass Version Manager tool. If the tool has been configured to always apply client-side updates to users’ computers automatically, users will receive the client-side updates upon their initial login of Encompass following the release.
Again, the item listed below will not be fully implemented until both the Server Patch and the client-side updates are applied to your Encompass system.
An issue related to field descriptions occurred for some users with the Encompass Reporting Database in Encompass 24.1.
If a field (or fields) had been added to the Reporting Database in any version of Encompass prior to 24.1 with a field description that included the properties described below, users would receive an error message when performing a loan save after upgrading to Encompass 24.1:
-
A # symbol, and then a space, and then an integer (for example, Document# 1)
OR
-
A parenthesis followed by a # symbol, then an integer, and then a string (for example,
Document(#1A))
This issue has been resolved and field descriptions like these no longer trigger error messages when loans are saved in Encompass 24.1.
Refer to knowledge article #000115434 for additional information.
Updates to the Encompass Client Machines
The Encompass 24.1 Critical Patch 3 release includes the following updates, which will be applied to users' Encompass client machines (24.1.0.3). 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.
When using Encompass eClose to order closing documents, some customers received the following error after selecting Approve for Signing during the closing workflow:
Plan code selection is required prior to proceeding with the document order. Please select the applicable plan code. Please contact your administrator for assistance.
This issue occurred in loans where a custom plan code was applied to the closing documents.
The cause of the issue was identified and this issue is now fixed. Customers using Encompass eClose to generate closing documents no longer receive this error message due to custom plan codes.
An issue was introduced in Encompass 24.1.0.2 Server Patch 2 that resulted in application errors being triggered when non-administrator users attempted to generate a report for TPO loans. After setting up a report in the Reports tool to capture data for TPO loans, and then clicking the Generate Report button to generate the report, an application error was triggered. This issue has been resolved and non-administrator users can now successfully generate a TPO loans report.
An issue occurred where, depending on the scenario, the Starting Adjust Price value in field ID NEWHUD.X1721 on the Bona Fide Discount Point Assessment popup window (accessed from the ATR/QM Management form) was converted from points (-1.49) to price (101.49).
-
When a lock request was submitted and then the loan data (including field ID NEWHUD.X1721) was copied to the lock request before it was locked and confirmed.
In the Encompass 24.1 release, issue SEC-24467 "NEWHUD.X1720 and NEWHUD.X1721 Fields No Longer Cleared When Loan Locked and Confirmed or Lock Extended" was resolved. As part of the resolution, field ID NEWHUD.X1720, field ID NEWHUD.X172, field ID 3873, and field ID 3875 were added to the Compare with Current Loan Data popup window.
-
When the Zero Based Par Pricing setting was enabled for a channel, a lock request was submitted for a loan in that channel, and then it was locked and confirmed.
This issue has been resolved. The format of the Starting Adjust Price value in field ID NEWHUD.X1721 is no longer converted from points to price when copied to the lock request and confirmed or when the setting is configured to receive the Starting Adjust Price in points.
There is a known issue in this release where if the Zero Based Par Pricing setting is enabled and the following APIs are called, field ID NEWHUD.X1721 will be displayed in price instead of points. (i.e., 101.49 vs. -1.49).
-
New Lock API
-
Lock and Confirm API
-
Revise Lock API
An issue with trades occurred where the following error message was triggered when users attempted to assign a loan to a trade:
The loan [loan number] could not be updated due to the following error: String was not recognized as a valid Boolean.
This issue, which prevented the loan from being assigned to the trade, has been resolved. The error message is no longer returned and loans can be assigned to trades as expected.
Previous Section: Introduction |