Fixed Issues for Version 25.1 (Banker Edition)

This section describes the issues that have been fixed in 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.

Encompass Forms and Tools

Updates have been made to address issues with the MSA Number field (699). In Encompass instances set up to automatically apply/populate loans with MFI data based on the subject property ZIP code (15) that is entered, the MSA Number field was being populated with incorrect data (i.e., the wrong code) or it was being populated with a code even though the ZIP code was for a city that was considered non-metropolitan. These issues have been resolved. The MSA Number field will now be populated with the correct MSA code or it will not be populated with any data if the ZIP code is for an area that is not applicable for MFI data.

CBIZ-62886, CBIZ-64111

When working with data for construction loans, an issue occurred where the Loan-to-Value (LTV) fields on the Construction Management input form were not recalculating when the Appraised Value (356) was changed. Only after the loan file was saved or when the Appraised Value field was changed on a different input form would these fields recalculate to a new LTV. This issue has been resolved and now these LTV fields (353, 976, 975) are recalculated based on changes to the Appraised Value.

CBIZ-63865

In previous versions of Encompass, after creating a HELOC loan, creating a new linked HELOC loan via the Piggyback Loans tool, and then syncing the data between the two loans, the Type of Credit checkboxes (URLA.X234) and the Borrower Count field (URLA.X194) were not recalculating (updating) in the linked loan. This issue has been resolved and these fields are now calculated and display the correct data in the linked HELOC loan.

CBIZ-63511

Using the Edit icon provided for the Prepayment Penalty / Prepayment Penalty Term checkbox (675) on the 1003 URLA - Lender input form, users can enter prepayment penalty data. If the Prepayment Penalty / Prepayment Penalty Term checkbox is then cleared, the data in the Quick Entry - Prepayment Penalty pop-up window is cleared. However, if this checkbox was cleared as result of a business rule or a Loan Program template being applied to the loan, the data in the Quick Entry - Prepayment Penalty pop-up window was not cleared. This issue has been resolved and now the data is cleared as expected when the checkbox is cleared via a business rule or loan program template.

CBIZ-62698

Users are now able to exclude escrow and prepaid fees from the Total Closing Costs Less Guarantee Fee (VASUMM.X124) for VA Cash-Out loans. Starting in Encompass 25.1, when the VA Loan Code (958) is set to Cash-Out Refi, the Prepaids (VASUMM.X145) and Initial Escrow Payment at Closing (VASUMM.X146) checkboxes will be cleared by default. This excludes these values from the Total Closing Costs Less Guarantee Fee calculation. Users have the option to manually update these checkboxes as needed on the VA Management input form’s Qualification tab.

CBIZ-34354

After importing a ULAD/iLAD (MISMO 3.4) file into Encompass, the supported iLAD enumeration code plus the description of the loan documentation is now populated to the Loan Documentation Type Code field (MORNET.X67) in the imported file. Previously, only the enumeration code (a single letter) was populated to this field.

For example, if the imported iLAD file included reduced documentation, the Loan Documentation Type Code field was populated with only R. Starting in Encompass 25.1, this field will be populated with (R) Reduced in the imported file.

CBIZ-63355

An issue occurred where a “Confirmed” log was created when a Deny Lock request was updated using the Update Sell/Comparison button. This issue has been resolved and a “Denied” log is now created instead of a “Confirmed” log.

SEC-29211

(Updated on 2/24/2025)

After un-linking a piggyback loan, a confirmation message is displayed in a pop-up window. The message in this window has been updated to correct a grammatical error.

Before Encompass 25.1: The current link information has been removed and both loan have been saved.

Encompass 25.1: The current link information has been removed and both loans have been saved.

CBIZ-62864

Encompass Document Management (EDM) / eFolder

In previous versions of Encompass, eFolder document attachments were displayed in landscape format instead of the expected portrait mode. For example, after a credit report was returned and then saved to the eFolder, the report displayed in landscape when a user viewed the report in the Document Details window. This issue resulted in portions of the document being cut off. This issue has been resolved and the documents now display in portrait format as expected.

DOCP-67436

In previous versions of Encompass, the eConsent forms returned from borrowers were displaying in landscape format when viewed from the Disclosure Tracking tool. This prevented users from printing the eConsent forms correctly. This issue has been resolved and now the eConsent forms are displayed in portrait form as expected.

DOCP-67957

For users who have set up Auto Retrieve for disclosure packages so that signed documents are automatically returned to the lender (in Encompass) when the required milestone is completed, there was an issue where not all of the signed documents were being returned. Typically, some signed documents in the package were returned, but some were not. Users would then need to manually retrieve the remaining signed documents. This issue has been resolved and all signed documents are now returned as expected when auto retrieve is enabled.

DOCP-67955

For users who have their Status Online Tool set up to automatically send notification emails when updates were made, an issue occurred where an application error message was triggered for these users when they saved and then exited a loan. The cause of this issue was identified and has been addressed. The error message is longer being triggered in this scenario.

DOCP-66444

When using the Tools > Rep and Warrant Tracker in a loan file, an issue occurred where an Application Error was triggered after the user clicked the Save to eFolder button. This issue has been resolved and now the Rep and Warrant input form can be saved to the eFolder. Once saved, a Rep and Warrant Tracker document is added to the eFolder's Documents tab.

DOCP-67285

Encompass Settings

An issue occurred where an incomplete document was displayed when an ICE PPE integration was selected as the Provider and then the More Info link was selected on the Product and Pricing setting. This issue has been resolved and a complete and relevant document will now be displayed.

SEC-28610

(Added on March 4, 2025) 

The following Personas options are now included in the Personas Settings Report. These Personas options were introduced in Encompass 24.3, but they were not added to the Personas Settings Report at that time.

  • MI Center (for the Personas >  Forms/Tools tab > MI Center option on the Tools panel)

  • MI Center and related options (for the Personas > Web Version tab > Services > MI Center and the related MI Center options located on the Standard Features panel) 

  • Lock Comparison Tool (for the Personas > Forms/Tools tab > Lock Comparison Tool and the related Validate Pricing option located on the Tools panel)

Refer to the Settings Reports help topic for instructions for generating a Persona-based settings report.

NICE-51741

Encompass Developer Connect APIs

An issue with foreign residence addresses occurred for users creating a JSON object file to create a loan using the MISMO converter API (API_SERVER/encompass/v3/converter/loans?mediaType=mismo). When the address in the XML file was a foreign address with a postal code containing alphanumeric values, the API was skipping the alpha characters in the postal code and only including the numeric characters in the loan file, resulting in incomplete/incorrect ZIP Code/post code data in the loan. This issue has been resolved and the complete postal code is now reflected in the new loan file.

The following fields were impacted by this issue and will now reflect the complete postal code:

  • [Borrower Mailing Address] Zip Code / Postal Code (1419) on the 1003 URLA Part 1 (and other input forms)

  • [CoBorrower Mailing Address] Zip Code / Postal Code (1522) on the 1003 URLA Part 1 (and other input forms)

  • [Borrower Mailing Address] Zip Code / Postal Code (BR001) on the Verification of Residence (VOR)

  • [CoBorrower Mailing Address] Zip Code / Postal Code (CR0111) on the Verification of Residence (VOR)

  • [Borrower Mailing Address] Zip Code / Postal Code (BE0107) on the Verification of Employment (VOE)

  • [CoBorrower Mailing Address] Zip Code / Postal Code (CE0107) on the Verification of Employment (VOE)

  • [Property Information] Zip Code / Postal Code (FM0108) on the Verification of Mortgage (VOM)

CBIZ-63584

For V3 API users creating loans through the ‘Create Loan’ API, an internal service error was returned when the loan amortization term (loanAmortizationTermMonths) was any number other than 1, 2, 8, 9, or 10. All other numbers of months returned the service error which prevented the loan from being created. This issue has been resolved and the loan is now created successfully when any number of months is entered for the loan amortization term.

CBIZ-63668

Fixed Issues for Version 25.1.0.1 Server Patch 1

(Added on 3/7/2025)

This update contains an update to users' Encompass client machines (25.1.0.1) and a Server Patch (server patch 1) that is applied to the Encompass server. The fixed issues below are 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. 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 the upgrade is complete, your new version number will be 25.1.0.1 Server Patch 1.

The Encompass SDK has been repackaged with this 25.1.0.1 Server Patch 1 update. If you are utilizing the Encompass SDK, upgrading to this new package is needed to ensure that your SDK has the same functionality as this latest version of Encompass. Visit the Encompass SDK and Other Install Files page to access the latest download links to the SDK and common tools, including eFolder print drivers and the Encompass Document Converter.

Update to the Encompass Server (i.e., Server Patch 1) and Client Machines (25.1.0.1)

The Encompass 25.1.0.1 Server Patch 1 release includes the following update. In order for this item to be fully integrated into your Encompass system, both the Server Patch and the client-side update provided with this release must be applied. The Server Patch included with this release is applied to the Encompass Server automatically and cannot be controlled manually via the Encompass Version Manager tool. The client-side update in this release can be controlled manually via the Encompass Version Manager tool. If the tool has been configured to always apply client-side updates to users’ computers automatically, users will receive the client-side updates upon their initial log in of Encompass following the release.

Again, the item listed below will not be fully implemented until both the Server Patch and the client-side update is applied to your Encompass system.

(Added on 3/7/2025)

System updates have been made to help reduce the time it takes to save a loan file after updating files in the eFolder (i.e., merging files, splitting files, or dragging and dropping files from one location to another).

DOCP-74700

 

Next Section: Change Log  
  Previous Section: Feature Enhancements