Fixed Issues for Version 19.1.0.4
This Encompass 19.1 Critical Patch 2 includes updates to users' Encompass client machines.
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 Client Machines
The Encompass 19.1 Critical Patch 2 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.
Please note that these issues impact features available in Encompass Banker Edition only.
Issue Resolved: Dynamic Data Management (DDM) Fee Rules Result in Recording Fee Resetting to Zero $0.00
An issue occurred for Encompass users who set up and activated Dynamic Data Management (DDM) fee rules. If one or more DDM fee rules had been set up for any lines except line 1202 on the 2015 Itemization input form, and then the rule(s) were activated, the borrower paid amount for Recording Fees (field ID 390) on line 1202 was reset to a value of zero (0.00) each time a user updated and saved the loan file. This issue resulted in this recording fee being reset to zero for all customers using DDM fee rules (for lines which were not line 1202) even if they did not have rule set up to update this recording fee. This could result in issues with fee variances since customers were not aware that this recording fee was being reset to zero when the loan was saved. This issue has been resolved and field 390 is no longer reset to zero in this scenario.
Workaround Information:
The following workaround was provided for this production issue and is no longer required for Encompass 19.1.0.4 and later:
- Use the Edit icon next to line item 1202 to set the value for this field, and it will retain the information when the DDM calculation engine is triggered.
Issue Resolved: Dynamic Data Management (DDM) Field Rules Causing Borrower Pair 1 Information to Display on Disclosures for Borrower Pair 2
An issue occurred for customers using active Dynamic Data Management (DDM) field rules with loans with multiple borrower pairs. When a loan file contained multiple borrower pairs, and then the user generated disclosures to send to Borrower Pair 2, the Borrower Summary - Origination input form data was reset to the Borrower Pair 1 data. This resulted in the Loan Estimate (LE), Closing Disclosure (CD), and other disclosures being populated with the primary borrower pair's information (Borrower Pair 1) instead of the Borrower Pair 2 information. This could result in disclosures with Borrower Pair 1's information on it being sent to Borrower Pair 2. Note that this issue occurred in loans with multiple borrower pairs only when a DDM field rule that copies a date value from one date field to another date field was active. If a DDM rule that copies a date value from one date field to another date field was not created or not active, then this issue did not occur. This issue has been resolved and the correct borrower data is now provided for disclosures intended for Borrower Pair 2.
