Fixed Issues for Version 19.4.0.7 Server Patch 6
This Encompass 19.4 February Service Pack includes updates to users' Encompass client machines (19.4.0.7) and a Server Patch (server patch 6) that is applied to the Encompass Server.
Why we fixed these issues: This issue was fixed to improve usability and to help ensure Encompass is operating as expected. This issue was chosen to be fixed based on the severity of its impact to clients and client feedback.
Updates to the Encompass Server (i.e., Server Patch 6)
Below is the update 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 issue. 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.
Recipient dropdown Now Displays on Disclosure Details Window in Developer Connect Environments
An issue was resolved that caused the Select Disclosure Recipient dropdown list to not display at the top of the Details tab in the Disclosure Details pop-up window for loans with a non-borrowing owner listed in the File Contacts tool. The pop-up window displays when you double-click a Disclosure History entry on the Disclosure Tracking tool. This issue, which interfered with the ability to track disclosure viewing and signing details for the non-borrowing owner, has been resolved and the dropdown list now displays as expected when a loan file has a non-borrowing owner.
NOTE: Encompass Developer Connect environments are available in Encompass Banker Edition only.
EBSP-8946
Update to the Encompass Server
(i.e., Server Patch 6) and Client Machines (19.4.0.7)
The Encompass 19.4.0.7 Server Patch 6 release includes the following fix to an issue that occurred in previous versions of Encompass. In order for this fix 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.
The fix listed below will not be fully implemented until both the Server Patch and the client-side updates are applied to your Encompass system.
Update to Calculation for Bona Fide Discount Point That Can Be Excluded Based on Reduction in Rate
The calculation used to determine the Discount Points that can be excluded based on reduction in rate (field ID QM.X367) on the Bona Fide Discount Point Assessment pop-up window has been updated to use the lowest of the following three values:
-
APOR Test
-
Reduction in Rate Basis Test
-
Starting Adjusted Rate Basis
There is a known issue where, if no value is entered in one of the three fields listed above, Encompass interprets the field as having a value of 0 (zero) and uses that as the Discount Points that can be excluded based on reduction in rate. This issue is scheduled to be addressed in a future release of Encompass.
CBIZ-29903
Updates to the Encompass Client Machines
The Encompass 19.4 February Service Pack includes the following fix, which is a client-side update that is 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.
Encompass Forms and Tools
Data Retained in AUS Tracking Fields When Borrower Pair Positions Switched
The tracking fields that display at the top of the AUS Tracking tool in Encompass for a borrower pair are now being retained when the positions of the borrower and co-borrower are switched within a borrower pair or across two different borrower pairs.
Previously, the fields were tied to the primary borrower in the pair and were being cleared when the borrower positions were switched. The data is now tied to the borrower pair as a whole rather than to an individual borrower, and the data is no longer cleared when the borrower positions are switched.
Migration
To restore the AUS Tracking data for loans with borrowers who were switched prior to the Encompass 19.4 February Service Pack release, open the affected loans to trigger the data migration in each loan or have your administrator rebuild the Encompass Pipeline to trigger data migration in all loan files.
If the AUS Tracking fields were added to the Encompass Reporting Database, your Encompass administrator must rebuild the Encompass Pipeline to correct the AUS tracking data in the reporting database for loans with borrower who were previously switched.
CBIZ-29544
FNMA 3.2 Data from TPO Connect Loans now Populated to TPO Custom Fields in the Loan File in Encompass
(Added on 2/6/2020)
An issue occurred in Encompass with custom fields set up and mapped to display data from Encompass TPO Connect loans. Using the Encompass Settings > External Company Setup > Company Details > Custom Fields tab, administrators can set up and map custom TPO fields to loan fields in Encompass so that when a loan is registered or submitted from the TPO company or contact, the custom fields will be automatically copied to the corresponding custom fields in the loan. However, this functionality was not working for loans originated in Encompass TPO Connect where the TPO had imported a FNMA 3.2 file as part of the loan origination process. For these types of TPO Connect loans, the imported FNMA 3.2 data was not being populated into the TPO custom fields in Encompass, which could impact business rules and other triggers dependent on these custom fields. This issue has been resolved and the custom fields are now populating with the FNMA 3.2 data as expected.
Workaround Information:
The following workaround was provided for this production issue and is no longer required for Encompass 19.4.0.7 Server Patch 6 and later.
- Open the loan file in Encompass, open the TPO Information tool, and click the Find icon (magnifying glass) next to the Name field (field ID TPO.X14) to re-assign the TPO Organization. Re-assigning the organization will populate the custom fields as expected (based on the custom field values set up and mapped for the TPO organization in the Encompass Settings > External Company Setup > Company Details > Custom Fields tab).
Fixed Issue for Version 19.4.0.8 Server Patch 7
(Added on 2/9/2020)
This critical patch contains updates to users' Encompass client machines (19.4.0.8) and a Server Patch (server patch 7) that is applied to the Encompass Server to fix an issue that was introduced by the Encompass 19.4 February Service Pack. This new update was released on February 9, 2020.
This client-side update (19.4.0.8) 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 (server patch 7) 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. When you apply the client-side update, your new version number will be 19.4.0.8 Server Patch 7.
The Encompass SDK (Encompass Software Development Kit) has been repackaged with this 19.4.0.8 Server Patch 7 release. Although it is not required, it is 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.
Visit the Encompass SDK Install Files page to access the SDK install files for this release.
Again, upgrading to this latest SDK package is recommended, but not required, for this 19.4.0.8 Server Patch 7 update.
Update to the Encompass Server (i.e., Server Patch 7)
Below is the update 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 issue. 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.
Fixed Issue
Users Receiving 'Object not set to an instance of an object' Error Message When Saving Changes to Loan
An issue was introduced with the Encompass 19.4 February Service Pack. For Encompass users who had recently performed a batch update to a series of loans prior to upgrading to 19.4.0.7 Server Patch 6 (i.e., the 19.4 February Service Pack), when they then tried save changes to one of those loans after upgrading, they would receive an 'Object not set to an instance of an object' error and the save was not completed. The cause of this issue was identified and this issue is now fixed. These loans can now be saved successfully.
Update to Encompass Client Machines
This critical patch includes a client-side update that is 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.
The purpose of this client-side update (19.4.0.8) is to help ensure Encompass client machines are in sync with the new Encompass Server version (server patch 7) being applied in this critical patch. This client-side update is not required to fix the loan save issue, but it is recommended that you apply this update to help ensure the client machines and Encompass server remain in sync.
Fixed Issue for Version 19.4.0.9 Server Patch 7
(Added on 2/14/2020)
This critical patch contains an update to users' Encompass client machines (19.4.0.9) to fix an issue that was introduced by the Encompass 19.4 February Service Pack. This new update was released on February 15, 2020.
This client-side update (19.4.0.9) 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. When you apply the client-side update, your new version number will be 19.4.0.9 Server Patch 7.
The Encompass SDK (Encompass Software Development Kit) has not been repackaged with this 19.4.0.9 Server Patch 7 release. Upgrading the SDK is not required.
Updates to the Encompass Client Machines
This critical patch contains the following fix, which is a client-side update that is 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.
Index Out of Range Error with Auto Assign
An issue was addressed that caused the following error message to display in some scenarios when users selected a file attachment and clicked the Auto Assign button in the eFolder:
Auto Assign Error: Index out of range. Must be non-negative and less than the size of the collection. Parameter name: index.
After a user closed the error message, the file attachment was still being auto assigned correctly. This issue has been resolved and the error message no longer displays.
DOCP-9388
