Fixed Issues for Version 20.2.0.5 Server Patch 3 (Banker Edition)

This section describes the issues that have been fixed in this release.

This Encompass 20.2 January Service Pack release includes updates to users' Encompass client machines (20.2.0.5) and a Server Patch (server patch 3) that is applied to the Encompass Server.

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.

Update to the Encompass Server (i.e., Server Patch 3)

Below are updates in the Server Patch that is 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.

Authorized users can use the Loan Reassignment tool in Encompass Settings to assign a different user to one or more loans. However, an issue occurred where the Loan Reassignment tool was not updating certain loan officer information fields on the 1003 (and other) input forms. After using the tool to assign a different loan officer to the loan, the following fields in the loan file were not being updated with the new loan officer’s information:

  • 3238 – Loan Originator NMLSR ID #
  • 3968 – Email
  • LCP.X21 – Loan Officer Name
  • LE3.X4 – Loan Officer
  • 1256 – Contact Name

This issue has been resolved and these fields now reflect the newly assigned loan officer as expected.

NICE-25352

In the Encompass 20.2 December Service Pack release, a new setting, Do not allow changes after pricing has been retrieved, was added to the Product and Pricing setting that only disabled the pricing fields and buttons except for the Submit Request button and the Comments (field ID 2144) field to prevent changes to the Lock Request Form before a lock request is submitted. In this release, the behavior of the Lock Request Form when the setting is enabled has been updated to disable all fields and buttons except for the Submit Request button, Reset Button, and the Comments (field ID 2144) field.

SEC-19448

An issue occurred when reports were generated using the “TPO Settings” data source on the Reports tab. If a Filter was added to a report using TPO Settings field “BrokChannelType” and/or “CorrChannelType” with an Operator “Is any of” for Options “N” and/or “Y”, an error message “There are no TPO settings records that match the selected criteria for this report.” was displayed when the Generate Report button was selected, regardless of whether TPO Settings records that matched the selected criteria existed. This issue has been resolved and reports are now correctly generated when “BrokChannelType” and/or “CorrChannelType” filters are used.

SEC-15806

An issue occurred where depending on how a lock was submitted, the same loan was erroneously counted toward the Best Efforts (BE) daily limit, and if the limit was exceeded, an error message was displayed. This issue has been resolved and if the Request Type is “New Lock” or the Rate Lock API is called with No Action or Action is "Confirm", the same loan will only be counted once towards the BE daily lock limit.

SEC-19253

Update to the Encompass Server
(i.e., Server Patch 3) and Client Machines (20.2.0.5)

The Encompass 20.2 January Service Pack release includes the following fixed issue. 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 log in of Encompass following the release.

Again, the update listed below will not be fully implemented until both the Server Patch and the client-side updates are applied to your Encompass system.

When using the Loan Reassignment tool, the loans that can be reassigned are listed in a table. This list displays 50 loans at a time, and each column can be sorted in ascending and descending order by clicking the column header. An issue occurred where the list of loans in the table could only be sorted within the currently displayed segment. For example, if the table contained 122 loans, the first 50 loans (1-50) were listed in order according to the to the selected column header (for example, the loan number). However, when you navigated to the next segment (51-100) the loans in the list were not sorted according to the loan number. This issue has been resolved so that the loans are sorted based on the selected column header across each segment of 50 loans, rather than only the loans that are currently displayed in the table.

NICE-25992

Updates to the Encompass Client Machines

The Encompass 20.2 January Service Pack release includes the following items, which are client-side updates that are applied to users' Encompass client machines. These client updates 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 these updates upon their initial log in of Encompass following the release.

Encompass Forms and Tools

When a loan with a borrower or co-borrower work phone number with an extension is exported to a MISMO 3.4 file and then reimported into Encompass, the extension number is now importing correctly. Previously the extension number was not importing back into Encompass. This issue affected the following field IDs:

  • 66

  • 98

  • 1480

  • 1490

  • 4553

  • 4534

CBIZ-35212

An issue was resolved that caused the value for the Estimated Cash to Close (field ID LE2.X26) generated on some alternate versions of the Loan Estimate output form to not match the value recorded in the Disclosure Tracking record. This issue has been resolved. The Estimated Cash to Close on the output form now matches the value captured in the Disclosure Tracking Record.

CBIZ-35528

When you create a condition form (Encompass > Settings > Loan Setup > Conditions Forms) for enhanced conditions and the enhanced conditions use default condition types (Approval, Docs, Funding, Closing, and Purchase) and default condition statuses (Added, Fulfilled, Received, Reviewed, Rejected, Cleared, and Waived), these Enhanced Conditions are now added to the output form.

CBIZ-35077

An issue was resolved that caused a Loan Originator Organization street address to populate incorrectly on the URLA 1003 Part 4 input form when switching from the 2009 to the 2020 versions of the URLA forms. This issue caused a street address with a unit number (for example Suite 300) to include the entire street address in the Street Address field (field ID URLA.X188) instead of entering the unit information in the Unit Type (field ID URLA.X189) and Unit # (field ID URLA.X190) fields. This issue has been resolved and the Unit Type and Unit # fields now populate with the correct information.

CBIZ-27136

Encompass Settings

In addition to the updates for the Loan Reassignment mentioned above, a separate issue related to sorting the data in the Loan Reassignment tool was also resolved with this release. In earlier versions, when you were viewing a segment of loans in the table, and then sorted the data by one column (for example, loan number), followed by sorting the data in additional columns (for example, loan amount and borrower name), and then selected a new segment of loans to view in the table from the dropdown list provided at the top of the table, the Encompass system would become non-responsive and eventually the user would be forced to close Encompass in order to proceed. This issue has been resolved.

NICE-33586

 

  Previous Section: Updates & Enhancements