Fixed Issues for Version 21.3.0.1 Server Patch 1 (Banker Edition)
This section describes the issues that have been fixed in this release.
This Encompass 21.3 Critical Patch 1 release includes updates to users' Encompass client machines (21.3.0.1) and. an update to the Encompass Server (server patch 1).
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 1)
Below are updates in the Server Patch 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 occurred where the loan amount value in a loan was not being rounded when the user selected the Loan Amount Rounding checkbox (field ID 4745) in the loan if the Loan Amount Rounding policy in the Encompass Admin Tools was set to Disabled. This issue has been resolved so that the loan amount value is rounded as expected when the Loan Amount Rounding checkbox is selected.
For more information, refer to KA #40020 – Loan Amount Not Rounding when Field 4745 is Checked if Loan Rounding is Disabled by Default.
CBIZ-41769
In the Encompass Settings > eFolder Setup > Documents setting, administrators can create and manage loan documents, as well as the tracking information associated with the loan documents and services. An issue occurred where the following error message was triggered when administrators tried to delete one or more documents from the Documents list in this setting if more than 1000 documents were listed.
This issue has been resolved and documents can now be successfully deleted from the Documents list even if more than 1000 documents are listed.
NICE-38120
Currently, when the ICE Mortgage Technology Professional Services team migrates customers’ new loans into a new instance of Encompass, the tool they use copies the loan file (and its associated documents) on CIFS (Common Internet File System) from one instance to another. Once complete, they perform a rebuild of the customers’ Pipeline (using the Rebuild Pipeline tool in Encompass) to complete the migration.
However, an issue with loan migrations occurred for some customers when loan documents in one instance used a storage type that was different than the storage type used for the destination instance. Loans, along with document attachments and supporting documents, can be stored in CIFS or in cloud storage. During the Pipeline rebuild, the loan storage settings for the destination Encompass instance (which could be CIFS or cloud storage) are used to set the loan values for attachments and supporting documents without taking into account the loan storage settings that the loan used in the original instance. This resulted in loan attachments and supporting documents displaying as blank after the Pipeline rebuild was completed in the new instance if the loan storage settings were different between the two instances.
To resolve this issue, the Rebuild Pipeline tool now reviews where the document attachments are stored and uses that loan storage type in the destination instance. If there are no document attachments in a loan, then the storage settings used in the destination instance are used.
NICE-37585
Updates to the Encompass Client Machines
The Encompass 21.3 Critical Patch 1 release includes the following items, which are client-side updates 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.
If you are utilizing the Encompass SDK, upgrading to the new SDK package for 21.3.0.1 is required to receive this fix.
There was an issue reported where the MI Cutoff value was being calculated based on the Appraised Value when the Appraised Value was higher than the Purchase Price for a purchase transaction. The MI Cutoff LTV calculation has been corrected and now uses the following hierarchy for determining valuation for MI Cutoff (matching value used for calculation of LTV/CLTV/HCLTV):
-
Purchase transactions with appraisal: lower of Purchase Price or Appraised Value
-
Purchase transactions with no appraisal: lower of Purchase Price or Estimated Value
-
Purchase transactions with no appraisal and no estimated value: Purchase Price
As a result of these changes, the LTV calculations initially implemented in the Encompass 21.3 release and described in the Calculations for LTV Ratios Updated to Use Estimated Value If Appraisal Value Is Blank release notes entry
Workaround Description
The following workaround was provided for this production issue and is no longer required for Encompass 21.3.0.1 Server Patch 1 and later:
-
In the PMI section on the Loan Submission input form, manually edit the first entry for Months Per Adjustment (field ID 1198) to reflect the MI cut-off date in the Amortization Schedule.
-
Clear the following fields:
-
The second Months Per Adjustment field (field ID 1200)
-
The second Periodic Factors field (field ID 1201)
-
The Cancel at % field (field ID 1205)
CBIZ-42102
An issue occurred for some users utilizing APIs in Encompass from Encompass Developer Connect, where executing the GET users request returned an invalid (BOM) character in response. This issue has been resolved so that the GET users request now executes as expected.
EBSP-34683
Next Section: Change Log | ||
Previous Section: Introduction |