Fixed Issues for Version 22.1 (Banker Edition)
This section describes the issues that have been fixed in this release.
Why we fixed these issues: These issues were fixed to improve usability and to help ensure Encompass is operating as expected. The issues that are chosen to be fixed are based on the severity of their impact to clients and client feedback.
Encompass Forms and Tools
An issue was resolved that resulted in a discrepancy between the General Qualified Mortgage Safe Harbor Eligibility results in Encompass and the results return by the Encompass Compliance Service (ECS) for some ARM transactions. This issue resulted in some loans being flagged as a Higher-Priced Covered Transaction in ECS and in Encompass on the higher-priced covered transaction checkbox (field ID QM.X382) on the Qualification tab on the ATR/QM Management input form as shown below.
However, on the ATR/QM Eligibility tab, the flag for General Qualified Mortgage Safe Harbor Eligibility ATR/QM Management form would show that the loan met the ATR/QM standard for safe harbor eligibility.
The calculation used by Encompass to indicate Safe Harbor Eligibility has been updated and the Safe Harbor Eligibility flag now matches the results returned from the Encompass Compliance Service.
CBIZ-41044
An issue was resolved with mortgage or HELOC Verification of Liability (VOL) records that were added to a loan file and marked as Will be paid off. If the VOL was then attached to the Verification of Mortgage (VOM) for the subject property, the payoff amount was populated in the Existing Liens to be Paid Off (field ID 26) but was not cleared from the Credit Cards and Other Debts Paid Off (field ID URLA.X145). This causes the payoff amount to be included twice in the Total Due from Borrower (fields ID 1073) and Cash to Borrower (field ID 142).
Workaround Description:
The following workaround was provided for this production issue and is no longer required for Encompass 22.1 and later.
-
Open the Verification of Liabilities record
-
Clear the Will be Paid off checkbox, and then select it again.
CBIZ-39773
Calculation updates have been made to ensure that the Present Housing expense fields are now populating correctly for HELOC loans when the Investment checkbox (field ID 1811) is selected in the Property Will Be section on input forms such as the Borrower Summary – Origination, 1003 URLA Part 4, 1003 URLA – Lender, and RegZ-LE.
For a HELOC loan that is not for a primary residence, the following logic is now used to populate values for the First Mtg. P & I (field ID 1724) and Second Mtg. P&I (field ID 1725) on input forms such as the ATR/QM Management, HELOC Management, and Transmittal Summary:
-
The First Mtg. P & I (field ID 1724) is now populated with the value from the present housing expenses First Mtg. payment (field ID 120).
-
The Second Mtg. P&I (field ID 1725) is now populated with the value from the present housing expenses Other Fin. payment (Field ID 121).
This logic update applies to loans using either the 2020 or 2009 versions of the URLA forms.
CBIZ-25545
A None option has been added to the Flood Zone dropdown list (field ID 541).
CBIZ-42157
For loans using the new URLA forms, an issue was resolved that caused the Total Military Entitlements amount on the Calculate Military Entitlements pop-up window to not update when a loan with military entitlements was imported into Encompass or when the Encompass SDK was used to populate fields on the window. The Calculate Military Entitlements pop-up window is accessed by clicking the Edit icon next to the Military Entitlements field for the borrower or co-borrower on the 1003 URLA Part 2 input form. This issue has been resolved and a recalculation of the total amount is now triggered on the pop-up window under the scenarios described above.
CBIZ-39417
When importing a borrower from another loan file using the Manage Borrower icon at the top of the loan, the Date Hired (field ID BE0151) is now importing correctly into the Verification of Employment input form for the borrower.
CBIZ-39660
(Added on 3/4/2022)
An issue occurred where the Job Title field was not populated in the File Contacts tool for external users. If an external user’s profile included a Title, and then that user was assigned to a Milestone Free Role in the File Contacts tool, the external user’s profile data except Title was populated into the Milestone Free Role fields. This issue has been resolved and all the external user’s profile data, including Title, now populates the Milestone Free Role section.
(Added on 3/4/2022)
An issue occurred where an error message “A Future ONRP Lock Date and Time are not acceptable for Get ONRP Pricing feature.” was displayed when after 1:00 pm the Get ONRP Pricing button was selected on the Lock Request Form, and then a time between 12:00 pm and 12:59 pm was selected for the current date in the Get ONRP Pricing pop up window. This issue has been resolved and the error message is no longer generated when a time in the past is selected.
(Added on 3/4/2022)
An issue occurred where a Lock Confirmation email was generated when the Save button was selected (displayed after the Update Sell/Comparison button is selected) on the Secondary Lock Tool. This issue has been resolved and the following changes have been made to the behavior of the Save button.
For additional information on the Save button, see SEC-20229 in the Encompass 21.3 release notes.
-
A Lock Confirmation log will no longer be created.
-
A new Lock Request log will be created. The Buy Side fields will be copied from the existing Lock Request log.
-
A new snapshot will be created.
-
No CalcAll for the Update Sell/Comparison button will be triggered.
-
No Log entry will be created.
File Imports
An issue was resolved that caused the military pay amount to import incorrectly from a MISMO 3.4 files in the following scenarios:
-
A loan included a borrower with pay for multiple military jobs.
-
A loan included a borrower and a co-borrower, each of whom had pay for a military job.
In these scenarios, when a MISMO 3.4 file was imported into Encompass, the Military Base Pay (field ID FE0119) for one of the borrowers was showing the combined pay for both jobs or the combined pay for both borrowers.
CBIZ-39883
When importing a MISMO 3.4 loan file into Encompass, if both the Hispanic or Latino (field ID 4210) and Not Hispanic or Latino (field ID 4211) checkboxes are selected in the Ethnicity section of the 1003 URLA Part 4 input form, both checkboxes are now selected after the loan is imported into Encompass.
Previously, only the Hispanic or Latino checkbox selection was imported.
CBIZ-38885
Encompass Developer Connect
When the percentage of the loan amount that is covered by the mortgage insurance (field ID 1199) is update via the SDK, the proposed monthly payment for Mortgage Insurance (field ID 232) is also updated. Previously the monthly payment was not updating when the SDK was used to update the loan amount covered by mortgage insurance.
CBIZ-42524
(Added on 2/18/2022)
An issue was resolved where the Loan.InterviewerLicenseIdentifier attribute was being updated in the loan contract each time the loan was modified and saved with the V1 Update Loan API. With this issue, when users saved the loan after making any updates, the State License ID # field (2306) would also be updated. This issue has been resolved and now the Loan.InterviewerLicenseIdentifier attribute is updated only when Loan.Property.State is passed through the payload with a different value.
EBSP-34760
In Encompass 22.1 an issue occurred for users when creating loans through an API where an ‘Invalid character in the given encoding’ error was returned. This issue was introduced in Encompass 22.1 due to a change to the encoding type from ‘default’ (the encoding type indicated in the loan settings XML file) to UTF-8. This caused the ‘invalid character’ issue in loan settings files using the UTF-16 encoding type, which has some special characters that are valid in UTF 16 but not in UTF-8.
Updates to Encompass and the relevant APIs in Encompass Developer Connect have been made to resolve this issue and recognize these special characters in the XML. This update is scheduled to be applied to Encompass 22.1 on April 2, 2022.
NICE-40246, EBSP-38506
Enhanced Conditions
For companies that use enhanced conditions, the filter for the Latest Status Date on the Conditions tab in the eFolder is now working correctly. Previously, filtering by the Latest Status Date would return no results, even when there were conditions that matched the filter terms.
DOCP-31975
Encompass Settings
(Added on 3/4/2022)
An issue occurred where a custom Lock Desk Shutdown Message on the Lock Desk Schedule/ONRP tab of the Lock Desk Setup setting reverted back to the default message after an Encompass major release was installed. This issue has been resolved and the custom Lock Desk Shutdown Message now remains after an Encompass major release is installed.
Trade Management
Fixed Issues for Version 22.1.0.1 Server Patch 1 (Banker Edition)
(Added on 4/4/2022)
This update contains updates to users' Encompass client machines (22.1.0.1) and a Server Patch (server patch 1) that is applied to the Encompass Server. The fixed issue below is included in this update.
The client-side update (22.1.0.1) 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. The Server Patch included with this release (server patch 1) will be applied to the Encompass Server automatically and cannot be controlled manually via the Encompass Version Manager tool.
In Encompass, go to Help > About Encompass in the menu bar to view your Encompass version. Once the upgrade is complete, your new version number will be 22.1.0.1 Server Patch 1.
The Encompass Software Development Kit (SDK) enables developers to build custom applications that can be added on, or connected to, Encompass and the ICE Mortgage Technology Platform. The Encompass SDK has been repackaged with this 22.1.0.1 Server Patch 1 update. If you are utilizing the Encompass SDK, upgrading to this new package is needed to ensure that your SDK has the same functionality as this latest version of Encompass.
The fixed issue described below requires the new Encompass SDK package:
You may elect to not upgrade your SDK and still be upgraded to Encompass 22.1.0.1 Server Patch 1. All features and functionality in the 22.1.0.1 Server Patch 1 release will be provided when you upgrade Encompass, except for the SDK-dependent item listed above.
If your SDK application utilizes the Encompass SmartClient, you can automate this process so the SDK is upgraded automatically every time you apply an Encompass release. If your SDK application is installed on a computer at your location, you must manually upgrade the SDK for every release. For instructions for automating the upgrade process or manually upgrading the SDK, refer to the Upgrading the Encompass SDK page or view the SDK Programmer’s Guide.
Visit the Encompass SDK and Other Install Files page to access the SDK install files for this release.
The fixed issue listed below is included in this update as part of the Server Patch (Server Patch 1) that is applied to the Encompass Server and as part of the update to users' Encompass client machines (22.1.0.1).
If you are utilizing the Encompass SDK, upgrading to the new SDK package for 22.1.0.1 Server Patch 1 is required to receive this fix.
The formatting used when populating data from enhanced condition virtual fields to a custom print form was updated with the initial Encompass 22.1 release during the implementation of the new options described in the Additional Options for Printing Enhanced Conditions on Custom Print Forms entry in these release notes.
Prior to implementation of the new options, the naming convention for a condition used the following formatting:
-
sequence number + log.status + internal/external description
Example:
1 Added External Description for Prior To Close ID1
With the new options, the naming convention used the following formatting:
-
log.title + internal/external description
Example:
Prior To Close ID1 External Description for Prior To Close ID1
The naming convention for the new options has now been revised to match the prior formatting:
-
sequence number + log.status + internal/external description
CBIZ-44726
Next Section: Change Log | ||
Previous Section: Feature Enhancements |