Fixed Issues for Version 20.1.0.10 Server Patch 8
This Encompass 20.1 June Service Pack release includes updates to users' Encompass client machines (20.1.0.10) and a Server Patch (server patch 8) 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.
Update to the Encompass Server
(i.e., Server Patch 8) and Client Machines (20.1.0.10)
The Encompass 20.1 June Service Pack release includes the following item. 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 updates are applied to your Encompass system.
External Company Setup
Issue Resolved: AE User with Custom Persona Cannot be Assigned as a TPO Sales Rep
An issue occurred for administrators modifying persona access rights for External Settings.
After assigning a user with the Account Executive persona, and then modifying the assigned user’s settings so they are different than the default Account Executive persona settings, the AE user would not display as an eligible user to be added as the TPO Sales Rep for a TPO company. This issue has been resolved so that the customized AE user can be assigned as a TPO Sales Rep.
NICE-30206
Correspondent Trades
Commitment Date and Commitment Expiration Date Now Cleared on Correspondent Loan Status Screen When Loan Removed from Correspondent Trade
An issue occurred where the Commitment Date and Commitment Expiration Date were not cleared when a loan was removed from a Correspondent trade. If the Use Commitment Terms fields (4527, 4528, 4529) setting was enabled, a loan allocated to a Correspondent trade was extended from the trade, and then that loan was removed from the trade, the Commitment Date and Commitment Expiration Date were not cleared on the Correspondent Loan Status screen. This issue has been resolved and the two dates are now cleared when a loan is removed from a Correspondent trade.
Percent Values on the Trade Pipeline View Now Calculated Correctly
An issue occurred where the percent values (e.g., Assigned Percentage, Delivered Percentage, etc.) displayed on the Trade Pipeline View were incorrectly calculated. If a Correspondent trade had no loans assigned to it, the percentage calculations incorrectly included the pair-off amount. This issue has been resolved and the percentage calculations now never include the pair-off amount.
The correct percentages were correctly displayed on the Loans tab.
Updates to the Encompass Client Machines
The Encompass 20.1 June Service Pack release includes the following items, which are 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 these updates upon their initial log in of Encompass following the release.
Correspondent Trades
Incorrect Message No Longer Displayed When Changes Made to Correspondent Trade Loans View on the Loans Tab
An issue occurred with the Correspondent Trades Loans tab where if a change was made to the Loans View without making any changes to the trade, a warning that the trade had unsaved changes was displayed when the user attempted to exit the trade. This issue has been resolved.
The same incorrect message was also displayed if assigned pending loans were updated or if assigned loans were extended.
This issue has been resolved and if a user attempts to exit the trade without saving their change to the Loans View, a warning is no longer displayed when no changes have been made to the trade.
Electronic Document Management
Electronic Fulfillment Data Populating as Expected in Disclosure Tracking
An issue was resolved that caused blank values to display for the following fields when fulfillment services were ordered electronically for eDisclosures:
-
The Fulfillment Ordered By and Date/Time Fulfillment Ordered fields in the eDisclosure Information section of the 2015 Disclosure Tracking Details output form.
-
The Fulfilled By field in the Disclosure Tracking Tool (on the eDisclosure Tracking tab in the Disclosure Details window for a Disclosure History entry).
This issue has been resolved and these fields are now populated as expected on the tool and in the output form.
DOCP-10684, DOCP-10681
Encompass Software Development Kit (SDK)
Issues with Encompass SDK Calls for External TPO Companies Resolved
An issue with the Encompass SDK was introduced in Encompass 20.1 where the GetPrimarySalesRep() SDK call resulted in the following error message, even if a TPO Sales Rep has been correctly set up and indicated in the External Company Setup > Company Details settings for the appropriate TPO company.
ExternalOrganization.GetPrimarySalesRep() failed: Index was out of range: Must be non-negative and less than the size of the collection. Parameter name: index
In addition, the ExternalOrganization.GetExternalOrgSalesRepUsersForCurrentOrg() SDK call also resulted in the following error message, even if a TPO Sales Rep has been correctly set up and indicated for the TPO company being referenced.
Exception occurred: System.ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index
at System.ThrowHelper.ThrowArgumentOutOfRangeException(ExceptionArgument argument, ExceptionResource resource)
at EllieMae.Encompass.BusinessObjects.ExternalOrganization.ExternalOrganization.BatchLoadSettings(List`1 settings)
at EllieMae.Encompass.BusinessObjects.ExternalOrganization.ExternalOrganization.GetExternalOrgSalesRepsForCurrentOrg()
at EllieMae.Encompass.BusinessObjects.ExternalOrganization.ExternalOrganization.GetExternalOrgSalesRepUsersForCurrentOrg()
The cause of these error messages was identified and these issues have been fixed.
NICE-31021, NICE-31039
