An issue occurred where the PMI Coverage (field ID ULDD.FNM.430) field was cleared when the loan was locked. If a value was entered in the PMI Coverage field, the loan was locked (Get Pricing or manual lock), and then the lock was confirmed, the value in the PMI Coverage field was cleared. This issue has been resolved and the value in the PMI Coverage field now remains when the loan is locked.

The 203H option now functions properly when selected from the SOA dropdown list (Field ID 1039) on a custom form. Previously, when an Encompass user selected 203H from the dropdown list on a custom form, the selection displayed as 203 on the FHA Management, FNMA Streamlined 1003, HUD 1003 Addendum, HUD-928005b Conditional Commitment, HUD-92900LT FHA Loan Transmittal, and VA 26-1806 Reasonable Value input forms. Additionally, when 203H was selected on a standard input form, the selection was cleared from the SOA dropdown list on any custom forms. This issue has been resolved and 203H now display correctly on all SOA dropdown lists in Encompass when selected on a standard or custom input form.

Workaround Information:

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

• Open the custom form in the Input Form Builder and complete the following tasks:

  1. Select the dropdown box for the SOA field.

  2. In the Properties window, under Data, click Options.

  3. Click the button on the right to open the Dropdown Options Editor window.

  4. Double-click the entry in the Value column for 203H, and change the value to 203H.

  5. Click OK.

Prior to this release, when a loan was removed from a correspondent trade (AOT, Direct Trade, or Forwards) on or after the Trade Expiration Date, the system updated that loan’s lock status to “Cancelled”. With this release, when a loan is removed from a correspondent trade, that loan’s lock status is updated to “Cancelled” only after the Trade Expiration Date. If the loan is removed on the Trade Expiration Date, the loan’s lock status reverts back to “Not Locked”.

The loan is still considered “Not Locked” even if the loan has been Submitted for Review when removed on the Trade Expiration Date.

An issue occurred where trades (loan or correspondent) and MBS pools with a number of loans (150 – 200) assigned to them took several minutes to save. This issue has been resolved and the save time has improved.

In order to determine what features and tools a user will have access to, the administrator can assign the appropriate persona to the user, and then they can also specify personalized security settings for the user which enables the administrator to customize the default persona rights. An issue occurred where administrators would customize the user’s rights for the Move Loans feature, but then discover that the new rights they assigned were not being retained by Encompass. As shown below, administrators can select the loan folders that the user has permission to move loans from and move loans to. However, the selections made by the administrator in the Select Loan Folders windows were not being saved or enforced by Encompass. This issue has been resolved and the selections made by the administrator here are now retained as expected.

Workaround Information:

The following workaround provided for this issue and is no longer required for Encompass 18.4 and later:

1. Create a new Persona
2. Assign appropriate "Move" rights to the new Persona
3. Assign new persona to impacted users

Admins can also attempt to save the modified Persona settings a second time to try and retain the updated rights.

When configuring business rules, administrators can specify Encompass fields that will trigger the rule and specify fields as conditions for the rule. An issue occurred where fields that are “not reportable”, which are fields that are not visible on input forms or tools, and cannot be included in Encompass reports, but are necessary components of certain internal system calculations and functionality, were being added to business rules but they were not being saved and retained in the setting. For example, if an administrator added field DENIAL.X64 to a Field Triggers business rule setting and then saved this update to the setting, the field would not be indicated as part of the rule the next time the administrator accessed this setting because the system was not retaining this settings update. Starting in Encompass 18.4, fields that are “not reportable” can be added to the Field Triggers, Print Auto Selection, and Loan Form Printing business rule settings and they will be retained in the settings as expected.

An issue occurred where the Access to all loans in the same level setting in the User Details setting was not functioning correctly. If an internal Encompass user was listed as a “TPO Sales Rep” or “Account Executive” on an External Organization, that user had access to all loans associated with that TPO company. If another Encompass user account was placed within the same internal company Organization folder, the second user had access to the same TPO company loans even though that user was not a “TPO Sales Rep” or “Account Executive” with any TPO company and the Access to all loans in the same level setting was disabled. This issue has been resolved and if the Access to all loan in the same level setting is disabled, a user cannot access TPO company loans associated with the other Encompass user accounts within the same Organization folder.

The Encompass system and the Encompass Software Development Kit (SDK) perform the Loan Open and Loan Lock operations in two separate API calls. Prior to the update being introduced in this release, when a user opened a loan file through the Encompass SmartClient or the Encompass SDK, the loan would be opened and then “locked” to prevent modifications from other users. However, it is possible for another user, say User A, to have modified and closed the loan in between the time the same loan is opened and locked for another user, say User B. The effect of this would be that User B would unknowingly be working with a stale copy of the loan. When User B went to save the loan, Encompass would reject the save, saying that there is a newer version of the loan file available, namely the one that User A saved, and therefore they could not overwrite it.

To resolve this issue, the Encompass system and the Encompass SDK have been updated to ensure that the Loan Open and Loan Lock operations are performed in the proper sequence. When a user opens a loan, the Loan Lock operation is now performed prior to the Loan Open operation. This ensures that when a user successfully opens a loan, they will be working the latest copy and will have their saves succeed.

Please note – there are two different Open methods that can be used in the Encompass SDK:

• Open (string guid)
• Open (string guid, bool loanlock, bool exclusive)

In order to get this new fix in your Encompass SDK instance, the following method should be used: Open (string guid, bool loanlock, bool exclusive)

The following DLL files are now included in the Encompass SDK Installer package:

• GdPicture.NET.10.dll
• GdPicture.NET.10.filters.dll
• GdPicture.NET.10.image.gdimgplug.dll
• GdPicture.NET.10.PDF.dll
• itextsharp.dll

The addition of these files will help prevent Unhandled Exception errors that some users encountered when attempting to attach PDF files (and other file types) to the eFolder via the Encompass SDK.

An issue occurred in testing environments where all of the configurable workflows in the Configurable Workflow Templates setting that were created in Encompass 18.3.0.8 (or earlier) were cleared out from the setting when Encompass was upgraded to version 18.4. This issue has been resolved.

An issue was resolved that resulted in the Lock Request Form tool not being updated when changes were made to relevant fields on the Subordinate Mortgage Loan Amounts pop-up window in a loan file. This resulted in incorrect LTV, CTLV, and HCLTV ratios being calculated on the Lock Request Form tool. This issue has been resolved and changes in the following loan file fields are now being updated in the corresponding Lock Request fields.

• Updates to the Closed End Primary Mortgage Total (field ID 427) on the Subordinate Mortgage Loan Amounts pop-up window now trigger an update to the 1st Mortgage amount (field ID 3035) on the Subordinate Mortgage Loan Amounts pop-up window on the Lock Request Form tool.

• Updates to the Closed End Subordinate Mortgage Total (field ID 428) on the Subordinate Mortgage Loan Amounts pop-up window now trigger an update to the 2nd Mortgage amount (field ID 3036) on the Subordinate Mortgage Loan Amounts pop-up window on the Lock Request Form tool.

• Updates to the Total Open End (HELOC) Draw Amounts (field ID CASASRN.X167) on the Subordinate Mortgage Loan Amounts pop-up window now trigger an update to the HELOC Actual Balance (field ID 3846) on the Lock Request Form tool.

Administrators can configure a Persona Access to Loans business rule that provides loan officers with custom access to loans. For example, they can set up a rule where a loan officer can edit a loan task, but only view the Conversation Log, not edit it. There are numerous custom access options that can be configured for loan officers. When a rule like this is active and a loan officer attempts to open a loan file, a warning message is triggered that informs the loan officer that access to the loan file is limited and the actions they can take on the loan file is listed for them. In Encompass 18.4, this warning message was no longer being triggered for loan officers when the business rule was active. This issue has been resolved so that the warning message informing the loan officer of their “custom” access to the loan is once again being provided for them.

As part of the new Dynamic Data Management (DDM) tool, administrators can set up scenario-based fee rules and field rules to automate fee and field data population rather than using templates and field triggers business rules. The tool is designed that once you have created a fee rule or a field rule in your test or lower environment and validated it, you can then export it and then import that rule in your production environment. However, it was discovered in the 18.4 test environment that when users attempted to export a field rule they received the following Application Error: 

Application Error: 

An error occurred. Please contact the administrator with the following information: 

One or more errors occurred.

This issue has been resolved so that users can now export field rules successfully using DDM, and this error message is no longer triggered.

In the Encompass 18.4 release, a race condition issue that was occurring in Encompass 18.3 (and earlier) between Loan Open and Lock Operations was addressed (as discussed in the Update to Address Race Conditions Issue That Occurs Between Loan Open and Loan Lock Operations entry on this Fixed Issues page.) Normally, Encompass SDK programs that try to lock an already locked loan will get an EllieMae.Encompass.BusinessObjects.Loans.LockException exception. However, it was discovered in Encompass 18.4 test environments that using the Loan.Open method with the lock flag set to 'True' would instead throw an internal EllieMae.EMLite.ClientServer.Exceptions.LockException exception. Clients capturing and acting on the previous Exception type from Encompass 18.3 and earlier would see their SDK processes fail after upgrading to Encompass 18.4. To address this issue, the exception generated from a Loan Open operation in these circumstances has been changed to throw the EllieMae.Encompass.BusinessObjects.Loans.LockException that clients have been handling in prior versions.

To limit user access to the Piggyback Loans Tool, the following buttons on the new Subordinate Mortgage Loan Amount pop-up window can now be controlled via Persona Access to Fields business rules: Link to Loan (field ID BUTTON_Link to Loan), Add New Closed End (field ID BUTTON_Add New Closed End), Add New HELOC (field ID BUTTON_Add New HELOC), and Remove Link (field ID BUTTON_Remove Link).

An issue was resolved that caused blank space to print on the Funding Worksheet output form in the section that includes the list of fees that are excluded from the wire amount. This issue has been corrected and the excluded fees now print as expected on the Funding Worksheet output form.

An issue occurred in Encompass 18.4 for non-admin Encompass SDK users (i.e., users assigned with any persona besides Administrator or Super Administrator) where the QueryPipeline was not returning the correct number of loan results. In some cases, zero (0) loans were returned in the Pipeline for the non-admin users, but if they logged into the Encompass SmartClient, the correct number of loans were returned. In other cases, QueryPipeline returned some loans for non-admin users, but still significantly fewer loans than should have been returned. Users assigned with the Administrator or Super Administrator persona received the correct number of loans from QueryPipeline.

This issue has been resolved so that non-admin users now receive the correct loan results from QueryPipeline in the Encompass SDK.

An issue occurred in Encompass when attempting to save changes to certain loans that had been originated in, or modified by certain business rules, in Encompass TPO Connect, Encompass Consumer Connect, Encompass Loan Officer Connect, or Encompass Developer Connect. It was discovered that these Connect products were incorrectly evaluating business rules- specifically field triggers, rule conditions or custom field calculations- that were using the "@" operator within their Advanced Code. For example, [@762] Today. As a result, the business rules were populating the incorrect date into applicable date fields in the loan. These incorrect dates were considered invalid by the Encompass system's Reporting Database and Audit Trail. As a result, the following Application Error was triggered when attempting to save the loan in Encompass:

This issue has been resolved, and this error is no longer triggered when saving impacted loans in Encompass.

Please note: 

• The error triggered by the Audit Trail due to the invalid date is only one indicator that an invalid date has been populated to a loan: 

  • If a date field in a loan in a Connect product was modified by a business rule using a field trigger that uses the "@" symbol in an Advanced Code action, this code may have executed incorrectly and caused an unexpected result.

  • If a date field in a loan in a Connect product was modified by a field trigger that uses the "@" symbol in an Advanced Code condition of the trigger, the trigger may have run when it should not have or may not have run when it should have. As a result, the effect of the trigger may have been applied to the loan when it shouldn't have or may not have been applied when it should have.

• It is recommended that you evaluate your custom field calculations and field triggers in your Connect product to determine which are potentially affected and what the potential effect would be. You should then open each potentially affected loan (i.e., loans originated on or after October 14, 2018) and inspect the fields that could have been impacted and ensure they have the expected values.

• This issue did not affect Advanced Code in business rules executed within Encompass. It only affected loans that were modified by Advanced Code in business rules executed in the Connect product suite.