When duplicating a 2009 or 2020 URLA loan, the URLA version applied in the duplicate loan will match the URLA version used in the original loan with the following exception:

• If a Loan Duplication Template is used to create the duplicate loan, the new loan will use the 2020 URLA forms if the Trans Details Print 2003 Appl field (field ID 1825) is not included in the list of Additional Fields in the Loan Duplication template (Encompass > Settings > Loan Setup > Loan Duplication).

  

An issue was resolved that caused multiple blank VOE (Verification of Employment) records to be created when creating a duplicate loan file by using a Loan Duplication Template that included repeatable VOE fields (for example, BE0202, BE0203, BE0204, BE0205, etc.). This issue has been resolved and Encompass no longer creates additional blank VOE entries under the scenario described above.

(Added on 4/30/2021)

An issue occurred where if a Persona Access to Fields business rule was activated where certain fields (field ID 3587, 3589, 3591, 3593, 3595, 3597, 3599, 3601, 3603, 3605, 3607, or 3609) were set to View Only/Disabled for All Personas, and then a non-Super Administrator user opened the Correspondent Purchase Advice Form and navigated to the Purchase Details section, the selected fields were disabled (greyed out) but the drop down buttons next to the fields were still enabled. If an option was selected, an error was generated. This issue has been resolved and now both the field and its drop down button are disabled.

(Added on 5/6/2021)

For loans using the new URLA forms, an issue was resolved that caused an error message to displaywhen sending an eDisclosure package that contained only the new 1003 URLA form. The message indicated that there were no eSignable documents in the package for the borrower, co-borrower, or both.

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

(Added on 4/30/2021)

An issue occurred where manual price adjustments or SRP in the Secondary Lock tool that was not part (unchecked) of the Loan Data Synchronization for a loan trade bulk trade assignment was not included in the Total Sell Price (field ID 2295) calculation. This issue has been resolved and the Total Sell Price is now calculated correctly during loan trade bulk trade assignments.

(Added on 5/6/2021)

An issue occurred where the CreateTrade API allowed notes to be added to a correspondent trade without a date/time stamp. When a note without a date/time stamp was opened, closed, and then saved, that note’s description was blanked out. This issue has been resolved and a note without a date/time stamp will now either inherit the date/time when the trade is created or an error will be generated if the datetime format is incorrect.

When you select the Reg-Z Business Days Calendar option in the Compliance Calendar Setting (Encompass > Settings > Loan Setup > Compliance Calendar) the following dates now display as business days. Previously, these dates displayed as holidays:

• July 5

• December 24

• December 31

Additionally, December 25 now displays as a holiday. It was previously marked as a business day.

(Added on 5/14/2021) 

When a Field Data Entry business rule set up with Advanced Code that referenced 'CurrentUser' was triggered when the rule criteria was met, the following error was returned and the rule did not execute as expected in Encompass LO Connect: 

Loan can't be saved due to the following validation error(s): Advanced Code Definition execution failed.

Additionally, for loans where this type of Field Data Entry business rule was set up to order Encompass eClose, the following error was returned in Encompass LO Connect when the business rule was triggered : 

Forbidden - User does not have permission to perform this operation on entity "userid" with identifier.

The issues resulting from using 'CurrentUser' in Advanced Code for the business rule have been resolved and these errors are no longer returned.

Administrators can use the Milestone Completion tool to set up rules that define and manage requirements or tasks that must be met before a milestone is finished. They can specify a condition for applying the rule, documents that must be received, and fields that are required. However, an issue occurred with required tasks where these tasks were not being enforced correctly in loans when milestone completion rules with required tasks were imported or exported from one Encompass environment to another. When the imported/exported milestone completion rule was viewed from a Milestone Worksheet in a loan, required tasks were not displayed with red asterisks like they were prior to the rule being exported or imported. Since these tasks were no longer indicated as ‘required’, loan team members could complete milestones without finishing the required tasks. The only way for the tasks to display as ‘required’ as they should have was to open the milestone completion rule, save the loan, and then re-open the rule. This issue has been resolved so that required tasks are now correctly indicated as required in imported or exported milestone completion rules with a red asterisk and the rule is enforced accordingly.

An issue occurred for administrators utilizing the Settings Sync Tool where the following Application Error was triggered when attempting to sync Milestone Completion business rule settings:

An error occurred. Please contact the administrator with the following information: Object does not exist.

The cause of this issue was identified and addressed. This error is no longer triggered when syncing Milestone Completion business rule settings.

(Updated on 6/11/2021)

An issue with Underwriting Condition details in the eFolder not being saved in specific scenarios has been resolved. If the eFolder window was already opened in a loan file, and users proceeded to order automated underwriting (DU or LPA), receive the findings, return to the eFolder to open a condition and update the Description field and the Tracking status checkbox(es), and then attached the underwriting findings document to the condition, the updated description and Tracking checkbox selections were not retained after the user closed the eFolder, and then re-opened the eFolder and returned to the Underwriting Condition Details window.

As part of the fix to retain the condition Description and Tracking as expected, the following message displays when you submit your loan to an Automated Underwriting Service (AUS) and the submission is paused:

The service you are running has updated the loan file data. Encompass will close eFolder to prevent data loss.

After you click OK to close the notification window, the eFolder is automatically closed, and you need to re-run the AUS to continue your loan submission to DU, LPA etc.

(Added on 4/30/2021)

An issue occurred where if Auto-Lock and Shut Down Lock Desk (Temporary) were enabled, and then a lock request was submitted via EPPS, a message was erroneously displayed in Encompass that the lock was successfully confirmed. This issue has been resolved and now no message confirming the lock is displayed when both settings are enabled.

(Added on 5/6/2021)

An issue occurred where if the Allow ONRP for Cancelled/Expired Locks setting on the Company Details ONRP tab was not selected, and then a re-lock request for an inactive lock was submitted during the ONRP window, that lock request was submitted successfully. This issue has been resolved and when the Allow ONRP for Cancelled/Expired Locks setting is selected, the lock request is now denied.

An issue occurred where an administrator could configure a Persona Access to Fields business rule to disable the Loan Program field (1401) for a specific persona, however users assigned with this persona could bypass the rule by applying a Loan Program template via the Lookup (magnifying glass) icon for the Loan Program field. This could result in incorrect data being applied to the loan, as the pre-requisite conditions to populate data from the Loan Program template is not validated by Encompass.

In order to prevent a persona from updating field 1401, a Persona Access to Fields Business Rule can be set up to prevent access to both field 1401 and the Lookup icon. (In earlier versions of Encompass, the option to restrict access to this Lookup icon was not provided in the rule settings.) When setting up the rule, indicate Button_loanprog as the field to add to the rule (as shown below) and then set the persona's access level. Administrators can elect to restrict access to field 1401 or the Lookup icon or both.

Workaround Information:

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

• Without applying the data through Loan program template, user has to manually provide the data. In such case, system checks the pre-requisite field condition and presents the message to the user.

Administrators can manage which users have permission to delete or export TPO Contacts listed in the Encompass > Settings > External Company Setup > Company Details > Third Party Contacts panel by configuring access to these two actions in the Company/User Setup > Personas > External Settings > settings screen. However, an issue occurred where personas without access to these two actions could still perform these actions. These action icons would be disabled/greyed out as expected in the Third Party Contacts panel for personas without permission to perform these actions, however, if the persona right-clicked on a TPO Contact in the list, these actions were enabled in the right-click menu, and the persona could perform one or both of these actions by selecting them from the menu. This issue has been resolved so that the right-click menu actions are enabled/disabled as expected according to the persona settings configured by the administrator.

Workaround Information:

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

• Client would utilize the TPO AE persona and add themselves as an additional Sales Rep / AE to that company.

(Added on 5/24/2021)

An issue was resolved that resulted in slower performance times when a file attachment was opened and then closed in the eFolder Cloud Viewer (the new document viewer recently developed by ICE Mortgage Technology). This occurred because the Chromium browser used by the viewer was generating a debug file when a document was closed, even if Encompass was not running in debug mode. This issue has been resolved. The Chromium debug process is now disabled when Encompass is not running in debug mode.

(Added on 5/24/2021)

If you are utilizing the Encompass SDK, upgrading to the new SDK package for 21.2.0.1 is required to receive this fix.

An issue was resolved that intermittently caused one of the following error messages to display when a Secondary/Lock Desk Manager accessed the Optimal Blue website and attempted to push a lock confirmation back to Encompass:

• Retry

• Object reference not set to an instance of an object

If the user tried again, the push would eventually succeed. This issue has been resolved. The error messages no longer display, and the lock confirmation is successfully loaded into the eFolder.