Fixed Issues for Version 19.4
View the Encompass Administrator Checklist for 19.4 Major 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.
New URLA
For loans using the new URLA 2020 forms, an issue was resolved that caused checkboxes in some sections of the URLA 2020 input forms to be cleared or selected when a user clicked the text label for a different checkbox on the form. In the example shown below, clicking the self-employed label for the checkbox in the co-borrower section on the 1003 URLA Part 2 would cause the checkbox for the borrower option to be selected or cleared.
The following section of the forms were affected:
-
1003 URLA Part 1 – Military Service
-
1003 URLA Part 2 – Current/Self Employment and Income
-
1003 URLA Part 2 – Additional/Self Employment and Income
-
1003 URLA Part 2 – Previous Employment and Income
-
1003 URLA Part 2 – Income from Other Sources
-
1003 URLA Lender – Property and Loan Information
-
1003 URLA Lender – Mortgage Loan Information
This issue has been resolved. Clicking the text label for a checkbox on the URLA 2020 input forms listed above now selects or clears the correct checkbox.
CBIZ-22225
To maintain the correct formatting for addresses on URLA 2020 forms, the address fields listed below, which display on non-URLA forms, are no longer editable. This change was introduced to ensure that addresses are populated correctly on the URLA forms, which contain separate fields for the Street Address, Unit Type, and Unit #.
-
Borrower Current Address (field ID FR0104)
-
CoBorrower Current Address (field ID FR0204)
-
Borrower Former Address (field ID FR0304)
-
CoBorrower Former Address (field ID FR0404)
-
Borrower Mailing Address (field ID 1416)
-
CoBorrower Mailing Address (field ID 1519)
-
Borrower Current Employment Address (field ID FE0104)
-
CoBorrower Current Employment Address (field ID FE0204)
-
Subject Property Address (field ID 11)
-
Loan Originator Address (field ID 319)
Previously, addresses entered on non-URLA forms were copied to the address field on the URLA forms and would require manual adjustment when the address included a Unit Type and Unit #. These addresses must now be entered on the URLA forms. This change reduces the possibility of human error when adjusting addresses that have been copied to the URLA fields from non-URLA forms. Instead, the Street Address, Unit Type, and Unit # from the URLA forms are combined into a single address and entered in the corresponding Address field on non-URLA forms.
CBIZ-22631
On the Verification of Gifts and Grants input form, when the option selected from the Source dropdown list is changed from Other to any other option, the Other Source Description (field URLARGG0102) is now cleared. Previously, when another option was selected, the text entered in the description field would not clear and the field would become read-only.
CBIZ-22784
To match MISMO specifications, there is now an 11-character limit for entries in the Unit # address fields for loans that are using the URLA 2020 input forms. This change affects fields on input forms such as the 1003 URLA (parts 1-4), 1003 URLA – Lender, Verification of Employment, Verification of Mortgage, Verification of Residence
CBIZ-23606
The Lender section of the Closing Disclosure Page 5 is now being populated with lender information as expected when the Copy to Lender in File Contacts checkbox (field ID 1969) is selected in a data template that is applied to an existing loan or used to start a new loan. Previously the Lender section remained blank, even though the checkbox was selected.
Workaround Information:
The following workaround was provided for this production issue and is no longer required for Encompass 19.4 and later.
- Click the Copy From 1003 button on the Closing Disclosure Page 5 input form or create a Field Trigger Business rule to populate the data.
CBIZ-23806
Updates have been made to the Appendix Q tab on the ATR/QM Management input form to support changes in the way other liabilities and expenses are handled for loans using the new URLA 2020 forms. These changes are only visible on the ATR/QM Management input form for loans that are using the new URLA forms. The changes are not applied to the input form for loans using the pre-2020 URLA forms.
In the Debt/Obligation Analysis section, the liabilities and expenses fields shown below have been removed. The Encompass field ID for the fields are shown in red font.
This section has been replaced with the fields shown below, which are used for liabilities and expenses on the URLA 2020 forms. This new section includes a Show All Other Liabilities button, which opens the Verification of Other Liabilities pop-up window. The Encompass field ID for the fields are shown in red font in the image below.
Additionally, because the fields on the Appendix Q tab are not appropriate for use in predefined templates, the Appendix Q tab has been removed from the Data Template setting in the Encompass settings.
CBIZ-24016
The label for the first checkbox (field ID URLA.X119) at the top of the To be completed by lender section on the 1003 URLA Part 1 has been changed from Print ULI on URLA to Print ULI/NULI on URLA to make the label consistent with the checkbox at the top of the 1003 URLA - Lender input form.
On the Fee Variance Worksheet tool, the label for the first line in the Items that Cannot Decrease section has been changed from Form 1003 Sec. L Lender Credits to Form 1003 Lender Credit. The new label omits the section number so that the tool is accurate for both the old and new URLA forms. The lender credits are now in section M on the new URLA 2020 forms.
CBIZ-24903
When configuring Data Templates in the Encompass settings, the buttons listed below are now disabled on the new URLA 2020 input forms in the template to prevent data entry for the fields accessed via the buttons.
Form | Button |
---|---|
1003 URLA Part 1 |
|
1003 URLA Part 2 |
|
1003 URLA Part 3 |
|
1003 URLA Part 4 |
|
CBIZ-25140
In the property type dropdown lists for borrower and co-borrower in section 5a of the 1003 URLA Part 4 input form, the option for Secondary Residence has been changed to Secondary Home to match the terminology used in the declaration.
CBIZ-25285
The checkboxes that indicate whether assets and liabilities were completed Jointly or Not Jointly (field ID 181) have been added to the header at the top of the 1003 URLA Part 3 input form for loans that are using the new URLA forms. Only one checkbox can be selected at a time.
In Data Templates, both checkboxes are cleared by default on both the new 1003 URLA Part 3 and the old the 1003 URLA Page 2. Previously the Jointly checkbox was selected by default for the 1003 URLA Page 2.
CBIZ-25287
The following updates have been made on loans using the new URLA forms to enable underwriters to view accurate amounts for total assets and liquid assets that display on forms such as the Borrower Summary – Origination, Borrower Summary – Processing, and Underwriter Summary:
-
Total Assets (field ID 732) now includes the cash or market value of all Verification of Other Assets (VOOA) entries for loans where the loan version is URLA 2020.
-
Total Liquid Assets (field ID 915) now includes the cash or market value of all Verification of Other Assets (VOOA) entries listed below.
-
Bridge Loan Not Deposited (FHA/VA)
-
Cash On Hand
-
Earnest Money
-
Lease Purchase Fund
-
Proceeds From Sale of Non Real Estate Asset
-
Proceeds From Secured Loan
-
Proceeds From Unsecured Loan
-
Other - Other Description of Other Liquid Asset
-
-
Both Total Assets and Liquid Assets now exclude amounts from the following fields when loans are using the new URLA forms, but still include the amounts when loans use the URLA 2009 forms.
-
Cash Deposit (field ID 183)
-
Cash Deposit (field ID 1716)
-
Stocks and Bonds (field ID 1605)
-
Stocks and Bonds (field ID 1607)
-
Stocks and Bonds (field ID 1609)
-
Life Insurance (field ID 210)
-
Vested Interest in Retirement Fund (field ID 212)
-
Net Worth of Business Owned (field ID 213)
-
Automobile (field ID 215)
-
Automobile (field ID 217)
-
Automobile (field ID 1718)
-
Other Asset (field ID 222)
-
Other Asset (field ID 224)
-
Other Asset (field ID 1053)
-
Other Asset (field ID 1055)
-
CBIZ-25402
Due to a misspelling in the Fannie Mae Desktop Underwriter (DU) XML option for the Accessory Unit Income value, the value in this field was being captured incorrectly on the Verification of Other Income input form in Encompass for loans using the new URLA forms. Instead of importing the income with an Income Source (field ID URLAROIS0118) of Accessory Unit Income, the income would be imported with an Income Source of Other with Accessory Unit Income populated as the Other Description. This Issue has been resolved and the typo is now adjusted for when importing the value into Encompass.
CBIZ-25454
To comply with GSE guidelines, the following changes have been made to the location of the Total for Gifts and Grants field (field ID URLA.X150) and the following calculations that use the field amount. These changes affect loans using the new URLA forms.
-
The Total of Grifts and Grants field has been moved from line M2 in section L4 of the 1003 URLA – Lender and now displays in section 4d on the 1003 URLA Part 4.
-
The remaining entries for lines M3-M7 on the 1003 URLA – Lender have been renumbered as lines M2-M6.
-
The label for line M on the 1003 URLA – Lender has been updated to M. Other Credits (Total of M1 to M6).
-
The calculation for M. Other Credits (field ID URLA.X149) and N. Total Credits (Total of L and M) have been adjusted to exclude the Total of Gifts and Grants amount.
No changes have been made to the calculation of the Total Gifts and Grants amount (field ID URLA.X150).
Section M on 1003 URLA -Lender (Pre-Encompass 19.4)
Section M on 1003 URLA -Lender (Encompass 19.4)
New Total Gifts and Grants Location on the 1003 URLA – Part 4
CBIZ-25520
(Added on 9/16/2019)
For loans using the new URLA input forms, the following updates have been made to field calculations for Other Liability amounts to make the calculated value match the value expected by Fannie Mae’s Desktop Underwriter (DU) automated underwriting system:
-
Alimony / Child Support (field ID 272) – The sum of the monthly amounts (field ID URLAROLXX03) on Verification of Other Liability (VOOL) records for the borrower and co-borrower where the Description (field ID URLAROLXX02) is Alimony or Child Support.
-
Job Related Expenses (field ID 256) – The sum of the monthly amounts (field ID URLAROLXX03) on VOOL records for the borrower and co-borrower where the Description (field ID URLAROLXX02) is Job Related Expense.
-
Other Expense (field ID 1062) – The sum of the monthly amounts (field ID URLAROLXX03) on VOOL records for the borrower and co-borrower where the Description (field ID URLAROLXX02) is not Alimony, Child Support, or Job Related Expense.
Additionally, the fields for Alimony / Child Support, Job Related Expenses, and Other Expenses are now read-only by default and Lock icons have been added to the fields. Click a Lock icon to edit a field value. The calculations for these fields are updated whenever a change is made on a VOOL input form.
CBIZ-25391
(Added on 9/16/2019)
An issue was resolved that caused military entitlements to not populate to the Military Entitlements (field ID FE0153) in Gross Monthly Income section on the 1003 URLA Part 2 input form when a MISMO 3.4 loan file with a military entitlement was imported into Encompass. This issue occurred because previously Encompass users had to click the OK button on the Military Entitlement pop-up window to trigger an update to the Military Entitlements field on the 1003 URLA Part 2. Importing a MISMO 3.4 file would automatically populate the value to the pop-up window without requiring users to manually click the button. This issue has been resolved and imported Military Entitlement values are now flowing through to the 1003 URLA Part 2.
CBIZ-25417
(Added on 9/16/2019)
For loans using the new URLA forms, the Print Additional Borrower URLA checkbox (field ID URLA.X121) has been removed from the 1003 URLA Page 1 for the borrower in all borrower pairs. Previously this checkbox was displaying for the borrower in all non-primary borrower pairs for a loan (the second through sixth borrower pair).
CBIZ-25746
(Added on 9/16/2019)
The default behavior has been corrected for automatically formatting the Date Hired fields (field IDs BEXX51 and CEXX51) for the borrower and co-borrower on the Verification of Employment input form and the Quick Entry – VOE pop-up window that can be opened from the 1003 URLA Page 2. Previously, numerical entries were not automatically converted in the dates using MM/DD/YYYY formatting and the field was also allowing the entry of non-numeric characters (for example, letters of the alphabet and special characters). When this occurred, the following error message would display:
This issue has been resolved and numbers entered in these date fields are now automatically converted into the correct formatting for dates.
The two center digits in the field IDs (BEXX51 and CEXX51) are variables that increase by a value of 1 with each new record. For example, the field ID for the first borrower employment verification record is BE0151 and the field ID for the second employment record is BE0251.
Workaround Information:
-
The following workaround was provided for this production issue and is no longer required for Encompass 19.4 and later.
-
Type the date as numbers only, with forward slashes separating the month, day, and year to match the MM/DD/YYYY format. Delete the two forward slashes at the end of the date.
CBIZ-25799
(Added on 9/16/2019)
In section L3 on the 1003 URLA - Lender input form, the Gov’t Loan Type dropdown list (field ID Term.USDAGovtType) is now enabled for selection only when the USDA-RD checkbox is selected for the Mortgage Type Applied For (field ID 1172). Previously the dropdown list was enabled for selection even for loans that were not USDA-RD. Additionally, the Other description field (field ID 1063) is now automatically populated with RHS and disabled from editing, which matches the behavior used for loans using the URLA 2009 forms.
CBIZ-25944
(Added on 9/16/2019)
For loans using the new URLA forms, access is now disabled for the Lien Position dropdown list (field ID 4494) unless the Subordinate Lien checkbox is selected for the Mortgage Lien Type (field ID 420), which matches the behavior used for loans using the URLA 2009 forms
CBIZ-25991
(Added on 9/16/2019)
The following miscellaneous updates have been made to address issue with fields on the new URLA forms:
-
The Balloon / Balloon Term checkbox (field ID 1659) is now read-only on the 1003 URLA Lender input form. This field is a read-only field on all other input forms where it is present. The field is selected or cleared automatically based on values entered in other fields.
-
Two updates have been made to the behavior of the Credit Cards and Other Debts Paid Off (field ID URLA.X145):
-
The amount is now updated when an Encompass user updates the Balance amount (field ID FLXX13) is updated on a Verification of Liability (VOL) record. This change affects other calculated fields that include the Credit Cards and Other Debts Paid Off amount in their calculations.
-
The amount now includes payoff amounts for VOLs that are not associated with the subject property when the Account Type for the VOL is Mortgage or HELOC.
-
-
On the Verification of Other Liability (VOOL), Verification of Other Asset (VOOA), and Verification of Additional Loans (VOAL) input forms, the Title (field IDs URLAROLXX14, URLAROAXX14, and URLARALXX11) entered by the user is now retained. Previously, Encompass would delete the entry or replace it with the default entry the first time the user entered the information. The user would have to enter the information twice before it was retained.
CBIZ-25210
(Added on 9/18/2019)
A new Source of Funds dropdown list (field ID URLARAL0133) has been added to the Verification of Additional Loans input form for loans using the new URLA forms to enable lenders to identify the source of the additional loan.
CBIZ-25932
(Added on 9/18/2019)
An issue has been resolved with the behavior of the two checkbox options for printing the ULI/NULI and loan number on loans using the new URLA forms. Previously, selecting either the Print ULI/NULI on URLA checkbox (field ID URLA.X119) or the Print both ULI/NULI and Loan # checkbox (field ID URLA.X238) would disable the other checkbox. Encompass users would then have to clear the selected checkbox before selecting the other checkbox. Now both checkboxes are enable for selection, but only one checkbox can be selected at a time. Selecting one checkbox will automatically clear the other checkbox.
CBIZ-26580
HELOC Loans
(Added on 9/16/2019)
An issue was resolved that caused the First Qualifying Payment (field ID 1742) and DTI ratio (field ID 740) to be blank when a user created a new loan using a Loan Template Set under the following conditions:
-
The Loan Template Set included a Loan Program Template.
-
In the HELOC Qualifying Payment Basis section of the Loan Program Template, the Index option was selected in the first dropdown list (field ID 4465) for the Rate option in the HELOC Qualifying Payment Basis section.
-
After applying the Loan Program Template Set, a value was then entered for the Index (field ID 688).
This issue has been resolved by triggering a recalculation of the two fields when a change is made to the Index (field ID 688).
Workaround Information:
The following workaround was provided for this production issue and is no longer required for Encompass 19.4 and later.
-
Enter a value of 0.00 for the HELOC Initial Draw (field ID 1888). This triggers a recalculation of the First Qualifying Payment and DTI.
CBIZ-25901
Encompass Forms and Tools
Some users experienced an issue where the Actual Receipt Dates for Loan Estimates and Closing Disclosures (CD) were not being populated when these disclosures were being sent prior to the borrower providing consent to receive and sign disclosures electronically even if the consent and receipt occurred on or before the CD Due Date. This issue has been resolved for CD’s that are sent electronically so that these individual Disclosure Tracking entries reflect the actual receipt of the CD as follows:
-
The Borrower and Co-borrower Actual Receipt Dates are populated if consent is obtained after disclosures are sent so long as either the borrower or co-borrower provides consent and accesses the disclosure package on or before the CD Due Date. This is new logic being introduced in this release.
- The Actual Receipt Date will be left blank if either the borrower or co-borrower do not access the disclosure.
Again, these updates address the issues with CDs disclosed electronically only. Disclosures sent by any other method (for example, in person, by mail, other, etc.) will persist as they do today.
NICE-25995
In Encompass 19.1, the system was updated to enable values to be manually entered into the Closing Disclosure (CD) Page 1's Changed Circumstance field (CD1.X64) once the Changed Circumstance checkbox (field ID CD1.X61) was selected. However, in Encompass 19.1 and subsequent Encompass releases, the CD1.X64 field was not enabled for manual entry. This issue has been resolved so that users can now enter values in this Changed Circumstance field on the CD Page 1.
An issue occurred where the Lock Request Form reverted back to the original lock request data when any data other than the original lock was selected via the Encompass Product and Pricing Service (EPPS), submitted to update Encompass with the new lock request data, and then another input form was opened before the relock request was submitted. This issue has been resolved and a warning message “You have received pricing on this relock. If you navigate away without first submitting your request, the pricing will be lost.” Is now displayed if users attempt to navigate to another input form before submitting the relock request.
An issue occurred where the LTV (field ID 3241), CLTV (field ID 3242) and HCLTV (field ID 4514) on the Lock Request Form did not match the LTV (field ID 353), CLTV (field ID 976), and HCLTV (field ID 1540) in the loan file when the MI is paid by Seller. This issue has been resolved and the LTV/CLTV/HCLTV values now match when MI is paid by Seller.
An issue was resolved that cause extra fields, including an extra Balance amount, to be listed on the Payoffs & Payments pop-up window on the Closing Disclosure Page 3 input form when the Delete icon on the upper-right of the window was used to delete an entry. Immediately after deletion, the entry would no longer display on the pop-up window, but the next time a user opened the window, an additional row would display at the bottom of the list. This line contained the Balance amount and other fields from the entry that previously occupied the same row on the table. The additional amount field would also be included in the Total Payoffs and Payments amount on the pop-up window and in the VOL (Verification of Liabilities) input form.
For example, in the window show below, the second entry is being deleted using the Delete icon on the upper-right.
When the window was reopened, content that previously occupied the last row in the list still displayed even though the entry was deleted. In this example, the content included a $555.00 balance amount from the entry that previously occupied this row. That amount was being included in the Total Payoffs and Payments amount.
The Payoff Amount would also continue to display in the VOL, even though the record for the record the for the deleted entry.
This issue has been resolved and all data from the deleted entry is now removed from the Payoffs and Payments pop-up window and the VOL input form.
CBIZ-19493
An issue was resolved that caused the File Starter field on Milestone Worksheets to be blank for imported FNMA 3.2 (old URLA) or MISMO 3.4 (new URLA) loan files when applying a Loan Template Set that included the default Milestone Template. This issue has been resolved and the File Starter name is now populated as expected when importing FNMA or MISMO loan files and applying a Milestone Template.
Workaround Information:
The following workaround was provided for this production issue and is no longer required for Encompass 19.4 and later.
-
In the Milestones setting, create a copy of the default template. Then open the Loan Templates Set setting and replace the default Milestone Template in the set with the new Milestone Template.
CBIZ-10069
An issue occurred where the Loan Mailbox was indicating that loan applications were available to import, but there were no new loan applications in the Loan Mailbox. This issue has been resolved and the Loan Mailbox indicator (shown below) now displays accurately.
NICE-18166
(Added on 9/16/2019)
An issue occurred where the Delivery Information section of the Shipping Detail tool was cleared if no Investor was selected in the Shipping Detail section, and then a user navigated away from and returned to the Shipping Detail tool. This issue has been resolved and the Delivery Information section is no longer cleared if no Investor is selected.
(Added on 9/16/2019)
An issue occurred when creating new third party originators (Encompass>Settings>External Company Setup>Company Details). If a third party originator was created and assigned an LO Comp plan with today’s date, any LO Comp plan that was subsequently assigned with “today’s date” was removed after saving and exiting, and then the record was reopened. This issue has been resolved and all assigned LO Comp Plans are now saved to the third party originator on the LO Comp tab.
(Added on 9/16/2019)
An issue occurred where field ID 2861, which is not an input field, was cleared when a new loan was created in Encompass or an FNMA 3.2 field was imported into Encompass, a Loan Template set with only a loan program was applied, the Borrower Name was populated, and then the loan was locked (manual or auto-locked). This issue has been resolved and field ID 2861 is no longer cleared.
(Updated on 10/29/2019)
A change has been made on the Fee Details pop-up window for the Owner’s Title Insurance on line 1103 of the 2015 Itemization input form to comply with recent guidance issued by the Consumer Financial Protection Bureau. The guidance states that for states where the owner's title insurance policy is a seller-obligated fee, any negative seller-obligated amount must be disclosed to the borrower and indicated in the seller-obligated area so as not to affect any seller credits.
The Fee Details pop-up window has been updated so that when the Seller Obligated checkbox (field ID NEWHUD2.X3331) is selected and the seller-obligated amount is a negative number, the Seller Obligated amount (field ID NEWHUD2.X3332) now displays a negative value. Previously when the seller obligated amount was negative, the Seller Obligated amount field was populated with a blank value and the field was not editable.
CBIZ-24723
Calculation Updates
An update was made to the calculation for the In 5 years Total you will have paid amount (field ID LE3.X17) that displays in the Comparisons section on the Loan Estimate Page 3 input form. This amount now includes any prepaid mortgage insurance payments entered on line 902 of the 2015 Itemization input form.
Workaround Information:
The following workaround was provided for this production issue and is no longer required for Encompass 19.4 and later.
-
Click the Lock icon next to the In 5 years Total you will have paid field and enter the amount manually.
CBIZ-19677
An issue was resolved that caused the Late Fee (field ID 3876) and the Total Late Payment (field ID 3877) to populate with a value that is one cent (0.01) lower than it should be when the Minimum Late Charge (field ID 2831) was within the range of 1.13 to 1.16. This issue has been resolved and the late fee amounts are now calculating as expected for Minimum Late charges within the specified range.
CBIZ-22367
For construction or construction-to-permanent loans, the borrower-paid or seller-paid post-consummation charges entered on the 2015 Itemization input form are no longer included in the calculations for the following amounts on the Funding Worksheet:
-
Wire Transfer Amount (field ID 1990)
-
Total Deductions (field ID 1989)
Additionally, post-consummation charges are no longer included in the list of fees in the table at the bottom of the Funding Worksheet.
CBIZ-22389
For FHA Purchase transactions, the Down Payment amount (field ID 1117) on the FHA Maximum Mortgage and Cash Needed Worksheet is now populating as expected. The Down Payment amount is now populated with the lower of the following two values:
-
The Statutory Investment Req amount (field ID MCAWPUR.X2)
-
The Contract Sales Price (field ID MCAWPUR.X12) plus the Borrower FHA Closing Costs (field ID 1132) minus the FHA Mortgage Amount (field ID MCAWPUR.X14).
Previous the field was being populated with the larger of the two amounts. This issue has been resolved and the correct Down Payment amount is now being populated.
CBIZ-22560
Electronic Document Management (EDM)
(Updated on 11/6/2019)
Two changes have been implemented to address situations where co-borrowers on an Encompass Consumer Connect loan could mistakenly access electronic packages intended for the other borrower. These changes apply when sending eConsent requests, document requests, initial eDisclosures, pre-closing packages, and Status Online updates, or when using the Send button in the eFolder to send files to borrowers for Encompass Consumer Connect loans created after upgrading to Encompass 19.4.
-
Encompass users are no longer allowed to enter the same authorization code for co-borrowers on an Encompass Consumer Connect loan. When an Encompass user enters an authorization code that was already entered for one of the co-borrowers, the following error message now displays. The Encompass user must enter a unique authorization code for each recipient before completing the request, eDisclosure, or update notification.
-
To make it easier for co-borrowers to immediately identify the intended recipient, the subject line of the email notification for the request, eDisclosure, or update notification now includes the name of the intended recipient as a prefix.
The recipient’s name is added to the subject line after the package is sent and is not visible to the Encompass user from the eFolder Send windows.
DOCP-5394, DOCP-5081
Encompass Settings
Personas
(Added on 9/16/2019)
The Modify this user's rights checkbox displays at the top of the Personas Settings pop-up window that displays when the administrators clicks the View/Edit Rights button on an Encompass user's profile. The Modify this user’s rights checkbox enables administrators to enable/disable persona rights for the individual user without modifying the persona setting directly.
Users experienced two issues with this setting. Once the Modify this user’s rights checkbox was selected, the administrator could make changes to the persona settings, save the changes, and then close the Persona Settings pop-up window. However, when the administrator returned to the Persona Settings screen in a future session, the checkbox was still selected in some instances and in others it was not selected. This inconsistency with the state of the checkbox has been resolved so that when the Modify this user’s rights checkbox is cleared by the administrator, it remains cleared in future sessions.
In addition, when the administrator selected the Modify this user’s rights checkbox and made changes to the default persona settings for the user, these changes were not always reflected accurately when the administrator returned to the Persona Settings screen in future sessions. Again, there were inconsistencies with how these updated settings were reflected in this setting for the user. This issue has been resolved so that the updated settings are now retained for the user in future sessions.
An issue occurred where users with limited access to the new URLA 2020 input forms could still access a new URLA 2020 form. Specifically, if the administrator had a set up a user’s persona so that they could only access one section of the new URLA 2020 form (for example, the 1003 URLA Part 1) and the Change URLA Form Version toggle, the user could bypass these Persona restrictions by opening a 1003 input form (for example, the 1003 Page 2) and then selecting the Form > URLA Form Version > URLA 2020 option to switch to the new URLA 2020 forms. After making this switch to the new forms, only the new URLA 2020 form that the user had permission to view was listed in the Forms list as expected (for this example, the 1003 URLA Part 1), but the new URLA 2020 version of the form that the user had selected when viewing the 2009 version of the URLA forms displayed for the user as well (for this example, the 1003 URLA Part 2 displayed since the user was viewing the 1003 Page 2 before switching to the 2020 version of the URLA forms). This issue has been resolved so that only the new URLA 2020 forms that the user is intended to access (based on their persona settings) are accessible to the user.
NICE-26242, NICE-26248
An issue occurred where if an Encompass user was assigned with the Administrator persona, then the first investor option that was supposed to be listed in the Investor Services menu in the Pipeline would not be displayed. If a user with any other persona viewed this Investor Services list, then the first option would display as expected. For example, if Deliver to NewRez Correspondent was listed first, then this option would not display for an Encompass user assigned with the Administrator persona.
Administrator persona view:
Non-Administrator persona view:
This issue has been resolved so that the first investor option is provided in this list as expected if the user has been assigned with the Administrator persona.
In addition, in the Persona settings, the Select Investors pop-up window that lists the investor options that the administrator can manage to determine what the persona will be able to access from the Pipeline > Investor Services menu was missing the Wells Fargo Funding option if the Administrator persona had already been assigned to a user:
This issue has been resolved so that the Wells Fargo Funding option is provided as expected if the Administrator persona has been assigned to a user previously:
NICE-25969
Business Rules
Automated Condition business rules are now working as expected when an advanced condition for the business rule is based on the Detached Condominium option for Property Type (field ID 1553). Previously, the following error message would display when the rule was activated and used:
This issue has been resolved and Automated Conditions business rules function as expected when the Property Type is used in an advanced condition for the rule.
CBIZ-22548
-
Field Access Business Rules - An issue occurred where administrators could successfully export a Field Access business rule, but when trying to import the rule, the following error message was triggered when the administrator clicked the Validate Dependencies button:
Error during serialization or deserialization using the JSON JavaScriptSerializer. The length of the string exceeds the value set on the maxJsonLength property.
-
Field Triggers Business Rules – An issue occurred with Field Triggers business rules with multiple field events in the rule that were set up to be triggered based on a specific value and a blank value being populated into the same field. When this type of business rule was imported, the field event based on the blank value was not included in the rule.
For example, the business rule could be set up so that a field event that activates when a custom checkbox CX.CHECKBOX is set to a specific value of "X" and a second field event that triggers the rule when CX.CHECKBOX is set to a specific value of " " (i.e., a blank value). When this type of field triggers business rule was imported, the field event with specific value of " " was not included.
These issues have been resolved and these business rules can now be imported successfully without these issues occurring.
NICE-9359, NICE-13997
(Added on 9/16/2019)
An issue occurred where Field Triggers business rules that are set up with a Date field as the trigger field and the Criterion for the rule is set to When field is set in a range of values could not be exported when from Encompass. When attempting to export this type of rule, the following error was triggered:
Response status code does not indicate success: 400 (Bad Request)
This issue has been resolved and these types of business rules can now be exported successfully.
NICE-9644
Dynamic Data Management (DDM)
-
Timeout Occurs when Importing a .CSV File to a Data Table – Some administrators experienced system timeouts when attempting to import larger .CSV files into a Data Table. This issue has been resolved so that these .CSV files can be imported successfully.
-
Custom Fields Cannot be Added to Data Tables – When administrators accessed the Dynamic Data Management > Data Tables setting and attempted to add a custom checkbox field (for example, field ID CX.001) to a DDM Data Table, no values were provided in the Value Type dropdown menu in the Set Field Value pop-up window. With no values provided, the administrator could not provide a value for the checkbox and an ‘Object Reference’ error was triggered when the administrator clicked the Next Field button.
-
Error Triggered in Data Table When Adding a Field Value - When setting up a Data Table and adding new rows, administrators received an error message. After adding a field with a value type of ‘List of Values’ (as shown below), selecting values, and proceeding to the next field, the following error message was returned when the administrator set the Value Type for the field to ‘Range’, entered a range, and then clicked the Next Field button to proceed to the next field:
“Numeric value can not be over 0 characters”
- Issue with Special Characters in Field Rules– Field rules set up with field values that included parentheses were not being applied as expected when executed in Encompass. If parentheses were included for the field value that the was supposed to be populated to a field when the rule was triggered, the value was not being populated to the field. DDM has been updated to recognize parentheses and other special characters that may be used for a field value in a field rule.
- Field Rules: Secondary Borrower Pair Fields Populated by DDM Calculations When Loan Has Only One Borrower Pair – When Field Rules are set up in DDM, calculations can be set up based on custom secondary borrower pair fields by utilizing the # identifier. For example, a rule could be set up to populate the first name (field ID 4000) of the secondary borrower pair by entering 4000#2 in the Calculation window for the custom field being added to the rule. When a Field Rule was set up in this manner and activated, an issue occurred where data values from the primary borrower pair was being populated to secondary borrower pair fields even when the loan did not have a secondary borrower pair. When these types of calculations were triggered when the loan had multiple borrowers existed, the calculations executed as expected. However, when a loan had only one borrower pair, information was being populated to the secondary borrower pair fields.
-
Fee Rules Not Being Enforced Due to Lower-Case Characters Used in the County Name - After creating a Data Table with a Fee Rule designed to to populate the correct appraisal fee to field 641 in line 804 on the 2015 Itemization input form, the rule was triggering as expected but the fee was not being populated to field 641. The cause of this issue was due to a lower-case character being used in the County name (field ID 13). For example, when Miami-dade was entered in the County field, field 641 was not populated with the appraisal fee. When Miami-Dade was entered in the County field, field 641 was populated with the appraisal fee as expected. Encompass has been updated to resolve this issue and the use of lower-case characters in the County name does not prevent the appraisal fee from being populated to field 641.
All of these issues occurring with the DDM features have been resolved.
-
The on-screen description for the Stop applying Dynamic Data Management Rules section of the Global DDM Settings screen has been updated with the highlighted text below to ensure the stop condition functionality is described correctly.
NICE-21574, NICE-14841, NICE-23119, NICE-24172, NICE-15260, NICE-16852, NICE-25570
Loan Templates
When the four ARM adjustment fields shown below are included in a Loan Program template, the data for these fields is also copied to the corresponding ARM fields on the ULDD/PDD input form. The mapping takes place when the fields, which display on forms such as the RegZ-LE and RegZ-CD, are populated from a Loan Program template or from a Loan Template Set that includes a Loan Program template.
ARM Field Name | ARM Field ID | ULDD/PPD Field Name | ULDD/PPD Field ID |
---|---|---|---|
1st Adj Cap | 697 | First Rate Maximum Increase | ULDD.X61 |
1st Change | 696 | First Rate Adjustment Frequency | ULDD.X59 |
Adj Cap | 695 | Subsequent Rate Maximum Increase | ULDD.X169 |
Adj Period | 694 | Subsequent Rate Adjustment Frequency | ULDD.X167 |
CBIZ-21160
Custom Forms
An issue occurred with custom input forms and the Default Input Forms setting. After setting up a Default Input Forms list where one or more custom input forms was placed at the top of the list of forms (i.e., above standard input forms), the list could be added to an Input Forms Set (in the Loan Templates setting). But when the loan template including this Input Forms Set was applied to a loan, the custom forms were located at the bottom of the Forms tab’s list. This issue has been resolved so that the forms are listed in the same order in the loan as configured in the Default Input Forms list.
NICE-21221
System Audit Trail
When System Audit Trails expire out of the Encompass database, they are exported to a CSV file for long-term storage. The CSV files being created were incorrectly formatted and did not comply to the RFC4180 standard. Specifically:
- Single quotes are being used to enclose each value instead of double-quotes
- In some cases, quotes within the field values are not properly escaped (i.e. "" -> """")
Because of these formatting issues, tools that consume CSV were unable to parse and read these files reliably. Updates have been made to ensure newly exported CSV files (starting in Encompass 19.4) are formatted correctly and in compliance with the RFC4180 standard.
NICE-24015
Encompass Admin Tools
The Description fields in the Encompass Reporting Database have been updated with the correct descriptions for the HMDA reporting fields listed below. These fields display in Encompass in the Information for Government Monitoring section that display on forms such as the HMDA Information input form:
- The dropdown list indicating whether the co-borrower’s sex was determined based on visual observation or surname (field ID 4134)
- The co-borrower No co-applicant checkbox in the Ethnicity section (field ID 4188)
- The co-borrower No co-applicant checkbox in the Sex section (field ID 4189).
The descriptions in the database are updated only when the three fields listed above are added to the database after the Encompass 19.4 release.
If these fields were already added prior to the Encompass 19.4 release, your Encompass administrator has two options for updating the descriptions:
-
The recommended best practice is to open the reporting database, double-click fields 4134, 4188, and 4189 in the Selected Fields panel, and then manually update the Description field for each field. This option takes effect immediately.
- The other option is to delete the fields from the Encompass Reporting Database and then add them back. This option requires that the database be repopulated with loan data, which can take a significant amount of time, depending on the amount of data being repopulated.
CBIZ-18760
The Loan Number (field D 364) is now being assigned as expected when a loan processor imports a FNMA 3.2 loan file when the Create New Loan # on Import option is enabled in the Server Settings Manager in the Encompass Admin Tools. Previously, the Loan Number was being assigned and then reassigned when the loan file was imported, causing the loan number to increment by two values rather than one value. For example, a loan number would initially be assigned as 1904EM000027 and would then be reassigned as 1904EM000028. Because the ULI (universal loan identifier) for the loan was assigned only once (when the first loan number was generated) the Loan Number would be out of sync with the ULI. This issue has been resolved. The Loan Number is now assigned as expected and is in sync with the ULI.
Workaround Information:
The following workaround was provided for this production issue and is no longer required for Encompass 19.4 and later.
- On the HMDA Information form, click the Calculate ULI button to regenerate the ULI number.
CBIZ-19044
Encompass Software Development Kit (SDK)
An issue occurred where External Company Setup custom fields could not be updated using the Encompass Software Development Kit (SDK). The sample code in the SDK help only provided a get expression (and not a set expression), which resulted in all changes reverting back to their original values. This issue has been resolved and the SDK help has been updated to provide both a get and set expression, which enables External Company custom fields to be updated via the SDK.
SEC-14711
(Added on 9/27/2019)
An issue occurred with Disclosure Tracking Tool entries and the Encompass SDK. When a tracking entry for the Settlement Service Provider List (SSPL) was created (for example, when the SSPL was sent in an eDisclosure package or when it was previewed or printed from the Print window), the tracking entry incorrectly reflected that both the SSPL and the SSPL with No Fees forms were sent even when only the SSPL was sent. This resulted in an inaccurate enumeration for the StandardDisclosures 2015 in the Encompass SDK. This erroneous enumeration could then lead to inaccurate tracking data. This issue has been resolved for applicable new loans originated in Encompass 19.4 and will no longer occur in the Encompass SDK. (Note that this issue occurred only with the SDK enumerations. The SSPL tracking was reflected correctly in the Disclosure Tracking Tool entries in the Encompass user interface.)
Fixed Issues for Version 19.4.0.1 Server Patch 1
(Added on 10/4/2019)
This update contains updates to users' Encompass client machines (19.4.0.1) and a Server Patch (server patch 1) that is applied to the Encompass Server. The fixed issues listed below are included in this update and were first released on October 19, 2019.
This client-side update (19.4.0.1) 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 1) 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.1 Server Patch 1.
The Encompass SDK (Encompass Software Development Kit) has been repackaged with this 19.4.0.1 Server Patch 1 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.1 Server Patch 1 update.
Updates to the Encompass Server (i.e., Server Patch 1) and Client Machines (19.4.0.1)
The Encompass 19.4.0.1 Server Patch 1 update includes the following fixed issue. A portion of the relevant code to implement this fixed issue is provided in the Server Patch included with this release, which will be applied to the Encompass Server automatically and cannot be controlled manually via the Encompass Version Manager tool. Another portion of the code is provided in the client-side updates that are applied to users' Encompass client machines and 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 update upon their initial log in of Encompass following the release.
The fixed issue listed below will not be fully implemented until both the Server Patch and the client-side updates are applied to your Encompass system.
VA Loans
An adjustment has been made to the rounding method used when populating the Recoup Closing Costs months (field ID VASUMM.X27) on the VA Management input form. Previously, the calculation was rounding up the value to the next highest whole number only when a value was present in the first two decimal numbers. Now the calculation is rounding up even when a value is present beyond the two decimal numbers that display on the field, for example, if the value calculates as 36.000000007, it will round up to 37. This issue affected VA loans with the following characteristics:
-
The Monthly Decrease in Payments amount (field ID VASUMM.X22) was greater than 0.
-
The Application Date (field ID 745) was on or after 02/15/2019.
-
The Prior Loan Type (field ID VASUMM.X50) was not VA-Fixed or VA-ARM/HARM.
-
The refinance type selected (field ID VASUMM.X125) was not TYPE I Cash-Out Refinance.
A portion of the relevant code to fix this issue is provided in the Server Patch, which will be applied to the Encompass Server automatically and cannot be controlled manually via the Encompass Version Manager tool. However another portion of the code to fix this issue is provided in the client-side updates that are applied to users' Encompass client machines. These client updates can be controlled manually via the Encompass Version Manager tool. This issue will not be resolved until both the Server Patch and the client-side updates are applied to your Encompass system.
CBIZ-26180
Fixed Issues for Version 19.4.0.2 Server Patch 2
(Added on 10/29/2019)
This update contains updates to users' Encompass client machines (19.4.0.2) and a Server Patch (server patch 2) that is applied to the Encompass Server. The fixed issues listed below are included in this update and were released on November 2, 2019.
This client-side update (19.4.0.2) 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 2) 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.2 Server Patch 2.
The Encompass SDK (Encompass Software Development Kit) has been repackaged with this 19.4.0.2 Server Patch 2 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.2 Server Patch 2 update.
Updates to the Encompass Server (i.e., Server Patch 2)
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
The issue addressed with this Server Patch was impacting the Dynamic Data Management tool which is provided in Encompass Banker Edition only.
In Encompass 19.4, rows in Dynamic Data Management (DDM) data tables were unable to be duplicated correctly when the duplicated row was not the last row in the list. When any other row was selected and then the administrator clicked the Duplicate icon to duplicate the selected row, the newly duplicated row contained different (and incorrect) data. If the data table was then exported, it would display the duplicated row with data outside the number of columns specified in the table.
This issue has been resolved for new data table rows going forward. Starting with Encompass 19.4.0.2, any new data table row that is duplicated will contain the same data as the original row that was duplicated in the data table.
If you have data tables that were impacted by this issue in previous versions of Encompass, you will need to manually correct these data tables. You can export the impacted data table, identify the duplicated rows that contain incorrect data, delete those rows, and then import the updated data table back to Encompass 19.2.0.4. You can then duplicate the desired row(s) and the new rows will contain the expected (correct) data.
Updates to Encompass Client Machines
The Encompass 19.4.0.2 update includes the following items, which are client-side updates that are 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.
Fixed Issues
An issue occurred when one or more fees were removed from the Charges that in Total Cannot Increase More Than 10% category (either the fee was deleted or moved to the Charges that Cannot Increase section), the Legal Limit (Net Baseline + 10%) field was not updated based on the remaining fees. As a result, if the remaining fee(s) increased above the Legal Limit, Encompass was not triggering a Good Faith Fee Variance Violated alert as expected. In addition, when the loan was submitted to an Encompass Compliance Service review, a FAIL message is returned due to the service applying the updated Allowable Charges.
This issue has been resolved so that the Legal Limit (Net Baseline + 10%) value is now updated accordingly based on the remaining fees in the Charges that in Total Cannot Increase More Than 10% category.
An issue occurred for users starting a new loan file where clicking the label for a checkbox on an input form resulted in an unrelated checkbox being automatically selected. If the original checkbox's label was clicked again, then the unrelated checkbox would be automatically cleared, and so on. For example, if you clicked the Sync with Prepaid Interest Date checkbox label (field ID 2852) on the RegZ-CD input form, the Buydown checkbox (field ID 425) on this (and other) input forms would be automatically selected. Clicking the Sync with Prepaid Interest Date field label again resulted in the Buydown checkbox being automatically cleared. This issue, which occurred with multiple checkboxes, has been resolved for all impacted fields. Clicking a checkbox field label no longer impacts other checkbox fields.
In the Encompass 19.4 Major Release, an issue was addressed (SEC-14711) to enable External Company custom fields to be updated using the Encompass Software Development Kit (SDK). However, a new issue then occurred where an exception was generated when the custom fields contained null values. This issue has been resolved and null values are now accepted when updating the External Company custom fields via the SDK.