Fixed Issues for Version 18.2

View or print the PDF version

 

Why we fixed these issues: These issues were fixed to improve usability and to help ensure Encompass is operating as expected. The issues that are chosen to be fixed are based on the severity of their impact to clients and client feedback.

Encompass Forms and Tools

An issue has been resolved that caused the Use Alternate checkbox (field ID LE2.X28) to not be selected in a loan file that was created using a Loan Template Set that included a Loan Programs template and a Data template with the checkbox selected.

This issue has been resolved and the Use Alternate checkbox (field ID LE2.X28) is now being applied properly from a Loan Template Set that included a Loan Programs template and Data template with the checkbox selected.

Workaround Information:

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

  • Create a Custom Alert where when Loan Purpose (field ID 19) is Cash-Out Refi or No Cash-Out Refi and Use Alternate (field ID LE2.X28) is not checked, require Use Alternate (field ID LE2.X28) be checked. Alert will clear once complete.

CBIZ-13166

An update has been made to remove the 2015 Itemization mapping requirement for MLDS fees in a Data Template for California loans covered by the Know Before You Owe rule. Prior to Encompass 18.2, when starting a loan using a Data Template or when applying a Data Template to a loan for a Subject Property in California, fees on the MLDS form in the Data template would override existing fees on the 2015 Itemization for loans subject to the Know Before You Owe Rule. This behavior was implemented because California loans were required to map fees from the MLDS to the 2015 Itemization. Under the Know Before You Owe rule, the MLDS form is no longer required for loans on subject properties located in California.

Loans not covered by the Know Before You Owe rule or supported through the 2010 Itemization continue to use the existing MLDS fee mapping process.

CBIZ-13551

An issue has been resolved that caused the descriptor field at the bottom of the Loan Estimate column (field ID CD3.X92) in the Calculating Cash to Close section on the alternate Closing Disclosure Page 3 to incorrectly display To Borrower when it should have displayed From Borrower. This would occur for loans that were disclosed with payoffs and payments that exceeded the loan amount, and then redisclosed later with adjusted payoffs and payments that did not exceed the loan amount.

This issue has been resolved and From Borrower now displays for loans under the conditions described above.

Workaround Information:

The following workaround was provided for this issue and is no longer required for Encompass 18.2 and later.

  • Lock the Total Payoffs and Payments (K) (field ID CD3.X90) to change the value to From Borrower.

CBIZ-14160

A typo was corrected on line 3A on the FHA 203(K) tab on the FHA Management input form.

  • Corrected Description: Sum of Step 2E + Step 1E (i.e. Adjusted As-Is Value + Step 1 Total)

  • Previous Description: Sum of Step 2E + Step 1D (i.e. Adjusted As-Is Value + Step 1 Total)

CBIZ-14095

An issue was resolved that caused the total borrower-paid fees (field ID NEWHUD2.X44) that display in the section 1200 header and the total for the Recording Fees and Other Taxes (field ID NEWHUD.X607) in line 1201 on the 2015 Itemization input form to not update correctly when one of the 1200 section fields included in the total fields was updated via a business rule. This issue has been resolved and the totals are now updating correctly when a business rule triggers a change in one of the fields that are included in the total.

Workaround Information

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

  • Manually set the total borrower-paid fees (field ID NEWHUD2.X44) to the sum of all fields in the 1200 section of the 2015 Itemization.

CBIZ-14707

An issue occurred where an error message was generated when the “Construction” option was selected as the Purpose of Loan (field ID 19) on the Current Loan Info tab on the Secondary Registration screen. This issue has been resolved and the error message is no longer generated when “Construction” is selected as the loan purpose.

SEC-12235

An issue occurred when multiple Payment transactions were added on the Interim Servicing Worksheet. On the last Payment transaction, only dates and the Interest Rate was entered. This issue has been resolved and the Total Amount Due, Principal, and Interest amounts are now calculated and entered on the Payment transaction.

SEC-2216

An issue occurred where an error was generated because the selection for field ID 1811 and field ID 2950 did not match on the Compare with Current Loan Data pop-up window (field ID 1811 was “Investor” while field ID 2950 was “Investment”). This issue has been resolved and both fields now use “Investment” as their selection.

SEC-10243

An issue occurred where the Comments on the Lock Request Form were overwritten by the Program Notes after a loan was priced via the Encompass Product and Pricing Service (EPPS), and then updated in Encompass. This issue has been resolved and the program notes will now be appended to the comments.

SEC-12630

An issue occurred where the Lock # Days on the Secondary Lock Tool was recalculated if it was modified when submitting current pricing via the Worst Case Pricing Tool. This issue has been resolved and the Lock # Days is no longer recalculated.

SEC-12856

Construction Loans

The following update has been made to the calculation for the As Completed Appraised Value (CONST.X59) to ensure that the correct LTV ratio is being calculated for loans with the Construction or Construction – Perm option selected for Purpose of Loan (field ID 19):

  • When an amount is entered or modified for the Appraised Value (field ID 356), the As Completed Appraised Value (CONST.X59) is populated with the Appraised Value.

  • When no Appraised Value is entered, the As Completed Appraised Value is calculated by adding the Present Value of Lot (field ID 22) and the Cost of Improvement (field ID 23).

Previously, the As Completed Appraised Value (CONST.X59) was always calculated by adding the Present Value of Lot (field ID 22) and the Cost of Improvement (field ID 23), even when an amount was entered for the Appraised Value (field ID 356).

When updating to Encompass 18.2, the As Completed Appraised Value (CONST.X59) field is locked for an existing Construction or Construction-Perm loan file to prevent the ratio from being recalculated. Click the gold Lock icon provided for field CONST.X59 to trigger a recalculation of the value to apply the new calculation

CBIZ-11609

FNMA File Imports

An issue was resolved that caused the Apply Actual Payment Change checkbox (field ID PAYMENTTABLE.USEACTUALPAYMENTCHANGE) on the Projected Payments table on the Loan Estimate Page 1, RegZ-LE, Closing Disclosure Page 1, and RegZ-CD input forms to be selected by default when creating a new loan by importing a FNMA loan file. This issue has been resolved and the checkbox is no longer selected when a loan file is created by importing a FNMA loan file.

The Apply Actual Payment Change checkbox is visible only when the ARM option is selected for the Amortization Type (field ID 608).

Workaround Information

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

  1. Create a data template.

  2. In the data template, select ARM for the Amortization Type (field ID 608).

  3. On the RegZ-CD input form, select the Apply Actual Payment Change checkbox, and then clear the checkbox.

  4. Clear the ARM option for the Amortization Type.

  5. Save the data template

  6. Add the newly created data template to a loan template.

  7. Import a Fannie Mae loan file.

  8. On the Import from Fannie Mae window, apply the loan template created above.

  9. The cleared value in the Loan Template for the Apply Actual Payment Change checkbox is copied into the newly created loan file.

CBIZ-14738

Encompass Pipeline

Some clients reported receiving the following error message when they attempted to access a loan from the Encompass Pipeline:

"The selected loan has been deleted or is no longer accessible."

It was determined that the database (what the client sees in the Pipeline view) was showing the loan in one loan folder location, but the File Server was showing the loan in a different loan folder location. This variance resulted in the error message being triggered. This issue has been resolved.

This issue was originally resolved in the Encompass 17.3 August Service Pack. However, the relevant code for this fix had to be rolled back in the ensuing Encompass 17.3 August Service Pack Critical Patch 3 release because the new code actually introduced a different issue.

Workaround Description

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

Work-around A:

- Have the client first rebuild the loan folder that the loan shows up in the Pipeline view.

- Next, rebuild the loan folder where the file server shows the loan.

Work-around B:

- Contact Ellie Mae to move the loan on the file server to the loan folder that the loan shows in the Pipeline view.

CFUN-6024

Encompass Reports

In the Encompass Reporting Database, the VA Loan Summ Cred Score field (field ID VASUMM.X23; credit score for decision making) is listed as a String. If a user enters, for example, 1000 as the credit score, Encompass will automatically put a comma after the 1 (1,000). This leads to errors like this one being triggered when generating reports:

To help alleviate this occurrence, users can no longer enter a comma in this VASUMM.X23 field in the loan file.

CFUN-10729

When running reports to generate Business Contact information, some users received the following Exception error when at least one business contact included in the report was associated with multiple loan files:

“This report could not be generated due to the following error: Report failed due to an error: Error executing query: Violation of PRIMARY KEY constraint 'PK_#contact_5C####'. Cannot insert duplicate key in object 'dbo.#contact_ids'.

This issue has been resolved and the reports for Business Contacts can now be generated successfully.

CFUN-11036

Trade Management

An issue occurred when the Eligible Loans filter on the Correspondent Trades Details tab was switched from “Simple” to “Advanced” to “Simple” again. If switched during one session, the Note Rate data was cleared. If switched after a session is saved, the EPPS Loan Programs were cleared and the Note Rate data was cleared. This issue has been resolved and when the Eligible Loans filter is switched, the EPPS Loan Programs and Note Rate data remain.

SEC-12829

Encompass Settings

An issue occurred where the Persona Access to Fields business rules set up to prevent user access to the Lock icons on lines 901 and 902 on the 2010 and 2015 Itemization input forms were not being enforced. When the rule was configured to give specific personas “View Only” rights to these Lock icons, users with this persona were still able to click these Lock icons on the form. This issue has been resolved and when this type of business rule is set up to give specific personas “View Only” access to these Lock icons, they are disabled on the 2010 and 2015 Itemization for these users.

When setting up this rule, the Lock icon on line 901 is field ID LOCKBUTTON_L245 and the Lock icon on line 902 is field ID LOCKBUTTON_337.

NICE-6881

An issue with Field Triggers business rules and custom calculated fields was discovered where the rules were not triggering correctly. When the business rule was set up to trigger and initiate an action when a custom field- that is also a calculated field- was changed, the rule was not triggered when the field was changed manually (i.e., a user manually changed or entered data in the field). This issue has been resolved and Field Triggers business rules set up to trigger based on manual changes to a custom calculated field are now triggering as expected.

A custom calculated field is a field that has been configured with a custom calculation that is an expression that returns a number or text value which is then saved into the field.

NICE-8161

Additional Update

An issue was resolved that loans created by duplicating an existing loan to copy the Universal Loan ID (field ID HMDA.X28) from the original loan file instead of creating a new Universal Loan ID (ULI) for the duplicated loan file. This issue has been resolved and duplicated loan files are now created with their own unique Universal Loan ID.

Workaround Information:

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

  • Click the blue Lock icon next to the Universal Loan ID (field HMDA.X28). The icon will turn blue. Click the icon again to update the Universal Loan ID.

CBIZ-14466

 

Fixed Issues for Version 18.2.0.1 Server Patch 1

This update contains updates to users' Encompass client machines (18.2.0.1) and a Server Patch (server patch 1) that is applied to the Encompass Server. The fixed issues listed below are all included in this update.

The client-side update 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 this update upon their initial log in of Encompass following the release.

Please note that 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.

In Encompass, go to Help > About Encompass in the menu bar to view your Encompass version. Once you upgrade, your new version number will be 18.2.0.1 Server Patch 1.

The Encompass SDK (Encompass Software Development Kit) has been repackaged with this 18.2.0.1 update. Although it is not required, it is strongly recommended that you upgrade to this latest SDK delivered with this update to ensure the same functionality that is in this latest version of Encompass is also available in your SDK. If your SDK application utilizes the Encompass SmartClient, you can automate this process so the SDK is upgraded automatically every time you apply an Encompass release. If your SDK application is installed on a computer at your location, you must manually upgrade the SDK for every release. For instructions for automating the upgrade process or manually upgrading the SDK, refer to the Upgrading the Encompass SDK page or view the SDK Programmer’s Guide.

Again, upgrading to this latest SDK package is strongly recommended, but not required, for this 18.2.0.1 update.

Visit the Encompass SDK Install Files page to access the SDK install files for this release.

Updates to the Encompass Server (i.e., Server Patch 1)

These are the 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.

Organization/ Users Folder Hierarchy in Encompass Settings

Encompass administrators use the Organization/Users tool in Encompass Settings to establish and maintain a hierarchy of their company and its branches, as well as users within each branch. When you create your organization hierarchy, you will typically add an organization for each branch office or job function. You will then add your users to the appropriate organization. A user's ability to access other users' loan files depends on the position within the organization hierarchy. An issue with this organization hierarchy was resolved that caused Encompass users to lose their ability to view or access loans assigned to other Encompass users who were moved into a newly created organization folder that was placed further down in the same branch of the organization hierarchy. This issue has been resolved and Encompass users can now access and view loans assigned to other Encompass users below them in the organization hierarchy.

NICE-7948

An issue was resolved that prevented an Encompass administrator from deleting an Encompass user who had been assigned to a user group with access to other user’s loan files. Attempting to delete the user would result in an Application Error message. The error message would display only when the user was an individual user who had been added to the group. The error message would not display if the user was included in a hierarchy folder that had been added to the User Group. This issue has been resolved and administrators can now delete these users in this scenario.

NICE-7711

Encompass Reporting Database

Encompass now provides a more graceful handling of connection exceptions when administrators are rebuilding the Encompass Reporting Database. This updated process prevents the Encompass Server from crashing when connection exceptions occur. Previously, users would be disconnected when this occurs, and would be prompted to reconnect.

NICE-8275

An issue was resolved that caused values to be cleared in the Encompass Reporting Database for fields that record the most recent rate lock values for a loan. This issue affected fields that begin with the following prefixes:

  • LOCKRATE.
  • LOCKRATE3.
  • LOCKRATE.CONFIRMED.
  • LOCKRATE.DENIED.
  • LOCKRATE.REQUEST.

This issue has been resolved and the Encompass Reporting Database fields are now being populated with the correct values for the most recent rate lock values.

SEC-13350

Updates to the Encompass Client Machines

The following items are all 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 this update upon their initial log in of Encompass following the release.

HMDA Updates

Visit the HMDA Support page for helpful resources about the HMDA changes going into effect in 2018, 2019, and 2020 including field reference guides, FAQs, webinars, instruction guides, and more.

An update was made to the logic used to populate HMDA values for Total Loan Costs (field ID HMDA.X77), Total Points and Fees (field ID HMDA.X78), Origination Charges (field ID HMDA.X79), and Discount Points (field ID HMDA.X35) to ensure that the appropriate values are populated based on whether a loan uses the RESPA 2010 or RESPA-TILA 2015 forms.

The fields are now populated with NA unless the loan meets all the following conditions:

  • The loan is not a reverse mortgage (field ID HMDA.X56).

  • The loan is not an open-ended line of credit (field ID HMDA.X57).

  • The loan is not primarily for a business or commercial purpose (field ID HMDA.X58).

  • The loan is not exempt from RegZ Ability-to-Repay requirements (field ID QM.X103).

  • The loan has either Active Loan, 1. Loan originated, or 6. Purchased loan selected for the Action Taken (field ID 1393).

For loans that meet these conditions and are using the 2010 forms:

  • Total Loan Costs (field ID HMDA.X77) is populated with NA.

  • Total Points and Fees (field ID HMDA.X78) is populated with 0 or the total Section 32 points and fees (field ID S32DISC.X48), whichever is greater.

  • Origination Charges (field ID HMDA.X79) is populated with 0 or the Your Adjusted Origination Charges for HUD-1 (field ID NEWHUD.X796), whichever is greater.

  • Discount Points (field ID HMDA.X35) is populated with the discount amount paid by the borrower or is left blank if the borrower does not pay discount points.

For loans that meet these conditions and are using the 2015 forms:

  • Total Loan Costs (field ID HMDA.X77) is populated with 0 or the Loan Costs (field ID CD2.XSTD), whichever is greater.

  • Total Points and Fees (field ID HMDA.X78) is populated with NA.

  • Origination Charges (field ID HMDA.X79) is populated with 0 or the Section Total A (field ID CD2.XSTA) from section D on the closing Disclosure Page 2, whichever is greater.

  • Discount Points (field ID HMDA.X35) is either populated with the sum of the borrower-paid PAC and POC fees (field IDs NEWHUD2.X935 and NEWHUD2.X936) from the Fee Details pop-up window for line 802e on the 2015 Itemization input form, or is left blank when the borrower does not pay discount points.

For more detailed information about the logic used to populate these fields in different scenarios, please refer to the Additional Mapping Logic tab in the HMDA Data Field Reference Guide.

CBIZ-16085

An issue was resolved that causes the HMDA Profile field value (field ID HMDA.X100) and the LEI [Legal Entity Identifier] field value (field ID HMDA.X70) to not be applied to a loan file that was imported from Encompass WebCenter or from a FNMA 3.2 loan file when multiple HMDA Profiles were configured in the Encompass Settings. The issue has been resolved and the HMDA Profile and LEI are now populating correctly for these types of imported loan files.

CBIZ-16428

Additional Updates

When working in the Construction Management form's Loan Info tab, the following error message was triggered after entering data in the following fields, navigating away from the form to a different form, and then returning to the Construction Management form: 

  • Purpose of Loan (field ID 19; Construction)
  • Number of Days (field ID 1962; 365/365 or 365/360)
  • Amortization Type (field ID 608; ARM)

Upon returning to the form, this error message was triggered: 

An error has occurred on the form: CreateControls method threw an exception.

In addition, if you then attempted to save the loan file- and the Estimated Closing Date field (field ID 763) did not contain a value- the following Application Error was triggered: 

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

The value 'NaN' is invalid for field '799'. The value 'NaN' cannot be converted to a numeric value.

The cause of these errors, which was introduced in the Encompass 18.2 release, has been identified and addressed. These errors are no longer triggering on the Construction Management form in these scenarios.

CBIZ-16620

An issue with rate locks has been resolved. In the scenario listed below, when a user then submitted a new lock request from the Lock Request Form, the new lock request submission would fail and a new lock snapshot was not being created:

  • The Auto-Lock setting was not enabled in the Encompass Settings.
  • A previous lock request was submitted, but not locked and confirmed.
  • The previous lock request had expired.

This issue, which was introduced with the Encompass 18.1 February Service Pack release, resulted in data from the previous lock request being cleared from the Lock Request Form when the new lock request was submitted, but the lock request submission failed and no new lock snapshot was created. The issue has been resolved. New lock requests are now being submitted and new lock snapshots are now created in this scenario.

SEC-13373

The Sell Side Total Price Adjustment (field ID 2273) amount on the Secondary Registration tool is no longer being increased by the value of Field 3529 on loans updated via a trade. The increase was triggered when the Price Adjustments option was cleared in the Loan Data Synchronization section of the Trade Management Setup setting, a loan was assigned to a trade, and the trade was then updated. This issue has been resolved and the Sell Side total Price Adjustment now retains its original value.

SEC-13370

An issue occurred with Field Triggers business rules configured to utilize advanced conditions for triggering the rule. Administrators and authorized users were able to create and save Field Triggers rules that included advanced conditions code in the rule to specify the conditions that must be met in order to trigger it. However, upon closing the Add/Edit Trigger window that is used to configure the rule or closing the Encompass Settings screen or logging out and lagging back into Encompass, the advanced conditions code for the business rule had been truncated in the Add/Edit Trigger window. This resulted in the rule not being configured properly and if the rule had been activated it resulted in the rule (and other associated rules) not triggering as expected. This issue has been resolved so that the original advanced conditions code entered for the rule now remains intact in this scenario and the rule operates as expected.

NICE-8694

 

Fixed Issues for Version 18.2.0.2

Updates to the Encompass Client Machines

This update includes the following fixes that are applied to users' Encompass client machines. This client update 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 this update upon their initial log in of Encompass following the release.

There is no impact to the Encompass SDK (Encompass Software Development Kit). A new SDK package has not been created for this release. Visit the Encompass SDK Install Files page to access the latest SDK install files.

In Encompass, go to Help > About Encompass in the menu bar to view your Encompass version. Once you upgrade, your new version number will be 18.2.0.2.

Why we fixed these issues: These issues were fixed to improve usability and to help ensure Encompass is operating as expected. These issues were chosen to be fixed based on the severity of its impact to clients and client feedback.

Electronic Document Management

An issue was resolved that resulted in borrowers being unable to select the attestation checkbox when eSigning the non-classic version of the Request for Copy of Tax Return (4506) or Request for Transcript of Tax (4506-T) form. The eSigning process would skip the attestation checkbox and move borrowers directly to the signature point for the form. This issue was introduced with the Encompass 18.1 release. The issue has been resolve and borrowers can now select the checkbox when eSigning the non-classic 4506 or 4506-T forms.

EDM-19240

An issue was resolved that caused the following ARM fields on the Adjustable Interest Rate (AIR) Table on the Loan Estimate Page 2 and the Closing Disclosure Page 4 to be blank when migrating an existing ARM loan from Encompass 18.1 to Encompass 18.2:

  • Margin (field ID 689)

  • Initial Interest Rate (field ID 3)

  • Max (field ID KBYO.XD2625) on the line for Min / Max Interest Rate

  • First Change (field ID 697)

  • Subsequent Changes (field ID 695)

This issue has been resolved and the ARM fields listed above are now populated correctly on the AIR Table for loans migrated after the Encompass 18.2.0.2 release. If you previously migrated ARM loans from Encompass 18.1 to 18.2 in a test environment and experienced this issue, complete the workaround described below. This workaround is not required for loans migrated after the 18.2.0.2 release.

Workaround Information:

  • Manually complete the ARM fields described above. Click the gold Lock icon next to the Min field (field ID 1699) to manually edit the Max field (field ID KBYO.XD2625).

CBIZ-16737

 

Proceed to Change Log

 

Go Back to Feature Enhancements