Fixed Issues for Version 18.1
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 occurred where the FHA MIP (field ID 3045) on the Lock Request Form did not match the Upfront MIP (field ID 1826). The current MIP calculation was rounding amounts to two decimal places instead of truncating to two decimal places. This issue has been resolved and the calculated upfront MIP amount is now truncated and field ID 3045 matches field ID 1826.
SEC-11957
An issue occurred where the Lock Expiration Date (field ID 2151) on the Secondary Lock Tool was incorrectly calculated on loans allocated to a correspondent trade after a revised lock. If the Lock Desk Setup Calendar settings excluded Saturday/Sunday, the Lock Desk Setup Expiration Settings used the next business day for expiration dates falling on an excluded day, and the expiration date for loans allocated to a correspondent trade after a revised lock fell on an excluded day, the Lock Expiration Date was updated to use the next business day instead of matching the correspondent trade’s Expiration Date (field ID 3912). This issue has been resolved and the Lock Expiration Date will now always equal the trade Expiration Date for loans allocated to a correspondent trade after a revised lock.
The Lock Expiration Date will also equal the trade Expiration Date for loans allocated to a correspondent trade after a re-lock for an active lock on the Lock Request Form.
SEC-12015
An issue occurred where the Lock # Days (field ID 2150) on the Secondary Lock Tool was incorrectly calculated on loans allocated to a correspondent trade. The Lock # Days was calculated by taking the difference between the Lock Expiration Date and Lock Date and then adding 1 day. This issue has been resolved and the Lock # Days will now be the difference between the Lock Expiration Date and the Lock Date for loans allocated to a correspondent trade.
SEC-12186
An issue was resolved that caused the you declined it checkbox (field ID DISCLOSURE.X913) for the escrow account to clear on the Closing Disclosure Page 4 input form when the Escrow Account Selected at Borrower’s Option checkbox (field ID DISCLOSURE.X339) was selected on the State Specific Information input form for Oregon. On Oregon State Loans, user should be able to select both checkboxes.
To address this issue, a new field ID was created for the Escrow Account Selected at Borrower’s Option checkbox (field ID DISCLOSURE.X1164) specifically for the State Specific Information input form for Oregon. Field ID DISCLOSURE.X339 continues to be used for the Borrower Elects to Establish Escrow Account checkbox on the State Specific Information input form for California.
CBIZ-10070
The field-level help that displays when you place your mouse pointer on the two checkboxes on the Connecticut State-Specific Disclosure Information input form (field ID DISCLOSURE.X1097) has been adjusted to display information that is specific to these fields on the Connecticut version of the form.
CBIZ-2901
The correct field-level help now displays when you place your mouse pointer on the second Net Profit or (Loss) field (field ID FM1084.X179) on line 3a on the 1084A Cash Analysis input form. Previously the field-level help displayed the definition for the first W-2 Income from Self-Employment field (field ID FM1084.X7) on line 1 of the 1084A Cash Analysis input form.
CBIZ-3534
Within the Dashboard, you can click the Manage Snapshots button to view a list of all current snapshots and then edit existing snapshots and add or remove them. An issue occurred when users would click a snapshot in the Snapshot list to view its details in the Snapshot Details section. After clicking one snapshot and reviewing its details, the Snapshot Details section was not being updated to show the details for the next snapshot that was clicked. As users clicked different snapshots in the list, the Snapshot Details section was not displaying the correct details. This issue has been resolved and the details for the currently selected Dashboard snapshot are now displayed.
North Carolina Compliance Report
An issue was resolved that cause blank values to be populated in the Property Type column on the North Carolina Compliance Report when the following options were selected from the Property Type dropdown list (field ID 1041) in Encompass:
-
Attached
-
Condominium
-
PUD
This issue has been resolved and the values are now populating correctly.
CBIZ-2434
Encompass Settings
Some clients received an application error related to the "timeout period elapsed prior to completion of the operation or the server is not responding" when attempting to delete an unused Organization folder from the Organization/Users hierarchy (in the Company/User Setup tool in Encompass Settings). This issue has been resolved and unused folders can now be deleted from this hierarchy successfully.
CFUN-8207
The Additional Information field (field ID SP.ADDITIONALINFO) from the Settlement Service Provider List input form can now be added to the Encompass Reporting Database.
To Add the Additional Information Field:
-
On your Windows task bar, click the Start menu or Start icon, navigate to the Ellie Mae Encompass program folder, and then click Admin Tools.
-
Double-click Reporting Database.
-
If you are prompted to log in to the server, type the User ID, Password, and Server that you use to log in to Encompass as the Admin user.
-
On the Fields tab in the left panel, type SP.ADDITIONALINFO in the Find Next field.
-
In the left panel, select the entry for SP.ADDITIONALINFO.
-
Click the Add button.
-
Click Update to update your database.
-
Click Yes to confirm the update.
-
Click Yes or No when asked if the newly added fields should be made accessible to all personas.
-
When the database has been updated, click Yes to populate the database.
-
Click OK in response to the completion message.
CBIZ-11090
- Error Triggered When Syncing Dashboard Snapshots - When users utilized the Encompass Settings Sync Tool and attempted to sync Dashboard snapshots between a local build and another Encompass instance, an Application Error was triggered and the syncing could not progress. The user was then forced to abort the process. This issue has been resolved and users can now sync Dashboard snapshots successfully.
-
Error Triggered When Syncing Personas – When migrating one or more personas from one Encompass system to another via the Encompass Settings Sync Tool, some users received the following error:
Internal error: Server stack limit has been reached. Please look for potentially deep nesting in your query, and try to simplify it. ---> System.Data.SqlClient.SqlException: Internal error: Server stack limit has been reached. Please look for potentially deep nesting in your query, and try to simplify it.
This issue has been resolved and this error is no longer triggered when syncing personas with the tool.
CFUN-2874
Access permissions for Encompass Consumer Connect are controlled by the Encompass Personas settings. An issue occurred where users who had not been granted full or partial access rights via their persona were still able to access the administration portal and website builder features and functions in Encompass Consumer Connect and make changes in these areas. This issue has been resolved and the persona settings for Encompass Consumer Connect are now being enforced as expected.
Encompass administrators can grant this access in Encompass Personas settings as follows:
- Loan Officer Persona – Grants partial access to the Encompass Consumer Connect administration portal. Users with this persona and Encompass login credentials can access the Incomplete Apps page in the Encompass Consumer Connect Administration portal to view any unsubmitted applications.
- CMS Admin – Grants administrator access to the persona. Permissions include full access to the administration portal and website builder features and functions. This is the only role that can create and delete sites.
- CMS Contributor – Grants partial access to the persona. Permissions include access to the Website Builder page of the administration portal. Users cannot create or delete websites and cannot access other pages in the administration portal.
CFUN - 9837
An issue occurred for clients with a large number of standard and custom input forms in their Encompass system. After updating a persona’s access rights to grant them access to one or more new forms and then clicking the Save icon to save these updates, they experienced latency in their system. The relevant code has been updated in Encompass to resolve this issue and the time Encompass takes to save these persona updates has been improved.
CFUN-10744
Encompass TPO Connect
The County field is now populating correctly in Encompass TPO Connect when importing FNMA 3.2 loan files that include the County field. Previously the County field (field ID 13) on forms such as the 1003 Page 1 was not being imported properly from a FNMA 3.2 file unless the loan was an FHA or VA loan. This issue has been resolved and the County field is now being imported properly into Encompass TPO Connect when the filed is included in a FNMA 3.2 loan file.
CBIZ-12198
Fixed Issues for Version 18.1.0.1 Server Patch 1
This update contains updates to users' Encompass client machines (18.1.0.1) and a Server Patch (server patch 1) that is applied to the Encompass Server.
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. 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. If you apply both of the client-side update and the Server Patch, your new version number will be 18.1.0.1 Server Patch 1.
The Encompass SDK (Encompass Software Development Kit) has been repackaged with this 18.1.0.1 Server Patch 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.1.0.1 Server Patch 1 update.
Visit the Encompass SDK Install Files page to access the SDK install files for this release.
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.
Updates to the Encompass Server (i.e., Server Patch 1)
A new Loan Purpose field (field ID HMDA.X107) has been created for use with HMDA 2018 loan information to enable lenders originating HMDA-reportable loans to accurately disclose the loan’s purpose. The new field is available in the Encompass Reporting Database.
Previously the HMDA Loan Purpose was populated from the same Loan Purpose field (field ID 384) used for NMLS Mortgage Call Reports. However, the HMDA 2018 reporting options include an expanded set of Loan Purpose options, some of which are not available on NMLS Mortgage Call Reports. To avoid mapping conflicts, this new field was created to record the HMDA 2018 Loan Purpose.
CBIZ-14788
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.
Because different loan scenarios use different property values in the LTV calculation, the logic for populating the Property Value (field ID HMDA.X85) used for 2018 HMDA reporting purposes has been updated to use the same valuation amount that is used to calculate the LTV for the loan file. Previously the HMDA Property Value was populated with the Appraised Value for the subject property.
Additionally, a new Property Value Not Relied Upon checkbox (field ID HMDA.X108) has been added to the Underwriter Summary tool. The new checkbox displays in the HMDA Factors Not Relied Upon in Decision section at the bottom of the form. The new field is available in the Encompass Reporting Database. If the underwriter does not rely upon a valuation in the underwriting decision for the loan, they may select this checkbox to indicate that the value was not used. This will populate the reporting value for HMDA Property Value (field ID HMDA.X85) to NA. In addition, if the HMDA Action Taken is Application withdrawn or File closed for incompleteness, Encompass will also report NA in HMDA.X85.
CBIZ-14722
When field ID 2949 (Appraised Value) on the Lock Request Form was modified with a new value, and then the loan was priced (using the Get Pricing button) or saved, the value in field ID 2949 reverted to the value in field ID 356 (Appraised Value). This issue has been resolved and field ID 2949 now retains the correct value.
SEC-12647
Fixed Issues for Version 18.1.0.2
This update contains updates to users' Encompass client machines (18.1.0.2).
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.
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.1.0.2.
The Encompass SDK (Encompass Software Development Kit) has been repackaged with this 18.1.0.2 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.1.0.2 update.
Visit the Encompass SDK Install Files page to access the SDK install files for this release.
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.
Updates to the Encompass Client Machines
The following updates have been made around the Rate Spread field (field ID HMDA.X15) used for 2018 HMDA reporting. This field indicates the spread between the loan’s APR and the APOR of comparable maturity.
-
To comply with the Final HMDA Rule reporting requirements (reference: 1003.4(a)(12)-7 and 1003.4(a)(12)-8), the field mapping logic for HMDA.X15 has been updated to take into account certain options that can be selected from the Action Taken dropdown list (field ID 1393) on the 2018 HMDA Information form. For 2018 HMDA reporting (i.e., 2018 is entered in the HMDA Reporting Year field (HMDA.X27)), if 3. Application denied, 4. Application withdrawn by applicant, 5. File closed for incompleteness, 6. Purchased Loan, or 7. Preapproval request denied is selected from the Action Taken (1393) dropdown list, NA will be automatically populated to the Rate Spread (HMDA.X15) field. NA will also be populated to the Rate Spread field when 1. Reverse mortgage is selected from the Reverse Mortgage dropdown list (field ID HMDA.X56). If any other options are selected for the Action Taken or Reverse Mortgage fields, then the Rate Spread field will remain an editable field. Authorized users can click the Lock icon for the field to enter a value or they can click the Rate Spread button on the 2018 HMDA Information form to calculate the rate spread and populate this field. In earlier versions of Encompass, NA was populated to the Rate Spread field only when 6. Purchased Loan was selected from the Action Taken dropdown list or 1. Reverse mortgage was selected from the Reverse Mortgage dropdown list.
-
An issue occurred where the Rate Spread field (HMDA.X15) was being populated with values with more than three decimal places (for example, 1.82000000) when an Encompass Compliance Service (ECS) review was run and the Rate Spread value was imported to the field. In addition, the rate spread did not match the rate spread amount calculated by the Encompass Compliance Service when the rate spread value went beyond three decimal places. This issue has been resolved so that the correct value is being imported from the ECS and the value is adhering to the HMDA Profile settings configured by the administrator. (Some users also reported the Rate Spread field being blanked out automatically when the ECS value should have been imported here. This fix resolves that issue as well.) Prior to this fix, if the Display Rate Spread to 3 decimal places option in the HDMA Profiles setting was set to Yes, the ECS imported value was still beyond three decimal places. If this setting was set to No, the rate spread value from ECS was not imported.
It is important to note that this fix to the Rate Spread value formatting issue has been addressed in Encompass as described above. However, starting on the evening of January 4, 2018 the HMDA Rate Spread Loan Enterprise Rule Reviewer in the ECS will be updated to only run on loans with a final action (originated, declined, withdrawn, closed, etc.) taken before January 1, 2018. The HMDA Rate Spread Loan Enterprise Rule Reviewer will be turned off for loans with a final action on or after January 1, 2018. (For more details about this update, refer to the ECS Rules February 2018 Critical Patch 1 release notes.) Therefore, while this reviewer is turned off, rate spread values will not be available to import from ECS into field HMDA.X15 for 2018 loans. The HMDA Rate Spread Loan Enterprise Rule Reviewer is scheduled to be turned back on in an upcoming ECS release in January to work with loans with a final action on or after January 1, 2018. Once this reviewer is turned back on, the fix to the Rate Spread field in Encompass 18.1.0.2 (and later) as described above will be evident.
-
Until the HMDA Rate Spread Loan Enterprise Rule Reviewer is turned back on, please go to the following CFPB/FFIEC website to obtain the applicable rate spread needed to complete field HMDA.X15 in Encompass for loans subject to 2018 HMDA reporting requirements: https://cfpb.github.io/hmda-platform-tools/rate-spread
-
For the prior Rate Spread Calculator for loans with a final action date before January 1, 2018, please go to the following CFPB/FFIEC website: https://www.ffiec.gov/ratespread/newcalc.aspx
CBIZ-12620, CBIZ-14945, CER-11929
An issue occurred on the FHA Management form’s FHA 203k tab. The Existing Debt on property being refinanced field provided on this tab in Encompass 18.1 was field 3052. However, the correct field to be provided here is field MAX23K.X132 (introduced in Encompass 17.3). This issue has been resolved. Since field MAX23K.X132 is a read-only field, an Edit icon is now also provided for this field. Click the Edit icon to open the 203k Existing Debt quick entry window. The values you enter in the quick entry window are calculated and automatically populated to field MAX23K.X132.
In Encompass 18.1:
In Encompass 18.1.0.2
An issue was introduced in Encompass 18.1 that prevented administrators and other authorized users from modifying individual user details, such as passwords, email address, their assigned persona, etc. in Encompass Settings. For example, when an administrator navigated to System Administration > All User Information, opened the User Details screen for a user, and then changed the user’s phone number, they could click the Save icon to save this change, but the Save function did not perform. The change was not saved and the administrator was forced to cancel out of the User Details screen. This issue has been resolved and now administrators can successfully update and save changes on the User Details screen as expected.
It is very important to note that this issue occurred only for those clients who had exceeded their licensed user limit in earlier (pre-18.1) versions of Encompass. For example, if the client’s licensed user limit was 100 users, but they had set up 105 users in Encompass 17.4, they would encounter this issue in Encompass 18.1 when they attempted to update and save changes on a User Details screen for a user. Going forward in Encompass 18.1.0.2, these clients will be permitted to save modifications to user details. However, they will not be permitted to enable an existing user or create a new user if they have met or exceeded their licensed user limit. For more information about this new enforcement of licensed user limits introduced in Encompass 18.1, refer to the New Notifications Provided When Clients Meet or Are Nearing Their Encompass User License Limits entry on the Feature Enhancements page in the Encompass 18.1 release notes.
Fixed Issues for Version 18.1.0.3
This update contains updates to users' Encompass client machines (18.1.0.3).
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.
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.1.0.3.
The Encompass SDK (Encompass Software Development Kit) has been repackaged with this 18.1.0.3 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.1.0.3 update.
Visit the Encompass SDK Install Files page to access the SDK install files for this release.
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.
Updates to the Encompass Client Machines
An issue was resolved that caused the HMDA Demographic Information indicator (i.e., the Use 2018 DI checkbox (field 4142)) to not remain cleared (i.e., un-checked) if the user had cleared it (or if it had been cleared by a business rule) once the loan was saved or documents were printed. This issue impacted loans begun in 2017 where the lender opted to collect government monitoring information rather than demographic information. This issue resulted in the following symptoms:
-
The previously cleared Use 2018 DI checkbox (field ID 4142) was again automatically selected on the HMDA Information input form, and the HMDA 2018 Demographic Information displayed on input forms such as the HMDA Information and 1003 Page 3.
-
On the 1003 Page 3 output form, a red X displayed across the Information for Government Monitoring Purposes section and the 1003 Addendum printed with the 2018 Demographic Information.
This issue has been resolved:
- On the affected input forms, the Use 2018 DI checkbox now remains cleared and the 2017 Government Monitoring Information continues to display after the loan is reopened when the user (or business rule) modifies the checkbox entry.
- On the 1003 output form, the red X no longer displays across the Information for Government Monitoring Purposes section on Page 3, and the 1003 Addendum no longer prints.
This update also applies to any loan affected by a business rule that clears the Use 2018 DI checkbox.
The following workaround was provided for this production issue and may no longer be required for Encompass 18.1.0.3 versions and later.
Ellie Mae recommended implementing a Field Trigger business rule for the Use 2018 DI checkbox (field ID 4142) to retain the reporting of aggregate data on loans begun in 2017. Following the Encompass 18.1.0.3 update, please reassess the need for this Business Rule and disable it if no longer needed.
Once this 18.1.0.3 update has been deployed to their Encompass system, lenders who wish to generate 1003s with aggregate (Government Monitoring) information on 2017 loans can identify any impacted loans by writing a report using the Loan Number (364), Application Date (745), Closing Docs 1003 Signature Date (3261), and RegZ Application Date (3142) fields, which can be adjusted based on lender policy with regard to usage of particular fields for application date. For more detailed information and instructions for running this report, please refer to this Update to the HMDA 2018 DI Indicator - Recommended Report Fields document.
CBIZ-15005
When administrators manage users in Encompass they can control the level of access the users have to loan files and different areas of Encompass. Administrators control user access based on their persona settings, and they can also utilize a Persona Access to Loans business rule to indicate the areas of loan files that the persona can view and/or edit. An issue occurred for these types of users with limited access to loan files. After opening a loan file, they could then save the loan file successfully, but then when they attempted to close the file, the following error message was displayed:
The loan can not be saved as a more recent version may already be available on the server.
This issue has been resolved and this message is no longer displayed for these users in this scenario.
NICE-6480