Release Notes Change Log for Version 19.1

A new version of the Settlement Service Provider List printed output form is now available to generate and/or print in Encompass. The purpose of this new version is to provide a version of the Settlement Service Provider List that does not contain the Estimate column for fees in the Additional Details for Services You Can Shop For and the Additional Details for Services You Cannot Shop For sections of the form.

The title of this new form is 2015 Settlement Service Provider List - No Fees.

To access and print this form in Encompass, click the Print icon from a loan file or Pipeline view, click the Standard Forms tab, and then select General Forms from the Look In dropdown list. Locate the form in the list, and then click Add to move it to the Selected Forms list. Use the buttons at the bottom of the window to print or manage the form.

It is important to note that when this version of the form is disclosed, it is currently not tracked by the Disclosure Tracking tool automatically. If you opt to use this form and include it in a disclosure, you will need to manually create a disclosure tracking entry in the tool to track its disclosure details. The Disclosure Tracking tool will be updated to include this version of the form in a future release.

For new installations of the Encompass Smart Client, ExpertPDF version 12 is now included in the installation package. ExpertPDF.is a .NET library that is used by Encompass to convert HTML to PDF documents. This upgraded version of ExpertPDF helps ensure that PDF files in the eFolder can be exported, converted, and managed without issue. Please note that for existing Encompass systems that are upgraded to Encompass 19.1, ExpertPDF version 12 will also be included with the upgrade.

For new installations of the Encompass Smart Client, Adobe’s Expert PDF version 12 is now included in the installation package to help ensure PDF files can be exported, converted, and managed without issue. Please note that for existing Encompass systems that are upgraded to Encompass 19.1, Adobe’s Expert PDF version 12 will also be included with the upgrade.

Updates have been made to the calculation used for the Proposed Monthly Payment (PITI) amount (field ID VASUMM.X99) on the VA Management input form.

Updates have been made to the calculations used for the Proposed Monthly RE Taxes (field ID 1405) in the Monthly Housing Expenses section on the 1003 Page 2 and the Proposed Monthly Payment (PITI) amount (field ID VASUMM.X99) on the VA Management input form.

The new Rep and Warrant Tracker is a new Encompass tool that enables users to track details summarizing rep and warrant relief status from Fannie Mae’s Desktop Underwriter (DU) and Freddie Mac’s Loan Product Advisor (LPA). By being able to reference this data on one screen, lenders can quickly determine eligibility options between AUS findings and be better able to manage and maintain execution options at secondary marketing.

The fields in the Rep and Warrant Tracker tool are populated based on the applicable data entered in the following Encompass fields:

 

Label	Encompass Field
Loan Number	364
Borrower Name	4000 + 4001 + 4002
Coborrower Name	4004 + 4005 + 4006
Loan Amount	1109

Submission Statuses

Fannie Mae

Label	Encompass Field
DU Recommendation	TQL.X66
UCDP Status	MORNET.X93
CU Risk Score	MORNET.X92
EC Status (1003)*	MORNET.X94
EC Status (ULDD)*	MORNET.X95
UCD Collection Status	MORNET.X96

* This field is currently not operational. Functionality for this field will be provided in a future release.

Freddie Mac

Label	Encompass Field
LPA Risk Class	CASASRN.X34
LPA Purchase Eligibility	AUS.X120
Documentation Level	AUS.X118
UCDP Status*	TQL.X87
Collateral Risk Score *	TQL.X88
LQA Purchase Eligibility	AUS.X182
LQA Risk Assessment	AUS.X181
LCLA UCD Requirement	AUSF.X70

* This field is currently not operational. Functionality for this field will be provided in a future release. In addition, the fields in the Expiration Date column are currently not operational. This functionality will be provided in a future release.

Rep and Warrant Status

Fannie Mae

Label	Encompass Field
Appraisal Waiver Offered	MORNET.X97
Value Rep & Warrant Relief	MORNET.X98
Asset Rep & Warrant Relief	MORNET.X100
Verification of Employment	Borrower: MORNET.X131; Co-Borrower: MORNET.X143
Verification of Income
Base Income	Borrower: MORNET.X132; Co-Borrower: MORNET.X144
Bonus	Borrower: MORNET.X133; Co-Borrower: MORNET.X145
Overtime	Borrower: MORNET.X134; Co-Borrower: MORNET.X146
Commission <25%	Borrower: MORNET.X135; Co-Borrower: MORNET.X147
Commission <25%+	Borrower: MORNET.X114 Co-Borrower: MORNET.X112
Social Security	Borrower: MORNET.X136; Co-Borrower: MORNET.X148
Retirement (Pension, etc)	Borrower: MORNET.X130; Co-Borrower: MORNET.X142
Self-Employed	Borrower: MORNET.X137; Co-Borrower: MORNET.X149

Note that the fields in the Close By Date column are currently not operational. This functionality will be provided in a future release.

Freddie Mac

Label	Encompass Field
Appraisal Waiver Offered	TQL.X86
Collateral Rep & Warrant Relief	TQL.X90
Asset Rep & Warrant Relief	TQL.X92
Income Rep & Warrant Relief	TQL.X94

Note that Encompass fields populated with Apply or Eligible or other ‘Y’ indicators, a green checkmark will be populated for the field in this Rep and Warrant Status section of the tool.

When the Encompass fields are populated with Cancel, NotEligible, Unavailable, or other ‘N’ indicators, a red X will be populated for the field in this tool.

If the Encompass field is not populated with any data (i.e., the field is blank), then a grey dash will be populated for the field in this tool.

(Updated on 1/18/2019)

When searching for loans or using filters to display specific loans on the Pipeline, an issue occurred where loans indicated as subordinate loans were not displaying correctly on the Pipeline. On the Pipeline, the Lien Position column should display a blank value, First, or Subordinate to indicate the loan’s lien position. The value displayed here is based on the Lien Position indicator (field ID 420) that is selected on the 1003 Page 1 input form. However, when loans were indicated as Subordinate on the 1003 Page 1, the Lien Position column on the Pipeline displayed a blank value instead of Subordinate. This issue has been resolved so that Subordinate is displayed in this Pipeline column for applicable loans. In addition, if you select Subordinate from the Lien Position column’s dropdown list to filter your Pipeline to show only subordinate loans, the subordinate loans are listed in the Pipeline accordingly.

As part of the fix for this issue, the field description and field size for field 420 (Lien Position) were updated in the Reporting Database. In order for this fix to be applied and resolve this issue with your Pipeline, you must manually remove field 420 from the Reporting Database, and then add field 420 back to the Reporting Database. Once you have re-added the field and updated the Reporting Database, the issue will be resolved in your Pipeline. Refer to the Admin Tools: Reporting Database help topic for instructions to remove and add the field.

When searching for loans or using filters to display specific loans on the Pipeline, an issue occurred where loans indicated as subordinate loans were not displaying correctly on the Pipeline. On the Pipeline, the Lien Position column should display a blank value, First, or Subordinate to indicate the loan’s lien position. The value displayed here is based on the Lien Position indicator (field ID 420) that is selected on the 1003 Page 1 input form. However, when loans were indicated as Subordinate on the 1003 Page 1, the Lien Position column on the Pipeline displayed a blank value instead of Subordinate. This issue has been resolved so that Subordinate is displayed in this Pipeline column for applicable loans. In addition, if you select Subordinate from the Lien Position column’s dropdown list to filter your Pipeline to show only subordinate loans, the subordinate loans are listed in the Pipeline accordingly.

In previous versions of Encompass, the Actual Received Date for the Loan Estimate (LE) was not being populated when disclosures were sent electronically prior to the borrower or co-borrower providing their consent to receive disclosures electronically, even if the consent and the received date occurred on or before the LE Due date (field ID 3143).

Starting in Encompass 19.1, when disclosures are accessed electronically by borrowers, the Actual Received Date in the LE will be populated based on whether the borrower provided eConsent prior to them accessing the disclosures or not:

• If consent is obtained prior to disclosures being sent, the Actual Received Date for the borrower and co-borrower will be populated when the borrower or co-borrower accesses the disclosure package (existing behavior) or
• If prior consent status is No or has not been received, the Actual Received Date for the borrower or co-borrower will be populated as long as either the borrower or co-borrower provides consent and accesses the disclosure package on or before the LE Due Date. This is new behavior.
• The Actual Receipt Date will be left blank in the following scenarios:
  • The borrower (or co-borrower respectively) never accesses the disclosure package
  • If the borrower or co-borrower accesses the disclosure package after the LE Due Date when prior consent status was No
  • If there is no LE Due Date populated

Please note that this new behavior impacts electronic disclosures only. Disclosures sent by any other method (e.g. in person, by mail, etc.) will persist as they did in earlier versions of Encompass and the Actual Received Date will be populated accordingly. For loans started in previous versions of Encompass where disclosures have not been sent, this new logic will be used. For loans started in previous versions of Encompass that do have disclosures, the previous logic will continue to be used for those loans.

In previous versions of Encompass, the Actual Received Date for the Loan Estimate (LE) and Closing Disclosure (CD) was not being populated when disclosures were sent electronically prior to the borrower or co-borrower providing their consent to receive disclosures electronically, even if the consent and the received date occurred on or before the LE Due date (field ID 3143).

Starting in Encompass 19.1, when disclosures are accessed electronically by borrowers, the Actual Received Date in the LE and CD will be populated based on whether the borrower provided eConsent prior to them accessing the disclosures or not:

• If consent is obtained prior to disclosures being sent, the Actual Received Date for the borrower and co-borrower will be populated when the borrower or co-borrower accesses the disclosure package (existing behavior) or
• If prior consent status is No or has not been received, the Actual Received Date for the borrower or co-borrower will be populated as long as either the borrower or co-borrower provides consent and accesses the disclosure package on or before the LE Due Date. This is new behavior.
• The Actual Receipt Date will be left blank in the following scenarios:
  • The borrower (or co-borrower respectively) never accesses the disclosure package
  • If the borrower or co-borrower accesses the disclosure package after the LE Due Date when prior consent status was No
  • If there is no LE Due Date populated

Please note that this new behavior impacts electronic disclosures only. Disclosures sent by any other method (e.g. in person, by mail, etc.) will persist as they did in earlier versions of Encompass and the Actual Received Date will be populated accordingly. For loans started in previous versions of Encompass where disclosures have not been sent, this new logic will be used. For loans started in previous versions of Encompass that do have disclosures, the previous logic will continue to be used for those loans.

SDK Plugins Can Once Again be Disabled at the Workstation Level

In the Ellie Mae knowledge base article How to Disable Plugins at the Workstation Level(article # 5911 available here), Ellie Mae provides the relevant file locations and instructions for Encompass administrators and/or developers to quickly disable one or more Encompass SDK plugins in a systematic fashion from a single workstation. This proves especially useful when they receive reports of problematic behavior after a plugin has been deployed and it may not be known if the problem directly relates to the plugin or to something else. By disabling the relevant plugins they can quickly determine if the issue is directly related to the plugin or not. An issue occurred in Encompass 19.1 where the procedure provided in the knowledge base article was no longer working correctly and customers were unable to disable the SDK plugins. The source of this issue was identified and the relevant code was updated to resolve this issue. Customers can once again follow the steps in the knowledge base article and successfully disable the desired SDK plugins.

In earlier versions of Encompass, users who fail to enter the correct password when logging into Encompass a certain number of times are locked out of their accounts and must have an administrator reset the account. Starting in Encompass 19.1, administrators can now use new password policies in the Encompass Admin Tools to enable a time-based lock-out period for users (for example, 15 minutes) so that a series of failed log in attempts causes the account to be locked for a set period of time. It will then be automatically unlocked.

In addition, a new policy is also available where administrators can enable a time-based lock-out period for the user who logs into Encompass using the ‘admin’ user ID (i.e., the admin user).

This change does not impact your current password policy settings (even if they are less stringent than above). The validation is done only if you modify your password policy settings. If any of the existing policy requirements do not conform to these guidelines, a warning message will be triggered to notify the administrator that the settings should be more stringent in order to conform to best practices in security and password management and require the administrator to conform to these minimum guidelines. This will ensure that when users change their password after the subsequent expiration date, they set more stringent passwords.

In addition, once you make a change to your password policy (and thus the enforcement of the complexity rules will then be in effect), you need to ensure that all of the user passwords for the Encompass Software Development Kit (SDK) and Encompass Developer Connect API applications are also updated to meet the complexity rules so you can avoid any interruptions with these applications.

Failed log in attempts that occur during the time the user is locked out are now recorded in the System Audit Trail. All failed log in attempts will continue to be recorded in the System Audit Trail as in earlier versions of Encompass.

In earlier versions of Encompass, users who fail to enter the correct password when logging into Encompass a certain number of times are locked out of their accounts and must have an administrator reset the account. Starting in Encompass 19.1, administrators can now use new password policies in the Encompass Admin Tools to enable a time-based lock-out period for users (for example, 15 minutes) so that a series of failed log in attempts causes the account to be locked for a set period of time. It will then be automatically unlocked.

In addition, a new policy is also available where administrators can enable a time-based lock-out period for the user who logs into Encompass using the ‘admin’ user ID (i.e., the admin user).

Failed log in attempts that occur during the time the user is locked out are now recorded in the System Audit Trail. All failed log in attempts will continue to be recorded in the System Audit Trail as in earlier versions of Encompass.

When administrators are configuring a persona, they can set up access permissions for the Pipeline. As part of this configuration, they can create the default Pipeline view that the persona will see when they log into Encompass. As part of this set up, they have the option (but it is not required) to indicate the loan folder that will be used for the default Pipeline View.

In earlier versions of Encompass, if a user was viewing a loan folder in the Pipeline and then they switched to a different Pipeline View where no loan folder was defined by the administrator, the user would see the same loan folder that they were using in the previous Pipeline View. Starting in Encompass 19.1, when a user is viewing one (or more) loan folders in the Pipeline and then switches to a different Pipeline View where no loan folder was defined by the administrator, the user will now see the loan folder that has been indicated as the Working Folder in the user's user profile (i.e., the User Details screen).

Certain users experienced an issue with the Loan Folder dropdown field provided near the top of the Encompass Pipeline. When exactly 15 loan folders were listed in the Loan Folder dropdown list, the vertical scroll bar that should display on the right side of the Loan Folder dropdown list was missing, which prevented users from being able to select the checkbox for the last folder at the bottom of the list (since they could not scroll down the full folder list). This issue has been resolved and the scroll bar is now provided as intended in the Loan Folder dropdown list when 15 loan folders are listed.

(Updated on 2/6/2019)

The following options have been removed from the Offering Identifier dropdown list (field ID CASASRN.X163) on the Freddie Mac Additional Data Input Form because they are no longer supported by Freddie Mac:

• 210: Alt 97

• 220: Freddie Mac 100

• 230: Initial Int 10/20 FIXED

• 231: Initial Int 15/15 FIXED

• 232: Initial Int ARM

• 233: Initial Int ARM 10 Year

• 240: Home Possible 100

• 242: Home Possible Neighborhood Solutions 100

The remaining offerings are still available on the dropdown list:

• 241: Home Possible

• 243: Home Possible Neighborhood Solution

• 250: Home Possible Advantage

• 251: Home Possible Advantage for HFAs

• 310: Relief Refinance – Open Access

• 320: Enhanced Relief Refinance

The following options have been removed from the Offering Identifier dropdown list (field ID CASASRN.X163) on the Freddie Mac Additional Data Input Form because they are no longer supported by Freddie Mac:

• 210: Alt 97

• 220: Freddie Mac 100

• 230: Initial Int 10/20 FIXED

• 231: Initial Int 15/15 FIXED

• 232: Initial Int ARM

• 233: Initial Int ARM 10 Year

• 240: Home Possible 100

• 242: Home Possible Neighborhood Solutions 100

• 250: Home Possible Advantage

• 251: Home Possible Advantage for HFAs

The remaining offerings are still available on the dropdown list:

• 241: Home Possible

• 243: Home Possible Neighborhood Solution

• 310: Relief Refinance – Open Access

• 320: Enhanced Relief Refinance

An issue was resolved that caused non-borrowing owner file contacts to be unable to eSign document packages under the following conditions:

1. An eConsent request, document request, or eDisclosure package was sent to the non-borrowing owner from the eFolder.

2. The non-borrowing owner was deleted from the File Contacts tool and then added back.

3. Another eConsent request, document request, or eDisclosure package was sent to the non-borrowing owner.

Under these conditions, a Service is currently unavailable error message would display when the non-borrowing owner accessed the WebCenter.

This issue has been resolved and the error message no longer displays.

An issue occurred in Encompass 18.4.0.5 (and later) for some Encompass users where the font size in the Encompass user interface was changing in certain scenarios. When the user's computer that they access Encompass from was configured to use the Medium (125%) or Larger (150%) display settings (set up in Microsoft Windows' Control Panel > Appearance and Personalization > Display) and then they either uploaded a file attachment in the eFolder or ordered a service where an attachment was returned and uploaded to the eFolder, the font size in the Encompass user interface either increased or decreased in size to the point where the interface was very difficult to understand and use. Here is an example:

A similar issue with this font re-sizing occurred:

• For some users using the smaller (100%) Windows Display setting.
• For some users in Encompass Banker Edition accessing the Pipeline > Investor Services > Deliver Data and Docs to... option. After closing the resulting Deliver Data and Docs pop-up window, the system font re-size occurred.

This issue with the font system resizing has been resolved and is no longer occurring in these scenarios.

In previous versions of Encompass, the Actual Received Date for the Loan Estimate (LE) was not being populated when disclosures were sent electronically prior to the borrower or co-borrower providing their consent to receive disclosures electronically, even if the consent and the received date occurred on or before the LE Due date (field ID 3143).

Starting in Encompass 19.1, when disclosures are accessed electronically by borrowers, the Actual Received Date in the LE will be populated based on whether the borrower provided eConsent prior to them accessing the disclosures or not:

• If consent is obtained prior to disclosures being sent, the Actual Received Date for the borrower and co-borrower will be populated when the borrower or co-borrower accesses the disclosure package (existing behavior) or
• If prior consent status is No or has not been received, the Actual Received Date for the borrower or co-borrower will be populated as long as both the borrower or co-borrower provide consent and accesses the disclosure package on or before the LE Due Date. This is new behavior.
• The Actual Receipt Date will be left blank in the following scenarios:
  • The borrower (or co-borrower respectively) never accesses the disclosure package
  • If the borrower or co-borrower accesses the disclosure package after the LE Due Date when prior consent status was No
  • If there is no LE Due Date populated

Please note that this new behavior impacts electronic disclosures (i.e., esigned disclosures) only. Disclosures sent by any other method (e.g. in person, by mail, etc.) will persist as they did in earlier versions of Encompass and the Actual Received Date will be populated accordingly. For loans started in previous versions of Encompass where disclosures have not been sent, this new logic will be used. For loans started in previous versions of Encompass that do have disclosures, the previous logic will continue to be used for those loans.

In previous versions of Encompass, the Actual Received Date for the Loan Estimate (LE) was not being populated when disclosures were sent electronically prior to the borrower or co-borrower providing their consent to receive disclosures electronically, even if the consent and the received date occurred on or before the LE Due date (field ID 3143).

Starting in Encompass 19.1, when disclosures are accessed electronically by borrowers, the Actual Received Date in the LE will be populated based on whether the borrower provided eConsent prior to them accessing the disclosures or not:

• If consent is obtained prior to disclosures being sent, the Actual Received Date for the borrower and co-borrower will be populated when the borrower or co-borrower accesses the disclosure package (existing behavior) or
• If prior consent status is No or has not been received, the Actual Received Date for the borrower or co-borrower will be populated as long as either the borrower or co-borrower provide consent and accesses the disclosure package on or before the LE Due Date. This is new behavior.
• The Actual Receipt Date will be left blank in the following scenarios:
  • The borrower (or co-borrower respectively) never accesses the disclosure package
  • If the borrower or co-borrower accesses the disclosure package after the LE Due Date when prior consent status was No
  • If there is no LE Due Date populated

Please note that this new behavior impacts electronic disclosures only. Disclosures sent by any other method (e.g. in person, by mail, etc.) will persist as they did in earlier versions of Encompass and the Actual Received Date will be populated accordingly. For loans started in previous versions of Encompass where disclosures have not been sent, this new logic will be used. For loans started in previous versions of Encompass that do have disclosures, the previous logic will continue to be used for those loans.