Fixed Issues for Version 18.3.0.6
This Encompass 18.3 August Service Pack includes updates to users' Encompass client machines.
Why we fixed these issues: These issues were fixed to improve usability and to help ensure Encompass is operating as expected. The issues were chosen to be fixed based on the severity of its impact to clients and client feedback.
Updates to the Encompass Client Machines
The Encompass 18.3 August Service Pack 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.
Compliance Issue Resolved
The following remarks now displays in the Calculating Cash to Close section on the Closing Disclosure Page 3 when a tolerance cure is applied to a loan as a principal reduction with no lender credit:
-
Increase exceeds legal limits by $[amount of Applied Cure (field ID FV.X366)]
The updated remarks are mandated by regulatory requirement – Calculating Cash to Close (§ 1026.38(i)(1)(iii)(A)(3); Comment 38(i)(1)(iii)(A)-3)) – and are applied to the standard and alternate versions of the Closing Disclosure under the following conditions:
-
Standard – When Did Total Closing Costs Change? (field ID CD3.X111) is Y and a cure has been applied to the loan.
-
Alternate - When Did Total Closing Costs Change? (field ID CD3.X119) is Y and a cure has been applied to the loan.
The Did Total Closing Costs Change? fields are populated with Y when the value in the Applied Cure field is greater than 0.
CBIZ-19082
Encompass Forms and Tools
An issue occurred for users documenting a change of circumstance at the fee level, as introduced in the Encompass 18.3 Major Release. When using fee level change of circumstance for a loan (i.e., the Fee Level Disclosures checkbox (field ID 4461) on the Loan Estimate Page 1 or Closing Disclosure Page 1 is selected), the fee level change of circumstance reasons and details were not being printed to the Notice of Change Circumstances Reasons (GTRIDLECCRJ_S) nor the Notice of Change Circumstances Reasons Closing Disclosure (form GTRIDCDNCCR_S) output forms when users printed the documents prior to disclosing them. This issue has been resolved and fee level change of circumstance reasons and details are now printed to these output forms as expected.
An issue was introduced in Encompass 18.3 where the Comments field that is provided on the Disclosure Details window’s Reasons tab when viewing a Disclosure History entry in the Disclosure Tracking tool table was no longer editable. Therefore, users could not enter comments on the Reasons tab like they could prior to Encompass 18.3. This issue occurred specifically when users were not documenting changed circumstances at a fee level (i.e., the Fee Level Disclosures checkbox (field ID 4461) was not selected.) This issue has been resolved and the Comments field on the Reasons tab is now available again for users to enter comments.
An issue occurred where comments were populated into the Buy Side Lock and Pricing column in the lock extension snapshot when a lock extension request was submitted. If a lock extension request, including comments, was submitted, those comments populated the Buy Side Lock Request column and replaced any comments in the Buy Side Lock and Pricing column in the snapshot. This issue has been resolved and lock extension request comments are only populated into the Buy Side Lock Request column.
An issue occurred where comments were not saved in the lock snapshot when a lock was submitted using the Worst Case Pricing Tool. If a lock was submitted using either historical or current pricing, no comments (appended program notes or manually entered comments) were saved in the snapshot. This issue has been resolved and the comments are now saved in the lock snapshot.
Manually entered comments must be entered after the program notes are returned in order to be saved in the lock request snapshot.
Electronic Document Management (EDM)
An issue was resolved that caused updates to the Email Signature in a user’s Personal Settings (Encompass > Settings > Personal Settings > My Profile) to not populate in email notifications when the signature was applied from one of the following non-Consumer Connect HTML email templates:
-
Document Requests
-
Loan Level Consent
-
eDisclosures
-
Pre-Closing Documents
This issue, which was introduced with the Encompass 18.3 release, has been resolved. The signatures are now populating correctly.
Workaround Information:
The following workaround was provided for this production issue and is no longer required for Encompass 18.3.0.6 and later.
-
The user can manually edit the body of the HTML email template.
EDM-20474
An issue was resolved that caused the Loan Officer option to not display in the Sender Type dropdown list on the Send window for eDisclosures and when using the Request button in the eFolder to request an eSignable Loan Estimate or Closing Disclosure. Only the Current User and File Starter options displayed. This issue was introduced with the Encompass 18.3 release and only affected Encompass WebCenter loans not submitted from Encompass Consumer Connect websites. It has been resolved and the Loan Officer option now displays as expected.
EDM-20545
For South Carolina loans, when an eFolder document package contains a document that the loan officer is required to eSign, Encompass now delivers an email notification to borrowers as soon as the eSigning package is sent. In previous releases of Encompass, the loan officer was required to eSign the specified document before the email notification would be sent to the borrower.
EDM-19945
Trade Management
Two issues occurred where the Note Rate Range was not correct in correspondent direct trades.
- If a correspondent direct trade was created with a Note Rate Range, saved, and then opened at a later date, the Note Rate Range was blank.
- If a correspondent direct trade was created with a Note Rate Range, saved, and then another correspondent direct trade was opened, the Note Rate Range from the first trade is displayed.
These issues have been resolved and the correct Note Rate Range is now saved and displayed.