(Added on 7/2/2019)

When creating or modifying an employment record on the VOE input form, users experienced an issue with the VOE is for dropdown field. When clicking the dropdown to change the field's value to Borrower or CoBorrower, the field and the form would flicker or "flash" and the user was unable to select Borrower or CoBorrower.This issue has been resolved so that the dropdown field is now working as expected and users can successfully select an option from the dropdown to edit the field.

An update has been made to the logic used to populate the Loan Amount used for HMDA reporting purposes (field ID HMDA.X31) when option 2. Application approved but not accepted or option 8. Preapproval request approved but not accepted is selected from the Action Taken dropdown list (field ID 1393). When one of these options is selected, the Loan Amount used for HMDA reporting purposes (field ID HMDA.X31) is now populated with the value from the Loan Amount (field ID 2). Previously the Loan Amount used for HMDA reporting purposes (field ID HMDA.X31) was populated with the value from the Initial Application Amount (field ID NMLS.X11) on the Quick Entry – NMLS Report Information pop-up window (accessed by clicking the NMLS button in the Property Information section on the HMDA Information input form).

Migration

For loan files existing prior to upgrading to Encompass 19.3, the Loan Amount used for HMDA reporting purposes (field ID HMDA.X31) is now updated when the loan file is opened. The calculation used in the HMDA Batch Update tool has also been updated to use the new logic.

(Added on 7/16/2019)

The HMDA Batch Update tool now runs as expected when the Encompass Admin Tools are accessed by double-clicking the EncAminTools.exe file in the C:\SmartClientCache\Apps\Ellie Mae\Encompass folder. Previously when a user clicked the Execute button in the HMDA Batch Update Tool to apply the update, an error message would display stating that “An error occurred while downloading resource file EncompassObjects.dll.” This issue has been resolved and HMDA Batch Updates now execute as expected when the Encompass Admin Tools are opened via the EncAminTools.exe file.

Workaround Information:

The following workaround was provided for this production issue and is no longer required for Encompass version 19.3 and later:

• Have an Encompass user with admin permissions run the HMDA Batch Update Tool by opening the Encompass Admin Tools via the AdminTools.exe file.

(Added on 7/16/2019)

An issue was resolved that cause the credit information Other Scoring Model for the borrower (field ID 4176) and co-borrower (field ID 4179) to clear after saving and closing a file. This would occur when 8. Other Credit Scoring Model was selected as the option for the Credit Scoring Model field for the borrower (field IDs HMDA.X117) or co-borrower (field ID HMDA.X119) on the HMDA Information input form and then text was entered in the Other Scoring Model field. This issue has been resolved and the data is now being saved as expected.

(Added on 7/16/2019)

An issue was resolved that caused NA to not populate as expected for the HMDA County Code (field ID HMDA.X111) or HMDA Census Tract (field ID HMDA.X112) fields when both of the following conditions occurred:

• When NA is populated in the Census Tract (field ID 700) or County Code (field 1396) field.

• When one of the following options has been selected for the Action Taken (field ID 1393): 1. Loan Originated, 2. Application approved but not accepted, 7. Preapproval request denied or 8. Preapproval request approved but not accepted.

Workaround Information:

The following workaround was provided for this production issue and is no longer required for Encompass version 19.3 and later:

• Run a HMDA report for upload and manually adjust the Census Tract or County Code.

Encompass administrators can modify the access rights for users assigned with a non-administrator persona (such as Loan Officer or Manager) to enable them to access and view the information in the Encompass Settings > Company/User Setup > Organization/User settings and the System Administration > All User Information settings. However, when a non-administrator user who had been granted these customized access rights opened the Encompass Settings, selected a user from the list on the System Administration > All User Information screen, and then clicked the Find in Hierarchy button, an issue occurred where the search results found the correct sub-organization folder where the user was located, but the other organization and sub-organization folders were not displayed as expected. The entire organization hierarchy should have been displayed.

This issue has been resolved so that the correct level of organization folders are displayed for the non-administrator user when they search for a user by clicking the Find in Hierarchy button. Please note that these non-administrator users will not be able to see any organizational levels above them. Even for a local administrator, they would be able to see their level and below only.

In previous versions of Encompass, the organizational folders that should have displayed here were not.

Now that the issue has been addressed in Encompass 19.3, the organizational folders are displaying as expected.

Workaround Information

The following workarounds were provided for this production issue and are no longer required for Encompass version 19.3 and later:

• The user must log out of Encompass and log back in. The full organization will be available again until the next "Find in Hierarchy" search.

Using the User Groups setting, administrators utilize its Resources tab to define the selected user group’s access to public resources, including standard print forms. To define this access, administrators click the New icon in the Standard Print Forms section of the Resources tab, select forms from the All Standard Print Forms list (shown below), and then click the right-arrow button to move the forms to the Selected Forms list. Once done, the Selected Forms list displays in the Standard Print Forms section of the Resources tab and represents the forms the user group can access in Encompass.

An issue occurred where forms that had been removed from the ‘All Users’ user group’s Standard Print Forms list on the Resources tab were being automatically returned to the user group’s Standard Print Forms list when the administrator upgraded to a new version of Encompass. The following forms were being re-added to this list upon upgrading if they had been removed from the list in the previous version of Encompass:

Using the Privacy Policy Opt-Out forms for the example below, you can see the forms have been removed from the All Users user group’s Selected Forms list in one version of Encompass, but they are back in the Standard Print Forms list on the Resources tab after upgrading.

This issue has been resolved and the Standard Print Forms list on the Resources tab for the All Users user group is no longer impacted upon upgrading.

In Encompass versions 19.3 and 19.3.0.1 Server Patch 1, an issue occurred for non-administrator users (i.e., users not assigned with an Administrator or Super Administrator persona) in certain user groups where they were unable to generate 1003 forms in disclosure packages. Even when the eFolder Setup administrative settings were configured to include the 1003 forms in specific eDisclosure packages when specific criteria was met, when users were in the process of ordering disclosures, the 1003 forms were not listed in the Select Documents window that lists the forms to include in the disclosure package. As a result, users could not indicate that the 1003 forms should be included in the disclosure package.

Please note that this issue with the 1003 forms only occurred in one specific scenario: When an administrator in Encompass 19.3 and 19.3.0.1 Server Patch 1 accessed the User Groups setting and then selected a user group there to update, if they added or removed any forms in the Standard Print Forms list for the user group, this resulted in the error occurring for the users. When users in the impacted user group attempted to order disclosures, the 1003 forms were not listed in the Select Documents window.

This issue with generating the 1003 disclosures has been resolved.

An issue with tracking custom versions of the Settlement Service Provider List (SSPL) in the Disclosure Tracking tool was introduced in Encompass 19.2 and addressed with a fix in the Encompass 19.2 June Service Pack (19.2.0.4 Server Patch 4). This same fix is now being applied to Encompass 19.3 (and later versions).

When an administrator used the eFolder Setup > Documents tool to create a custom document that was “sourced” by the standard Settlement Service Provider List form and then added and sent this form in an eDisclosure package, the custom SSPL was not being indicated as Sent in the Disclosure Tracking tool’s LE Tracking section. The SSPL Sent field was not being populated with the date it was sent as expected. The SSPL tracking was also not indicating ‘Yes’ under the Disclosure Tracking log’s Provider List Sent section. The only time these fields were populated with the sent date and ‘Yes’ indicator when a custom version of the SSPL was sent was is if the administrator had named the custom document 2015 Settlement Service Provider List. Otherwise, the SPPL Sent field remained blank and the Provider List Sent would be indicated as ‘No’ when the custom SSPL doc was sent. This issue has been resolved so that any custom doc that is sourced by the 2015 Settlement Service Provider List, 2015 Settlement Service Provider List – No Fees, Settlement Service Provider List, or Settlement Service Provider List (Legal) forms is indicated as Sent in the SSPL Sent field when the document is sent with an eDislosure package.

In the Encompass 19.1 April Service Pack release (19.1.0.6 Server Patch 5), updates were made to the relevant code in the Encompass SDK to help reduce the amount of system memory that is required when larger calls are performed such as “View Pipeline”. However, a portion of this update caused an issue with the Velocify application that uses the Encompass SDK. It was also determined that this update did not substantially impact the issue with the amount of system memory that was being used. Therefore, this update has been rolled back and removed from Encompass 19.3 (and later versions) to prevent any additional issues that could occur with Velocify.