Fixed Issues for Version 18.3.0.8 Server Patch 3
This Encompass 18.3 September Service Pack Critical Patch 2 includes a Server Patch (server patch 3) that is applied to the Encompass Server. There are no updates to users' Encompass client machines in this release.
Why we fixed this issue: 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 3)
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 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.
The fixed issue being applied with this server patch is not applicable to Encompass Broker Edition.
Issue Resolved: Upon Loan Save, Application Error Triggered Due to Incorrect Dates Set in Date Fields
An issue occurred in Encompass when attempting to save changes to certain loans that had been originated in, or modified by certain business rules, in Encompass TPO Connect, Encompass Consumer Connect, Encompass Loan Officer Connect, or Encompass Developer Connect. It was discovered that these Connect products were incorrectly evaluating business rules- specifically field triggers, rule conditions or custom field calculations- that were using the "@" operator within their Advanced Code. For example, [@762] Today. As a result, the business rules were populating the incorrect date into applicable date fields in the loan. These incorrect dates were considered invalid by the Encompass system's Reporting Database and Audit Trail. As a result, the following Application Error was triggered when attempting to save the loan in Encompass:
This issue has been resolved, and this error is no longer triggered when saving impacted loans in Encompass.
Please note:
- The error triggered by the Audit Trail due to the invalid date is only one indicator that an invalid date has been populated to a loan:
If a date field in a loan in a Connect product was modified by a business rule using a field trigger that uses the "@" symbol in an Advanced Code action, this code may have executed incorrectly and caused an unexpected result.
If a date field in a loan in a Connect product was modified by a field trigger that uses the "@" symbol in an Advanced Code condition of the trigger, the trigger may have run when it should not have or may not have run when it should have. As a result, the effect of the trigger may have been applied to the loan when it shouldn't have or may not have been applied when it should have.
-
It is recommended that you evaluate your custom field calculations and field triggers in your Connect product to determine which are potentially affected and what the potential effect would be. You should then open each potentially affected loan (i.e., loans originated on or after October 14, 2018) and inspect the fields that could have been impacted and ensure they have the expected values.
-
This issue did not affect Advanced Code in business rules executed within Encompass. It only affected loans that were modified by Advanced Code in business rules executed in the Connect product suite.
