Fixed Issues for Encompass Investor Connect 19.3 August Service Pack

Encompass users can now include documents in loan packages even when the document is a protected package that the user is not allowed to access. Previously, when a stacking order was applied to a loan package, the stacking order would not pull in a protected document when the Encompass user was not allowed to access. If the document was listed as a required document in the stacking order, the user would be unable to submit the loan and an error message would display. If the document was listed as an optional document in the stacking order, no error message would display. In both cases, the user would have to manually add the document to include it in the loan package. This issue has been resolved and stacking templates are now pulling protected documents into loan submission packages even when the Encompass user does not have access to the document.

An issue was resolved that prevented some users from submitting loan packages when an investor had set their partner preferences to send FNMA 3.2 or MISMO 3.4 data files based on the version of URLA used in the loan file. This issue occurred when users were not able to see the checkboxes used to select the application print version (field ID 1825) because the user’s access rights for the field were set to Hide in a Persona Access to Fields Business Rules. Field ID 1825 is used to determine the URLA version being used for a loan, so Encompass was unable to determine the URLA version when field 1825 was not visible to the user submitting the loan package. This issue has been resolved and loan packages are now being sent with the correct FNMA 3.2 or MISMO 3.4 data file under the conditions described above.

Workaround Information:

The following workaround was provided for this production issue and is no longer required for loans in Encompass version 19.3.0.5 and later:

• Adjust the Persona Access to Fields Business Rule to give the user View Only / Disabled access rights to field 1825.